Since the morning of May 27 (Sat), 2017, several users have reported on the phenomenon of this question for the connection with “Remote Desktop Connection” of Windows.
As informal information, it seems that connection might become possible when you do the following measures. However, since this is not an official method and includes registry operations, please do it at your own risk after taking a backup in the following way.
How to backup the registry
Create a system restore point, or backup the registry as follows.
- Press R while holding down the Windows key on the keyboard. Launch the Registry Editor by entering “regedit” in the “Run” box.
- Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing, right-click on [MSLicensing], and click on [Export].
- Save it with an arbitrary name.
- When you need to restore later, launch the Registry Editor, click on [File] > [Import], and select the backup file you saved above.
- Launch the Registry Editor by entering “regedit” in the “Run” box.
- Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing\HardwareID, and delete “ClientHWID” (right-click on it and “Delete”).
- Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing\Store\LICENSExxx. The last three digits of LICENSExxx are numbers, and there may be two or more in consecutive numbers. Among them delete “LICENSExxx” whose “ProductID” value in it is “41 00 30 00 32 00 00 00”.
- Try to connect again. If you get a message saying “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.” then an error that you cannot write to the registry may have occurred. In that case, you can write to the registry by once executing the Remote Desktop Connection “as administrator” from the right-click menu, and after that you can connect as usual.