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 — 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:
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:
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: You can also use Run to run RDP as an administrator. Here’s how to do it:
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:
How to Fix RUST EAC Disconnected ErrorHow to Fix the ‘Disconnected by VAC: You Cannot Play on Secure Servers’ Error on…Fix: Mapped Drive is Disconnected After RebootHow to Fix “You have been disconnected” Error in Halo Infinite?
