RDP issue after latest Windows Update on Windows 11 VM

Thank you. I tried this and it seemed to work. I originally thought it was just one particular Win 11 VM, but after trying to RDP to a couple of other VMs, it was happening on all of them, and this seemed to have fixed the issue.
Same here, I first thought it's only the Proxmox Win11 VM, as here the problem occured always.
But in meanwhile almost any Win11 machine seems to be affected, one more other less....
 
@wesker : is reproductible between VMs same PVE host, same subnet, same bridge ?
I haven't managed to reproduce it mine yet, with Win11 24H2, but I can test only inter VMs.
Neither with Win2025 (26100 build , same as Win11 24H2 ) , KB5051987 installed build = 26100.3194 , where I can test over WAN.

EDIT: Windows Server 2025 impacted too , with WAN user using mstsc client.
Not impacted myself because I use Microsoft Sysinternals Remote Desktop Connection Manager.
GPO fix it : https://forum.proxmox.com/threads/r...ws-update-on-windows-11-vm.162160/post-748171
(sorry for my english)
 
Last edited:
I cam't test if it's happening within same PVE Host, as I only have running this one WIndows VM on Proxmox. Others are Ubuntu Servers and Home Assistant.

Anyway, I'm sure it would, as it also happens between physical Windows machines on same LAN (but not as often).

In all cases, the workaround I posted before did solve the problem.
 
I cam't test if it's happening within same PVE Host, as I only have running this one WIndows VM on Proxmox. Others are Ubuntu Servers and Home Assistant.

Anyway, I'm sure it would, as it also happens between physical Windows machines on same LAN (but not as often).

In all cases, the workaround I posted before did solve the problem.
If you're users use a Windows client and the old Remote desktop client : go advance options , tab Experience/performance network, set it to LAN and disabled Background desktop, that works for me 2 VM ,
also i tried (without doing previous step )report update for 1 month & uninstalling KB5051987 worked for me.
 
Hi,

I got a very weird but reproducable issue with Windows Remote Desktop connections since installed latest cummulative Windows Update KB5051987, which is rolled out by Microsoft automatically since yesterday:

Wenn I connect remotely to the freshly started VM, everthing is fine. But when I close remote session (without logging off the user!) and then reconnnect, remote session gets stuck. - And only in this case! (But it's a common workflow, keeping the Windows user session logged in to reconnect later; it never caused a problem before)

It happens both when connecting remotely from another Windows 11 RDP-client and also when using the official Remote App "Windows" on iOS. See screenshots attached.

I've had this issue already with an "Preview-Update" that Microsoft has rolled out few weeks ago. I have even reinstalled the whole machine then and problem was gone.
Before installing official update KB5051987 today, i took a snapshot. And same result, after rolling back from snapshot, problem is gone (again).

So, I'm sure there is some issue with combination of Windows 11 + latest update KB5051987 + running Win11 as a Proxmox VM.
I have other bare metal machines running Windows 11 and also Hyper-V VMs, where the problem does not exist after installing KB5051987.

Unfortunately, I could not find out where the problem comes from. Nothing in Windows Logs, etc.

Further, it's still possible to connect to the running Win11 user session using Proxmox Console in Browser, even though the connection by RDP stucks.

Also I've tried connecting from local network instead of VPN, tried Intel virtual network adapter instead of VirtIO network adapter and much more.
Seems to be no network issue at all, as it also does not happen when logging in the user freshly (after logoff or reboot).
I'm running out of ideas...

I think this issue may affect all or many Proxmox users running a Windows 11 VM, as there is absolutely nothing special about my configuration, neither with the Proxmox host, nor with the Win11 VM.

It also is no special kind of Windows user, as it's just a test-machine. Just a normal, local Windows user account (no Cloud/AAD-, or local AD-user)

As a workaround, I have paused Windows Updates for 5 weeks (maximum) in update settings, after I've rolled back snapshot.

Hope for your ideas or a solution, many thanks in advance!
Came here to tell you your not crazy we have virtualized and non-virtualized clients/Companies having this exact problem we have seen a few "fixes", but nothing is really working ATM a few times we rebuilt the host machines with an new win 11 iso and it worked.
 
Weskers fix worked for me, I exported the bit of the registry this changes and imported it on my other 50+ vms and that worked fine.
 
The workaround also worked for me. Thanks @wesker !!

I also noticed that when a reconnecting session had problems. I could try to reconnect and eventually it succeded. Sometimes I needed one try, sometimes two, three or four, but in the end I managed to reconnect without rebooting the VM.

With the workaround it works like charm. Thanks a lot!
 
Finally, a workaround, that even worked for my Proxmox Win11 VM:

Setup local or AD-enrolled group policy on/for the RDP destination machine (see also screenshot attached):
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

Just for those who are not familiar with GPOs, you can run group policy editor for the local machine by:
Hitting Windows-Key + R, then typing "gpedit.msc" in the field and then click "OK".

Source:
https://www.reddit.com/r/sysadmin/comments/1gbq4y7/windows_11_24h2_rdp_session_hangs_on_logon/

None of the other settings needed additionally (like disabling of UDP, disabling wallpaper, etc.)!
This worked for me wesker! Thank you buddy!