Windows 10: RDP first login after restart

Greetings, I have a home server and manage it via RDP. Sadly, this technology is pretty non-stable and every time I restart the server, I get an error when I try to log in to my server. It says, that "The number of connections to this computer is limited and all connections are in use right now. Try connecting later or contact your system administrator.". I searched web for a couple of times on this subject and found out that there's a key in registry that sets how many connections can be open simultaneously. I followed that guide and set the value to 10. However, that didn't solve my problem. The important part is that it fails with that error only on first login after restart for each user. I have two users there, and for each of them I have to login on the server itself first, then I can connect via RDP. Is there something that could be done in order to get rid of that annoying problem? Because every power outage now tooks nearly an hour to bring that server up for RDP.

:)

 

Can't login to new computer w/Windows 10

Hi,

Thank you for your reply.

• 
  Are you able to login to Microsoft Account on Web?
  
• 
  Have you installed any language pack?
  

I suggest you to follow the steps below and check if it helps.

Step 1: I suggest you to select the appropriate language in login screen at the bottom right corner and check if it helps.

Steps 2: Use On-screen keyboard in the login screen to login and check if it helps.

Hope this helps. If the issue remains unresolved, please get back to us and we would be happy to help.

 

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
  
  

 

RDP Will no longer login to Windows 7 VM

I have a Windows 7 VM running an old application, because the application will not run on Windows 10. I have been RDP into it for months, and now it is giving me this error:

"Your password may have expired or the remote PC might not accept blank passwords"

Here's my environment:

Windows 2008r2 DC

Windows 7 & 10 Pro PC's

VM is on Win10 Pro PC, Workgroup

Like I said, worked a month ago.

I attempted to RDP from Win7 Pro PC and received the same message. But the old RDP gives you more information, and I saw that I was trying to login with a domain user, instead of a local user. Changed the login to login as a local user and it connected right
away.

I then tried to change the login on the Win10 PC to a local login and it still gives me the same error. Is the format of local login (Machinename\Username) different on the new RDP?

Any help would be greatly appreciated.