This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
We discovered that since the Windows 11 24H2 update, we have encountered an issue on computers running an RDP server with this build.
When someone tries to connect with a MacOS to these desktop PCs with the latest version of Windows App, the first try goes well, but if the session is Disconnected (either by pressing the X button to close the RDP session window or even by making a proper Disconnect in the power button), then we cannot reconnect with the same user to the desktop PC again. The screen is only showing the blue background and nothing happens.
Steps to reproduce:
1, Log into a Windows 11 24H2 build computer with Windows App using MacOS
2, Disconnect the session with the X to close the window, or disconnect using the power options
3, Try to log into the same computer with the same credentials again via the RDP session
4, You get a frozen login screen or only the background of the login screen
To resolve the issue usually we need to reboot the computer to reset the user's session entirely. Seems like the user session is somehow still there in the system, but cannot be terminated or even initiated after these actions.
Logging in with other users is possible meanwhile.
Steps we tried to resolve the issue:
Checked logs for errors, but they show a successful user login
Reset certificates regarding the RDP service
Reinstall Windows - We could even see that when we reinstalled that in build 23H2, it worked perfectly, but after updating to the latest 24H2 build, we got the error again
Workaround we found so far:
Users MUST Sign off their account every time they close the RDP session - It is not always a viable workaround as some users would like to continue their previous work, and this makes them unavailable to do this.
Based on the proofs we have, I highly think this is a bug in the new 24H2 build, I just hope to get this issue on Microsoft's radar to repair this in the near future, but if anyone has another workaround for this please let me know.
***Move from Windows / Windows 11 / Connect Phone and PC***
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.
Answer accepted by question author
Rolling out the Group Policy company-wide probably solves this issue until it gets fixed by Microsoft:
Local Computer Policy> Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Remote Session Environment > Enforce Removal of Remote Desktop Wallpaper - set to Enabled
We are experiencing the same issue when connecting from a Windows 365 Cloud PC (Windows 11 Enterprise 24H2) to a locally hosted Hyper-V Windows VM (Windows 11 24H2). Everything was fine until the update to 24H2.
We also tried different connection settings in mstsc but nothing seems to work - even disabling everything. Only a restart or clean sign-out on the target machine fixes the issue. We are currently hoping that MS fixes this soon.
Thanks for sharing. Confirmed this workaround is great with MSTSC. Hopefully this is a bug Microsoft can easily patch soon.
RDCMan 2.93 doesn't appear to be respecting the desktop background option though. I turn it off from Tools, Experience and 24H2 still freeze with the desktop background. I connect to a Windows 10 device through RDCMan and it still shows the desktop background even with the option unchecked. So, the option seems like it is broken in RDCMan.
