RDP issue after latest Windows Update on Windows 11 VM

W

wesker

New Member
Aug 17, 2023
14
3
3
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!
 

Attachments

  • iOS Windows App.PNG
    iOS Windows App.PNG
    918.8 KB · Views: 14
  • Windows Remote Desktop Client.jpg
    Windows Remote Desktop Client.jpg
    72.3 KB · Views: 14
Last edited:
This has nothing to do with Proxmox. Please choose other forums in the future for this kind of questions.

As you answered a part of the question by yourself, MS‘ patchcrap looks like the culprit. You can try to modify the connection settings for your RDP session. Try to disable „show desktop background“ (dunno the exact phrase in Windows).
 
cwt said:
This has nothing to do with Proxmox. Please choose other forums in the future for this kind of questions.

As you answered a part of the question by yourself, MS‘ patchcrap looks like the culprit. You can try to modify the connection settings for your RDP session. Try to disable „show desktop background“ (dunno the exact phrase in Windows).
Click to expand...
I don't see it that way. If the problem can be proven to only occur when Windows 11 is running on Proxmox, the cause may at least indirectly lie with Proxmox; as may the corresponding solution.
 
I saw other important issues with windows 11 integrated rdp client connecting to windows server (both not hosted on proxmox).
On users with these issues I workaround it using the "Microsoft Remote Desktop" from microsoft store instead the integrated one, I don't know if it can be useful also in this case.
 
Fantu said:
I saw other important issues with windows 11 integrated rdp client connecting to windows server (both not hosted on proxmox).
On users with these issues I workaround it using the "Microsoft Remote Desktop" from microsoft store instead the integrated one, I don't know if it can be useful also in this case.
Click to expand...
Thanks, I may try as a workaround, if problem is not solved till next Microsoft "Patch Day" in 1 month.
Anyway, this workaround would, in best case, only solve my problem when connecting from Windows PC. When connecting from iOS, there is no more good alternative app. Remotix was good, but hasn't been patched since years.
And as problem also occurs when connecting from iOS app, I guess it also will be the same with app from Windows Store.
 
Last edited:
I don't have experience with ios but FWIK someone use also freerdp on it, have you tried it?
 
Fantu said:
I don't have experience with ios but FWIK someone use also freerdp on it, have you tried it?
Click to expand...
Seems this is only for Desktops (Windows, Linux, MacOS). Anyway, I'm still sure the problem is not the Client, but the "Server" (= Proxmox-virtualized Win11 machine).

In meanwhile I've found some other reports about this issue related to latest Windows Updates + Virtualization (not only Proxmox). I hope one side, either Microsoft or the Hypervisor devolpers may find a solution for that; as it seems it does not happen on non-virtualized Win11 machines.
 
cwt said:
This has nothing to do with Proxmox. Please choose other forums in the future for this kind of questions.

As you answered a part of the question by yourself, MS‘ patchcrap looks like the culprit. You can try to modify the connection settings for your RDP session. Try to disable „show desktop background“ (dunno the exact phrase in Windows).
Click to expand...

Guess I found what you meant with disabling to show desktop Wallpaper, it's written as a solution here in the comments.
https://www.borncity.com/blog/2025/02/12/patchday-windows-10-11-updates-11-februar-2025/?

Anyway, problem persists, even when disabling Remote Wallpaper in case of my Proxmox VM!
 
There is no fix. Disabling Wallpapers, changing group policys etc, nothing will help.
Its simply a bug, i have the same issue on all Windows 11 Instances (Physical and VM's) where you have more as one Account on the PC/VM.

There is no fix.
And everyone has the same issue!

BTW, This happens 100% of the time with the normal RDP Client.
And this usually wont happen with the Remote Desktop Client from the Windows Store.

Cheers
 
_gabriel said:
Disable UDP protocol seems to be a workaround.
https://answers.microsoft.com/en-us...connects/5826f779-5bc2-437c-9fe5-3c16f3e4a2d0
Click to expand...
This is not a solution. The problem is NOT that RDP radomly disconnects! - The problem is that if a user session is still active from previous login and I reconnect another time (no matter if 10 seconds or half a day later), RDP will get stuck at Windows Welcome-Screen.
On the other hand, if I restart the machine, it's working normal (only once, as it's a fresh user logon then)
Also it's not possible to use TCP in various RDP clients, such as the "Windows"-App on iOS.
 
Ramalama said:
There is no fix. Disabling Wallpapers, changing group policys etc, nothing will help.
Its simply a bug, i have the same issue on all Windows 11 Instances (Physical and VM's) where you have more as one Account on the PC/VM.

There is no fix.
And everyone has the same issue!

BTW, This happens 100% of the time with the normal RDP Client.
And this usually wont happen with the Remote Desktop Client from the Windows Store.

Cheers
Click to expand...
You are right.
In the meanwhile I got this issue on 1 bare metal machine and another virtualized (Hyper-V in that case).
Anyway, could not reproduce it on another bare metal machine at all... But seems to affect many machines.
Can't believe that MS is rolling out such a faulty update. They should have seen the problem in their Preview-Version, which already caused the same issue o_O

Edit: It doesn't seem to matter how many user accounts exist or are used. In case of my Proxmox VM, it's just one, local Windows user account.
 
Last edited:
_gabriel said:
block udp port from within Windows firewall, not clients side.
UDP doesn't play well even with win10 with some networks.
Click to expand...
Thanks for this hint, it seems to help. Will try to reinstall KB5051987 on affected Proxmox-VM again now and report if it helps here too.

I also was surprised that in my case the connection is TCP anyways, when established, even when UDP is not blocked in any way. Maybe there is a UDP handshake in the beginning though, that causes the problem.

Anyway, it's weird. Never had to block UDP for RDP in the past, has not caused any issue recent update...
And surprisingly, the problem also does not exist when connecting to any of the servers (2016, 2019, 2022)...
 
Last edited:
wesker said:
Thanks for this hint, it seems to help. Will try to reinstall KB5051987 on affected Proxmox-VM again now and report if it helps here too.

I also was surprised that in my case the connection is TCP anyways, when established, even when UDP is not blocked in any way. Maybe there is a UDP handshake in the beginning though, that causes the problem.

Anyway, it's weird. Never had to block UDP for RDP in the past, has not caused any issue recent update...
And surprisingly, the problem also does not exist when connecting to any of the servers (2016, 2019, 2022)...
Click to expand...

Forbidding RDP over UDP in Windows Firewall does not fix the problem with the Proxmox-virtualized Win11 machine. Same behavior as before.
 
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.)!
 

Attachments

  • windows-11-24h2-rdp-session-hangs-on-logon-v0-xf9xsbj0n6ge1.webp
    windows-11-24h2-rdp-session-hangs-on-logon-v0-xf9xsbj0n6ge1.webp
    70.1 KB · Views: 35
Last edited:
  • Like
Reactions: Ramalama, bbv and _gabriel
wesker said:
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.)!
Click to expand...
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.
 
  • Like
Reactions: wesker
You must log in or register to reply here.
Top Bottom