SteamCMD Error 0x202 After Update Job: Fix "Not Enough Disk Space

Error! App '<id>' state is 0x202 after update job means SteamCMD stopped the download because the drive it was writing to ran out of free space. The fix is to free up space (or point the install at a bigger drive), delete the half finished download, and run app_update again. The catch is that SteamCMD needs more room than the finished server takes up, because it stages new files next to the old ones before swapping them in.

What 0x202 actually means

The number after "state is" is not an error code in the normal sense. It is a set of status flags that Steam uses for every app, added together in hexadecimal. 0x202 is two flags at once:

So the message reads as "this server still needs an update, and the update stalled". In practice, the reason it stalls almost every time is free space. The LinuxGSM docs list 0x202 and the closely related 0x212 as "not enough disk space", and that matches what admins see on Steam forums for Rust, ARK, DayZ and every other big server.

You will often see it right after a large patch. A server that sits at 30 GB can need 60 GB or more free during an update, because SteamCMD writes the new chunks into a staging folder, verifies them, then commits them over the old files.

Step 1: check free space on the right drive

Check the drive that holds the install folder (the path after +force_install_dir), not just your system drive. Also check where SteamCMD itself lives, because it keeps its own download cache under its folder.

On Linux:

df -h /home/steam/serverfiles
df -h ~/Steam ~/.steam 2>/dev/null
du -sh /home/steam/serverfiles/steamapps/downloading

On Windows, open File Explorer, right click the drive and pick Properties, or run this in PowerShell:

Get-PSDrive -PSProvider FileSystem

As a rough rule, keep at least the full size of the server free on top of the installed size. Big games are large: ARK: Survival Ascended, DayZ and Rust are all several tens of GB, and modded installs add more.

Step 2: free up space

Common places that eat disk on a game server box:

• Old backups. Automatic world backups pile up fast. Move them off the machine or delete the oldest ones.
• Logs. Rust, ARK and Unreal Engine servers can write huge log files when something spams warnings. Look in the Saved/Logs folder for Unreal games and in the server root for .log files.
• Crash dumps. .dmp files from repeated crashes are often hundreds of MB each.
• The stale downloading folder. A failed update leaves partial chunks in steamapps/downloading/<appid>. These are safe to delete when SteamCMD is not running.
• Workshop content for mods you removed. It stays in steamapps/workshop/content/<appid> until you delete it.

On Linux, this finds the biggest folders under your server path:

du -h --max-depth=2 /home/steam/serverfiles | sort -h | tail -20

Step 3: clear the stuck state and rerun

Once there is room, clean up the failed attempt so SteamCMD starts fresh:

1. Stop the game server so nothing holds files open.
2. Delete steamapps/downloading/<appid> and steamapps/temp/<appid> inside the install folder, if they exist.
3. If the error keeps coming back, also delete steamapps/appmanifest_<appid>.acf. This makes SteamCMD rebuild its record of what is installed. Your world and configs are not touched.
4. Run the update with validate once:

steamcmd +force_install_dir /home/steam/serverfiles +login anonymous +app_update 258550 validate +quit

Swap 258550 (Rust) for your game's server app ID. Note that force_install_dir goes before login: current SteamCMD builds warn "Please use force_install_dir before logon!" if you do it the other way round.

When it works you get Success! App '258550' fully installed.

When there is plenty of space and it still says 0x202

A few setups report free space wrongly or limit it in ways df does not show:

• Disk quotas. On shared Linux boxes, the user running SteamCMD may have a quota. Check with quota -s.
• Docker or container volumes. The container may be writing to a small overlay layer instead of the mounted volume you checked. Run df -h from inside the container.
• Network shares and NAS mounts. SteamCMD does not cope well with SMB or NFS paths that report odd sizes. Install to a local disk.
• Inodes, not bytes. A filesystem can run out of file entries before it runs out of space. df -i shows this. Games with thousands of small files (Garry's Mod with lots of addons, for example) can hit it on small volumes.
• Temp folder on a different drive. On Windows, a full C: drive can break updates even when the server sits on D:, because Windows itself needs room to work.

If you have ruled all of these out, look at the full state code again. 0x402 and 0x602 are different problems and have their own guides: SteamCMD error 0x402 is usually a connection issue, and 0x602 is usually a stuck or locked download.

How to stop it happening again

• Keep a free space buffer equal to the full server size, more if you run mods.
• Rotate backups: keep a handful of recent ones locally and move the rest off the machine. Our guide on how to back up a game server covers sensible schedules.
• Cap log size, or clear logs on every restart with a small script.
• Remove Workshop content for mods you no longer use.
• Watch disk usage with a simple cron job or monitoring tool that warns you at 80 percent.

Skipping the disk space juggling

If you are hosting at home or on a small VPS, disk is usually the first thing to run out, and the server goes down on patch day right when everyone wants to play. On a GamezServers server the game is installed for you, you get a file manager and SFTP to clear out old files, one click backups, and you can move to a bigger plan from the panel at any time with the price prorated. For big games like Rust or ARK: Survival Ascended, that takes patch day storage worries off your plate.

FAQ

Is SteamCMD error 0x202 always a disk space problem?

Nearly always. The flags mean "update required" plus "update paused", and the most common reason a download pauses is a full disk. Quotas, container volumes and network drives can cause it even when the disk looks free.

How much free space does SteamCMD need for an update?

Plan for roughly the full installed size of the server free on top of what is already used. SteamCMD stages new files before replacing old ones, so a big patch can briefly need double the space.

Will deleting the appmanifest file delete my world?

No. appmanifest_<appid>.acf only records what build is installed. Deleting it makes SteamCMD check the files again, but saves and configs are left alone. Take a backup anyway if you are unsure where your game stores its world.

What is the difference between 0x202 and 0x212?

0x212 adds the 0x10 flag on top of 0x202. Both are listed as disk space problems, and the fix is the same.