Link to home
Start Free TrialLog in
Avatar of manav08
manav08Flag for Australia

asked on

RDP to Windows 10 hangs at Please wait screen. Whats the permanent solution to this. It started happening a month back (Dec 2021)

When I try to RDP to Windows 10 Pro machine it hangs at the "Please wait" screen for a user. The only way to fix it is to restart the remote machine and then try to remote in again. But the issue happens again. 

Another working solution that didn't require a reboot was to RDP using an admin account, go to task manager>users, and then right-click on the previous user and select connect. Enter the password and your session will change to the previous user.

Avatar of arnold
Flag of United States of America image

Please wait dealing with another user being logged in?

RDP is an administrative feature for win10

The user has to be a member of the Remote Desktop users.

Gave you considered using an RDS server os?
Avatar of manav08


@arnold The workstation where user is trying to remote in is dedicated for the user itself. no one else has access to that machine other than administrators and that user. Also no one is logged in to that machine when user is trying to remote in. There seems to be a lot of discussion on the same issue, but none of them have provided a solution yet.
Is the user logged in at the time of the attemp? user profile/redirected folders, FSLOGIX?
as a possible explanation what the system is doing on login.
Chances it may be due to userprofile corruption. please try with some other account or administrator and see how it behaves. If other account works, you can try to recreate the user profile.

Often these issus are due to Roaming profile , folder redirection, network issues,, Do you see any errors related to profile load in the  event logs
1st of all, see if it happens for all user profiles or just for one in order to determine if it's a profile problem or not. If not, do an in-place upgrade for repairs.
Avatar of manav08
Flag of Australia image

Link to home
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
"Since nothing else work..." - So you did try the inplace-upgrade?
We are also facing the same issue but there is no solution to this. We even tried Windows10 upgrade to recent build but no luck. today only I saw a post where someone reported that the issue exists even after upgrading to Windows11.