RDP to Windows 10 hangs at Please wait screen

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.

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

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.

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?

I just experienced this issue for the first time and saw something odd not mentioned here. Someone called me about not being able to connect to their office desktop. They were getting the please wait screen. I logged in from one of my computers and saw exactly the same thing. Being ignorant of all this, I told him an update probably got stuck and someone would have to reboot his machine in the morning. This morning I logged into his computer from a different computer and all was fine. I called him and said it must have been an update taking a long time to install and all was fine. He tested and said, "no it still says please wait!" I remoted into his laptop and checked and sure enough he was right.

Some computers were getting the "please wait" screen and others were not. That is somewhat at odds with what is being said here, so I thought I would mention it. The difference between the two computers is the one not experiencing the issue is running Windows 11.