Well not it’s 2016 and just got this error, luckily server is in AWS so a hard shutdown and restart fixed the issue. it is a terminal server and i got this error when logging out of my session via my user name. I was able to then log in as administrator kill the svchost but after doing so the server crashed and i couldn’t ping it or remote to it any longer. A shut down in AWS and restart worked, problem is for how long!!! Microsoft really needs to get their **** together on this…
↧