Forum Discussion
Solved
Windows Version 24H2 Causes Remote Desktop to Freeze on reconnect.
After upgrading to Windows 11 latest version We lost the ability to reconnect in Remote Desktop as the screen just went black and froze. The only fix was to login as a different user and kick the other account out or login locally and log out. I researched this and was told to install all new updates and this would resolve the issue. We have homeworkers that connect over a VPN and this is causing work loss. When I look it up I get all kinds of different answers like. I read to deploy the latest patches to fix this, but nothing has worked. The only work around I have is to kick the user using qwinsta to find the session and rwinsta to kill it. I have tried turning off UDP and all the other work arounds I found with no luck. I am getting ready to just switch them out to another remote program as this is ridiculous that Microsoft would release a patch and not have tested it on a highly used application.
We had the same problem with the 24H2 update. On our office computers we made the following changes that fixed the remote desktop issue for us.
We went to the local computer policy > computer configuration > administrator templates > Windows components > remote desktop services > remote desktop session host > connections and enabled the select network detection on the server and set the drop down to turn off connect time detect and continuous network detect.
We also went to the remote desktop session host > remote session environment and enabled the enforce removal of remote desktop wallpaper.
I hope this helps your network.
20 Replies
What seems to be helping our users, after testing, was removing the desktop wallpaper and also setting the experience setting to WAN, rather than automatic. Not sure if both are needed, but from our tests of users so far that seems to prevent the freeze on the reconnect from occuring.
+1. The approved solution seemingly resolved our issues "getting in" to an RDP session, but then users complained about lag.
Setting the Experience to WAN or LAN in the RDP session helped. I read somewhere that when you disable the settings in the solution, Windows basically tells RDP that it's a "Dial Up" connection and seemingly throttles the connection.
Another interesting thing that we found was unchecking printers from the RDP session, that seems to help a little too.
Waiting for the March Cumu Update (preview is out now - KB5052093), supposedly the resolution will be there. We'll probably end up shorting our test period and get it out pretty quick.
Seems the latest update fixed the problem
2025-01 Cumulative Update Preview for .NET Framework 3.5 and 4.8.1 for Windows 11 Insider Preview for x64 (KB5050577)
Sadly not for us, i've applied the patch and restarted a test machine and it continues to freeze on the second connection / if you close and try to reconnect straight away.
I was experiencing the same issue and what worked for me (at least for the time being) was to go to the Experience tab and change to "Low-speed broadband (256 kbps - 2 Mbps)" instead of "Detect connection quality automatically". I haven't tried any of the other settings to see if they work yet.
Thanks, this work for me!
Yes, played with that as well, edited the registry to turn off UDP, turned off UDP in Group Policy an still no luck. I am testing the latest patch from Microsoft that may fix the issue. Another bug this causes is with Windows 11 users logging into older windows 10 PCs they drop every 2 min, Microsoft loves to test us...
As Frank indicated yesterday, there's a lot of success with the gpedit/gpo/reg keys.
It's apparently a 'known issue'.
RDP Hangs up on login after 24H2 update - Microsoft Community
We've got a similar issue with a workstation, but the difference being the workstation seems to completely lock up and stop responding to any RDP requests until it is hard reset.
Leaning towards hardware on that though, since most of what I can find seems to lack that specific detail, but here's hoping the reg keys fix this one too.
Cheers!Hey technical peoples,
Thank you!
We also had to change the remote Experience Tab to Highspeed because it limits the resources checked to connect. You could use LAN also you just need to uncheck the other resources below in the list.
We're seeing the same issue with computers in our org. I originally thought it was due to Duo Desktop as it was seemingly freezing after authenticating, but i'm starting to lean towards it being a Windows issue as all computers affected have been recently upgraded to 24H2 / Latest Feb Cumu update
Uninstalling KB5051987 worked for me. I had been troubleshooting this issue for a customer the last couple of days hoping that MS would release a patch. I provided them with a workaround using a tool that I use solely for remote support and not remote working. Today the customer indicated that they were losing productivity without the dual monitor capabilities provided with RDP sessions through a VPN, so I went nuclear and removed the patch / paused updates for 5 weeks. HTH!
Try the following from this post:
"Local Computer Policy> 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"
I am trying the setting Turn off Connect Time Detect only since the proposed setting above seems to degrade performance. - *Edit: this didn't work. Going back to Turn off Connect Time Detect and Continuous Network Detect.
So I did what any diligent worker would do; I researched. You ever Google something and end up with more options than IKEA furniture? “Install new updates; it'll fix it!” – Yeah, right! If I had a penny for every time I heard that line! I’m starting to think Microsoft has a team of developers playing roulette with our operating systems. They just spin the wheel, whatever it lands on, boom, that’s the next patch!
Please Re-Read the Post all the latest updates and patches have been deployed. No resolve. I also researched and opened a ticket with Microsoft, they are aware of the problem, and working on a fix.
We had the same problem with the 24H2 update. On our office computers we made the following changes that fixed the remote desktop issue for us.
We went to the local computer policy > computer configuration > administrator templates > Windows components > remote desktop services > remote desktop session host > connections and enabled the select network detection on the server and set the drop down to turn off connect time detect and continuous network detect.
We also went to the remote desktop session host > remote session environment and enabled the enforce removal of remote desktop wallpaper.
I hope this helps your network.
This also seems to have resolved the issue Update KB5050577
Just to clarify for anyone facing the same issue as I did, this GP change needs to be on the remote host, not on the client.
Apologies for the potentially daft question but we have users connect to a remote desktop server and then, from there, connect to their desktop. Only a few people have the freezing issue, so i had assumed it was something i had to fix on their end desktop to resolve this? Are you saying i need to apply the GPO fix to the RDS server OR their home machines (in particular i have users on macs that use a windows app so i know i cant sort that on there)?
Thanks Frank225 , we've attempted the above across our company as multiple reports were coming in at random of this issue, and its seemingly worked on some users that had issues with sessions not able to reconnect, but we have some other users that this continues with even after that change, and disabling UDP. We've tried clearing their account off the affected PCs and numerous other suggests registry / gpo fixes and it remains a problem for them. I'm trying to find the silver bullet fix but thus far we cant say its solved across the board with the above.
We tried the same, I am looking at (KB5050577) that was just released as a windows insider preview. Hoping this has the fix. I have to test via my remote site to see if the issues has been fixed.
