K
Konstantin Boyandin (ProwideLabs)
Guest
OS: Windows 10 Enterprise
winver output: Version 1903 (OS Build 18362.295)
After the most recent cumulative update (August 13, 2019—KB4512508 (OS Build 18362.295)) and subsequent automated reboot, the below problem started.
Problem: after remote desktop (rdesktop) session is disconnected (without logging off), CPU usage of the system raises to 100% and system becomes irresponsible:
- it responds to PING
- it doesn't serve further rdesktop connections (although it listens on port 3389 and can be connected via telnet-like utility)
- when attempted to log on from console, it takes ages to ask for password and verify it, then it shows black screen (remaining in that state until reset)
Is the problem known? If yes, how should it be handled?
Logging off rdesktop connections is undesirable.
Considering rolling back the buggy "quality" update, as the first step - unless more sensible advice is posted here.
Thanks in advance.
More...
winver output: Version 1903 (OS Build 18362.295)
After the most recent cumulative update (August 13, 2019—KB4512508 (OS Build 18362.295)) and subsequent automated reboot, the below problem started.
Problem: after remote desktop (rdesktop) session is disconnected (without logging off), CPU usage of the system raises to 100% and system becomes irresponsible:
- it responds to PING
- it doesn't serve further rdesktop connections (although it listens on port 3389 and can be connected via telnet-like utility)
- when attempted to log on from console, it takes ages to ask for password and verify it, then it shows black screen (remaining in that state until reset)
Is the problem known? If yes, how should it be handled?
Logging off rdesktop connections is undesirable.
Considering rolling back the buggy "quality" update, as the first step - unless more sensible advice is posted here.
Thanks in advance.
More...