The Server 2016 link gets a Sorry - Page Not Found error for me.
Remote Desktop Gateway frequent disconnects after KB5040430
![](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)
Anonymous
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.
48 answers
Sort by: Newest
-
Anonymous
2024-09-10T19:48:57+00:00 -
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
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!
-
Anonymous
2024-08-22T09:34:51+00:00 Patch Tuesday Megathread (2024-07-09) : r/sysadmin (reddit.com)
Check out veloce-dragon post after their MS call. I haven't tried it yet or validated with my own MS call yet so buyer beware.
-
Anonymous
2024-08-22T06:53:45+00:00 Hi Everyone!. Was there an update on the solution for this?
-
Anonymous
2024-08-21T22:48:55+00:00 The port 3388 Windows firewall blocks didnt change anything, still crashes when a user disconnects. I didnt try disabling the RPC protocol suggested on the Microsoft learn site. However, the non-public patch that I found on Reddit for Server 2019 did work.