Issues with Remote Desktop on Windows 11 after Update 22H2

Anonymous
2022-09-22T13:54:07+00:00

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.

0 comments

125 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2022-10-02T13:03:55+00:00

    Thank you so much for that explanation! I am a home user, but I use RDP via a browser to connect to my company's database. I took the 22H2 update and that's where all the problems started. The company's I.T. department is unavailable on weekends generally. Your explanation saved the day!

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2022-09-29T22:54:37+00:00

    You need to add it

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2022-09-27T22:20:53+00:00

    Hey Jeff thanks for the tip - I got impatient and ended up upgrading to Pro and downloading the Microsoft RD app. which is working for my purposes. I'm sure others who are experiencing the same issue will appreciate your advice to change the registry value.

    Thank you

    Fran

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2022-09-27T19:00:45+00:00

    It also is working for Windows 11 up until this latest update 22H2. This has occurred for about 15 computers so far at our company and many other users in the community site as well.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2022-09-27T18:35:02+00:00

    Thank you Jeff, I understand the issue is with the Client, it makes absolute sense. I am asking all these questions in the attempt to reproduce the issue on my side. The build number i am looking for is in Start > run > Winver.exe, it will have Version 22h2 (OS BUID 22621.XXX) i need the last 3 digits.

    It would be great if you see events in the Terminal Server Gateway logs. That event path is located on the RD Gateway Server.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments