This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
After installing KB5040430, we are seeing issues on the Server 2019 Remote Desktop Gateway on RDS.
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:
The system was operating normally before the Windows Update.
What steps can be taken to resolve this issue please?
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.
Very poor. from Microsoft - again.
An update has broken the only thing a server was used for - namely as a gateway server. Wasted over a day trying to fix it, not to mention the staff who cannot access their machines. Eventually discovered that it was not a configuration fault or a malicious attack, but an "update" which last time I checked was supposed to improve software.
No dates for resolution - I wonder how many users have been affected by this?
Disappointing.
After going through the painful experience of contacting Microsoft support they still don't have a practical fix for this. The only option they gave me was a client side registry change that isn't feasible with thousands of clients coming in from hundreds of different companies. Crowdstrike makes a huge programming error so Microsoft had to come in a scream hold my beer.
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.*
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