After KB5122882 installed overnight, users could no longer establish new RDP sessions to my Windows Server 2022 host. Existing sessions continued working, but new connections authenticated and then hung. Task Manager also became unresponsive, even though CPU, memory, and disk usage looked normal, and the Remote Desktop Services service was still running.
A reboot temporarily restored access, but the problem returned about an hour later. Removing KB5122882 and rolling back from build 20348.5622 to 20348.5499 fixed the issue, and the server has been stable since. Has anyone else seen this behavior on Server 2022 or other RDS versions? I'm pausing updates until there's a confirmed fix.
4 Answers
Yes, this appears to affect multiple RDS versions. Several administrators have reported Terminal Services becoming stuck after users disconnect, with both new RDP sessions and even local console logons failing. Removing the update and temporarily blocking it has been the practical workaround so far.
The timing and the rollback result make the update the main suspect. I’d pause deployment on production systems, test it on a noncritical server first, and keep an eye on the RDS and system event logs for a clearer failure pattern.
Agreed. Existing sessions surviving while new ones hang is a particularly strong clue that the connection setup path is being affected rather than the whole server simply running out of resources.
One possible angle is a mismatch in encryption or Kerberos support between the RDS host and the domain controllers. If the update changed supported protocols on one side but not the other, authentication could succeed while session establishment fails. I’d compare installed updates and security protocol settings across the RDS server and DCs before ruling that out completely.
Reports indicate the problem may span Server 2016 through Server 2025, not just one build. Until the issue is confirmed and corrected, uninstalling the rollup on affected hosts and pausing further installation seems to be the only consistently reported workaround.
That makes me concerned about our Server 2019 hosts too. I’m going to hold the update there until Microsoft provides more information.