Most of the time a developer or tester spends his/her precious time in either cleaning the setup or preparing the setup for testing (Unit testing, white or black box testing). Sometimes testing for intermediate development changes in your setup might end up screwing your system. This requires uninstalling and cleaning the product traces responsible for the mess. Same holds true even for NSL, which needs uninstallation, but sometimes it becomes very difficult to uninstall, as installation would have not completed and some error is encountered.

This article describes how to uninstall and clean up NSL from the machine where a decent uninstallation from Add/Remove Programs or directly from the install package does not work.

Initially try uninstalling from Add/remove programs or by double clicking the NSL msi. If these fail then try the following steps to uninstall and remove NSL from the workstation.


  1. Goto Run -> execute the command:
    MsiExec.exe /I{PC}

    (Please refer to the table for value of PC depending on the NSL release you have installed)

  2. Type regedit and delete the following entries:

    (Please refer to the table for value of PC,PCR and UPCR depending on the NSL release you have installed)

  3. In case you have installed NSL in LDAP Gina mode, you will have to delete:
    HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WinLogon -> GinaDLL value.
  4. In case you have installed NSL in LDAP credential provider mode, you will have to delete:
    HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Authentication\Credential Providers\{83C8014C-D31E-4551-A88C-CDA35A329F2A} 


    HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Authentication\Credential Provider Filters\{4C9DA06C-41F9-4831-BEE6-BF357679680C}"

    Use this table for appropriate PC and PCR and UPCR depending on the NSL version installed on your machine.

    UPCR – 56AB6C41A76FFE541ADF88C21F4A37B5

    (common for all)

  5. To ensure further cleanup, we can also remove the SecureLogin folder. To get the path of SecureLogin Folder. Run regedit and goto
    HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\slproto.exe -> Path value

    This gives the installation folder. Delete this folder for more cleanup.

    This cleanup ensures that NSL can be freshly installed on the workstation. After performing these steps, install a fresh copy of NSL.


This approach is very useful for people who are testing the intermediate builds and would like to recover in case of an incomplete, failed, or wrong installation. Also, this saves the time of the test engineers of reformatting, reimaging the machine in case of failed scenarios.

All in all this is the best approach of cleaning your machine where NSL installation has failed and made the machine unsuitable for further NSL installation.

Neha Kanchan
Mithilesh Katre
Sabita Rani

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this post.

Disclaimer: As with everything else at NetIQ Cool Solutions, this content is definitely not supported by NetIQ, so Customer Support will not be able to help you if it has any adverse effect on your environment.  It just worked for at least one person, and perhaps it will be useful for you too.  Be sure to test in a non-production environment.

Leave a Reply

No Comments
By: kneha
Oct 13, 2009
4:46 pm
Active Directory Authentication Automation Cloud Computing Cloud Security Configuration Customizing Data Breach DirXML Drivers End User Management Identity Manager Importing-Exporting / ICE/ LDIF Intelligent Workload Management IT Security Knowledge Depot LDAP Monitoring Open Enterprise Server Passwords Reporting Secure Access Supported Troubleshooting Workflow