Why does 24h2/2025 host give only RDP over TCP?

Question

After upgrading to 24h2, the ability to connect to RDP via UDP disappeared everywhere. However, on previous versions everything is fine, configuring policies and substituting mstsc.exe etc. does not solve the problem. This problem itself was still in insider versions and how could it go in production? This creates some performance issues and network overhead. Of course I really appreciate that 24h2 was rewritten to sse4.2 and it gives a noticeable speed increase everywhere, but however rdp only via tcp messes everything up... The problem still exists to this day and on the latest version 26100.2605 and is exactly the same on the server variant of Windows, and has absolutely no dependence on the client and group policy settings. If a client with 24h2 connects to any old version of Windows, there is UDP. But if there is 24h2 on the host, then only TCP. And what's to be done about it? Reinstalling on 23h2 is not an option as well as switching to other solutions like anydesk... More importantly, why is there no mention of it anywhere? Antiviruses and firewalls, opening ports, etc. have nothing to do with it.

Answer 1

Hello,

 

Thank you for posting in Q&A forum.

Far from now there's none official fix in the Windows 24H2 OS patch for this issue, I would suggest rolling back to 23H2 to avoid such issue.

Meanwhile, you can also try some third-party RDP application as workaround.

 

I hope the information above is helpful.

If you have any questions or concerns, please feel free to let us know.

 

Best regards，

Jill Zhou

 

---

If the Answer is helpful, please click "Accept Answer" and upvote it.