2 min Applications

Update to Windows Server messes up Remote Desktop connections

Update to Windows Server messes up Remote Desktop connections

Microsoft acknowledges that a bug in an update to Windows Server 2022 is causing issues with the Remote Desktop functionality of this OS. The bug entered Windows via the KB5040437 update under build number 20348.2582 and came live on July 9.

The problem causes connection hiccups when organizations use the legacy protocol in Remote Desktop Gateway (Remote Procedure Call over HTTP). That causes users to have to reconnect to the server each time.

Pending an official patch, IT administrators can detect the termination of the TSGateway service by looking for exception code 0xc0000005. Microsoft states that two mitigation options are then available to fix the problem.

How to fix it

The first solution is no longer allowing connections through the Remote Desktop Gateway over the pipeline and port 0xc00005. This means additional configuration is required for firewall or connection software. Exactly how to do that depends on the software used, so admins should consult their documentation.

Another method is to edit the registry on client devices: this requires deleting a key related to RDGClientTransport. Admins must go to HKCU in the Windows Registry Editor and set the ‘DWORD’ value to ‘0x0’. By the way, the problem affects not just Windows Server 2022 but also Windows Server 2019, 2016, 2012, and 2012 R2.

Bitlocker bug also causes headaches

The KB5040437 update does cause more problems. Another bug causes systems to boot into BitLocker recovery mode after installing the July 2024 Patch Tuesday updates.

This issue mainly affects users with the ‘Device Encryption’ option enabled through Settings > Privacy & Security > Device Encryption. Fixing this issue requires the Bitlocker recovery key from the associated Microsoft account.

Unlike consumer versions of Windows 11, Windows Server 2022 receives updates only once a month as part of the Patch Tuesday cycle. Microsoft says it is working on a permanent fix for the problems.

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