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 Server Remote and virtual desktops 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. To protect privacy, user profiles for migrated questions are anonymized.

0 comments No comments
{count} votes
Accepted answer
  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.

    74 people found this answer helpful.
    0 comments No comments

27 additional answers

Sort by: Most helpful
  1. Anonymous
    2016-12-20T21:15:24+00:00

    Setting the rdp to run as administrator through task manager seems to be holding steady for my need.

    0 comments No comments
  2. Anonymous
    2017-01-18T23:46:58+00:00

    Hi. 

    I checked on the Store folder and found 3 entries saved. 

    If I delete the entries will it affect anything else. 

    I could not get any info on the entries(such as what it is for, date created or modified.)

    Any info will greatly appreciated.

    0 comments No comments
  3. Anonymous
    2017-02-13T14:59:58+00:00

    I can delete the registry and it works...only one time. The next time I try to log in, I get the same error and I need to delete the key again. Any suggestions?  I have this issue on two computers.

    L Trainer, any luck solving the recurring problem?  I too can get it to work one time by deleting the key, but it reappears the next time I try to log in.  Thanks!

    0 comments No comments
  4. Anonymous
    2017-03-06T20:38:56+00:00

    Hopefully there will be an "Official" fix for this terrible issue. I am under the impression that MS understands the need for a reliable RDP program. It's not as strange or uncommon for folks to work remotely these days away from the head office.

    Then again this may be something MS is cracking down on to prevent unwanted use of their software?? 

    Are there any aftermarket RDP programs that can be installed as a workaround to this issue??

    Thanks much

    0 comments No comments