How to fix the Remote Desktop in licensing protocol error

by Matthew Adams
Matthew Adams
Matthew Adams
Windows & Software Expert
Matthew is a freelancer who has produced a variety of articles on various topics related to technology. His main focus is the Windows OS and all the things... read more
Affiliate Disclosure
  • The Remote Desktop connection protocol error happens due to system file problems.
  • Running the Remote Desktop app as an administrator should quickly fix the issue.
  • Using the system's administrator account to access the app will also get rid of the error.
  • Try installing and using a third-party remote control tool that has more features.
fix remote desktop error

To fix various PC problems, we recommend Restoro PC Repair Tool:
This software will repair common computer errors, protect you from file loss, malware, hardware failure and optimize your PC for maximum performance. Fix PC issues and remove viruses now in 3 easy steps:

  1. Download Restoro PC Repair Tool that comes with Patented Technologies (patent available here).
  2. Click Start Scan to find Windows issues that could be causing PC problems.
  3. Click Repair All to fix issues affecting your computer's security and performance
  • Restoro has been downloaded by 0 readers this month.

The remote desktop in licensing protocol error is one that occasionally pops up for some users who utilize the Remote Desktop Connection tool in Windows 10.

The full error message states:

The remote computer disconnected the session because of an error in the licensing protocol. Please try connecting to the remote computer again or contact your server administrator. 

Consequently, users can’t connect with Remote Desktop Connection. These are a few fixes for that RDC error.

How can I fix Remote Desktop protocol errors on Windows 10?

  1. Run Remote Desktop as an Administrator
  2. Run Remote Desktop in the built-in admin Account
  3. Delete the MSLicensing Registry Key
  4. Scan the Registry
  5. Roll Windows Back to a Restore Point

1. Run Remote Desktop as an Administrator

  1. Press the Windows Key + S and type in Remote Desktop Connection.
  2. Right-click on the Remote Desktop Connection and select Run as administrator.
  3. Now your Remove Desktop Connection should open with administrator rights.

Some users have confirmed they’ve fixed the remote desktop mslicensing issue by running Remote Desktop Connection as an administrator.

Running RDC as administrator ensures that the app has the required permissions to modify the registry.

2. Run Remote Desktop in the built-in admin account

  1. Press the Windows Key + S and type cmd.
  2. Right-click on the Command Prompt and select Run as administrator.
  3. Type in the following command and press Enter: net user administrator /active:yes
  4. Restart your Windows to log in with the new admin account.

Alternatively, try running RDC within an admin account. You can activate a built-in admin account with the Command Prompt.

Opening cmd with administrator rights is mandatory for these solutions to work, so check out this useful article that will teach you what to do if your cmd won’t open with admin rights.

3. Delete the MSLicensing Registry Key

  1. Click the Create button to open the window below.
  2. ess the Windows Key + S and type in Create restore point.
  3. Then click Create a restore point to open the Control Panel window below.
  4. Click the Create button to open the window below.
  5. Then enter a title for the system restore point in the text box, and press the Create button.
  6. To delete the MSLicensing key, press the Windows key + R hotkey.
  7. Then you can enter Regedit in Run and click OK to open the Registry Editor.
  8. Next, open this key in the Registry Editor: HKEY_LOCAL_MACHINESOFTWAREMicrosoftMSLicensing
  9. Right-click the MSLicensing key and select Delete to erase it.
  10. Restart your desktop or laptop, and run Remote Desktop Connection as an administrator.

Users have also confirmed that deleting the MSLicensing key in the registry fixes the RDC licensing protocol error.

Expert tip:


Some PC issues are hard to tackle, especially when it comes to corrupted repositories or missing Windows files. If you are having troubles fixing an error, your system may be partially broken.
We recommend installing Restoro, a tool that will scan your machine and identify what the fault is.
Click here to download and start repairing.

You can delete that key with the Registry Editor, but you should set up a restore point first that you can go back to if required.

4. Scan the Registry

As the RDC licensing protocol error can be due to corrupted registry keys, some registry cleaners might also resolve the issue.

There are plenty of third-party registry utilities to choose from, and most of them will automatically find damaged or corrupted files, then replace them with pristine ones.

Get CCleaner

5. Roll Windows Back to a Restore Point

  1. You can open System Restore by pressing the Windows key + R keyboard shortcut, entering rstrui in Run and clicking OK.
  2. Click Next to open a list of restore points.
  3. Select the Show more restore points option to fully expand the list of restore points.
  4. Select a restore point that will restore Windows to a date when the remote desktop in licensing protocol error wasn’t popping up.
  5. Then click the Next button and select Finish to confirm the restore point.

Rolling Windows back to a previous date with System Restore has also fixed the RDC licensing protocol issue for some users.

System Restore might fix the error as restoring Windows to a system restore point can fix corrupted registry keys. You can find more information about creating a system restore point in this detailed article.

If any of the solutions above don’t work in your case, you can also try using Mikogo. It’s a valid alternative that works well across all platforms and has additional features like multi-monitor, profile manager and file transfer. Or you can go for some other amazing remote software options as you prefer.

Those are resolutions that have fixed the RDC licensing protocol error for some users. We hope this guide provided all the information you needed to fix your problem.

This article covers:Topics: