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: Newest
Most helpful Newest Oldest
  1. Anonymous
    2022-12-08T02:45:34+00:00

    I would like to execute the fix, but I can't RDP to the troubled pc from my remote location or from within the local network (via RDP on another local pc).

    I would like to force a restart on the troubled pc, but since I don't have physical access to that troubled pc, I have to find a way to do it via a RDP session. So far, all my attempts from another local pc (via RDP) give me an "access denied".

    Does anyone know how to solve this issue.

    Thanks

    Was this answer helpful?

    0 comments
  2. Anonymous
    2022-12-07T13:08:52+00:00

    Hi

    We tried this solution and it worked but only temporarily.

    We found that any further attempts to connect to our servers via Remote Desktop only worked if we rebooted the laptop. Had to do this each time the Remote sessions were closed. The fix also had a knock on effect that prevented Outlook from syncing and returned server connection issues (local version of Outlook using Gmail as host). Deleting the fix got us back up and running with email but put us back where we started.

    Any ideas on why the fix only worked 'once' before having to reboot and how to prevent the knock on effect to Outlook?

    Thanks

    Was this answer helpful?

    0 comments
  3. Anonymous
    2022-12-07T08:09:34+00:00

    Jerry, you have to create it or run the command (as admin):
    REG ADD "HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\Client" /v fClientDisableUDP /t REG_DWORD /d 1 /f

    Was this answer helpful?

    0 comments
  4. Anonymous
    2022-12-07T07:51:37+00:00

    the specified path (Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\Client

    KEY VALUE - fClientDisableUDP SET TO 1 ) is not available

    is there any other work around?

    Was this answer helpful?

    0 comments
  5. Anonymous
    2022-12-07T03:19:39+00:00

    Well,

    After my fix working for about a month, I've completely lost remote desktop for a second time. This time it doesn't even work on the network level. This is incredibly frustrating.

    Was this answer helpful?

    0 comments