RDP to Windows 10 hangs at Please wait screen

kiran kumar 51

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.

Frank Alexander van Ede 6 Reputation points

2021-06-28T14:37:42.083+00:00
I am having the exact same behaviour with a user working from home on a domain-joined laptop, connecting to the office over VPN to a domain-joined workstation.

It is a unique case and I am wondering if it is related to how the RDP session is ended.

Our IT group works similar and never has issues. We connect to the VPN, open RDP, do our stuff, close RDP/disconnect, close VPN
The user leaves everything connected and closes the lid of the laptop. That action puts the laptop to sleep.

To resolve the issue we connect remotely with RDP to the computer of the user, and after a reboot, she can connect again over VPN, with RDP.

It seems something gets stuck; googling I saw this link: where they recommend killing the rdp client with

taskkill /f /im msrdc.exe

`
Ter 1 Reputation point

2021-11-10T02:50:38.413+00:00

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.
||v|| || ((=;; ||_|| ||£ ||_ 16 Reputation points

2022-10-26T23:30:33.957+00:00

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.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
SPH 50 Reputation points

2023-07-15T19:42:30.5233333+00:00
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
Alexander Niazi 1 Reputation point

2023-10-19T11:05:47.5+00:00

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

34 answers

Michael Pardo 96 Reputation points

2022-04-01T14:30:54.927+00:00
I ran into the same issue as a end-user with limited security. I was able to resolve my issue as an end-user:

in Powershell, I ran "query user /server:<SERVERNAME>". The server name was my remote desktop at the office.

I made note of my session id that was stuck.

I then ran "reset session <SESSION ID> /server:<SERVERNAME>".

That did the trick for me. Anytime, I run into this problem I run this. I'm trying to make it a habit to always log off my session every time to prevent this from happening.

If someone creates a temporary ps script for this, it would be interesting.
Please sign in to rate this answer.

19 people found this answer helpful.
jnw 1 Reputation point Microsoft Employee

2022-06-08T05:42:45.717+00:00

Thank you very much! It's helpful!!

PrashantV 76 Reputation points

2023-03-17T09:23:26.4533333+00:00

I am using the following commands. invoke-command -ComputerName <computername> -ScriptBlock {quser} invoke-command -ComputerName <computername> -ScriptBlock {logoff <session id from earlier command>}

03214309 0 Reputation points

2023-05-31T08:52:34.8133333+00:00

Thanks a lot!!!

HG 0 Reputation points

2023-06-15T19:07:34.5233333+00:00

worked perfectly for me, thanks!

ScottoR 5 Reputation points

2023-06-27T01:24:31.09+00:00

Can confirm this works, but I should have RTFM first. It doesn't kill connections/in prog auths to the session, it kills the session completely. Equivalent to a logout. Kinda had a lot of stuff open. :/ Again, not your fault.. just a word of warning to others.

(Incidentally, I got into this state bc my VPN disconnected while a session was still active. Which has happened plenty of times before, but this is the first time it resulted in the "Please Wait" screen issue.)

David Refoua 0 Reputation points

2024-05-02T17:37:57.59+00:00

I wish I hadn't run random commands found on the net on my machine :(

They should have named this "destroy session" instead of reset, or something with a similar word that would indicate that the open desktop and everything in it will instantly be lost, without any warnings, without any confirmations, etc.

If I wanted to restart my machine, I would have simply done so.

I sincerely hope that you would add a disclaimer or a warning above your commands, saying something like "Caution: This will DESTROY any open windows and ALL unsaved data that you were working on!"
Sign in to comment
Eric 186 Reputation points

2021-11-19T06:36:56.093+00:00
Hi MarlowSchlebusch-9296 and Marschos-8403,

Sorry I didn't post this sooner. I wanted to see if MS would respond (nope).

Windows PC - RDP Client mehtod- save the RDP connection to a ".rdp" file and edit the configuration through MS 'Notepad' to add a configuration line that will disable NLA login method and force Windows Login

Open MS RDP (Start->type "mstsc"->Enter) and type in the IP address you want to connect to

Click the "Options" button at the bottom and Click "Save" to save your connection as a ".rdp" file. Remember where you saved the file.

Click Start, type Notepad, Hit Enter

Click File, Open, traverse to the ".rdp" file you saved in 3 and open it.

Scroll to the last line and hit enter to add another line.

Add the following to turn of the Network Level Authentication: "enablecredsspsupport:i:0"

Click File, Save to save the ".rdp" file

Click Start, type "File Explorer"

Traverse to the directory which contains the ".rdp" file (do I need to provide instructions for this?)

Double Click the ".rdp" file

Connect, see Windows style login screen.

Enter your credentials and get past the "Please Wait" screen

Note: After adding this configuration line, when you double click the ".rdp" file to connect, it will connect to the Windows PC and then display the login page where you will have to manually type in the User and Password. Unfortunately, it will save the User for next time you connect but not the Password. You'll have to enter it every time, but you will at least get past the "Please Wait" screen.
Please sign in to rate this answer.

11 people found this answer helpful.
Eric 186 Reputation points

2021-11-19T06:37:27.647+00:00

Note: Adding this configuration line will make it so that when you double click the .rdp file to connect, it will connect to the Windows PC and then display the login page where you will have to manually type in the User and Password. Unfortunately, it will save the User for next time you connect but not the Password. You'll have to enter it every time, but you will at least get past the "Please Wait" screen.

Eric 186 Reputation points

2021-11-19T06:37:58.093+00:00

Android mobile method

Only solution I have found is to download the free "aRDP Free" app on the Google Play store and use that to connect.

It will ask for User and Password before connecting, but seems to use the Windows Login page and select "Other User", then pipe the User and Password into the box and hit enter for you.

If you use the official MS RDP Client, it will use NLA and get stuck at "Please Wait". Since "aRDP Free" does not use NLA, it is able to get past "Please Wait".

I do not know if this application is available for iOS, but if it is then I would assume that it will also connect successfully and bypass the "Please Wait" screen.

Eric 186 Reputation points

2021-11-19T06:38:15.03+00:00

Possible Universal Solution (Untested, someone please try) - Turn of Network Level Authentication (NLA) on source PC
This method comes from Microsoft support, though I have not tried it due to the fact that I did not have access to the PC at the time to make the changes
If we disable NLA on remote win10 computer and reboot the issue win10, will the same issue happen?
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp
REG_DWORD: SecurityLayer
Value: change 2 for 0
But the little check box that Enable or Disable NLA is actually the following registry key
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp
REG_DWORD: UserAuthentication
Value: change 1 for 0

how to disable NLA
https://social.technet.microsoft.com/Forums/en-US/c07323c2-77fa-4eb4-91ed-7ba6fa23bd00/how-to-disable-nla?forum=winserversecurity

roger_the_pan 6 Reputation points

2021-11-24T19:27:31+00:00

Editing the .rdp file as you suggested (add "enablecredsspsupport:i:0" to the end) worked for me. Thanks!!

Marschos 1 Reputation point

2021-11-26T09:09:43.34+00:00

@Eric Thank you for sharing your solutions.

The solution to edit the rdp file actually did not work, some error of something is not supported on connecting.
But changing the registry option on the remote system seems to work.

xiao yu 1 Reputation point

2022-12-30T12:22:44.54+00:00

thanks a lot. your method solved my problem.

Naveen Kumar NL 0 Reputation points

2023-01-14T03:35:49.6+00:00

Awesome! this worked like a charm!!

powermonger 0 Reputation points

2023-03-01T09:52:52.7466667+00:00

Worked for me thank you
This is a workaround, not a fix as such. Would love if someone has found a fix.

I had "require computers to use network level authentication to connect", that needs to be disabled (if its enabled).

RC 0 Reputation points

2023-11-27T03:38:58.37+00:00

This worked flawlessly for me. Thank you!

Quentin Muller 0 Reputation points

2023-12-19T09:18:39.73+00:00

Incredible! It just works.

Arnel Joaquin 15 Reputation points

2024-03-12T20:45:53.4066667+00:00

This fix still works and it's 2024...thanks!

Dietrich, Max 5 Reputation points

2024-04-05T07:53:18.8233333+00:00

What did you do exactually with the two reg keys?

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp REG_DWORD: SecurityLayer Value:

-> Here we have 2 defined

Change will remove secure RDP. What did you choose?

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp REG_DWORD: UserAuthentication Value:

-> Here we have defined Value 1

And you have choose 0?
Sign in to comment
Tomas Zadravec 41 Reputation points

2021-08-18T09:47:14.927+00:00
Hi,

This is how I have solved the problem:

Connect via RDC to a different account.

Then open Task Manager.

Navigate to users.

Locate the user account which has hanged i.e. you cannot connect to.

Right click on the user name and select reconnect.

Type in the password.

Get connected to the desired account.

That worked for me on WIN10 via Android RDC.
Please sign in to rate this answer.

8 people found this answer helpful.
Dennis Villa 0 Reputation points

2023-03-16T16:25:08.1466667+00:00

Thanks for providing this solution. It resolved my problem.

PrashantV 76 Reputation points

2023-03-17T09:21:55.13+00:00

This is not a solution but a work around. I think we all should raise this with Microsoft with highest priority. This is not done. Multiple organizations are suffering due to this and losing too much time.

James Wang 0 Reputation points

2023-06-18T15:07:27.5733333+00:00

Thank you. I used your method and reconnected to my remote login. Then I signed off. Next time I remote login using my account, the "Please wait" disappeared.
Sign in to comment
Eric 186 Reputation points

2021-07-14T14:39:32.813+00:00
Hello Leila MSFT,

I have found new information that could lead to a solution of the issue if RDP getting stuck at "Please Wait" after connecting. Please determine why this alternate app allows a normal connection, even when MS RDP app gets stuck at "Please Wait":

Recreate issue- using RDP to connect to the destination pc gets stuck at "Please Wait", usually after connecting through a VPN and then putting the client laptop in sleep by closing the loud and reopening later (makes destination pc RDP service get stuck)

On an Android phone, use "Microsoft Remote Desktop" app to connect, it also gets stuck at "Please Wait".

From Google Play store, install "aFree RDP" which is a 3rd party RDP app. Setup the connection with the exact same user/ lpassword you used on MS RDP and connect to the destination pc. You will notice that the aFreeRDP connects as "Other User"and then enters the user/password credentials in there, and then it connects to the pc successfully with the desktop being shown as normal. You can use the pc as you would.

That's it. At this point if you disconnect and try MS RDP it is still stuck at "Please Wait" since it doesn't appear to use the "Other User" method to log in. But if you connect back using aFreeRDP it uses "Other User" which enters the credentials there and logs in perfectly.

It seems when connecting to the session as "Other User" and entering the credentials there, the system creates a new session, whereas the official MS RDP is stuck using the old session which is somehow in an infinite loop wait state.

MS PLEASE FIX IT
Please sign in to rate this answer.

3 people found this answer helpful.

0 comments No comments
Sign in to comment
Jerad Ries 11 Reputation points

2021-11-19T18:21:20.72+00:00

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.
Please sign in to rate this answer.

2 people found this answer helpful.
Frenchy 1 Reputation point

2021-11-25T11:46:01.693+00:00

Exactly the same issue here !

Frenchy 1 Reputation point

2021-11-25T12:17:21.403+00:00

Exactly the same issue here !
Sign in to comment