RDP Hangs up on login after 24H2 update

Question

It seems like there is an issue that I wasn't aware of before updating a few machines to 24H2. So before reverting back to 23 I wanted to see if anyone knew of a fix.

https://www.reddit.com/r/sysadmin/comments/1gbq4y7/windows_11_24h2_rdp_session_hangs_on_logon/

Similar to this guys issue, I was wondering if anyone was aware of any actual fix for this? I haven't seen anything in my searches yet that would indicate any new patch for it. I wanted to move forwards preferably rather than backwards if that makes sense. So i figured if I post here while searching maybe someone knows or has experience on this.

So basically what happens is that you log into an RDP session after a the VM has been on for a while and it will freeze with the dots that normally spin in a circle will stop moving. This will require that we restart the entire VM each time we want to log back in after an extended period. This only started happening after upgrading to the following build.

Edition Windows 11 Enterprise

Version 24H2

Installed on ‎1/‎8/‎2025

OS build 26100.2033

Experience Windows Feature Experience Pack 1000.26100.23.0

Answer 1

Run "gpedit.msc" as Admin

From LDP, make the following changes to:

*LCP\Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Connections*

1. ..\Restrict Remote Desktop Services users to a single Remote Desktop Services session

Enabled : Select Detection Level : Turn off Connect Time Detect and Continuous Network Detect

If you disable Connect Time Detect and Continuous Network Detect, Remote Desktop Protocol will not try to determine the network quality at the connect time; instead it will assume that all traffic to this server originates from a low-speed connection, and it will not try to adapt the user experience to varying network quality.

2. ...\Select RDP transport protocols Enabled : Select Transport Type : Use only TCPIf the UDP connection is not successful or if you select "Use only TCP," all of the RDP traffic will use TCP.

3. ...\Select network detection on the server

Enabled

If you enable this policy setting, users who log on remotely by using Remote Desktop Services will be restricted to a single session (either active or disconnected) on that server. If the user leaves the session in a disconnected state, the user automatically reconnects to that session at the next logon.

This solution posted by @Alexander has worked for my situation, but is NOT ideal.

I too, wanting to understand the issue, tried many variations on this Policy Edit and configuration.

So, for the record, here is my environment.

Win11 Enterprise (23H2 Build) with Corporate Policies (Work Laptop) - This is my primary system that I RDP from.

• Connected to the Corporate Network via PaloAlto VPN
• Connected to a lab network (Which is were all my engineering systems reside) via the same VPN.
• So, the VPN is required and no way to connect to my lab network any other way if I want Corporate Resources

Lab Windows System - Win 11 Enterprise (24H2 Build)

• Lab Network Only

This configuration worked perfectly when my Lab Windows System was running 23H2.

I upgraded to 24H2, per Corporate Direction.

When I did this, my RDP sessions would hang (or seem to) on the Login Dot-Pinwheel. It would never move past this.

I got so frustrated with the situation, as my job requires this system, I went and bought a KVM-over-ip-Gateway. This solution worked, but not nearly as well as the RDP as I typically use 2 monitors and the KVM only uses one. Not ideal, but better than nothing.

I then found this thread that described what I was experiencing. I went and tried many variations on the policy edits to see what worked and what didn't. I could do this as I have direct KVM access and not dependent on the RDP. I found that I had to use the Group Policy Changes, exactly as described, in order to get the client to work. The sad part is that now the performance and responsiveness of the RDP session is pretty bad. Not anywhere close to how it used to be prior to the 24H2 update. Makes sense. We've now disabled all the adaptive network quality adjustments and forced the client to bare minimum.

I even tried the RDP client on the Microsoft Store. I found this client vastly inferior to the built-in RDP client. It looks nicer, but, lacks the controls and options provided by the built-in. This client also hangs on the login dot-pinwheel about 85% of the time. I think it worked twice at first. And in both cases, soon hung after I was already logged in.

Microsoft,

Please investigate the change-set that went into the network quality adaptation system for 24H2 and why it is no longer compatible with 23H2 or other RDP clients. It is definitely a test escape for the following scenario:

TCP Only (VPN Client with no, or poor, UDP bridging)

23H2 RDP Client

24H2 RDP Host

Also, please keep your built-in RDP Client! The App version is pretty, but lacks functionality for IT professionals who rely on quality software for their jobs.

Sincerely and Kind Regards,

-Paul Dunnells

Answer 2

Same investigation for me, the settings mitigating the problem seems to be the one disabling network detection...

3. ...\Select network detection on the server

Enabled : Select Detection Level : Turn off Connect Time Detect and Continuous Network Detect

---

Answer 3

Switching to WAN/LAN instead of "Detect connection quality automatically" on the Remote Desktop Connection applications Experience tab so far seems to be working for me.

I'm waiting for feedback from some of my users before I'll look into pushing this setting as the default

Answer 4

The one from the store doesn't support dual monitors.

Answer 5

The one from the store doesn't support dual monitors.

Instead of using the Remote Desktop app from the Microsoft store you can also use the Windows app - that one does support multiple monitors AND sends Alt-Tab keystrokes to your remote session the way it should.