RDP issue after latest Windows Update on Windows 11 VM

[wesker]

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....

 

[_gabriel]

@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 impatect 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)

 

[wesker]

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.

 

[NBMTEC]

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.