How to Fix the Remote Desktop in Licensing Protocol Error

Here we can see, “How to Fix the Remote Desktop in Licensing Protocol Error”

• System file issues are the root cause of the Remote Desktop connection protocol error.
• The problem should be rapidly resolved if the Remote Desktop program is run in administrator mode.
• The problem can also be fixed by accessing the app using the system administrator account.
• Consider downloading and using an additional remote control program from a third party.

Some customers who use the Remote Desktop Connection tool in Windows 10 may see the remote desktop in licensing protocol error.

The complete error message reads:

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.

Users are unable to use Remote Desktop Connection as a result. These are some solutions to the RDC error.

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

1. Run Remote Desktop as an Administrator

1. 1. Run as administrator by using the right-click menu to select Remote Desktop Connection. Type Remote Desktop Connection into the search box by pressing Windows Key + S.
   2. Now that you have administrator permissions, your Remove Desktop Connection should launch.

Some users have reported that the remote desktop mslicensing problem has been resolved by starting Remote Desktop Connection as an administrator.

Running RDC as the administrator guarantees that the program has the necessary rights to change the registry.

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

1. 1. Type cmd by pressing Windows Key + S.
   2. Run as administrator by choosing with the right-click menu on the Command Prompt.
   3. Enter after you enter the following command: Administrator for net users /active:yes
   4. To log in using the new admin account, restart Windows.

Run RDC alternatively using an admin account. With the Command Prompt, an integrated admin account can be activated.

These methods require cmd to be opened with administrator permissions in order to function, so read this helpful article to learn what to do if your cmd won’t open with admin rights.

3. Delete the MSLicensing Registry Key

1. 1. To reveal the window below, click the Create button.
   2. Press Windows Key + S and enter “Create restore point” to start.
   3. The Control Panel window will then appear once you click Create a restore point.
   4. To reveal the window below, click the Create button.
   5. Afterward, type a name for the system restore point in the text box and click Create.
   6. By pressing the Windows key + R hotkey, you can erase the MSLicensing key.
   7. The Registry Editor will then open once you type “Regedit” in the Run box and press “OK.”
   8. Next, launch the Registry Editor and select this key:

      • HKEY_LOCAL_MACHINESOFTWAREMicrosoftMSLicensing

   9. To remove the MSLicensing key, right-click it and choose Delete.
   10. Launch Remote Desktop Connection as an administrator after restarting your computer or laptop.

Additionally, users have verified that the RDC licensing protocol error is resolved by deleting the MSLicensing entry from the registry.

The Registry Editor allows you to delete that key, but you should first create a restore point so you can return to it if necessary.

4. Scan the Registry

Some registry cleaners may also help with the RDC licensing protocol error since damaged registry keys may be the cause.

There are many third-party registry applications available, most of which will automatically detect corrupted or damaged files and replace them with brand-new versions.

5. Roll Windows Back to a Restore Point

1. 1. By hitting the Windows key + R keyboard shortcut, typing rstrui in Run, and selecting OK, you may access System Restore.
   2. To view a list of restoration points, click Next.
   3. To completely expand the list of restore points, use the Show more restore points option.
   4. Choose a restore point that will take Windows back to a time when the licensing protocol error for remote desktop wasn’t present.
   5. To confirm the restoration point, click the Next option and then choose Finish.

Using System Restore to restore Windows to a previous time has also resolved the RDC licensing protocol problem for some customers.

Conclusion

I hope you found this guide useful. If you’ve got any questions or comments, don’t hesitate to use the shape below.

User Questions

1. How do I modify the license server for Remote Desktop?

Click Start, select Administrative Tools, select Remote Desktop Services, and then select Remote Desktop Licensing Manager to launch it. Click Properties from the context menu when you right-click the license server whose settings you want to modify.

2. How do I find my RDS licensing server?

You can check for open ports using the PortQry tool or the Test-NetConnection cmdlet. Try to check the RD License Server status and the number of the issued licenses using the Remote Desktop Licensing Diagnoser tool ( lsdiag. msc or Administrative Tools -> Remote Desktop Services -> RD Licensing Diagnoser).

3. How can I tell if my RDS is authorized?

Hi, Please launch RD Licensing Manager to check your license details (licmgr.exe). If you don’t have an RD Licensing server, you’ll need to utilize Server Manager to install the RD Licensing Role Service before activating it and installing your RDS CALs.

4. RDP protocol error only for specific users : r/sysadmin – Reddit

RDP protocol error only for specific users from sysadmin

5. Terminal Services, user cannot login to remote profile : r … – Reddit

Terminal Services, user cannot login to remote profile from sysadmin