SteamCMD crashing/locking up whole OS

[Caliban55]

I am currently experiencing an issue with the SteamCMD tool, where it keeps locking up the whole operating system. Only a hard reboot helps, RDP is not usable any more. Usually the download starts, but at some point the lock up happens, at different per percentage download. There is no entry in the Event Manager, no log file from SteamCMD. Sometimes the Steam installation works without any problems, but Insurgency seems to be especially affected. Has anyone noticed a similar behaviour? If everything else fails, I might have to reinstall the OS. A very far fetched idea would be a failing hard drive, but I would put that as very unlikely.

OS: Windows Server 2008R2 64bit

[soja]

Never heard of steamcmd locking up the OS. Are you able to install other apps fine? A list of dedicated server app ids can be found here, along with a column showing if it can be downloaded with the anonymous account: https://developer.valvesoftware.com/wik ... rvers_List

Does a separate steamcmd install do the same thing? How about changing the install directory?

[Caliban55]

Happens with both anonymous logins and subscription apps. Clean installs/folders make no difference. Never had this before and it only started when I tried to update Insurgency servers, as there was a recent update.

Using SteamCMD on my home system with Windows 10 works without any problems, so it's either something particular to this OS, or machine. The only other ideas I have is disabling EMET, but even then a complete unresponsive OS is very strange and should not happen.

[soja]

Are you able to use VNC at all when RDP is inaccessible?

[Caliban55]

Are you able to use VNC at all when RDP is inaccessible?

No, the complete machine is not accessible/locked up, neither RDP or VNC accept a connection. Completley unresponsive. The only thing I was left with doing was a reboot, after which the machine runs fine.