Remote Desktop stuck on please wait Windows 10

Hi,
Could you please help to confirm bit more details for us to better understand your problem?

1.What is the exact message prompted when "please wait issue" occurred? Were the problematic users finally logged in?

2.At the same time another user can login without any issues in same PC.
Did you mean that the issue only occurred some users while some other users will not experiencing the same issue?

3.Were the problematic users are belong to the same user group?
If so, kindly check the group policy assigned to this group and comparing with other working user groups.

Looking forward to your reply.

If the Answer is helpful, please click Accept Answer and upvote it.

Thanks,
Jenny

1. User getting stuck on remote desktop session with "please wait screen". Attached image
   

2. Issue occurred recently in all machine , not specific user group or OU
   

3. Issue only in RDP, other tools like VNC is working without issues
   

4. While observing few machines, MS patches were installed and few of them were upgraded to latest build 21h2

   
   

Hi,

Sorry for late reply. I had an internal discussion and searched for a while to get more information.

1.Will domain administrators experienced the same hang issue when remoted to the server?

2.when issue occurred, please login to the server (either remotely or in console) to verify if any suspended sessions by checking task manager.

If so, workaround shared in below thread might be the reference for you to check.
https://docs.microsoft.com/en-us/answers/questions/451406/rdp-to-windows-10-hangs-at-please-wait-screen.html

3.Please also check both client and server side to verify if any details have been recorded in the event logs.
TerminalServices-RemoteConnectionManager and TerminalServices-LocalSessionManager logs to view information about connections.

Step 1: Press Windows+R to open the Run dialog, enter eventvwr (or eventvwr.msc) and hit OK.

Step 2: Navigate to Event Viewer\ Applications and Services Logs\ Microsoft\ Windows\ TerminalServices-*

If the Answer is helpful, please click Accept Answer and upvote it.

Thanks,
Jenny

Hi everyone
I have fixed this problem after I restart the computer which I want to remote lol.
Hope it would be helpful for you

Hi,

We have also started to experience this issue at a customer site who RDP to virtual Windows 10 machines (VDI) from their laptops that have remote access software. The issue only started after upgrading from 1909 to 20H2.

Currently the only "work arounds" are to reboot the machine or log in as an Admin via RDP to disconnect the problematic session, neither of which are fixes. Alternative accounts can RDP fine to the machine whilst the primary user experiences the "Please Wait" issue (tested from different machines).

I notice in the event viewer logs there are a lot of disconnect and reconnection messages (Event ID 40 code 0 and 5). Just waiting for further information from the customer as the disconnects do not correlate with what they are telling me is happening.

This is definately an OS issue though and Microsoft need to look at this.

My Remote Desktop stuck on please wait in Windows 10

“I used RDP to remote access my work computer (both Win 10) on my home computer, but it stucks on please wait screen on my Windows10 for days (I thought it would fix itself). Any suggestions for Remote Desktop Please wait blue screen?”

RDP (Microsoft Remote Desktop), a Windows built-in feature that allows you to remotely access a  PC from another PC, brings about super convenience to people. However, it’s frustrated for every user to meet with "RDP to Windows 10 hangs at please wait screen" when they remote into another computer over the Internet. And according to the feedback of many users, they found it’s useless even though they reboot the PC. So, in the next part, I‘ll talk about the solutions to fix the issue.

How do "I" fix RDP please wait in Windows 10?

If you have met “stuck on please please wait screen using Microsoft Remote Desktop” problem, what you can do? Here we provides 5 solutions to help you get out of the trouble.

Solution 1. Update to the latest version on the client PC

Actually, the issue can be fixed by running the command and checking the update. Now let's act the operations together.

Step 1. Press Win + I to open Settings and then find Update and Security.

Step 2. Check for updates, download, and install. Finally, Reboot the PC.

After that, this solution can effectively solve “Remote Desktop stuck on login screen”.

Solution 2. Run Windows Powershell

Step 1. Search Powershell in the search box and then right-click, select Run as administrator.

Step 2. Type the following command and after the completion, check if the issue persists.

Command Line:

$ID=query session /SERVER:WSMC027|select -skip 1|%{$_.Split(' ',[System.StringSplitOptions]::RemoveEmptyEntries)}

Disconnect-RDUser -HostServer WSMC027 -UnifiedSessionID $ID[8] -Force

exit 0

Solution 3. Run CMD to kill the program

Sometimes if the user leaves the connection and puts the PC to sleep, then the Remote Desktop will stuck on please wait. The better way for this is to kill the process and then restart the program.

Step 1. Search cmd in the search box and then right-click, select Run as administrator.

Step 2. Type taskkill /f /im msrdc.exe and press Enter key.

Step 3. Reboot the PC and check if the issue has been solved or not.

Solution 4. Perform clean boot

Clean Boot starts Windows with a minimal set of drivers and startup programs so you can figure out if a background program is interfering with the running program.

Step 1. Search System Configuration in the search box and then open it.

Step 2. Locate “Services” and then click on “Hide all Microsoft services”.

Step 3. Check all the services on the list and click on OK.

Step 4. Select Restart.

Step 5. Then the clean boot is successful after restarting.

Solution 5. Reconnect to the object user

If the object user in the connection process is not connected at the same time or something is wrong with the process of connecting, the RDP issue will also appear. Therefore, reconnecting can be a shot worthy to try.

Step 1. Connect via RDC to a different account.

Step 2. Send the "Ctrl + ALT + Del" command to the remote computer and then click on Task Manager.

Step 3. Navigate to users. Locate the user account which has hung and you cannot connect to. Right-click on the user name and select "Connect".

Step 4. Type in the password to connect to the desired account.

Looking for a free alternative to RDP? Try AnyViewer!

After trying the ways mentioned above, the issue “Remote Desktop stuck on please wait on Windows 10” may have been solved. But if it’s not, don’t worry. Actually, it’s completely not strange to run into the problems and errors in RDP, like RDP takes long time to connect, RDP fullscreen not working, and so on. At this time, you may want to ask, “is there any alternative to RDP?” Absolutely! That’s AnyViewer.

AnyViewer is free software that is devoted to remote access, remote control anywhere and anytime, the rapid connection, flexible connecting methods, and easy operation of AnyViewer will give you a big surprise. There’s no need to find the IP address and user name of the remote PC. And it supports Windows 11/10/8.1/8/7 and Windows Server 2022/2019/2016/2012 R2. In the next part, the instructions will be listed for you.

Before connections:

• Make sure the network is accessible.
• Download and install AnyViewer by clicking the download button.

Step 1. Install AnyViewer and then open it. Go to the “Log in” tab, and click on “Sign up”.

Step 2. Fill in the information to sign up.

Step 3. Now you can see your interface as the following picture. And your device will automatically be assigned to the account you’ve logged in to.

Step 4. If you log the same account on another device, there will be 2 devices in the “My devices” tab. Click the PC that you need to control and click "Remote control" to achieve unattended access with one-click. 

Note: If you  want to control the remote  PC  without logging your AnyViewer account, you can follow these steps:

Step 1. Open AnyViewer on both two computers and then locate the Settings and the device ID.

Step 2. Click on Settings on the host computer, and then select Recipient, choose the third option “Set my security code”, input the security code and then click on OK. Return to the main interface.

Step 3. On the client PC, enter the device ID of the host PC in the partner ID box. Click on “Connect”.

Step 4. A pop-up window appears, tick the second option “Input security code” and input the security code, click on “OK”.

Step 5. Now the connection is completed.

Note: Isn’t it easier than RDP? Another easy way is “Send a control request”, which is for the attended access.

Conclusion

5 ways demonstrated above to fix "Remote Desktop stuck on please wait" on Windows 10 are shown for you. If you’re disappointed to find that the solutions don’t work for you or you need to have an RDP session immediately, just try a free alternative to RDP, AnyViewer, which can truly realize your remote access without effort.  

How do you fix stuck on please wait?

How do I force a remote desktop restart?

How do I close a frozen program in remote desktop?

How do I fix a stuck Windows 10 Welcome screen?