Windows 10: RDP / "Please Wait"

I have a Dell Desktop running Windows 10 and both a HP Windows 10 laptop and a Macbook Air. I run RDP from each of the laptops, more frequently from the MAC. I use the Microsoft RDP client for MAC and the standard Windows RDP client on the HP. If I just access the Dell from the MAC, no problems; same if I do the same from the HP. But after using RDP from the HP, and then trying to use RDP from the MAC, after the client is configured, I get a big blue screen with "Please Wait" on the screen. The only thing that will solve this issue is a reboot of the Dell.Obv

:)

 

concurrent RDP

Hi Sundeep,

To better assist you, we would like to ask the following questions:

• Is Remote Desktop Protocol (RDP) working before the installation of Creators Update?
• Have you encountered any error messages?

We will wait for your response.

 

RDP

Hi Nikki,

We can see here that you are having issues using (RDP) Remote Desktop Protocol on your computer. There are several reasons why you are experiencing this concern. To set your expectation, we will be doing some troubleshooting steps to isolate
this problem. Before we proceed, may we know the following:

• Any changes made on the computer prior to this concern?
• What troubleshooting steps have you tried so far?
• Is this the first time that you encountered this problem?
• When did you notice about this issue?
• Can you send us a screenshot with the error message that you are getting? Note: Please do not include any personal information.

 

RDP

• Any changes made on the computer prior to this concern?
  
  Initially when we received the problem there wasn't any changes made on the computer since we couldn't figure out the problem, we upgraded the pc to windows 10. It fixed the problem momentarily and then it starts again. Then we re initiated the upgrade the
  same day I wrote this post and it was fixed again and then on today the issue is back

• What troubleshooting steps have you tried so far?
  
  In the past we would delete the MS Licensing Protocol folder as suggested by so many other posts and restart the RDP connection ad administrator to rebuild it. This time around it didn't fix anything. Like I said previously we've tried to upgrade the PC and
  the fix is temporal

• Is this the first time that you encountered this problem? No

• When did you notice about this issue? I'm not sure when it started because I haven't been on this project that long but I would say within the last month based on me. Based on other conversations this has happened in the past.

• Can you send us a screenshot with the error message that you are getting? Note: Please do not include any personal information.
  
  Sure