Since 5053656 and 5054979 the issue is no longer present. RDP is working normally.
KB5050094 Causes RDP Disconnects
Since computers installed update KB5050094 we are seeing RDP connections being disconnected randomly...sometimes after a few seconds or after a few minutes. We have confirmed that it was this update which caused it by removing the update and then testing, and RDP stayed active as it did previously without any disconnects. We then reinstalled the update and the RDP disconnects started again.
We have also tested this from Macs using the Windows App, and the same users who were disconnected on their Windows systems, where not getting disconnected from the Mac (so not the server end disconnecting).
Looking online, other users are reporting the same issue so this is not specific to our network, clients or servers.
As a note these are Windows 10 and 11 systems.
Windows for home | Windows 11 | Windows update
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
44 answers
Sort by: Most helpful
-
Anonymous
2025-04-03T20:14:47+00:00 -
Anonymous
2025-03-13T18:09:14+00:00 Try this .reg
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\Client]
"fClientDisableUDP"=dword:00000001
It should do the job.
-
Anonymous
2025-02-27T09:13:31+00:00 thank you very much for the answer.
the problem still exists ... We have decided to suspend these both updates (KB50500094, KB5051987) for now. To be honest, it's a disaster. It also doesn't speak for MS that it takes sooooo long to get rid of the problem. -
Anonymous
2025-02-13T13:03:01+00:00 I had the same trouble, here we use remote desktop 100% of the time so it's VERY annoying.
The option is to suspend windows update... for a while.. I guess.
I confirm that removing 5051987 AND 5050094 works.
-
Anonymous
2025-02-06T23:09:14+00:00 Not a valid resolution. KB5050094 is a Cumulative preview which we have not released in our environment yet. This issue has been present since the release of 24h2 for Windows 11 and none of the cumulative updates since its release have resolved the issue.
Interesting.
For us in 24h2 the issue was infrequent enough that it was annoying.
KB5050094 has made it worse, changed it from just annoying to almost unusable for many.