RDP to Windows 10 hangs at Please wait screen

I encountered the same issue.
Moreover, I can always use my laptop with the same Microsoft account logged in to connect RDP, while my phone, my pad and other people's Windows PC will be stuck at Please Wait screen.

To Leila-MSFT and everyone else with this issue:

I found a solution in MS RDP for the issue of RDP getting stuck at "Please Wait" after connectng, but I am only willing to explain and post it if I can speak with Leila-MSFT or someone at Microsoft directly. I would appreciate not having to post back and forth and be asked to "try" things when I clearly provided a possible solution in my last post that could be tested and confirmed by Microsoft support. If anyone from MS is willing to speak directly, please send me a direct message so that I can explain the problem and temporary solution, at which time you can confirm that it will become a permanent fix in updated versions of MS RDP. If you are willing to discuss the solution you will be helping many people with this issue, and if not at least I figured out the culprit of the issue and can post the solution elsewhere.

Hey, I have the same issue on certain machines.
It is a riddle to why some experience the problem and others dont.

If you have a solution I would love to hear it.
It seems this place has no way to private message it, but maybe you can still post it here after all.

I dont think you will be successful with the approach you took here.

Just post the solution here, why be so difficult?

Please see my new reply in the thread. Thanks.

Please see my new reply in the thread. Thanks.

The scope of the problem isn't limited to not being able to RDP in my experience. When the "Please Wait" RDP issue starts, other issues are introduced as well; logging in to the system locally and trying to "Run as administrator" for any program doesn't work as the UAC box never comes up. Curious if others have seen similar.

Since the solution was posted we have not had the problem, but will post the outcome if it happens again.

Exactly the same issue here !

Exactly the same issue here !

After getting past the "please wait" by starting a RDP session with a smartcard, the account does not seem to work as expected:

• it will not start a admin powershell or admin cmd window
• it will not start the event viewer
  For both of these cases, it just spins for a while then ignores the request.

And here's more strange behavior. I am able to avoid the "please wait" problem by connecting to the remote host using a saved (password) credential. Then, after deleting the saved credential and manually entering the password again, the "please wait" problem immediately reappears (until I reboot). I created the saved credential by mounting a shared drive from the remote computer.

Could this be the cause of the problem: Before accessing the computer with a password and encountering the 'please wait' issue, I mounted a drive from the remote host using a smartcard credential for the same domain account. Is windows confused because I am simultaneously using both types of authentication, smartcard and password?

I am having this exact problem today. I try to reconnect to a disconnected RDP session. I get the Please Wait blue screen after I submit the RDP Enter Your Credentials screen.
I am not using a smartcard, only typed in password. Connect over Microsoft VPN.
It has been an intermittent problem for many months.
Somebody has had to physically go to the stuck computer to restart it.
Microsoft needs to provide a solution for this problem. Microsoft, are you listening???

Please try my solution posted Nov 26 2021 at 4:09 AM . Look above your post a couple replies back. I suggested a workaround solution involving saving the connection details to an .rdp file and adding the line "enablecredsspsupport:i:0" to the file using notepad.

Disabling NLA is not an option in our organization. NLA is required to use Remote Desktop for us, and disabling it is a security risk.

I just started rolling out Duo 2 days ago for 50 users, and already I've had a user unable to login because of this issue. Setting their account to Bypass mode didn't help either. I was able to remote to their PC from another computer using their account, but we couldn't get them connected from the original computer they were using. Only rebooting the target computer resolved it, but this isn't a solution for the long term.

I NEVER FAILS, anytime I implement a new product or tech practice, things like this happen. Solutions always seem to bring more problems.

Has anyone actually figured out what causes this and how to fix it? It appears to be when sessions are disconnected and when you try to reconnect from the same machine.

My guess is it is when someone either has their computer go to sleep or closes their laptop before logging off the RDP session. This is an amazingly rare occurrence for me and the people I support in a number of businesses. I have only seen it happen with one person and it has only happened with him twice now. There are a number of solutions for rebooting the remote computer which you might gather from this topic. Alterative RDP clients may work, especially to reboot the remote PC.

We also see these problems with RDS Gateway/Hosts
For some reason this "Please Wait" issue mostly occurs with our customers trying to connect from a Microsoft Surface to one of our RDS Hosts.
A simple solution would be to manually logoff the user at the server end.. Sadly enough the user would lose all of his work.

I couldn't reproduce the "Please Wait" by disconnecting the session with the X on top for several times.
I figured out that by disabling Sleep on the Microsoft Surfaces the problem just vanished.
When I set the computer to go into sleep (after 5min) I can sometimes reproduce the "Please Wait" problem after few sleep cycles.

Remote reboot is just not a fix for an end user who would have to contact someone more knowledgeable at all hours of the night. I get that its rare, but it sure would be nice to reproduce this strange one and find an actual fix.

Stumbled upon this post after a user inquired about the issue. This was after not having seen the issue in (maybe 10) years.

Old school trick: try pressing CTRL+ALT+END (not DEL) on your keyboard -- this will effectively send a "CTRL+ALT+DEL" to your Remote PC and can sometimes fix the issue/give you additional options or insight into what's happening... or at least snap the system out of it.

I tried again this time and the workaround was still effective in my environment.

I am on macOS and set the option to "Ask when required" for credentials.

When prompted i gave just my user name and it attempted to login but since i didnt give password it shows the windows login screen.

Please I need a solution

I am getting this issue on two machines using Remmina in a Linux VM...

Had the same problem at work after transferring settings between identically configured machines (first working, the second had this issue). After trying things on this site and others, I believe I have the answer. After fighting the problem for two months, i have had no issues since applying this Group Policy (gpedit.msc) setting:

Computer Configuration >> Administrative Templates >> Windows Components >> Remote Desktop Services >> Remote Desktop Session Host >> Connections

At that level Enable the following setting

• Restrict Remote Desktop Services User to a Single Remote Desktop Services Session

SPH fix solved the issue for me, found the below article useful for creating a clean .reg key on my PC then exporting it for easier importing to other users in the future. https://admx.help/?Category=Windows_10_2016&Policy=Microsoft.Policies.TerminalServer::TS_SINGLE_SESSION

Recently I got the same problem and after losing my mid for 2 days and alredy given up, A sudden idea crashed my mind, should I do the fix on the PC that I want to connect? IT WAS THAT!!

the solution is to do as @SPH describes but ON THE HOST/REMOTE MACHINE the one you want to log in

Computer Configuration >> Administrative Templates >> Windows Components >> Remote Desktop Services >> Remote Desktop Session Host >> Connections

'Restrict Remote Desktop Services User to a Single Remote Desktop Services Session' and enable it and restart

I don't know why, but in my 2 PCs I was able to connect without problems, then I full reinstall windows 11/10 on 1 pc and It was stuck on the 'please wait screen', but in the other PC it was still working, so I try to apply the fix on the client PC (my PC) not on the host (remote PC)... ahh so much time wasted. Why in old installs works but not on new installs? no idea, use the fix

Easiest solution is to add this line in the rdp file:
enablecredsspsupport:i:0