Uninstall an agent
Cleanly remove the NetLock RMM agent from a Windows, Linux, or macOS device using the installer's uninstall mode.
Uninstall an agent
This guide removes the NetLock RMM agent from a device and leaves it in a clean state: services deleted, processes stopped, install and data directories gone. It is the counterpart to Guide H.1. Uninstalling only affects the local device; the device record stays in the Console until you delete it there (see Verify it worked).
Before you start
- You have administrator or root access on the target device. The uninstaller deletes services and protected directories, so it requires elevation on every supported OS.
- You have the matching agent installer binary for the device's platform and architecture. Any build removes the agent (the embedded server configuration is ignored in this mode), but it must match the OS and architecture (for example a
win-x64build to uninstall on 64-bit Windows). On Windows, use an installer from a server on 3.3.0.11 or later, so the uninstall also releases the Windows Update settings (see What gets removed). If you no longer have the original.zip, download one from Agent Installers as described in Guide H.1. - The uninstaller is part of the command-line installer that Agent Installers hands out. A graphical installer built with an earlier version does not uninstall; download the installer from Agent Installers instead.
What gets removed
The uninstall mode performs a full cleanup, in order:
-
Stops the services:
NetLock_RMM_Agent_Comm,NetLock_RMM_Agent_Remote, andNetLock_RMM_Agent_Health. -
Terminates the processes: the three agent services, the user process, the UAC helper, and the tray icon.
-
Deletes the services: removes the Windows services, the Linux
systemdunits under/etc/systemd/system/, or the macOS LaunchDaemons under/Library/LaunchDaemons/together with the LaunchAgents of the User Process and the tray icon under/Library/LaunchAgents/(unloaded from every signed-in user session first), and unregisters the user-process and tray-iconRunentries on Windows. -
Releases Windows Update (Windows): removes the Windows Update settings the agent applied for
Disable Windows built-in automatic updates(see Chapter 6 — Policies):NoAutoUpdateandSetDisableUXWUAccessunderHKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate, andTrayIconVisibilityunderHKLM\SOFTWARE\Microsoft\WindowsUpdate\UX\Settings. Only values the agent recorded as its own are removed; a WSUS configuration and values from your own group policies stay. Automatic updates resume, the Windows Update page shows its controls again without the "Some settings are managed by your organization" notice, and the Windows Update icon in the notification area is visible again.The step also removes the Microsoft Update registration the agent made for
Include updates for other Microsoft products (Microsoft Update), through the Windows Update Agent's service manager (powershell.exe). Only a registration the agent recorded as its own (markermu_opt_in_applied) is removed; one made by a user, by a group policy or before the agent was installed stays.Finally it removes the agent's registry key
HKLM\SOFTWARE\WOW6432Node\NetLock RMM, andHKLM\SOFTWARE\0x101 Cyber Securityonce it is empty. No service is restarted. -
Deletes the directories and logs: the install tree under Program Files and the data tree under ProgramData, plus the agent service logs on Linux and macOS. When the uninstall was started by the agent itself (remote uninstall or an update), the installer runs from
NetLock RMM\Temp\netlock rmm\installerbelow the data tree and leaves that folder with its executable and log behind; a manual uninstall removes the data tree completely.
After it finishes, no NetLock RMM service, process, or directory remains on the device, and Windows Update is back under Windows' control. The installer prints the outcome of the Windows Update step, including whether a Microsoft Update registration was removed.
Note: A fresh installation over an existing agent (
cleanmode, the--serverparameter mode, or the installer with its embedded configuration) runs the same cleanup first. On a device whose policy disables Windows' automatic updates, the agent applies the Windows Update settings again within a few minutes of its first policy sync. A repair (fix, also used by agent updates) keeps the settings.
Steps
- Copy the agent installer
.zipto the target device (or locate the one you already deployed with). - Extract it and run the installer with the
uninstallargument from an elevated shell.
Windows (PowerShell, elevated):
Expand-Archive .\NetLockAgent.zip -DestinationPath .\NetLockAgent
.\NetLockAgent\NetLock_RMM_Agent_Installer.exe uninstallFor an unattended removal via GPO, Intune, or a script, combine uninstall with the same flags the installer accepts:
.\NetLock_RMM_Agent_Installer.exe uninstall --hidden --no-log--hidden/-h: hide the console window (Windows only).--no-log/--nolog: delete installer logs after completion.--temp <path>/-t <path>: use a custom temporary directory (useful on appliance distros that block execution from the default temp location).
Linux / macOS (Bash, with sudo):
unzip NetLockAgent.zip -d NetLockAgent
chmod +x NetLockAgent/NetLock_RMM_Agent_Installer
sudo ./NetLockAgent/NetLock_RMM_Agent_Installer uninstall- Wait for the installer to print
Uninstall complete.and exit with code0.
Note:
uninstallis one of the installer's positional modes, alongsideclean "<path-to-server_config.json>"(fresh install with an external config) andfix "<path>"(repair while preserving the server config). See Guide H.1 for the install and repair modes.
Verify it worked
-
The installer reports
Uninstall complete.and exits without an error code. -
The agent services are gone:
- Windows:
Get-Service NetLock_RMM_Agent_*returns nothing. - Linux:
systemctl status netlock-rmm-agent-commreports "not found". - macOS:
launchctl list | grep netlockis empty, both as root and as every signed-in user (the LaunchAgents of the User Process and the tray icon), and/Library/LaunchAgents/holds nocom.netlock.rmm.*.plist.
- Windows:
-
The install and data directories no longer exist:
- Windows:
C:\Program Files\0x101 Cyber SecurityandC:\ProgramData\0x101 Cyber Security. After a remote uninstall onlyC:\ProgramData\0x101 Cyber Security\NetLock RMM\Temp\netlock rmm\installer(the installer executable and its log) remains. - Linux:
/usr/0x101_Cyber_Securityand/var/0x101 Cyber Security, and the logs under/var/log/netlock-rmm-agent-*.log. - macOS:
/usr/local/bin/0x101_Cyber_Securityand/Library/Application Support/0x101 Cyber Security.
- Windows:
-
Windows: the Windows Update settings are released. In an elevated command prompt:
reg query "HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /s reg query "HKLM\SOFTWARE\Microsoft\WindowsUpdate\UX\Settings" /v TrayIconVisibility reg query "HKLM\SOFTWARE\0x101 Cyber Security" /s powershell -Command "(New-Object -ComObject Microsoft.Update.ServiceManager).Services | Select-Object Name, ServiceID, IsRegisteredWithAU"The first command lists neither
NoAutoUpdatenorSetDisableUXWUAccess(it may report that the key does not exist, or show WSUS and group policy values, which stay). The second reports that the value was not found, the third that the key does not exist. The fourth lists no service with the ID7971f918-a847-4430-9279-4a52d1efe18d(Microsoft Update) unless it was registered by someone other than the agent, in which case it stays. Reopen Settings › Windows Update:Check for updatesis available again. -
The device still shows in the Console, because uninstalling does not delete the record. Remove it from
Devices(orUnauthorized Devices) by hand once the agent stops reporting in. See Chapter 3 — Managing Devices.
Troubleshooting
-
"Failed to elevate" and the installer exits. The uninstaller needs administrative or root privileges to delete services and protected directories. Re-run from an elevated PowerShell prompt (Windows) or with
sudo(Linux / macOS). -
A service is "marked for deletion" or a directory is locked. A process still holds a handle. The uninstaller already waits for the service manager to release handles, but if it raced an open management console or a running agent process, reboot the device and run
uninstallagain. The second pass clears any leftovers. -
The device keeps reappearing in the Console. That is the cached device record, not a live agent. Confirm the services are gone (above), then delete the record in
Devices. If the device genuinely re-registers, an installer or deployment task is reinstalling it. Check your GPO, Intune, or Ansible jobs. -
Windows Update stays locked after an uninstall with an installer before 3.3.0.6 ("Some settings are managed by your organization", no
Check for updates). Remove the values in an elevated command prompt:reg delete "HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU" /v NoAutoUpdate /f reg delete "HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v SetDisableUXWUAccess /f reg delete "HKLM\SOFTWARE\Microsoft\WindowsUpdate\UX\Settings" /v TrayIconVisibility /f reg delete "HKLM\SOFTWARE\0x101 Cyber Security\NetLock RMM\Comm Agent" /v wu_lockdown_applied /fThese commands delete single values, never a whole key; a value that does not exist only produces an error message. Skip the first two if your own group policy sets
NoAutoUpdateorSetDisableUXWUAccess. If the values come back after a while, a group policy writes them; check withgpresult /h report.html. -
Microsoft Update stays registered after an uninstall with an installer before 3.3.0.11 (
Receive updates for other Microsoft productsis on, orMicrosoft Updateis listed by the fourth command under Verify it worked). Remove the registration in an elevated command prompt:powershell -Command "(New-Object -ComObject Microsoft.Update.ServiceManager).RemoveService('7971f918-a847-4430-9279-4a52d1efe18d')" reg delete "HKLM\SOFTWARE\0x101 Cyber Security\NetLock RMM\Comm Agent" /v mu_opt_in_applied /fThe first command is the same as turning off
Receive updates for other Microsoft productsin the Windows settings; skip it if Microsoft Update should stay registered. The second removes the agent's marker and only produces an error message when the value is already gone. -
Uninstaller fails on a Linux NAS or appliance distro. Some distributions, notably Synology and similar NAS systems, block execution from the default temporary directory. Re-run with
--temp <path>/-t <path>pointing at a directory the system permits execution from, then retry.
Related
- Guide H.1 — Deploy your first agent — build an installer and install the agent; also documents the
cleanandfixmodes. - Chapter 3 — Managing Devices — remove the device record after the agent is gone.
- Chapter 4 — Tenants — deleting a tenant requires uninstalling its agents first.