SteamCMD "Failed to Install App (Disk Write Failure)": Fix It Fast

ERROR! Failed to install app '<id>' (Disk write failure) means SteamCMD tried to write a file into your server folder and the operating system said no. The four usual reasons are: the server (or another program) has the file open, the user running SteamCMD does not have write permission on that folder, antivirus blocked the write, or the drive is full or failing. Stop the server, install to a plain folder you own, add an antivirus exclusion, and check free space, in that order.

Reason 1: the server is still running

On Windows, a running program locks its own .exe and .dll files. If you update while the server is up, SteamCMD cannot overwrite them and reports a disk write failure. This catches a lot of people who set up a scheduled update without stopping the server first.

1. Stop the server and wait for it to save and exit.
2. Open Task Manager and confirm the process is gone. Look for names like RustDedicated.exe, valheim_server.exe, PalServer-Win64-Shipping-Cmd.exe or ArkAscendedServer.exe.
3. Run the update.

Also close anything else that might hold files open: a text editor with the config loaded, a backup tool copying the folder, an SFTP client in the middle of a transfer, or a second server sharing the same install.

On Linux, a running server does not lock files in the same way, so this reason is mostly a Windows one.

Reason 2: permissions

Windows

• Do not install under C:\Program Files. Writing there needs administrator rights. Use something simple like C:\servers\rust and point force_install_dir there.
• Running SteamCMD as administrator makes the error go away for protected folders, which is why it is the most common forum answer, but moving the server is the cleaner fix.
• Controlled Folder Access. If Windows Security's ransomware protection is on, it blocks unknown programs from writing to protected folders like Documents and Desktop. Either allow steamcmd.exe through it or install outside protected folders.
• Read only flag. Right click the folder, open Properties, and clear Read only if it is set.

Linux

The classic cause is running SteamCMD once with sudo, which leaves root owned files that a normal user cannot replace. Check and fix ownership:

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

Replace steam with the user that runs the server. From then on, always run SteamCMD as that user, never root. SteamCMD itself warns against running as root.

Reason 3: antivirus

Antivirus software scans new files as they are written, and some products block or quarantine game server files they do not recognize. Steam's own support pages list antivirus as a cause of disk write errors in the Steam client, and SteamCMD is no different.

1. Add exclusions for the SteamCMD folder and the server folder.
2. Check your antivirus quarantine for files from the server.
3. Run the update with validate so any removed files come back:

steamcmd +force_install_dir C:\servers\rust +login anonymous +app_update 258550 validate +quit

Reason 4: disk full or failing

A full disk normally shows as state 0x202, but it can also surface as a disk write failure. Check free space on the drive holding the server. Updates need room for the old and new files at the same time.

If space is fine, check the disk itself:

• Windows: run chkdsk D: /scan on the drive (swap in the right letter), and look at Event Viewer for disk errors.
• Linux: look for I/O errors with dmesg | grep -i error and check the drive with smartctl -a /dev/sda if smartmontools is installed.

A dying drive will keep throwing write failures no matter what else you fix. Move the server to a healthy disk and restore from a backup.

Reason 5: paths that Windows struggles with

• Very long paths. Some servers have deeply nested files. If your install folder is already deep, like C:\Users\Name\Documents\Game Servers\My Survival Server\files, a few files can pass the old 260 character path limit. Keep the install path short.
• OneDrive folders. Desktop and Documents are often synced to OneDrive, which locks files while uploading them. Never install a server inside a synced folder.
• Network drives and NAS shares. SteamCMD expects a local disk. Install locally.

Reason 6: a damaged SteamCMD folder

If none of the above applies, delete SteamCMD's own folder (not the server), download it again from Valve and let it update itself. Forum threads for Garry's Mod and other Source servers often end with "deleting the SteamCMD folders and trying again fixed it".

A quick checklist

A server where none of this is your job

Home and VPS hosting means you own every lock, permission and antivirus quirk. On a GamezServers server, the game is installed for you, you start and stop it from the panel, and you can still get at every file through the file manager or SFTP when you want to. Our control panel docs show what is in there.

FAQ

Why does SteamCMD say disk write failure when my disk has space?

Usually a locked file (server still running), missing write permission, or antivirus blocking the write. Space is only one of several causes.

Should I run SteamCMD as administrator?

It works around permission problems in protected folders, but the better fix is installing the server in a plain folder like C:\servers. On Linux, never use sudo for SteamCMD.

Can disk write failure corrupt my world save?

The update only writes program files, not saves. A failed update can leave the server unable to start until you rerun it with validate, but the world files are left alone. Back up before big updates anyway.

Why does this only happen on patch days?

Patch days are when you update, and updating is when files get written. If you also run the server while updating, or a backup job runs at the same time, the locks collide.