Update to Windows Server messes up Remote Desktop connections

Microsoft has acknowledged a significant issue affecting the Remote Desktop functionality of Windows Server 2022, stemming from a bug introduced via the KB5040437 update, which was released on July 9 under build number 20348.2582. This bug has been causing connection disruptions for organizations utilizing the legacy protocol in Remote Desktop Gateway, specifically when employing Remote Procedure Call over HTTP. As a result, users are frequently required to reconnect to the server, leading to frustration and inefficiencies.

In the interim, while an official patch is in development, IT administrators can identify the termination of the TSGateway service by monitoring for the exception code 0xc0000005. Microsoft has outlined two potential mitigation strategies that can alleviate the issue.

How to fix it

The first recommended solution involves disabling connections through the Remote Desktop Gateway over the affected pipeline and port 0xc00005. This adjustment necessitates additional configuration for firewall or connection software, and the specific steps will vary based on the software in use. Administrators are advised to consult their respective documentation for guidance.

Another approach requires modifying the registry on client devices. This entails deleting a key associated with RDGClientTransport. Administrators should navigate to HKCU in the Windows Registry Editor and set the ‘DWORD’ value to ‘0x0’. It is important to note that this issue is not isolated to Windows Server 2022; it also impacts Windows Server 2019, 2016, 2012, and 2012 R2.

Bitlocker bug also causes headaches

In addition to the Remote Desktop issues, the KB5040437 update has introduced another complication. A separate bug is causing systems to boot into BitLocker recovery mode after the installation of the July 2024 Patch Tuesday updates. This particular issue predominantly affects users who have enabled the ‘Device Encryption’ option through Settings > Privacy & Security > Device Encryption.

To resolve this problem, users will need the BitLocker recovery key linked to their Microsoft account. Unlike consumer versions of Windows 11, Windows Server 2022 receives updates solely on a monthly basis as part of the Patch Tuesday cycle. Microsoft has assured users that it is actively working on a permanent resolution for these challenges.

Also read: Windows Server 2025 no longer requires a reboot for security updates.

Winsage
Update to Windows Server messes up Remote Desktop connections