I think you have to do the regedit fix at the beginning of the thread. That seems to be the best fix. I am not an IT person, but I was able to follow the directions and that fixed it. I don't think MS has bothered to release any patches or fixes.
Issues with Remote Desktop on Windows 11 after Update 22H2
All of our Remote Desktop Users using Windows 11 are having problems connecting to Remote Desktop after installing this update. It just hangs at connecting.
We have found that there is a bug in the Remote Desktop client so that it is only trying the UDP connection and not trying TCP connection. We only allow the port 443 connection through on our firewall.
The only workaround we have found is to make the following change on the Windows 11 computer.
Have to set this value to 1 in the registry for Windows 11 client to work outside the network
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\Client
KEY VALUE - fClientDisableUDP SET TO 1
Otherwise the Remote client just keeps trying to connect via UDP.
This issue did not start until the Windows 11 update was installed over the last couple days.
Jeff
Windows for business | Windows Server | User experience | Remote desktop clients
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.
125 answers
Sort by: Most helpful
-
Anonymous
2022-11-11T20:30:42+00:00 -
Anonymous
2022-11-11T18:48:10+00:00 I have Windows 11 Home and am having trouble with RDP since the update. Is there a free trail key for the Windows 11 Pro that I can try to see if it slves the issue. I can then buy the actual upgrade if this solves my problem.
-
Anonymous
2022-11-11T10:19:26+00:00 I have tried that and it has fixed the issue for me
Thanks
-
Anonymous
2022-11-04T13:59:11+00:00 I do not have this registry entry on my win 11 pro
-
Anonymous
2022-11-02T12:33:39+00:00 That really only works if you're one of the few people where manually forcing a port for it, works. In my case and others? Nope. Sad to say, while I like the gaming changes that were stuck into Win11. Win10 is acting in a far more reasonable and less painful way, between this and the LSA errors. But that's a whole 'nother problem.
edit: As of the update pushed for KB5018496, this seems to be fixed at least on my end.