Known Issues

[SOLVED] - Terminal server unresponsive - 4005 error

Userlevel 7
Badge +47
  • Community and Advocacy Manager
  • 1306 replies
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.

Webroot Business Endpoint Protection

Windows Server acting as Terminal Servers

An identified cause of 4005 errors has been addressed by Business agent version, 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.

0 replies

Be the first to reply!


    Cookie policy

    We use cookies to enhance and personalize your experience. If you accept or continue browsing you agree to our cookie policy. Learn more about our cookies.

    Accept cookies Cookie settings