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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2022-10-04T13:30:21+00:00

    Hi Jeff,

    Thank's for your analyse.

    We had the same issue, and your regedit/UDP workaround has solve our stuck.

    Now RDP are running fine with 22H2.

    Fred

    Was this answer helpful?

    0 comments
  2. Anonymous
    2022-10-06T08:59:18+00:00

    Many thanks Jeff, this is greatly appreciated!

    Nouri A - I can confirm that this issue also affects my build of Windows 11 22H2 22621.608.

    I was able to connect successfully before the upgrade to 22H2 and it only works now after following Jeff's instructions.

    I also have a laptop that is running 21H2 22000.978, which is able to connect to the same remote access system (without the registry fix).

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2022-10-06T12:09:07+00:00

    Thanks your very much everyone for the information shared.

    we are working on this issue internally, will let you know the outcome.

    Appreciate the patience!

    Nouri

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments
  4. Anonymous
    2022-10-06T12:16:09+00:00

    Could you please provide step by step instructions?

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2022-10-06T12:30:03+00:00

    I’m getting 204 error and this fix (on client laptop) did not work. Is that the same error you got? Do we need to make additional changes to Firewall? I have been working w Microsoft support for over 1 month and they have not helped at all

    Was this answer helpful?

    0 comments