This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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
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.
Hi I cannot seem to find the KEY VALUE. I have the same problem after the windows 11 update.
It is the exact same way for me. I cannot find that value.
Several of the replies have already addressed this.
You have to create the value. Right-click the pane on the right, and then "New" and then "DWORD value." Rename the DWORD value "fClientDisableUDP"
Go to the Search icon in the bottom left hand corner of the screen and after clicking on it type in Command in the search window.
In the right side of the search screen it will show the Command Prompt app. Click on the text below that says Run As Administrator. A black window will open, at the prompt type in regedit. That will open the registry editor.
In the tree on the left click on the arrow to expand HKEY_LOCAL_MACHINE, Software, Policies, etc. until you get to the folder
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\Client
In the right side of the window do a right click and select New and then DWORD (32-Bit Value). For the name enter fClientDisableUDP and for the value enter a 1. Click OK.
Reboot your computer.
mstsc.exe is not working when I try to connect to remote computer on internet.
But It can access servers in environments that can be accessed by VPN. It can access servers in LAN (local area network).
I can access servers on the internet with third party software mRemoteNg but not with mstsc.exe. Please fix this app.
I installed the 22h2 01 and 22h2 02 updates but the problem did not go away.
When I look on Network traffic, I see that mstsc is trying 3389 remote port for remote computer. But It cannot connect.
When I look on network traffic for mRemoteNG, I see this app is trying 3389 remote port and connect.
As you see guys, mRemoteNg can connect but mstsc is waiting.
http transport : In Channel could not find corresponding out channel is the only error I can see anywhere in the log. I don't think the connections are reaching the RD Gateway unless that registry entry is changed to ignore UDP
I have 601, but I can't say that I am still having the issue since I already changed the registry setting months ago on my specific PC to not use UDP. There are lots of other people posting on the community with the same issue as do people at our company but they have all been resolved by disabling UDP. If you are trying to recreate it just use any version but make sure UDP is blocked from getting to your RD Gateway server.
