Remote Desktop Gateway frequent disconnects after KB5040430

Anonymous
2024-07-11T14:39:08+00:00

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?

Windows for business | Windows Server | Performance | System performance

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

48 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-10-09T08:34:03+00:00

    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?

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  2. Anonymous
    2024-07-16T20:23:30+00:00

    Yep, we had the same with one of the clients. Remote Destop Gateway service was crashing every 2-5 minutes.

    I removed KB5040430 and blocked. It looks like this cumulative update didn't affect any other severs.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  3. Anonymous
    2024-09-10T19:23:14+00:00

    Looks like this could be be fixed now in September's update, if I'm reading this correctly:

    Key issues that this update addresses:...​​​​​​​***[Remote Desktop (known issue)]***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.

    Server 2022 - KB5042881 https://support.microsoft.com/en-gb/topic/september-10-2024-kb5042881-os-build-20348-2700-5b548143-9613-4e5a-9454-8ed9be8b2bd2

    Server 2019 - KB5043050

    https://support.microsoft.com/en-gb/topic/september-10-2024-kb5043050-os-build-17763-6293-66e9809a-1838-4474-a6a7-90d64f042f00

    Server 2016 - KB5043051

    https://support.microsoft.com/en-gb/topic/september-10-2024-kb5043051-os-build-14393-7336-03d6cb4e-2d98-4048-a5fe-91ad913e34b5https://support.microsoft.com/en-gb/topic/september-10-2024-kb5043051-os-build-14393-7336-03d6cb4e-2d98-4048-a5fe-91ad913e34b5If

    Let us know how you get on!

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2024-07-23T16:47:27+00:00

    That temporary solution was removed this week by the poster.

    Beyond awaiting a permanent fix, we are still waiting for Microsoft to publicly acknowledge the problem

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2024-07-17T12:45:39+00:00

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments