Uninstall UserLock and remove all corresponding data
Learn how to completely uninstall UserLock, including all agents, servers, and configuration data, from your environment.
This guide explains how to uninstall all UserLock components and remove all related files, folders, registry entries, and scheduled tasks.
Follow these steps carefully if you need to permanently remove UserLock from your environment or perform a full reinstallation.
The recommended method is to use the automatic deployer in Uninstall mode.
Open the UserLock console.
Go to ⚙️ Server settings ▸ Agent distribution.
Enable Automatic distribution
Set Distribution mode to Uninstall agent.
)
Wait until all computers show Not installed in the list.
Note
Alternative methods:
From the console:
In the UserLock console, go to Environment ▸ Machines.
Select one or more machines and click on the Actions button.
In the menu, click to Uninstall the Desktop agent
In the upper right corner, the Admin action icon animates. Click it to monitor the uninstallation progress.
Manual uninstallation, learn more.
Through MSI technology (if originally deployed via MSI).
Using the PowerShell cmdlet Uninstall-UserLockAgent.
Using the UserLockAPI methods.
You can initiate the uninstallation of NPS and IIS agents directly from the UserLock console:
Open the UserLock console.
Go to Environment ▸ Machines.
Select one or more machines containing NPS or IIS agents.
Click the Actions button, then select Uninstall.
In the upper right corner, the Admin action icon animates. Click it to monitor the uninstallation progress.
Additional actions required:
for NPS agent, see how to uninstall the NPS agent manually
for IIS agent, see how to uninstall the IIS agent manually
Note
Alternative methods:
Using the PowerShell cmdlet Uninstall-UserLockAgent.
Using the UserLockAPI methods.
By default, the desktop console is installed on the main UserLock server, and the web application can be installed either on the same server or on a dedicated IIS server.
The cleanup steps described below must be performed on each of these servers.
If UserLock reports were scheduled from the console, follow these steps to remove all related tasks:
Open the UserLock console.
Go to Reporting ▸ Scheduled reports.
Delete all scheduled reports with the Delete option in the Actions button.
Check the following folder and delete any remaining files (if any):
%ALLUSERSPROFILE%\ISDecisions\Tasks
Note
Deleting them from the console will also automatically remove the corresponding tasks from the Windows Task Scheduler.
Choose one of the following methods:
Control Panel:
Open Programs and Features,
select UserLock,
then click Uninstall.
Command line:
Run the following executable (adjust path if UserLock was installed elsewhere.):%ProgramFiles(x86)%\ISDecisions\UserLock\CheckBeforeUninstall.exe
To locate the custom installation path via PowerShell (run as Administrator):
$userlock = Get-WmiObject Win32_Product | where Name -Like UserLock$guid = $userlock.IdentifyingNumber$installLocationObj = Get-ItemProperty "HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\$guid" -Name InstallLocation$installLocation = $installLocationObj.installLocationWrite-Host $installLocationNote
To uninstall a backup server, follow the same procedure.
After uninstalling all components, some files and registry keys may still remain.
To ensure a complete cleanup, follow the steps below on each machine where UserLock components were installed.
Delete the installation folders:
%ProgramFiles(x86)%\ISDecisions\UserLock\%ProgramFiles(x86)%\ISDecisions\
Note
Keep the ISDecisions folder if other IS Decisions products are installed.
Delete the configuration and log folders:
%ALLUSERSPROFILE%\ISDecisions\UserLock\Logs\%ALLUSERSPROFILE%\ISDecisions\UserLock\%ALLUSERSPROFILE%\ISDecisions\
Note
Delete only the UserLock folder if you want to keep settings from other IS Decisions products.
Delete folders:
%APPDATA%\ISDecisions\UserLock%APPDATA%\ISDecisions
Note
Delete only the UserLock folder if you want to keep settings from other IS Decisions products.
Clean up the registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ISDecisions\UserLockHKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ISDecisionsHKEY_CURRENT_USER\Software\ISDecisions\UserLockHKEY_CURRENT_USER\Software\ISDecisions
Note
Keep the ISDecisions key only if other products are installed.
Delete agent binaries and log files (depending on OS):
x64 OS:
%windir%\SysWOW64\ULAgentExe.exex86 OS:
%windir%\System32\ULAgentExe.exe%windir%\System32\ULAgent.log%ALLUSERSPROFILE%\ISDecisions\UserLock\Logs\UlAgent-%USERNAME%.err
Delete session and pop-up helper programs:
%windir%\SysWOW64\SessionAgent.exe%windir%\SysWOW64\SessionAgentUI.exe%windir%\SysWOW64\SessionAgent.log%windir%\SysWOW64\SessionAgentUI.log
Clean up the registry
Browse the
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon
then delete:All values starting with
UserLock(for example,UserLockServer,UserLockServerBackup, etc.)The subkey:
Winlogon\UserLock
Delete the agent binary file:
%windir%\System32\ULIasAgent.dllDelete the agent log file:
%ALLUSERSPROFILE%\ISDecisions\UserLock\Logs\UlIasAgent.csvDelete the registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\ISDecisions\UserLock\IAS
Delete the agent binary file:
%windir%\System32\UlHttpModule.dllDelete the agent log file:
%ALLUSERSPROFILE%\ISDecisions\UserLock\Logs\<Application Pool name>.http.txtDelete the registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\ISDecisions\UserLock\IIS
In some environments, the UserLock server names are deployed to workstations through a Group Policy Object (GPO).
This allows the Desktop Agent to automatically locate the Primary and Backup UserLock servers, even if it was installed before the server configuration.
When uninstalling UserLock, these GPO settings must also be removed; otherwise, the registry entries will be automatically recreated after each Group Policy refresh.
Open the Group Policy Management Console (GPMC) on your domain controller.
Locate and edit the GPO used to deploy UserLock settings.
)
Remove all settings related to the UserLock agent (for example: Primary server, Backup server, Lock on screensaver, etc.).
Close the GPMC and apply the changes.
On each workstation or server, update the local policies by running:
gpupdate /forceVerify that the registry key is removed:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\ISDecisions\UserLock\Agent)
UserLockServerName– name of the Primary UserLock server.BackupServer– name of the Backup UserLock server.LockWhenScreenSaverStart– enables session lock when the screensaver starts.
)
)
)
)
)
)
)
)