Share this article
Improve this guide
How to Fix the Remote Desktop in Licensing Protocol Error
System file issues can cause the Remote Desktop error
4 min. read
Updated onMarch 27, 2024
updated onMarch 27, 2024
Share this article
Improve this guide
Read our disclosure page to find out how can you help Windows Report sustain the editorial teamRead more
Key notes
The remote desktop 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:
Theremote computerdisconnected the session because of anerrorin the licensing protocol. Please try connecting to theremote computeragain 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
Some users have confirmed they’ve fixed the remote desktop licensing 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. Scan the Registry with a Specialized Repair Software
As the RDC licensing protocol error can be due to corrupted registry keys, some registry cleaners might also resolve the issue.
There are plenty ofthird-party registry utilitiesto choose from, and most of them will automatically find damaged or corrupted files, and then replace them with pristine ones.
A professional cleaning tool is capable of repairing broken registry entries and optimizing your system by erasing junk files.
With these repair tools, you will eliminate the clutter from your PC caused by unused files, outdated drivers, or duplicate files on your PC.
Hence, you can benefit from a detailed registry scan showing all your damaged registry keys. Then, you can fix them automatically in a few clicks.
3. Run Remote Desktop in the built-in 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 you shouldrun Command Promptwith admin rights accordingly.
4. Delete the MSLicensing Registry Key
Users have also confirmed that deleting the MSLicensing key in the registry fixes the RDC licensing protocol error.
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.
5. Roll Windows Back to a 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 theerroras restoring Windows to a system restore point can fix corrupted registry keys. You can find more information about creating a system restore point in thisdetailed article.
If any of the solutions above don’t work in your case, you can also try usingMikogo. 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 amazingremote software optionsas 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.
More about the topics:Remote Desktop Connection
Matthew Adams
Windows Hardware 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 surrounding it.
He is passionate about the tech world, always staying up-to-date with the latest and greatest. With an analytical view, he likes problem-solving, focusing on errors and their causes.
In his free time, he likes to read and write about history and tries to always develop new skills.
User forum
0 messages
Sort by:LatestOldestMost Votes
Comment*
Name*
Email*
Commenting as.Not you?
Save information for future comments
Comment
Δ
Matthew Adams
Windows Hardware Expert
He is passionate about everything surrounding Microsoft’s OS, focusing on troubleshooting guides & tips for everyday problems.
