SteamCMD Error 0x602 After Update Job: Fix a Stuck Server Update

Error! App '<id>' state is 0x602 after update job means SteamCMD started an update, the update paused, and it never resumed. Unlike 0x202 (disk full) or 0x402 (connection), Valve does not publish a single cause for 0x602, so you fix it by elimination: stop the server so no files are locked, make sure the user running SteamCMD owns the folder, confirm there is free space, then delete the stale download and app manifest and update again. That sequence clears it in the vast majority of cases.

What the flags in 0x602 say

The state value is three status flags added together:

So 0x602 = 0x400 + 0x200 + 0x2. The download got going, then something made SteamCMD pause it. The LinuxGSM docs list the cause as unknown, which is honest: several different problems produce the same flags. The checks below go from most to least common.

Check 1: make sure the server is stopped

This is the cause people miss most often, especially on Windows. If the game server process is running, its .exe and .dll files are locked, and SteamCMD cannot replace them. The update pauses and you get 0x602 or a "disk write failure".

1. Stop the server fully, then wait for the process to exit. Unreal Engine servers like ARK and Conan Exiles can take a minute to save and close.
2. Check nothing is left over. On Windows, look in Task Manager for the server process (for example ArkAscendedServer.exe or ConanSandboxServer-Win64-Shipping.exe). On Linux:

ps aux | grep -i server

3. Kill any leftover process, then run the update.

If you run several servers from the same install folder, all of them must be stopped. Sharing one install between servers is a frequent cause of 0x602.

Check 2: permissions and ownership

SteamCMD has to write to the install folder and its own folder. On Linux, a common mistake is running SteamCMD once with sudo and then as a normal user, which leaves root owned files that the normal user cannot overwrite.

ls -la /home/steam/serverfiles/steamapps
sudo chown -R steam:steam /home/steam/serverfiles /home/steam/Steam /home/steam/steamcmd

Replace steam with the user that runs your server. Never run SteamCMD or a game server as root.

On Windows, avoid installing servers under C:\Program Files, which needs admin rights to write. Use a plain folder like C:\servers\rust. Also check that the folder is not marked read only and that Controlled Folder Access in Windows Security is not blocking SteamCMD.

The related code 0x606 is listed by LinuxGSM specifically as "unable to write to the disk", usually permissions, often on symlinked folders. If your install path uses a symlink to another disk, try the real path instead.

Check 3: disk space

A disk that fills partway through a download can show as 0x602 instead of the usual 0x202. Check the drive holding the install folder:

df -h /home/steam/serverfiles

Leave room for roughly the full size of the server on top of what it already uses, because updates stage new files before swapping them in.

Check 4: clear the stuck job

Once the server is stopped, ownership is right and there is space, remove the leftovers from the paused job:

1. Delete steamapps/downloading/<appid> in the install folder.
2. Delete steamapps/temp/<appid> if it exists.
3. Delete steamapps/appmanifest_<appid>.acf. This only resets SteamCMD's record of the install. Worlds, saves and configs stay.
4. Run a full validate:

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

That example is ARK: Survival Ascended's server, app 2430930. Use your own game's ID.

Check 5: reinstall SteamCMD itself

SteamCMD caches data in its own folder, and a damaged cache can keep producing the same paused state. Delete the SteamCMD folder (on Linux often ~/steamcmd and ~/Steam, on Windows wherever you unzipped steamcmd.exe), download it again from Valve, and let it update itself on first run. Do not delete your server install folder unless you have backed up the saves.

A quick checklist

If you get a different number, the 0x6 guide and the 0x402 guide cover the other common states.

Avoiding the problem altogether

Most 0x602 errors come from the plumbing around SteamCMD: file locks, shared install folders, permission mixups. A hosted server removes most of that. On a GamezServers server the game is installed for you, the server is stopped and started from the panel, and you get a live console, file manager and SFTP if you want to look at files yourself. Support is on email 24/7 if an update still refuses to go through.

FAQ

What causes SteamCMD error 0x602?

There is no single published cause. The flags mean an update started and then paused. In practice it is most often locked files from a running server, folders the SteamCMD user cannot write to, or a disk that filled during the download.

Do I need to delete my server to fix 0x602?

Almost never. Deleting the downloading folder and the appmanifest_<appid>.acf file, then running app_update <id> validate, is enough in most cases. Your world is not stored in those files.

Should I run SteamCMD as administrator or with sudo?

On Windows, running as administrator can help if the server lives in a protected folder, but moving it to a normal folder is the better fix. On Linux, do not use sudo: it creates root owned files that break later updates.

Why does 0x602 keep happening on the same server?

A repeat usually points at something in your setup, such as a scheduled task updating while the server runs, two servers sharing one folder, or a backup tool holding files open. Fix the routine, not just the error.