Issues with Remote Desktop on Windows 11 after Update 22H2

Anonymous

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.

0 comments

125 answers

Anonymous

2023-04-08T20:50:33+00:00

Ok thank you! Do I do this on the computer I am trying to access or the one I am using to access or both?

I already completed it on the one I am using to access the other desktop..
Was this answer helpful?

0 comments No comments
Anonymous

2023-04-08T20:31:56+00:00

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.
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Anonymous

2023-04-08T19:59:33+00:00

Hi Jeff, Can you guide me how to set the registry to 1?
Was this answer helpful?

0 comments No comments
Anonymous

2023-03-07T15:07:57+00:00

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.
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Anonymous

2023-02-28T20:22:27+00:00

Well, I finally was forced to rollback the 2022H2 update. I tried everthing, including the suggested registry edit, to no avail. So I rolled back to my current build previous to this update, and I will have to stay that way until Microsoft either comes out with an official fix that works, or next major release, whichever is first.

I need RDP access sacroos my local LAN to 20+ servers. It's an absolute necessity as I'm a software engineer developing and testing IT enteprrise solutions, many of which have complex features that manupulate to group policy.

All I can do now is hope for a solution. I'll continue to watch this in the meantime.

Cheers,

-=Cameron

https://www.linkedin.com/in/cameronlandersexperience/
Was this answer helpful?

0 comments No comments