There is a problem with remote desktop Windows11 22H2. The app is not responding, can’t connect, etc. Finally, acknowledge the bug reported since October | Build a Niche Z PC gamer environment

Windows Update

MicrosoftWe announced that Windows 11 version 22H2 remote desktop is not working properly.

Fault overview

In a Windows 11 version 22H2 environment, when connecting to the remote desktop through Remote Desktop Gateway or Remote Desktop Connection Broker, the remote desktop app may not respond, cannot connect, or may be disconnect.

This connection method is not the default one used by the Windows remote desktop app, so it is unlikely that ordinary users will encounter this bug.

Work around/opportunity

If this problem occurs, first terminate “mstsc.exe” from the task manager.

This bug is caused by UDP connection and can be avoided by disabling UDP connection. Windows 11 Pro users can avoid the problem by setting the following group policy and disabling UDP connections.

  1. Open the Group Policy Editor (Press Windows + R to open the Run window, type gpedit.msc and enter)
  2. On the left, go to Computer Configuration → Administrative Templates → Windows Components → Remote Desktop Services → Remote Desktop Connection Client.
  3. On the right side, open “Disable UDP client”
  4. Select Enable and OK

If you are in an OS environment or edition that cannot use the Group Policy Editor, you can also start the Registry Editor (press[Windows]+[R]key and enter “regedit” and enter) and set the following registry as above. You can also disable UDP connections.

【キー】 HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindows NTTerminal ServicesClient
【DWORD】fClientDisableUDP
[Gwerth]”1″ disables UDP, “0” enables UDP
Disable UDP connection by setting

Note that disabling UDP connections may slow remote desktop performance over the WAN. Additionally, it is recommended to return to the original setting (UDP connection enabled) after the problem is resolved.

Users have reported this bug since early October 2022, but Microsoft finally acknowledged the problem. Microsoft is working to resolve the issue and plans to fix it in a future update.


Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.