Remote Desktop Gateway frequent disconnects after KB5040430

As so many others stated, I also had disconnecting RDS sessions & users could reconnect after about 1 minute of waiting. Periodically we would get popups for "Remote Desktop Licensing Issue" & just as it stated, users would be knocked off after about 60 minutes.
However, yesterday, we started having issues with DNS - users couldn't resolve website names anymore, thus no more web browsing for them.
A couple days earlier, I saw a time mismatch popup, but never saw it again, and all server's clocks are in sync... how strange...

When we had DNS problem, it'd only affect 1 RDS server, not all, so a simple restart that 1 RDS would temporarily fix its name resolution for perhaps an hour or two but then name resolution stopped again. The DCs were resolving/pulling up websites fine & DNS server service had no issues. And the problematic RDS DNS client service was running fine, but when name resolutions failed, nslookup suddenly showed "DNS Server: Unknown" whereas it had prior shown one of our DCs.

I had just ran updates in hopes, as others had, that recent releases would fix things. Nope.. Maybe made things worse, given the DNS issues.
I finally bit the bullet and uninstalled kb5040430. Given the number of user complaints for name resolution (and my concern over the strange time mismatch popup), I went sledge-hammer and uninstalled any updates that I could that were dated all the way back to July install date. I did this for RDS servers, GW, and DCs.

Anyhow, after doing the uninstalls I mentioned, it's been over 20 hours and no issues yet with RDS .. not yet.

@aw.windowsnutzer Thank you for the link. The Server 2016 KB now has the same notes: September 10, 2024—KB5043051 (OS Build 14393.7336) - Microsoft Support

I cannot recall the last time a Microsoft OS patch had an issue and then they failed twice over the next two months to resolve the issue.

The RDGW problem is now listed under “known issues” in the KB article. So now officially not fixed.

https://support.microsoft.com/en-us/topic/september-10-2024-kb5042881-os-build-20348-2700-5b548143-9613-4e5a-9454-8ed9be8b2bd2

In the German article it is still under “Improvements”.

KB5040437 July patch states: This issue is addressed in KB5042881

Curious

(Windows Server 2022)

I got some clarification from Microsoft. It looks like their release notes were incorrect.

With reference to you email below 9D.24 represent month of September, and 10 B represent month of October. Whereas D.24 is generally released in 4th week of the month and B is released on 2nd week of the month. We will keep you posted.

I still experience the issue on Server 2019.