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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2024-07-16T16:46:08+00:00

    I have the same issue on Server 2019 and removing the KB5040430 patch stopped it. I believe that for me the service crashed anytime someone disconnected from the gateway since it could work for hours without issue and the crashing was sporadic.

    Was 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-07-17T12:45:39+00:00

    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-26T10:55:19+00:00

    This is now listed as a Known Issue in each relevant KB article:

    Windows Server 2022 Link: KB5040437
    Windows Server 2019 Link: KB5040430
    Windows Server 2016 Link: KB5040434

    The Known Issue provides a couple of workaround options as well as the info: 

     ***Next steps****: We are working on a resolution and will provide an update in an upcoming release.*

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments