Windows Terminal Servers become unresponsive and require a reboot to recover.
With Windows Terminal Server, customers have reported that they become unresponsive and a reboot is required to recover. Post reboot, checking of the Windows event logs shows 4005 errors in the Application Event log.
Windows Server acting as Terminal Servers
An identified cause of 4005 errors has been addressed in WSA 188.8.131.52, released May of 2018.
Please ensure any servers experiencing this problem are using the latest version
and monitor for additional issues.
At this time we are not enabling comments on this article but please head over to our Product Discussion section to start the conversation.