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-09-13T09:58:57+00:00

    I still experience the issue on Server 2019.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2024-09-12T14:47:09+00:00

    @Dustin Winger1 And yet the September KB release notes state the issue was fixed. Either they didn't update the release notes properly or they really thought they had fixed the issue. 🤷‍♂️

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2024-09-12T14:41:43+00:00

    The response I got from my support case a few weeks ago was that the fix for this is available in 9D.24 (out of band) and 10B cumulative monthly rollout for all server versions. I am guessing that this means we have to wait until the October release.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2024-09-12T14:33:09+00:00

    The September CU doesn't seem to fix it for Server 2022.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2024-09-12T13:58:53+00:00

    Thanks Julien, sorry to hear that. Just checking on this Reddit thread, I see others are experiencing the same today, i.e. the problem has not been fixed in the update. Really hoping MS can sort this out soon.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments