Hi Cynthia,
Check this link and the registry settings windows-11-22h2-rdp-disconnects-and.html
Hope this helps.
==
Please "Accept the answer" if the information helped you. This will help us and others in the community as well.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I updated my WORK laptop over the weekend to Win 11 version 22H2, and now my remote virtual desktop will not work. I log into my remote desktop using a domain, through the internet. It does not have an actual "program" that is installed on my laptop, but a domain name that I log into (which, incidentally, is supported by Windows Server 2016). I am able to successfully LOG IN, and a status bar comes up that says "initiating remote connection", then "securing remote connection", then "loading the virtual machine". Generally, after the "loading the virtual machine" it will pop up the remote desktop in a new environment (that can be windowed), looks just like it would if you are starting up your computer. However, now it is just sitting at "loading the virtual machine" and does not progress.
To compare, I have a PERSONAL laptop that also runs Win 11, but has NOT been updated to the new version, and I can log into my remote desktop from it with NO PROBLEMS. (no, I can not use it for work as it has no anti virus on it and I work in healthcare).
I have contacted my IT department and they say this is not something they can troubleshoot.
Please help.
Hi Cynthia,
Check this link and the registry settings windows-11-22h2-rdp-disconnects-and.html
Hope this helps.
==
Please "Accept the answer" if the information helped you. This will help us and others in the community as well.
Thank you. Other than me having to google how to do the things advised in that link (I am no computer genius) - this worked beautifully.
FIX 1: Disable UDP Network Protocol
FIX 2: Disable the “Turn Off UDP On Client” Policy
FIX 3: Downgrade to Windows 11 21H2
Regards,
Peter
Yes, it works!
gpedit.msc
The regedit.msc did not work for me.
Thanks!