Same here!
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: Oldest
-
Anonymous
2023-01-14T10:10:50+00:00 -
Anonymous
2023-01-18T11:42:19+00:00 Hi Jeef, thanks for your post. I've also upgraded to Win11 Pro but remote desktop still wont work. I followed your instructions but on the registry location you mentioned I cannot find the line that says "fClientDisableUDP", the only lines I see are "fEnableUsbBlockDeviceBySetupClass", "fEnableUsbNoAckIsochWriteToDevice" and "fEnableUsbSelectDeviceByInterface", could you please help me with this?
-
Anonymous
2023-01-18T15:21:33+00:00 Hi Jeef, thanks for your post. I've also upgraded to Win11 Pro but remote desktop still wont work. I followed your instructions but on the registry location you mentioned I cannot find the line that says "fClientDisableUDP", the only lines I see are "fEnableUsbBlockDeviceBySetupClass", "fEnableUsbNoAckIsochWriteToDevice" and "fEnableUsbSelectDeviceByInterface", could you please help me with this?
You have to right-click -> "New" -> DWORD Value to create a new entry and then for the name, call it "fClientDisableUDP", and then set the value to 1.
-
Anonymous
2023-01-23T23:00:57+00:00 Wow, I just updated to W11 22H2 today from Windows 10 and found my RDC was not working to connect to my work.
Since I WFH full time, this was a huge problem.Can't believe adding a registry value from doing a google search that landed me here fixed it.
Why is this even a bug? MS should fix this.I should add that I do have Win 11 Pro from Win 10 Pro previously.
-
Anonymous
2023-01-23T23:21:43+00:00 I'd like to ask anybody who has an opinion about this weather it's better to roll back your windows version to 21H2, like I did, and keep waiting for Microsoft to provide an update that will fix it... Or do the registry modification. I had kind of assumed Microsoft would get to it by now, and I felt like playing it safe by waiting for their official fix; but I'm starting to wonder if they ever will.