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-09-27T18:13:26+00:00

    Hello,

    I have questions:

    It looks like there is an RD Gateway involved since you are allowing 443 traffic.

    Are you using an RDS Farm (Broker, RDWeb) or just a standard RDP from Client to a target with a gateway address?

    What is the Windows 11 build number? Edition?

    What is the Windows operating System of your RD Gateway?

    What do the RD Gateway logs report when the connection fails? eventvwr.msc > Application and Services Logs > Microsoft > Windows > TerminalServices-Gateway (admin/Operational).

    Thanks!

    Nouri

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  2. Anonymous
    2022-09-27T18:29:41+00:00

    Yes there id s RD Gateway. There is an RDS Farm, the Windows 11 build is already in the description 22H2.

    The RD Gateway is Windows 2012. The problem is with the client, not the Gateway since all clients on all versions of windows 7,10,11 work except those with Windows 11 build 22H2.

    That specific event path does not exist.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments
  3. 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
  4. Anonymous
    2022-09-27T18:44:54+00:00

    I have 601, but I can't say that I am still having the issue since I already changed the registry setting months ago on my specific PC to not use UDP. There are lots of other people posting on the community with the same issue as do people at our company but they have all been resolved by disabling UDP. If you are trying to recreate it just use any version but make sure UDP is blocked from getting to your RD Gateway server.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2022-09-27T18:51:39+00:00

    http transport : In Channel could not find corresponding out channel is the only error I can see anywhere in the log. I don't think the connections are reaching the RD Gateway unless that registry entry is changed to ignore UDP

    Was this answer helpful?

    0 comments