July 07-2024 Updates Break Remote Desktop Gateway Servers

Martin 65

We are seeing the issue on 2 of our four RDS Gateways (running 2022 STD).

Faulting application name: svchost.exe_TSGateway,
version: 10.0.20348.2520,
time stamp: 0xf862c7cb
Faulting module name: aaedge.dll,
version: 10.0.20348.2582,
time stamp: 0x78ded40f
Exception code: 0xc0000005
Fault offset: 0x000000000006613c
Faulting process id: 0x273c
Faulting application start time: 0x01dad77010a2bee1
Faulting application path: C:WINDOWS\system32\svchost.exe
Faulting module path: c:windows\system32\aaedge.dll
Report Id: d4502b05-b974-4660-bc13-5f2da108f403
Faulting package full name:
Faulting package-relative application ID:

and in TerminalServices-Gateway log:
The following exception code "3221225477" occured in the RD Gateway server. The RD Gateway will be restarted. No user action is required.

The results of these crashes are that all users connected via the affected gateway are immediately disconnected and must reconnect. Obviously very disruptive when its happening every 30 or so minutes!

Remove of the CU immediately "cures" the issue.

Anyone else seeing issues? Anyone managed to raise a case with PSS / get any feedback from Microsoft? Multiple reports of this starting to come out the woodwork on various forums.

Oh whilst I remember, why on earth did Microsoft kill off old technet forums, they were brilliant, compared to this garbage (progress right?)

Magzz 0 Reputation points

2024-07-16T11:58:22.08+00:00

We are having the same problem on 6 out of 7 2019 RDS-gateways

Have you found a solution yet?

Regards

Magzz
Martin 65 Reputation points

2024-07-16T12:38:35.97+00:00

Nothing yet other than rolling back the update :-( As you can imagine our security team aren't particularly happy with that "solution"
Mario M 5 Reputation points

2024-07-16T15:22:23.75+00:00

same problem on Windows Server 2016... rollback of KB5040434 fixed the problem....
Trey Contello 15 Reputation points

2024-07-16T20:22:47.6066667+00:00

I experienced the same issue on our Windows 2019 RDS Gateways. The problem started right after July patches were installed. I uninstalled the July update (KB5040430) and haven't seen the trouble since.
Deleted

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

2024-07-17T13:23:45.37+00:00

I experienced the same issue on our Windows 2019 RDS Gateways. The problem started right after July patches were installed. I uninstalled the July update (KB5040430) and am waiting to see the outcome. Have also temporarily blocked the update on our update server as KB5040430 will re-install itself (or did on ours)
Pokey_80 0 Reputation points

2024-07-17T13:25:57.0066667+00:00
how practical is this for a large setup? it seems like far too much hassle certainly where BYOD devices play a part.

From all Windows client machines, delete the registry entry associated with RDGClientTransport. The specific path to this entry is: HKCU\SOFTWARE\Microsoft\Terminal Service Client\RDGClientTransport.
Trey Contello 15 Reputation points

2024-07-17T13:41:54.1466667+00:00

Karlie, what RDP clients would typically use this transport? And once disabled, what alternate transport would be used?
Martin 65 Reputation points

2024-07-22T11:04:59.2066667+00:00

Karlie's "Answer" is incorrect.
Not sure where "port 3388" can from? TCP? UDP? what's the source?

Also not feasible / factually correct to delete the registry key from remote systems using an RDS Gateway, by definition these are likely to be BYOD endpoints, how does this fix a MAC or Linux client :-D

But thanks for trying to help.
TK 290 Reputation points

2024-07-22T18:54:37.5666667+00:00

When is Microsoft planning to acknowledge the issue?
Karlie Weng 18,111 Reputation points Microsoft Vendor

2024-07-23T00:09:08.07+00:00

Hello all,

I apologize for any misinformation that was provided. It appears there were some inaccuracies in the workaround I previously shared, so I've removed them to avoid any confusion for other users. I've noticed that quite a few people have already reported such issues to Microsoft. I understand the frustration that comes with waiting for the next updates. But rest assured, as soon as there's an update or a better solution, I'll make sure to share it right away.

Thanks for your patience.
Antonio Urban - Systech 5 Reputation points

2024-07-24T08:57:05.6966667+00:00

Same problem here, with server 2016 RDGs. I have two. In one I removed the patch, and no issues. The other one failed just now
John Randall 0 Reputation points

2024-08-09T08:52:53.2+00:00

We experienced same problem on Windows Server 2012 R2... Rollback of KB5040456 fixed the problem.
Malcolm 0 Reputation points

2024-09-04T04:11:43.7266667+00:00

After resolving the issue by removing July patch KB5040437 on Windows Server 2022, the August patching has re-created the issue, but this time the crash occurs when a user disconnects or logs off from the remote machine. After 5 minutes or so the service recovers and accepts connections again.
Ferry Knol 5 Reputation points

2024-09-06T00:45:08.72+00:00

For those who like to know.
I got the exact same issue as Malcom described.
Today (05-09-2024) i discovered that KB5041160 (august 2024 update) for Windows server 2022 is causing the issue.
After an uninstall of KB5041160 i was able to resolve it.
Bernhard Weitlaner 15 Reputation points

2024-09-12T05:53:44.4133333+00:00

Hello,

has somebody tried to install the september cumulative update? Are the issues resolved?
Thanks.
Bernhard Weitlaner 15 Reputation points

2024-09-13T06:18:33.9533333+00:00

I tried it, it is not solved in september cumulative update. :-(
Humpix 26 Reputation points

2024-09-13T09:05:21.2233333+00:00

Error is still there with September patches, Server 2019 - any news on this?
TK 290 Reputation points

2024-09-13T14:33:55.27+00:00

Microsoft has now updated the September OS KB links in the last 24 hours to acknowledge that the issue is still there. At least they didn't dilly-dally to acknowledge the issue, unlike previous months. See for example: https://support.microsoft.com/en-us/topic/september-10-2024-kb5043051-os-build-14393-7336-03d6cb4e-2d98-4048-a5fe-91ad913e34b5

6 answers

Kristofer Layman 1 Reputation point

2024-08-21T22:46:18.68+00:00

The port 3388 Windows firewall blocks didnt change anything, still crashes when a user disconnects. I didnt try disabling the RPC protocol as Antonio Urban suggested so I am not sure if that would work for me. However, the non-public patch that I found on Reddit for Server 2019 did work.
Please sign in to rate this answer.
Gustavo Correia Prado 0 Reputation points

2024-08-27T21:23:32.93+00:00

Could you say the link? I have the 2016 and I'm facing the same problem

Alan O'Riordan 11 Reputation points

2024-08-28T09:54:20.66+00:00

Does this help:

https://www.reddit.com/r/sysadmin/comments/1dyu3ia/comment/li45b67/
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

July 07-2024 Updates Break Remote Desktop Gateway Servers

6 answers

Your answer