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
    2023-04-08T21:49:12+00:00

    Hi! Microsoft has fixed this several weeks (month) ago. So if you have not replaced the mstc-files by replacing the ownership, the problem should be gone (do not remember the KB by now).

    Was this answer helpful?

    0 comments
  2. 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
  3. 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
  4. 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
  5. Anonymous
    2023-02-28T16:07:52+00:00

    My experience is this does not work reliably. I made the entry in the registry as described. I rebooted, and used a preexisting RDP shortcut which I had saved to my desktop that has alwauys worked. It still would not connect, and same symptoms as listed by others.

    However, I have also discovereed something new on this: If I create a fresh Remote Desktop Connection, instead of using the shortcut, I can connect just fine. But I don't want to have to create a fresh RDP connection everey time I want to connect to any one of my dozens of servers. I am finding that any time I save the connection to the file system, that's when it breaks. After killing the black screen (when it hangs) on the first try, on the second try, it actually pops up a file system error.

    So this (at least my issue) has something specific to do with storage in the file system. So the registry edit is not the full solution, at least for me. It's pretty useless if I can't save the connection to the file system. I hope someone else has had and solved this problem. I'll keep watching for a solution here.

    Cheers,

    -=Cameron

    Was this answer helpful?

    0 comments