RDP to Windows 10 hangs at Please wait screen

kiran kumar 56

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|| || ((=;; ||_|| ||£ ||_ 21 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 65 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
Alexander Oliva 0 Reputation points

2024-09-04T02:58:29.46+00:00

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

34 answers

Deleted

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

Comments have been turned off. Learn more
Deleted

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

Comments have been turned off. Learn more
RS Cosmetics 0 Reputation points

2023-08-12T19:27:29.8566667+00:00

I am facing the same issue when I connect from my PC that is on connected network ie main system/server connected to another connected router there all the pc/laptops connected to that router able to connect without “please wait” issue ,but my this PC is on connected router most of the time it gets stuck on “Please Wait”.

On this router when I connect via my laptop which is from my another organization’s ,it has an option to connect entering Windows Hello Pin (6 digit pin which I use to login into my laptop everytime I start it or unlock it) after entering pin it takes me to start screen of server where there are Users listed I can select the user an enter password for it and am successfully able to login, seems issue is with RDP client on my Pc??
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
SPH 65 Reputation points

2024-03-13T00:10:55.9833333+00:00
I am occasionally having still having this issue in my office where i cannot do some of the things posted here. Seems to happen most often after an update.

One of the techs recommended i add the following to my registry

Regedit.

Locate and then click the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System

On the Edit menu, point to New, and then click DWORD Value.

Type verbosestatus, and then press ENTER.

Double-click the new key that you created, type 1 in the Value data box, and then click OK.

Quit Registry Editor.

After reboot the messages from Windows provides a little more clarity. The Please Wait condition was now reported as "Please Wait for Group Policy Services"

What i found was GP was being shutdown and not restarted. Because i do not have total control, i could not change from Automatic (Triggered) to Automatic so I am still at the whim of this not automatically restarting when i return to the desktop, but perhaps this will help some of you and maybe even MS to figure out what they haven't got quite right.
Please sign in to rate this answer.
Dietrich, Max 5 Reputation points

2024-04-08T11:49:12.4466667+00:00

Anybody a solution for this problem? We have also 200 virtual desktops with windows 11 and everyday another user with the problem...
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

RDP to Windows 10 hangs at Please wait screen

34 answers

Your answer