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-19T03:32:39+00:00

    same here - except 204 error

    My error turned into a 204 error eventually.

    Not sure if you've fixed it yet, but I was able to find a fix that worked for my machine:

    1. Change port forwarding on the router to 3391
    2. Change port for remote desktop to 3391 in HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp - "PortNumber"
    3. Add exceptions in windows firewall by using firewall advanced settings - inbound rules - port. Specify 3391 and do this for UDP (I also repeated this process for TCP, but not sure if it's necessary)
    4. Turn remote desktop off and back on in system->remote desktop.

    I also did the fClientDisableUDP trick, but this didn't seem to work until after I did the above steps.

    It seemed like the default 3389 wasn't working for me, and neither was 3390, but someone somewhere else suggested port 3391 was working. I gave it a shot and it worked.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2022-10-16T00:55:23+00:00

    Thanks VERY much Jeff, as the Reg kill of the UDP absolutely fixed my issues. Like you, I had multiple W7, W10 machines with no issues RDP'ing. After the W11 machines updated, failed, hung, and had to task manager out. Thank you for sharing this, and I will be RE-sharing this post, to help others as well.

    Thank you.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2022-10-14T12:14:36+00:00

    There is a new update: 2022-10 Cumulative Update for Windows 11 Version 22H2 for x64-based Systems (KB5018427).

    I did the regedit fix that you posted for the remote issue, and I was able to fix the botched update that MS released.

    I am WARY of installing the above update, will it undo what I did to fix the buggy 22H2 release from a few weeks ago?

    Was this answer helpful?

    0 comments
  4. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  5. Anonymous
    2022-10-14T06:19:51+00:00

    Nope. Anyone working from home is a scope, -homeusers. Like me and a lot of others. So the post is on the right spot.

    Was this answer helpful?

    0 comments