If you have not heard about or seen the recent issues with Remote Desktop disconnecting, I would like introduce you to my current Hell. Have any of you had to deal with it and what did you do to fix it.

Basically resent windows updates have caused Windows11 Machines to disconnect from RDP sessions on a regular basis.

5 Spice ups

When you’re saying the devices are disconnecting, what are you seeing? We have had some people have the view of the RDP session freeze while the actions taken by the user are still being captured by the RDP session.

1 Spice up

Disconnecting how? Is the session being terminated prematurely? Is the connection being dropped while the session remains? Is there any lagging?

The short answer based only on your description is to roll back the updates.

1 Spice up

What does the event log say is the reason?

1 Spice up


Here is what shows on my screen, it has to do with the most recent upgrades to Windows11 24H2.
1 Spice up

Would this be on the Client or Server?

1 Spice up

I think both client and server logs are worth a look.
Do you know if there is a consistent uptime interval?

1 Spice up

try disabling IPV6 on one of the affected endpoints…

I hate recommending this, but we have observed some weird instabilities with IPV6 on 24H2 causing very hard to diagnose errors.

We have been holding back on a full rollout because of these issues

2 Spice ups

Here is a Reddit Post with more information.

https://www.reddit.com/r/sysadmin/comments/1isdifo/rdp_issues_with_windows_11_version_24h2_or_am_i/

1 Spice up

Trying that out on my computer to see if it helps, do you recommend a reboot or should it be live?

1 Spice up

Reboot isn’t required.

1 Spice up

IPV6 did not help.

2 Spice ups

There are known issues with the current 24H2 and RDM to other Win 11 and Server 2025 boxes. Seems to revolve around Bandwidth and Network detection. If you’re using something like Devolutions RDP, you can turn it off in the experience tab of the connection properties, uncheck Detect Bandwidth Automatically.

Or GPO it.

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 have not seen disconnects because of this personally but I have definitely seen hangs after initial connection where it refuses to continue on to the desktop.

3 Spice ups

Patrick,
is that done on the Client or Server side?

1 Spice up

See my warning here
What is going on with Microsoft Windows 11 Pro 24H2 updates - Networking - Spiceworks Community

Make sure you are using drivers from the manufacturer, not Microsoft updates.

1 Spice up

GPO is server side. Devolutions RDM fix is obviously client side. I started that way initially and after seeing it a few places, I threw a GPO in and set Devolutions back to normal. Problem solved. Should note it’s only affecting Win 11 and 2025. I have a WMI filter to target it to 2025 servers.

1 Spice up

I am attempting to just apply it to one server right now to test, does it require a reboot on the server? Or can I just edit its own Group policy directly?

1 Spice up

You can edit the local GPO to test. No reboot required. if you do a AD GPO, you will have to gpupdate /force from an admin prompt. No reboot should be needed there either. That’s how I initially tested. Remember to undo the Local GPO if you put an AD one in later.

1 Spice up

Thanks for the ides, still getting the disconnect on this server. Its a Server 2012 R2, I know ITS EOL, I am am in the works to get it updated to a newer version.

1 Spice up

You could try forcing a bandwidth setting client side here rather than auto detect, but I doubt that’s going to help. Still worth testing

1 Spice up