[German]Addendum from the October 2024 patchday (8.10.2024). The KB5044281 update for Windows Server 2022 (21H2) may cause problems with failover clusters. A reader has left a comment in the blog that the remote desktop services in his environment are being destroyed – at least in a failover cluster, as a German blog reader reported.
Advertising
Windows Server 2022 Update KB5044281
Cumulative Update KB5044281 was released for Windows Server 2022 on October 8, 2024. According to the support article, the update addresses a number of problems with this server operating system. Allegedly, a known problem with the Remote Desktop was also corrected, where Remote Desktop connections were interrupted throughout the company under Windows Server 2022.samten Unternehmen unter Windows-Server 2022 unterbrochen wurden.
According to Microsoft, this problem can occur if a legacy protocol (e.g. remote procedure call via HTTP) is used in the remote desktop gateway. Remote desktop sessions are then lost sporadically, e.g. every 30 minutes. Users then have to reconnect to the server. IT administrators can track this by the TSGateway service crashing. It no longer responds, triggering the exception code 0xc0000005. Microsoft now claims to have corrected this error.
Remote desktop services still disrupted
German blog reader ChristophH wrote a few days ago in this German comment and reported that KB5044281 continues to cause problems with Remote Desktop Services in a failover cluster for Windows Server 2022 (21H2).
The services would continue to crash. According to the reader, the update in turn damages an (unknown) component of the remote desktop services, which communicates with the Hyper-V services and/or the failover cluster manager. As there was no feedback on the comment, the question arises as to whether there are others affected.
A workaround
Blog reader ChristophH had already described a workaround in this German comment in September 2024.
1. Install update and boot
2. install the RD session host role (only add the role via Roles and Features
not the installation via the RDS management services !!!)
3. boot and test – error should be fixed
4. uninstall and boot the RD Session Host role
5. problem should be fixed permanently
Advertising
The described workaround repairs the defective or missing component. The process must be repeated on each cluster node.
Similar articles:
Patchday: Windows 11/Server 2022-Updates (October 8, 2024)
Patchday: Windows 11/Server 2022-Updates (September 10, 2024)
Advertising
