RDP Hangs up on login after 24H2 update

Anonymous
2025-01-13T20:54:05+00:00

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

Windows for business | Windows Client for IT Pros | User experience | Remote desktop services and terminal services

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. To protect privacy, user profiles for migrated questions are anonymized.

0 comments No comments
{count} votes

32 answers

Sort by: Most helpful
  1. Anonymous
    2025-01-21T14:31:46+00:00

    Hello,

     

    Recently, we have seen a similar situation in our local environment. In the state of reproducing hang on the logon interface, you can use another client to initiate mstsc, and the same account can be logged in normally.

    It is speculated that the current stuck problem may be related to the client, and then the logs will be collected in the environment where the problem is replicated locally, and the log will be compared and analyzed. If it is confirmed that it is a bug or a code defect, we will contact a code engineer for assistance. If there is any progress, we will reply to you as soon as possible, please be patient.

     

    I hope this information helps.

     

    Best regards,

    Jingjing Wu

    Where are we at with confirming this bug? or do we have any work arounds that don't involve me telling users to keep trying until i get a chance to reset their VM?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2025-02-08T02:20:10+00:00

    I noticed this myself, so did my own investigating before I even came onto Microsoft for answers. I found it interesting that you really log in just fine, its not frozen. But its not transmitting screen captures, which is why it does not show up on Event logs. I tested this by going through the motions to open run, start notepad, and type a message. I didn't see any of it of course, but upon logging back in there it was.

    You can cycle it easily by using RDP and assume you are opening Win+R for Run, paste "shutdown /r /t 0". After every restart each user gets a new session to start. Use it to import Group Policies. There are many ways to get this done, I leave that research up to you. Run "gpedit.msc" in Admin would be the easiest (Ctrl+Shift+Enter).

    It does not take long you wont be logging in any more as most of you us found out. Essentially you keep creating new RDP sessions until you trigger UDP protocol usage, and then your done seeing anything. Need to remain in TCP, like all the times before I have read so far.

    So far I have had 100% success for 2 days with adding these Group Policy Changes:

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

    ...\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.

    ...\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.

    ...\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.

    My Documents\default.rdp file I used all day. I went a little overkill because I work remote for an Higher Education institution and this is a busy time. Can't afford nonsense right now.

    full address:s:COMPUTER.DOMAIN.ROOT.TOPscreen mode id:i:2use multimon:i:0desktopwidth:i:2560desktopheight:i:1440session bpp:i:32winposstr:s:0,1,275,0,2367,1392compression:i:1keyboardhook:i:2audiocapturemode:i:0videoplaybackmode:i:1connection type:i:7networkautodetect:i:1bandwidthautodetect:i:1displayconnectionbar:i:1enableworkspacereconnect:i:0disable wallpaper:i:0allow font smoothing:i:0allow desktop composition:i:0disable full window drag:i:1disable menu anims:i:1disable themes:i:0disable cursor setting:i:0bitmapcachepersistenable:i:1audiomode:i:0redirectprinters:i:1redirectcomports:i:0redirectsmartcards:i:1redirectwebauthn:i:1redirectclipboard:i:1redirectposdevices:i:0autoreconnection enabled:i:1authentication level:i:2prompt for credentials:i:0negotiate security layer:i:1remoteapplicationmode:i:0alternate shell:s:shell working directory:s:gatewayhostname:s:gatewayusagemethod:i:4gatewaycredentialssource:i:4gatewayprofileusagemethod:i:0promptcredentialonce:i:0gatewaybrokeringtype:i:0use redirection server name:i:0rdgiskdcproxy:i:0kdcproxyname:s:enablerdsaadauth:i:0smart sizing:i:1drivestoredirect:s:remoteappmousemoveinject:i:1redirectlocation:i:0

    Edit: Oh geeze, was that really what ended up on this user account? So yeah, the policies work - and dont use that file, just use what you normally config but keep the colors down, fonts normal, and anything that usually chews up bandwidth.

    Anyways it should not be long now until we import this into the AD and set it loose on domain wide usergroup.

    Cheers,
    Alex

    12 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2025-01-15T12:38:47+00:00

    Hello,

    Recently, we have seen a similar situation in our local environment. In the state of reproducing hang on the logon interface, you can use another client to initiate mstsc, and the same account can be logged in normally.

    It is speculated that the current stuck problem may be related to the client, and then the logs will be collected in the environment where the problem is replicated locally, and the log will be compared and analyzed. If it is confirmed that it is a bug or a code defect, we will contact a code engineer for assistance. If there is any progress, we will reply to you as soon as possible, please be patient.

    I hope this information helps.

    Best regards,

    Jingjing Wu

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2025-01-17T14:36:10+00:00

    Hello,

    same problem here. Since the update to 24H2 we have a lot of machines with exactly the same issue here. Please increase the priority to solve the problem....

    I can not confirm "Recently, we have seen a similar situation in our local environment. In the state of reproducing hang on the logon interface, you can use another client to initiate mstsc, and the same account can be logged in normally." => Tried the connection from 2 differnet clients (Win10 22H2 and Server Server 2016) to a 24H2 machine. Both connections are "hanging"

    Michael

    2 people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2025-02-27T21:02:09+00:00

    Hi All,

    This has been very helpful info for us. What solved our problem is:

    Local Computer Policy Editor> Computer Configuration> Administrative Templates> Windows Components> Remote Desktop Services>Remote Desktop Session Host> Connections> Select network detection on the server - set to Enabled, Turn off 'Connect Time Detect and Continuous Network Detect

    Image

    Image

    >> Afterwards, a reboot isn't needed but a gpupdate /force is.

    I don't know if this will work for all but it did work for us. found the above on https://www.reddit.com/r/sysadmin/comments/1gbq4y7/windows\_11\_24h2\_rdp\_session\_hangs\_on\_logon/

    Best Regards.

    2 people found this answer helpful.
    0 comments No comments