Uninstalling SenseOn
Warning: If there is an attempt to uninstall the SenseOn agent, some SenseOn analytics detect the attempt and give an alert.
If you deployed SenseOn with an automation tool, such as a tool in 'Automated Deployment', use that tool to uninstall the agent if possible. The sections that follow tell you how to manually uninstall the Universal Sensor from supported operating systems.
What is installed on this device
The generation of the agent that the device runs controls what you must remove:
| Generation | Packages installed |
|---|---|
| Version 7.0 and later | The bootstrapper and the Universal Sensor. The bootstrapper installs and updates the Universal Sensor. The Universal Sensor collects and reports telemetry. |
| Version 6 and earlier, the legacy agent | The Universal Sensor only. There is no bootstrapper. |
Find out if this device has a bootstrapper before you start, because there are two routes. The steps in the sections that follow are for version 7.0 and later. Most devices run version 7.0 and later. A legacy device has no bootstrapper, no bootstrapper service and no bootstrapper data directory. As a result, the bootstrapper commands and paths in those sections do not apply to a legacy device. Also, nothing installs the sensor again after you remove it.
If you do not know which route applies to this device, refer to Troubleshooting: Is the bootstrapper installed?. Then, for a legacy device, follow Uninstalling a legacy device.
On version 7.0 and later, remove the bootstrapper and the sensor. While the bootstrapper is installed and runs, it does a check for the Universal Sensor. If the Universal Sensor is not there, the bootstrapper installs it again, usually in approximately ten minutes. As a result, if you remove only the sensor, the sensor comes back. You also cannot enrol the device again until you remove the bootstrapper.
The sequence in which you remove the packages is different for each platform. Each platform section gives the sequence.
Windows
The list of installed programs shows the two packages as separate items:
SEE, published by SenseOn. This package is the Universal Sensor.senseon-bootstrapper, published by SenseOn.
Sequence on Windows: remove the bootstrapper, and the bootstrapper schedules the removal of the sensor. The uninstaller of the bootstrapper immediately stops the services of the Universal Sensor. But the uninstaller does not remove the SEE package at that time. The uninstaller puts that removal in a queue as a RunOnce entry with the name UninstallSEE. This entry runs the next time that an administrator logs on to the device. Until then, the list of installed programs continues to show SEE. On a device that no person logs on to, such as a server, SEE stays installed.
This occurs only when you uninstall the bootstrapper. When the bootstrapper upgrades itself, it leaves the sensor in position on purpose.
The PowerShell script in the section that follows is the recommended method and uses the opposite sequence. The script stops the bootstrapper service before it removes anything. As a result, the bootstrapper cannot install the sensor again while the script runs. This lets the script remove the sensor first. The uninstall of the sensor can then report the removal to the SenseOn platform. Then the script removes the bootstrapper.
Using the PowerShell script (recommended)
This is the most reliable method. The script stops the bootstrapper service. Then the script removes the Universal Sensor. Then the script removes the bootstrapper. The script also clears the delayed sensor removal that the bootstrapper schedules for the next logon.
- Save a copy of the PowerShell script at this link to a location that you select.
- Open
PowerShellas anAdministrator. - Go to the directory that contains the script.
- Run the script.
- If you want a fully clean installation later, add the
-RemoveDataflag (.\uninstall_senseon.ps1 -RemoveData). The flag also deletes the SenseOn data folders underC:\ProgramDataand clears the enrolment of the device. The next install then starts from the beginning and does not use the existing device record again. - An error can say that the script "cannot be loaded because running scripts is disabled on this system". If you get this error, run
powershell.exe -ExecutionPolicy Bypass .\<script_name.ps1>from the same PowerShell instance. Replace<script_name>with the name that you gave to the script when you saved it.

The script writes a log to %TEMP%\SenseOnUninstall\. The script exits with code 0 only when the two packages are no longer installed. The end of the log then shows Both SenseOn packages have been removed. An exit code that is not zero means that the removal was not fully complete:
2: you did not run the script as an Administrator.10: the script could not remove the Universal Sensor.11: the script could not remove the bootstrapper.
If a package stays on the device, the log records it as Still installed after this run. Do not assume that the run was successful. Examine the exit code or the log before you treat the device as clean. If the log records REBOOT REQUIRED, restart the device to complete the removal.
The script skips a package that is not installed and does not treat it as a failure. As a result, the script also works on a legacy device. For the log entries on a legacy device, refer to Uninstalling a legacy device.
As most uninstallers do, the script does not delete the data folders under C:\ProgramData. To delete those folders also, add -RemoveData. This flag also clears the enrolment of the device. A later install then enrols the device from the beginning.
If you deploy the script with a software distribution tool, run the script with elevated privileges. You can safely run the script more than one time. The script skips a package that is already removed and does not report it as a failure.
Using Add/Remove programs
- Press Windows Key.
- Start to type
add remove program. - Select the first match. This is usually
Add or remove programs. - In the search bar, type
senseon. - Uninstall
senseon-bootstrapper. The uninstaller stops the Universal Sensor and schedules the removal ofSEEfor the next administrator logon. - To complete the removal now and not at the next logon, search for
SEE. Then uninstallSEEalso.

Using PowerShell with access to the deployed MSI
Use this method only if you have the MSI file that installed the device. You have this file only if you deployed the MSI yourself and kept a copy, for example through a software distribution tool. If you used the SenseOn install command from Settings > Universal Sensor, the installer automatically deletes the MSI after installation. This method is then not available. In that condition, use the PowerShell script (refer to 'Using the PowerShell script (recommended)').
- Open PowerShell as an Administrator.
- Run
msiexec.exe /x <absolute_path_to_bootstrapper_msi>. This command stops the Universal Sensor and schedules its removal for the next administrator logon. - To complete the removal now and not at the next logon, also run
msiexec.exe /x <absolute_path_to_sensor_msi>.

Removing the SenseOn Universal Sensor using Active Response
Use this method for a Windows device that you cannot physically get back and can no longer get access to by other methods. In this method, you run an uninstall script on the device remotely through Active Response.
Use this method only if no other method is possible. Run the script only when you are sure that you must remove the Universal Sensor from the device. Also make sure that you have no other method to remove it, for example because you lost access to the device. If you can still get access to the device, use one of the other methods in the Windows section.
What the script does
- The script removes the SenseOn registry entries.
- The script removes the SenseOn files.
- The script deletes all other persistence.
The Universal Sensor runs as a protected process. As a result, a process in user mode cannot stop the sensor. The removal is complete only when the device restarts, because the restart clears the sensor from memory. Restart the device yourself, or wait for its next scheduled restart. Until the restart, the sensor stays loaded.
Before you run it
The script ends your Active Response session. When the script is complete, you lose the connection to the device. You cannot use Active Response to connect to the device again. Before you start, make sure that you have the correct device, because you cannot undo the removal remotely.
Requesting the script
SenseOn does not publish the script. SenseOn supplies the script on request:
- Raise a ticket in the Support Hub and ask for the removal script for the Windows Universal Sensor. In the ticket, identify the device and state that you no longer have access to it.
- Run the script through Active Response on the device. The device must be in a segment that has Active Response enabled. You must have Active Response access. Refer to Permissions.
- Restart the device to complete the removal.
Removing all data
An uninstall does not delete the SenseOn data folders. This is usual for a Windows uninstaller. To remove the folders also, run the PowerShell script with -RemoveData. As an alternative, delete these folders manually after you remove the packages:
C:\ProgramData\senseon-bootstrapper
C:\ProgramData\senseon-see
The first folder contains the enrolment of the device. If you keep this folder, a later install uses the existing device record again and does not enrol the device as new. The second folder contains the antimalware signature sets. These sets use several hundred megabytes for each device. As a result, it is useful to clear this folder if you remove SenseOn from many devices.
Linux
Sequence on Linux: the bootstrapper first, then the sensor. If you remove the bootstrapper first, it cannot install the sensor again during the uninstall. On Linux, the removal of the bootstrapper package does not remove the sensor, which is different from Windows. As a result, the two commands are necessary.
Ubuntu/Debian
To manually uninstall SenseOn from Ubuntu/Debian devices, open a terminal prompt. Then run these commands in sequence:
sudo apt purge senseon-bootstrappersudo apt purge senseon-see
Run these as two separate commands. Do not use one apt purge command with the two package names. With one command, apt selects its own removal sequence from the dependency graph. It is possible that this sequence is different from the sequence in which you list the packages.
Use
purge, notremove.apt remove senseon-bootstrapperdeletes the pid file,/var/log/senseon-bootstrapper,/usr/share/senseon-bootstrapperandproxy.json. But it does not delete the other contents of/var/senseon-bootstrapper. These contents include the configuration blob of the device and its ledger. Onlypurgeremoves that directory.
CentOS/RedHat
To manually uninstall SenseOn from CentOS/RedHat devices, open a terminal prompt. Then run these commands in sequence:
sudo rpm -e senseon-bootstrappersudo rpm -e senseon-see
If you want to fully remove the device, delete
/var/senseon-bootstrappermanually, becauserpm -enever clears it. RPM has no equivalent ofapt purgehere. As a result, on an RPM host, the configuration blob and the ledger of the device stay after the uninstall. To delete the directory, refer to 'Removing all data' in the Linux section.
Removing all data
On Ubuntu/Debian and on CentOS/RedHat, /var/senseon-bootstrapper contains the enrolment of the device. To remove the enrolment also, delete the directory after you remove the packages:
sudo rm -rf /var/senseon-bootstrapper
Note: The uninstall deletes
proxy.jsonon purpose. As a result, a later installation cannot use an old proxy setting that is no longer correct. If the device must have a proxy after you install SenseOn again, configure the proxy again. Refer to Proxy Configuration.
macOS
Sequence on macOS: the bootstrapper first, then the sensor. Each package has its own uninstall script. You must run the two scripts. If you remove the bootstrapper first, it cannot install the sensor again during the uninstall. On macOS, the bootstrapper script does not remove the sensor, which is different from Windows.
- Open a terminal prompt. Then run:
cp /opt/senseon-bootstrapper/senseon-bootstrapper.app/Contents/Resources/osx_uninstall.sh /tmp/uninstall_bootstrapper.sh - From the same terminal shell, run:
sudo /tmp/uninstall_bootstrapper.sh. - Then run:
cp /opt/senseon-see/senseon-see.app/Contents/Resources/osx_uninstall.sh /tmp/uninstall_sensor.sh - From the same terminal shell, run:
sudo /tmp/uninstall_sensor.sh.
You must run the two scripts as root. If you remove the bootstrapper first, the sensor script can still send the removal report. To send the report, the sensor script reads the configuration of the sensor under /var/senseon-see. It does not read the configuration of the bootstrapper.
The bootstrapper script unloads and deletes the
io.senseon.bootstrapper,io.senseon.brokerandio.senseon.loggerLaunchDaemon definitions. It removes/opt/senseon-bootstrapper,/var/senseon-bootstrapperand/var/log/senseon-bootstrapper. It also removes the package listing withpkgutil.The sensor script sends a 'last breath' message to the SenseOn platform. This message shows SenseOn when a client is uninstalled. The sensor script then stops the agent and removes the
senseon-epnsuser and group from the device. Then it unloads the sensor, removes all sensor files, and removes its own package listing withpkgutil.
Removing all data
The uninstall script of the bootstrapper already removes /var/senseon-bootstrapper. This directory contains the enrolment of the device. As a result, no more steps are necessary on macOS. If that directory is still present after you run the script, delete it:
sudo rm -rf /var/senseon-bootstrapper
Uninstalling a legacy device (version 6 and earlier)
A legacy device has the Universal Sensor and no bootstrapper. As a result, there is one package to remove, and nothing installs the sensor again after the removal. Ignore each bootstrapper command and path in the other sections of this page. C:\ProgramData\senseon-bootstrapper and /var/senseon-bootstrapper do not exist on these devices.
If you do not know which generation a device runs, refer to Troubleshooting: Is the bootstrapper installed?.
Windows (legacy)
The PowerShell script is also the recommended route for a legacy device. The script skips a package that is not installed. As a result, on a legacy device, the script removes SEE and records The bootstrapper (senseon-bootstrapper) is not installed in the log. This log entry is expected and is not an error. The run still finishes with exit code 0.
As an alternative, to remove the sensor manually, uninstall SEE, published by SenseOn, from Add or remove programs. If you still have the MSI that installed the device, you can run msiexec.exe /x <absolute_path_to_SEE_msi> /quiet /norestart from an elevated PowerShell terminal as an alternative.
After the removal, make sure that Services does not show senseon-seed or senseon-quarantine. These are the two services that the legacy agent installs on Windows.
The uninstaller does not delete the data folder of the sensor, C:\ProgramData\senseon-see. This is usual for a Windows uninstaller. The folder contains the antimalware signature sets. These sets use several hundred megabytes for each device. As a result, it is useful to delete this folder when you remove SenseOn from many devices.
Linux (legacy)
Open a terminal prompt. Then run the command for your distribution:
- Ubuntu/Debian:
sudo apt purge senseon-see - CentOS/RedHat:
sudo yum remove -y senseon-see, orsudo rpm -e senseon-see
With each of these commands, the uninstall does these steps:
- It stops
senseon-seed. - It reports the removal to the SenseOn platform.
- It deletes the enrolment files of the device from
/etc/senseon-see(the flags file, the certificates andprecise.uuid). - It deletes the
senseon-epnsuser and group.
If you do not purge,
/var/senseon-seeand/etc/senseon-seestay on the device.apt remove,yum removeandrpm -edo not delete those two directories./var/senseon-seecontains the antimalware signature sets. These sets use several hundred megabytes for each device. Onlyapt purgeclears the two directories. On an RPM host, delete the two directories manually after you remove the package:sudo rm -rf /var/senseon-see /etc/senseon-see
macOS (legacy)
Run the uninstall script of the sensor as root. There is no bootstrapper script to run first.
- Open a terminal prompt. Then run:
cp /opt/senseon-see/senseon-see.app/Contents/Resources/osx_uninstall.sh /tmp/uninstall_sensor.sh - From the same terminal shell, run:
sudo /tmp/uninstall_sensor.sh.
The script removes /opt/senseon-see, /var/senseon-see and /var/log/senseon-see. As a result, there is no data directory to clear after the uninstall.