I can also confirm this issue. We're seeing this across hundreds of different environments that used to work fine just 24 hours ago. We've confirmed no widespread disk or permissions issues.

Some other reports too:

https://twitter.com/defenceforceorg/status/1402214880967630849?s=21

https://twitter.com/megumin2000/status/1402137709024485384?s=21

https://reddit.com/r/playrust/comments/nuxfvn/dedicated_server_setup_issues/

I'm getting the same error. I tried both in a new docker image based on ubuntu:18.04 and on the dedicated server.
Using root or another user does not change the error.
Removing +force_install_dir will install the server correctly but in the default steamapps directory.

Happens across all our (windows) servers too. Confirmed the same issue on at least 30 nodes across Europe.

I can confirm that the workaround when not using the force_install_dir command works.

Yea, having this issue on some servers since yesterday!

Also experiencing this across multiple Linux distros.

As a temporary workaround, if you create a steamapps directory in the directory that you're passing to force_install_dir, this should allow the install to proceed as normal.

So for example if you were installing to /home/steam/gameserver, create the /home/steam/gameserver/steamapps directory first, and then you should be able to install fine.

Same error here on Debian, is this something that will be fixed in an upcoming release of SteamCMD or do we have to do the workaround from @Cherry to "fix" the problem?

Also is there some way to actually inform Valve about this or is this the official way?

Experiencing this issue as well (using +force_install_dir) - unfortunately scripted and non-trivial to get around. Please fix Valve.

This error exists on debian as well. Please fix ASAP!

@kisak-valve Any chance we could get this fixed?

any fix?

@Cherry thank you so much for this temporary fix

Can someone FIX THIS ALREADY? how can it take this long time. I cant even start the servers because the script is not even "quitting" like it should....

"how can it take this long time." The fact that they messed this up this big in the first place is pretty bad.. Whoever did it may be working harder on their resume then they now are at valve.. (or perhaps they should be..) It's pretty sad that a CDN and game platform as large as valve has such crap testing for something this core to their business. Epic/Blizzard and other CDNs aren't taking marketshare for no good reason...

Valve, step up your game. Too many people depend on your software working right for you to let stuff like this slide..

As a temporary workaround, if you create a steamapps directory in the directory that you're passing to force_install_dir, this should allow the install to proceed as normal.

So for example if you were installing to /home/steam/gameserver, create the /home/steam/gameserver/steamapps directory first, and then you should be able to install fine.

Thanks this worked for me :)

As a temporary workaround, if you create a steamapps directory in the directory that you're passing to force_install_dir, this should allow the install to proceed as normal.

So for example if you were installing to /home/steam/gameserver, create the /home/steam/gameserver/steamapps directory first, and then you should be able to install fine.

A huge thanks for this workaround, it works for me.

Also reported the issue here yesterday:
https://www.reddit.com/r/SteamCMD/comments/nv9oey/error_failed_to_install_app_xxx_disk_write_failure/

This morning found this thread after raising a ticket at Valve support.

I can confirm the workaround by creating the steamapps subdirectory
Another workaround mentioned in the reddit is to not use the +force_install_dir.
The default install location for steamcmd is /home/<user_running_steamcmd>/.steam/steamapps/common/<game_name>

Can someone FIX THIS ALREADY? how can it take this long time. I cant even start the servers because the script is not even "quitting" like it should....

This repository is a free software project. No one is responsible for fixing this issue, except yourself.

Can someone FIX THIS ALREADY? how can it take this long time. I cant even start the servers because the script is not even "quitting" like it should....

This repository is a free software project. No one is responsible for fixing this issue, except yourself.

Yea that was ment to Valve or whoever actually pushes updated for STEAMDCMD.

As a temporary workaround, if you create a steamapps directory in the directory that you're passing to force_install_dir, this should allow the install to proceed as normal.
So for example if you were installing to /home/steam/gameserver, create the /home/steam/gameserver/steamapps directory first, and then you should be able to install fine.

Thanks this worked for me :)

Anyone able to break this down really simply for a total newbie? Can't seem to wrap my head around what I need to change in the .bat file to get this working.

A fix for this issue is available in the latest steamcmd release.

A fix for this issue is available in the latest steamcmd release.

Seems to be working for me. Thanks.

Can confirm everything is working as it where before, tested two games (one of them is a Goldsource game):
Valheim.log
DMClassic.log

Thank you for the fix!

Does not seem to be fixed - I tried it and it seems to ignore the force_install_dir option all together, although at least it downloads it now. I'm not sure where it is being saved to.

Edit: This may only be the case when downloading a different branch, I tried it with the public branch and it worked.

Fixed