Windows STEAMCMD V2.1 0x402 Error

ShadowRam

Refugee
Hey guys,

Still getting no answer on the Steam Discussion, moving it to here for visibility.


I've never had problems running/updating 7days to Die via STEAMCMD until V2.1 dropped.

Nothing seems to work, always reports 0x402 error when attempting to update it.

Looking for some help,
Servers been down for days now, ever since all my clients updated to V2.1 and the server is refusing to update.
 
Yeah, no real information in that provided thread for someone to help you. Same as your post here.
Details on your setup and what exact command you are running would be more useful in getting assistance.


This is the command I run, and I have no issues with it. Your file/folder paths will be different, of course.
Code:
"C:\Servers\bin\steamcmd\steamcmd.exe" +force_install_dir "C:\Servers\7DTD" +login anonymous +app_update 294420 -beta public +quit
You can also use "-beta v2.1".

I am referencing Windows because that is what most people use, even though it is far from the best.
 
yeah, that old command doesn't work anymore.

Yeah, since V2, 7Days made a change that you can't download/install a dedicated server with an anonymous login anymore.

So, I run STEAMCMD

force_install_dir "C:\7Days"

login *accoutnameremoved*

app_update 294420 -validate

This worked fine for V2.0 and we've been playing with no issues.
Now the server won't update to V2.1, it will report 0x402 error.

I'm not the only one with the issue as per the steam discussion.
 
SteamCMD cache was flushed.

> You can though. If you aren't, then something else is going wrong.

Others are asking for anonymous login to be enabled.

If something is going wrong, it's obviously not something I'm doing strange.
I've also run a number of other STEAMCMD servers such as Icarus, Satisfactory and others.
None of those give me errors about using an anonymous login.

Again, I'm not the only one with this issue specific to 7days to Die.
see latest reply here
 
Also was getting 0x402. It stared with 2.1 update. The fix for me was to download the latest steamcmd. I also placed it in a different directory to be sure there was no cache or anything causing issues.

Ive been running 7dtd servers for over 10 years. Never had a problem. I was 100% sure it was a steam issue. Turns out I was just using a very old steamcmd. The version I was using required my MFA code. I knew immediatley there was a difference when the new one worked with push notifications.

Have 2 other friends with the same issue (because I showed them how to setup a server and they also never updated steamcmd.) When they updated, their isswue was also resolved.

Hope this helps.
 
Back
Top