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)
All of our Remote Desktop Users using Windows 11 are having problems connecting to Remote Desktop after installing this update. It just hangs at connecting.
We have found that there is a bug in the Remote Desktop client so that it is only trying the UDP connection and not trying TCP connection. We only allow the port 443 connection through on our firewall.
The only workaround we have found is to make the following change on the Windows 11 computer.
Have to set this value to 1 in the registry for Windows 11 client to work outside the network
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\Client
KEY VALUE - fClientDisableUDP SET TO 1
Otherwise the Remote client just keeps trying to connect via UDP.
This issue did not start until the Windows 11 update was installed over the last couple days.
Jeff
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.
After entering username and password in remote desktop application
Windows stuck at securing connection........
My work is getting affected due to this issue. can any one help me out on this ?
Make sure you have at least the February 2023 Cumulative Update installed on the affected computer. Issue has been fixed in that update. Any update after that (March, April, May) will include the fix as well.
After entering username and password in remote desktop application
Windows stuck at securing connection........
My work is getting affected due to this issue. can any one help me out on this ?
Literally the only way I've found to resolve this to date is to rollback the 22H2 update. That's what I did. I have dozens od VMs and can't operate my current workflows without them. It would be a massive undertaking to move all my VMs to a different virtualization platform.
I'm in the process of building out a massive NAS with fault tolerance. Once that's done, I'm going to cut my VMs down to just a few, move them onto the NAS and migrate most of my apps, databases, etc into Docker images so i can run them in containers. It'll be easier to manage from there, much faster to spin up and tear down my dev environments. I need to be moving in that direction anyway.
If you have this 22H2 problem with RDP all you can do is roll it back and ignore the subsequent prompts from Windows update encouraging you to install it.
I'm waiting for MS to release a patch or some kind of fix for that update. Until that happens I'm not allowing that update on any of my Windows platforms, which means I'm stuck until a fix is available.
It appears MS is so far just ignoring the widespread issues this causes for people when RDP is broken.
If anyone has current info on a fix for this, please chime in. Othewise, rollback is apparently all we have for now.
I am still having the problem as of today..
I can connect to the Remote Desktop but when it asks for password it keeps telling me I have incorrect password which I am 100% sure I have the correct password.. so not sure where to go from here .. I even reset my Microsoft password and my Computer log in password but no luck..
Hi! Microsoft has fixed this several weeks (month) ago. So if you have not replaced the mstc-files by replacing the ownership, the problem should be gone (do not remember the KB by now).
