Share via

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. To protect privacy, user profiles for migrated questions are anonymized.

0 comments

48 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-07-11T16:15:06+00:00
    3 people found this answer helpful.
    0 comments
  2. Anonymous
    2024-07-12T08:10:48+00:00

    Uninstalling the update on the RD Gateway has restored normal operation.
    Obviously not having the update is not ideal.

    4 people found this answer helpful.
    0 comments
  3. Anonymous
    2024-07-15T12:53:37+00:00

    Hello, We have the same issue in my Compagny.

    The service TSGateway crash with id 700 and same message.

    Uninstalling the KB5040430 resolve the problem,

    We're waiting another security update to test.

    3 people found this answer helpful.
    0 comments
  4. Anonymous
    2024-07-15T16:59:16+00:00

    Just incase it helps anyone else, 2016 servers are affected by a very similar update under KB5040434. Uninstall of the update resolves the issue.

    3 people found this answer helpful.
    0 comments
  5. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more