RDP to Windows 10 hangs at Please wait screen

Question

RDP to Windows 10 hangs at the 'Please wait' screen forever until rebooted.

In our organisation, we are often seeing this issue on domain-joined systems & VMs with Windows 10 OS

This happens when users are trying to log in with their domain accounts. When the issue is reported, we IT team can log in with our Domain ADM accounts and reboot the system/VM. The user will be able to log in now, but the issue comes back again after a day or two. These systems/VMs are updated with the latest patches.

Even after running SFC Scan, the issue remains.

Answer 1

To solve this:

I use another remote PC and execute a remote restart command.

Answer 2

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.

Answer 3

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

Answer 4

After having this problem several times since 5/21 on one of three domain computers that i use RDP to access, I managed to log in without closing the session or rebooting the computer. I normally log in with a password but we also use smartcards. So this time, with RDP stuck on 'please wait', I opened a new RDP session and tried to log in my smartcard, which worked.

I know that won't work for everyone, but I was happy to have a solution in the case where I would lose work by rebooting.

Answer 5

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?