[German]Issues with remote desktop connections have been bugging Windows users for months. I had already reported about the problem in October 2022 in the blog post Windows 11 22H2: Microsoft investigates RDP issues. Microsoft has confirmed as of November 22, 2022 that connection problems with Remote Desktop Connections may occur in Windows 11 version 22H2. At the same time, it suggests measures to fix such problems.
The official confirmation by Microsoft took place on November 22, 2022 on the Windows Release Health status page of Windows 11 22H2. The article Connections may fail when using Remote Desktop Connection Brokers states:
After installing Windows 11 version 22H2, the Windows Remote Desktop application might stop responding when connecting through a Remote Desktop Gateway or Remote Desktop Connection Broker.
The problem can be observed when the client goes through the "Loading the virtual machine" or "Configuring the remote connection" steps and then hangs. The error is independent of the operating system version installed on the remote computer. In some cases, the error message "Your Remote Desktop Services session has been terminated" may be displayed.
The error should only occur in corporate environments – home user systems do not use these remote desktop connections. Clients running Windows 11 22H2 are affected.
Microsoft has therefore set an upgrade blocker for feature updates to Windows 11 22H2. Devices that are affected by this block will no longer be offered the feature update. For enterprise update compliance uses, the protection IDs are 41766570 and 41990091.
Workaround: Kill rdp application
Microsoft suggests as a workaround, if the application no longer responds, to terminate it with the Windows Task Manager.
- To do this, invoke the Task Manager using the key combination Ctrl, Shift and Esc.
- Select Processes in the Task Manager window
- Search the process mstsc.exe in the displayed list
- Right-click on the process name and select End Task
With these steps, the application is terminated and can be restarted to establish a remote desktop connection. In my blog post Windows 11 22H2: Microsoft investigates RDP issues I had stated that the cause is a bug in the remote desktop client (mstsc.exe) that only attempts connections over UDP and not TCP. A workaround was also outlined there using a registry entry to block UDP. Microsoft mentioned a special group policy in the support article based on this, which can be used to disable UPD on the affected client (see the notes in the support article). (via)
Cookies helps to fund this blog: Cookie settings