Since upgrading from Windows 11 23H2 Enterprise to Windows 11 24H2 Enterprise, RDP Has Not Worked.

After further research, I found my cause and solution here:

https://learn.microsoft.com/en-us/answers/questions/5650732/how-to-get-group-policy-for-duplicate-sid

Hello Maurice A. Miller,

This issue is directly related to Windows for Business environments, specifically Windows 11 Enterprise deployments, but it is not tied to Windows 365 Enterprise. The failure of RDP after upgrading from 23H2 Enterprise to 24H2 Enterprise is a Windows OS regression affecting on‑premises or domain‑joined enterprise systems, not cloud‑based Windows 365 instances.

Based on your description, the builds 26100.7840 and 26100.7922 are cumulative updates for 24H2, and the fact that RDP consistently fails across your environment indicates a systemic regression in the Remote Desktop Services stack. The error persists even after rollback attempts, registry edits, and GPO adjustments, which suggests that the issue is not configuration‑based but rather introduced by changes in the 24H2 kernel or RDP components. Microsoft has already documented RDP breakage in 24H2 under “known issues” in the release health dashboard, and the official workaround has been limited to out‑of‑band updates or disabling certain security hardening features. Since you’ve confirmed that the OOB updates are either not applicable or ineffective, the only remaining path is to wait for Microsoft to release a servicing fix specifically targeting RDP in 24H2 Enterprise.

At this point, there is no additional registry or GPO tweak that will restore functionality. The regression is within the updated RDP binaries themselves. The best practice is to hold back 24H2 deployment in production until Microsoft publishes a confirmed fix in the next cumulative update cycle. If you must run 24H2, the only supported mitigation is to use alternative remote management tools (PowerShell Remoting, Windows Admin Center, or third‑party RMM) until RDP is patched.

I hope you've found something useful here. If it helps you get more insight into the issue, it's appreciated to accept the answer. Should you have more questions, feel free to leave a message. Have a nice day!

Domic Vo.

For Windows 11 24H2 Enterprise environments where RDP stopped working after upgrade and previously tried steps (rollback, OOB updates, registry and GPO changes) did not help, the supported additional actions from current documentation are:

1. Ensure the RDP issues fixed by KB5053656 are actually remediated
   • RDP disconnects and freezes introduced by January–March 2025 updates on Windows 11 24H2 are explicitly addressed in KB5053656.
   • Confirm that all affected 24H2 devices have the March 27, 2025 or later update installed (KB5053656 or newer cumulative update for 24H2). This is required to fix:
     • Sessions disconnecting after ~65 seconds over UDP to RDS on Windows Server 2016 or earlier.
     • Remote desktop freezes and disconnects introduced by KB5050094 / KB5053598.
2. If not yet on KB5053656 or later, use the Known Issue Rollback (KIR) Group Policy
   • For enterprise‑managed devices that are still on updates earlier than March 27, 2025 and cannot yet move to KB5053656 or later, Microsoft provides a KIR policy that rolls back the problematic change.
   • Download and deploy the specific KIR policy for Windows 11 24H2 / Windows Server 2025:
     • “Windows 11 24H2 and Windows Server 2025 KB5053598 250314_20401 Known Issue Rollback”.
   • Import and configure it under:
     • Computer Configuration > Administrative Templates.
   • After configuring the policy, restart the affected devices so the rollback takes effect.
   • This KIR is documented to resolve the RDP disconnect issue caused by the January, February, and March 2025 updates.
3. Prefer installing the latest cumulative update instead of relying on KIR
   • If possible, move all affected 24H2 devices to the latest available cumulative update (which includes KB5053656 fixes). When this is done:
     • The KIR and special Group Policy are no longer required and should not be needed to keep RDP stable.
4. Validate whether the issue matches the known 65‑second UDP disconnect pattern
   • The documented 24H2 RDP issue specifically affects UDP‑based connections from Windows 11 24H2 to RDS deployments on Windows Server 2016 or earlier.
   • If the environment matches this pattern and RDP disconnects shortly after connection, the resolution path is:
     • Install KB5053656 or later on all 24H2 clients; or
     • Until that is possible, deploy the KIR Group Policy for KB5053598 as above.
5. If RDP is still non‑functional after KB5053656 and/or KIR
   • At this point, the environment is outside the scope of the currently documented 24H2 RDP issues and their resolutions.
   • The next supported step is to open a support case with Microsoft, referencing:
     • That all 24H2 devices are on KB5053656 or later (or that the KIR policy for KB5053598 has been deployed and devices restarted), and
     • That RDP remains non‑functional across the environment.

References:

• Resolved issues in Windows 11, version 24H2
• February 11, 2025—KB5051987 (OS Build 26100.3194)
• January 28, 2025—KB5050094 (OS Build 26100.3037) Preview
• February 25, 2025—KB5052093 (OS Build 26100.3323) Preview
• Windows 11, version 24H2 update history