Share via

Remote desktop error

Anonymous
2010-02-10T16:54:05+00:00

I am receiving the error "the remote session was disconnected because the remote desktop client access license stored on this computer has been modified" when trying to connect to a server 2003 machine.  I am running Windows 7 but have no trouble connecting to two other server 2003 machines or XP.  It seems to be some type of conflict with this specific machine and Windows 7.  I can connect to this server from an XP machine.

Windows for business | Windows Server | User experience | Remote desktop clients

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
  1. Anonymous
    2010-02-11T15:40:39+00:00

    Hi Russ,

    First, I would suggest you to create a System Restore Point manually, so that in case, something goes wrong while performing these steps, you may always perform a System Restore and revert back.

    Normally we receive this error message if the TS license in the computer is damaged or corrupt, you may need to remove it from the TS client. The license is stored in the client's registry.

    1.  Click on Start

    2.  In the start search box type REGEDIT and press enter.

    1. In the registry editor access the following key:  HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing.

    To clean the client's license cache, just delete this key and its sub keys. The next time the client connects to the server, it will obtain another license.

    Registry Disclaimer:

    Sometimes this problem is caused by two Windows registry entries that have become corrupted. To fix the problem, you have to use Registry Editor to delete the corrupted Registry entries.

    However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs.

    For more information about how to back up and restore the registry, follow the steps as in the KB Article: http://support.microsoft.com/kb/322756/

    Hope this helps. Let us know the results.

    Thanks and Regards,

    **Srinivas R Microsoft Support.**Visit our Microsoft Answers Feedback Forum and let us know what you think.

    70+ people found this answer helpful.
    0 comments

27 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2016-09-17T21:49:44+00:00

    I was receiving this same error on a Windows 10 laptop (Enterprise x64 ver 1607). I followed the steps above with deleting the entire MSLicensing key and subkeys that didn't work. I had exported the key before deleting so I reimported. I checked a clean Win 10 install on another machine (which had not connected to a Win Terminal Server before) and noticed that it had the MSLicensing key, along with the HardwareId and Store subkeys. However the Store subkey was empty. Do I deleted any values UNDERNEATH 'Store' (e.g. LICENSE000) and was able to connect. Hope this helps.

    The path i think that was meant is:

    1.  Click on Start 

    2.  In the start search box type REGEDIT and press enter.

    1. In the registry editor access the following key: HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing\Store

    then delete what you find in the "Store" folder.

    300+ people found this answer helpful.
    0 comments
  2. Anonymous
    2016-09-16T13:17:50+00:00

    I was receiving this same error on a Windows 10 laptop (Enterprise x64 ver 1607). I followed the steps above with deleting the entire MSLicensing key and subkeys that didn't work. I had exported the key before deleting so I reimported. I checked a clean Win 10 install on another machine (which had not connected to a Win Terminal Server before) and noticed that it had the MSLicensing key, along with the HardwareId and Store subkeys. However the Store subkey was empty. Do I deleted any values UNDERNEATH 'Store' (e.g. LICENSE000) and was able to connect. Hope this helps.

    9 people found this answer helpful.
    0 comments
  3. Anonymous
    2017-03-15T11:26:35+00:00

    Hi guys I found a fix for this which was a combination of fixes to solve this.

    In Regedit go to the key below and delete it (whole thing not just the subkeys:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing\

    Recreate the empty key "MSLicensing" at:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\

    Run mstsc.exe as administrator privileges and then log in to your remote gateway using an Admin account (not the user you want  to fix) < This part is critical

    Check in regedit that they HardwareID and Store subkeys have been recreated at:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing\

    Then log in as normal without administrator privileges using mstsc as the user you want to fix and the connection should be repaired and you will not have to continually delete the subkeys to fix anymore

    Took me a few hours of trying all the fixes. You need them all in this order or the problem will just keep coming back (or you will get errors about elevation, Bad Gateway errors etc.

    Hope this helps someone!

    8 people found this answer helpful.
    0 comments
  4. Anonymous
    2016-10-07T03:48:02+00:00

    You just deleted a registry key. To create another, you need admin privileges. Just run remote desktop next time you open as 'administrator'  to create the licenses again.

    6 people found this answer helpful.
    0 comments