Windows Server RDS sessions hanging after recent updates
Recent cumulative updates are causing Remote Desktop Session Host collections to lock up completely, trapping user connections at the connecting screen and disabling administrative tools like Task Manager or shutdown commands. Uninstalling the problematic update or rolling back the patch restores normal session host functionality and allows new connections.
What people tried
Every workaround mentioned in the threads below. We haven’t tested any of them — and nobody here is claiming they worked.
- 1Performing a hard reset on the server
- 2Rolling back the cumulative update package using DISM
- 3Checking FSLogix profile container logs
- 4Rebooting the server
- 5Uninstalling the problematic update
- 6Rolling back to a previous build version
- 7Pausing Windows updates
- 8Performing a hard shutdown of the server
- 9Changing server passwords
- 10Using alternate remote tools or remote shells like PSExec with query user and logoff commands
In their words
Unedited, most upvoted first, each linked to the thread it came from.
“Spent most of the morning chasing a weird RDS issue. KB5122882 installed around 3:20am and a few hours later nobody could RDP into the server.”source ↗
“Since installing this month's CUs, KB5122871 on Windows Server 2025 (build 26100.33438) and KB5122882 on Windows Server 2022 (build 20348.5622), every session host in our RDS collection has started hanging in the same way, on the same day, and it had never happened before.”source ↗
“Lately they've been having difficulty logging in with the RDP.”source ↗
“As soon as I login I get a message "You're unable to sign in because you're already signed into another session that is blocked. Session blocked by: Local Session Manager Minutes blocked: xx Do you want to sign out of that session so that you can continue.”source ↗
“If I hit yes or no Boom, disconnected Splashtop dies no connection. RDP still doesn't work.”source ↗
“The only way that I seem to get back in is with a hard shutdown as there is no monitor connected.”source ↗
“I removed KB5123099 and rebooted and it fixed the issue on my 2016 RDS servers.”source ↗
“Same issue on Windows Server 2022 RDS. Task manager not working, query user not working, even shutdown the server not working. New connections aren't possible and stuck at Connecting state. Rollback fix the issue.”source ↗
“yep i had around 8 rds with that .. the terminal service hang after mutliple user deconnection.”source ↗
“I was wondering if it would happen on 2019, a have a few of those as well, better start blocking the update on my other machines.”source ↗
“I get a black screen when I try to log into the cloud PC and get the following error: Your Remote Desktop Services session has ended, possibly for one of the following reasons: The administrator has ended the session. An error occurred while the connection was being established. A network problem occurred.”source ↗
Where this came up
People with this problem also raised
- 2Why do remote support tools keep giving generic error messages?
- 5Why does my VPN or remote connection keep dropping?
- 3How to handle clients ghosting during project discussions
- 10Why built-in software AI features don't fit real work
- 3Why does my outside AC unit keep running when turned off?
- 2Why does a high-end computer lag during basic multitasking?