Remote Desktop Gateway frequent disconnects after KB5040430

Question

After installing KB5040430, we are seeing issues on the Server 2019 Remote Desktop Gateway on RDS.

All users get disconnected approximately every 30-60 minutes, and the following is logged in the Application log on the RD Gateway:

Faulting application name: svchost.exe_TSGateway, version: 10.0.17763.3346, time stamp: 0xb6a0daab

Faulting module name: aaedge.dll, version: 10.0.17763.6054, time stamp: 0xce1c5805

Exception code: 0xc0000005

Fault offset: 0x000000000005abe2

Faulting process id: 0x1db0

Faulting application start time: 0x01dad38ae65f65ae

Faulting application path: C:\Windows\system32\svchost.exe

Faulting module path: c:\windows\system32\aaedge.dll

Report Id: bbb10a26-fc25-4bba-9ed8-45c2eff5f5ba

Faulting package full name: 

Faulting package-relative application ID: 

The system was operating normally before the Windows Update.

What steps can be taken to resolve this issue please?

Answer 1

Apparently this has now been fixed in this month's update:
KB5044281 Windows Server 2022

KB5044277 Windows Server 2019

KB5044293 Windows Server 2016

"​​​​​​​**[Remote Desktop (known issue)]** Fixed: Windows Servers might disrupt Remote Desktop connections across your company. This issue might occur if you use a legacy protocol in the Remote Desktop Gateway. An example protocol is Remote Procedure Call over HTTP. If the issue occurs, it is sporadic, like every 30 minutes. At that point, you lose sessions that you are signed in to. Then you must reconnect to the server. IT admins can track this as an end to the TSGateway service. It stops responding, with the exception code 0xc0000005."

Can anyone confirm this update has fixed the issue for them?

I just installed this update to one of our client's servers that was affected by this issue. I will be monitoring the event log for the rest of the day and I will report back here if the issue still exists or if it is resolved.

Answer 2

Nor can I. One of our teams has an open ticket to Microsoft on this issue and Microsoft has ignored repeated attempts to get an update.

Answer 3

I can confirm that the KIR from the Reddit article works on Server 2019 with the latest September CU. I was about to remove the KIR, but then found the known issue was not resolved in September's patch so I have left the KIR on.