Microsoft has confirmed the bug with UDP in RDP on Windows 11 22H2

As you could remember, several users reported a bug in Remote Desktop Protocol in Windows 11 version 22H2. It causes freezes and disconnections. Sometimes RDP simply fails to connect to the remote computer. Microsoft has officially confirmed the bug, but doesn't provide any new workaround besides the disabling UDP for RDP, that affected users already use.

Client Mstsc New RDP Port

Microsoft reports that the problem only occurs when establishing a connection using the Remote Desktop gateway or Remote Desktop Connection Broker. By default there is a different connection method, so most users shouldn't have any problems. However, when trying to access the Remote Desktop Services collection, or when using RemoteApp and Desktop Connection, you will most likely have issues.


Microsoft claims that the issue occurs regardless of the version of Windows you are trying to connect to. In some cases, the Remote Desktop application may simply stop responding, but you may also receive a message that the connection was lost. If the application is frozen, then you will have to open the Task Manager, find the mstsc.exe process and terminate it.

As a workaround, Microsoft suggests disabling UDP using the Group Policy editor. For this you need:

  1. Open the Group Policy Management Console or the Local Group Policy Editor.
  2. Go to "Computer Configuration" -> "Administrative Templates" -> "Windows Components" -> "Remote Desktop Services" -> "Remote Desktop Connection Client" .
  3. Find the policy "Turn off UDP On Client" and set its value to "Enabled" .
  4. Confirm the changes and restart your computer.

Alternatively, you can apply a Registry tweak. Open the Registry and navigate to the HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\Client key. There, create a new 32-bit DWORD named fClientDisableUDP and set it to 1.

Keep in mind that this change may reduce performance when working with a remote desktop over the Internet. After the hotfix is ​​released, you should disable this policy to restore performance.

The official note is here.

Source: TheCommunity

Support us

Winaero greatly relies on your support. You can help the site keep bringing you interesting and useful content and software by using these options:

If you like this article, please share it using the buttons below. It won't take a lot from you, but it will help us grow. Thanks for your support!


Author: Sergey Tkachenko

Sergey Tkachenko is a software developer who started Winaero back in 2011. On this blog, Sergey is writing about everything connected to Microsoft, Windows and popular software. Follow him on Telegram, Twitter, and YouTube.

5 thoughts on “Microsoft has confirmed the bug with UDP in RDP on Windows 11 22H2”

  1. Can anyone explain why our company’s Macintosh clients started experiencing the same type of timeouts as their windows counterparts around the same time this started occurring in Windows 11?

  2. How can you keep this always enabled? I need to enable it every time, I have to use remote desktop

    1. Hi Noman,

      Please try to set the correct key again then restart your computer using Clean Boot. Determine if a background program or a software conflict is causing the issue.

      Press Start then search and type: msconfig
      Select System Configuration > go to the Services tab.
      Select and put a check mark on “Hide all Microsoft services” > Click Disable all.
      Go to Startup tab > Open Task Manager > Disable all the unnecessary services running there. Restart your computer.

      After restart, try disable the udp again. It should work.

      Thank you.

    2. if that doesnt work, you can try to use this method also. First, export the key, or better, back up the Registry lest something go amiss.
      Change the value of LocalAccountTokenFilterPolicy to 1, as desired.
      Then, Right-click on the key containing the value.
      Click on Permissions.
      Click the Advanced button.
      Change Owner to yourself.
      Remove Full Control from other users than yourself, wherever possible.
      If this is not sufficient to “lock” the value after reboot, then repeat as above and finally change Owner to NT Service\TrustedInstaller.
      Thank you.
      Regards, Danial

Leave a Reply

Your email address will not be published.

Using Telegram? Subscribe to the blog channel!
Hello. Add your message here.