Fix: Remote Session was Disconnected

because there are no Remote Desktop License Servers available to provide a license

Windows 10, like the older versions, provides users with Remote Desktop Protocol (RDP) feature through which users can connect from one system to other Windows devices. However, there have been several reports where users aren’t able to form a connection. Whenever they try to establish a connection, they are prompted with the ‘Remote session was disconnected because there are no Remote Desktop License Servers available to provide a license.’ error.

Remote Sessions was Disconnected

This error can be easily resolved by modifying one or two entries in the Windows registry. If you have been encountering the said error, this article will show you how to isolate it in no time. But before that, let us give the possible causes of the error a read.

What causes the ‘Remote Session was Disconnected’ Error on Windows 10?

Well, from what we have salvaged, this error is most of the time due to the following factor —

  • TS not able to locate the license server. The major cause of the error would be the Terminal Server (TS). When this server is not able to locate the license server in the system, you will receive the said error message.

To circumvent the issue, you can follow the solutions given below. Please make sure to follow the instructions carefully as Windows Registry can cause critical issues to rise.

Solution 1: Deleting the MSLicensing Key

The reason due to which the Terminal Server (TS) is not able to locate the license server can potentially be due to this specific key. Therefore, you will have to delete the key and then try using RDP. Here’s how to do it:

  1. Press Windows Key + R to open Run.
  2. Type in ‘gpedit’ and then press Enter.
  3. Once the Windows Registry opens, navigate to the following path:
  4. Afterward, locate the MSLicensing key.
  5. Expand the key, right-click the ‘Store’ key and click Delete.
    Deleting Store Key in the Windows Registry
  6. Once prompted, select Yes.
  7. Check if the issue still persists.

Solution 2: Deleting the GracePeriod Key

You can also fix your issue by removing the GracePeriod key in the Windows Registry which, at times, can be the cause of the pop up. You can apply this solution if you are using Windows Server 2012 or later. Here’s how to do it:

  1. Open up the Windows Registry as shown in solution 1.
  2. In the Windows Registry, navigate to the following path:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM
  3. In the RCM key, locate the GracePeriod key and right-click on it.
  4. Select Delete to remove the key. In some cases, you might have to take permissions over the key in order to remove it.
    Deleting GracePeriod Key
  5. To take permissions over the key, just right-click GracePeriod and select Permissions.
    Changing Permissions of the GracePeriod Key
  6. Then select your User Account and check the ‘Full Control’ and ‘Read’ boxes.
  7. Click Apply and then hit OK.

Solution 3: Run RDP as an Administrator

In some cases, the error can be merely due to insufficient permissions of the Remote Desktop Connection application. Therefore, to eliminate such a possibility, you’ll have to run the app as an administrator. If it fixes the issue, make sure to run the application always. Here’s how to do it:

  1. Go to the Start Menu, type in ‘Remote Desktop Connection’. Right-click on it and select ‘Run as an administrator’.
  2. Try connecting to see if it fixes the issue.

You can also use Run to run RDP as an administrator. Here’s how to do it:

  1. Press Windows Key + R to open Run.
  2. Type in the following command and press Enter:
mstsc /admin
Running RDP As An Admin Using Run

Solution 4: Restart Remote Desktop Services

Finally, if the above solutions do not work out for you, you can resolve the issue by restarting the ‘Remote Desktop Services’ service. Here’s how to do it:

  1. Go to the Start Menu, type in Services and open it up.
  2. From the list, locate the ‘Remote Desktop Services’ service.
  3. Right-click on it and click ‘Restart’.
    Restarting Remote Desktop Services Service
  4. Try connecting again.

Kevin Arrows

Kevin Arrows is a highly experienced and knowledgeable technology specialist with over a decade of industry experience. He holds a Microsoft Certified Technology Specialist (MCTS) certification and has a deep passion for staying up-to-date on the latest tech developments. Kevin has written extensively on a wide range of tech-related topics, showcasing his expertise and knowledge in areas such as software development, cybersecurity, and cloud computing. His contributions to the tech field have been widely recognized and respected by his peers, and he is highly regarded for his ability to explain complex technical concepts in a clear and concise manner.