Environment
- Carbon Black Cloud Sensor: All supported versions
Objective
How to Troubleshoot Sensor Uninstall Issues
Resolution
- Please make sure the uninstall has been attempted via the following process per OS
- Windows
- If the uninstall is still failing the uninstall log will either be generated at %temp%\cb-installer-<version>.log or, if %temp% does not exist, %SystemRoot%\temp (typically C:\Windows\temp).
- Next, search for "Return value" in the install logs, 0 or 1's normally are ok, 1603 is a default Windows failure.
- These are code blocks, there will be a "Return Value" then a code block, and then another "Return Value". Review the data in the code block between the Return Values for the issue.
- MacOS
- Linux
- If not resolved please open a case with CB Support, the case will start by collecting information:
- Is the uninstall code enabled for this policy/policies containing the impacted device(s)?
- What steps were taken to uninstall?
- How many devices are exhibiting this behavior?
- What is the device sensor version?
- What is the device operating system?
- What is the device name?
- Is the sensor being uninstalled using the console, command line, or GPO?
- Is the sensor being uninstalled using attended or unattended method?
- If it hasn't been attempted yet please run the uninstall from the command prompt following these instructions
- Please upload the uninstall log to the case and include the uninstall/deregistration code used if any
Additional Notes
- If this issue cannot be solved with CB Support troubleshooting steps, it may need escalation to the CB Engineering team. Escalation will require information collected in the steps above as well as some additional diagnostics:
- Backend and ORG name
- Sensor Version
- Operating System of the Device
- cb-installer-x-x-x log for impacted device
- tcpdump for impacted device
- Procmon for impacted device taken during uninstall attempt
- CB support log analysis
Related Content
