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 No comments

125 answers

Sort by: Most helpful
  1. Anonymous
    2023-02-06T03:53:01+00:00

    We have tried this regedit settings but still not able solve RDP issue.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2023-01-23T23:21:43+00:00

    I'd like to ask anybody who has an opinion about this weather it's better to roll back your windows version to 21H2, like I did, and keep waiting for Microsoft to provide an update that will fix it... Or do the registry modification. I had kind of assumed Microsoft would get to it by now, and I felt like playing it safe by waiting for their official fix; but I'm starting to wonder if they ever will.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2022-11-16T12:31:29+00:00

    I agree - I did the work around but I have yet to see MS post a fix for the 22H2 update.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2022-11-11T21:20:51+00:00

    When I go to

    Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\Client

    This is not an option KEY VALUE - fClientDisableUDP SET TO 1

    I have

    UsbBlockDeviceBySetupClases

    UsbSelectDeviceByInterfaces

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  5. Anonymous
    2022-10-26T07:34:07+00:00

    Hi Jeff, hi Microsoft,

    Switching off UDP with one of the solutions mentioned at least means that a connection can be established again. We run an enterprise solution for our customers and are severely impacted by the issue. Excessive use of virtual channels is possible without UDP, but this means that drawing operations, for example when copying files through the channel, freeze. So far so good... The only solution from my point of view is to roll back the files (mstsc.exe and mstscax.dll) to the status before the 22H2 update. It is important that the permissions on the files are not modified, so that Microsoft can then cleanly update them again with the next update. Our solution is: - Stop all instances of mstsc.exe - Elevate to local administrator - Start Trusted Installer Service - Start a copy application (exchange files) in the context of the Trusted Installer (similar to here: https://github.com/rara64/GetTrustedInstaller/blob/master/BerlinDefence.cs) At least the functionalities used in our scenario are restored and customers can use our services without restrictions. I am not aware of any side effects. Unfortunately, the application used cannot share, as it was specially developed for our customers. However, if anyone needs help, he/she is welcome to get in touch on the subject.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments