Slow boot or high CPU
Usually a leftover driver or service still registered. The publisher's cleanup utility resolves this in most cases.
Whether you are replacing a product, moving a license to new hardware, or preparing a device for redeployment, a clean removal matters. Half-installed protection causes more deployment problems than no protection at all.
Only remove protection software if you have a replacement ready to install, or the device is being retired or redeployed. Perform the work on a trusted network, in one session, and keep a current backup.
Export anything you need — configuration files, exclusion lists, detection logs. Take a current backup of the device. Removal changes system state and a backup is your fallback.
In the product's account or console view, release or deactivate the seat so it returns to your available pool. Skipping this is the most common reason a license appears "in use" later.
Self-defence features block uninstallation by design. Turn them off in the product settings, or obtain the removal password from your console administrator.
Use the operating system's normal removal process, or the product's own uninstall option. Do not delete program folders manually — that leaves services and drivers registered.
Where remnants remain, the publisher's official cleanup utility removes leftover services, drivers and registry entries. Download it only from the publisher's own website.
Reboot the device, then confirm no protection services are running and the operating system's built-in protection has re-enabled itself where applicable.
Apply the released seat to the replacement device, or install the new product and reapply your documented exclusions and policies.
| Deployment type | How the seat is released | Who can do it |
|---|---|---|
| Single home device | Deactivate within the product's account view, then activate on the new device with the same key | Account holder |
| Business, console-managed | Delete or unassign the device object in the management console; the seat returns to the pool automatically | Console administrator |
| Business, publisher account | Remove the device from the account's device list | Account owner |
| Old device unreachable | Console-side removal, or a publisher support request where no console exists | Administrator, or us on your behalf |
Usually a leftover driver or service still registered. The publisher's cleanup utility resolves this in most cases.
An existing registration is being detected. Complete a full cleanup and restart before retrying — do not force the install.
The seat was never released. Remove the device object from the console or account, then reactivate.
Firewall filter drivers can remain registered after a partial removal. Restart first; if it persists, run the cleanup utility.
Every license purchase includes setup assistance, which covers clean removal of a previous product, installation and configuration of the new one, and verification that the seat is correctly allocated. Book a session using the form on this page.
The practical questions people have mid-uninstall.
Protection software installs kernel-level drivers, background services and system extensions. Deleting files leaves those components registered but broken, which causes boot delays, network problems and conflicts when you install a replacement product. Always use the proper removal process.
That is tamper protection, enabled by whoever configured the product. If it was deployed by us, your console administrator record has it. If it was set internally, the IT administrator who configured the console can release it. Contact us and we will help you locate the right record.
Deactivate or release the seat on the old device from the product's account view or management console, then activate on the new device with the same key. Transfers within the same organisation are normally permitted; check the publisher's license agreement for the specific product.
No. For business licenses, seats can be released from the management console without touching the device. For single-device licenses, contact us — publishers have a process for hardware failure and we will handle the request with you.
Yes, in almost every case. Two real-time protection engines running simultaneously cause file-locking conflicts, severe performance degradation and unreliable results. Remove the old product fully, restart, then install the new one.
macOS products install system extensions and configuration profiles that must be approved for removal in System Settings under Privacy & Security. Some publishers provide an uninstaller app; use it rather than dragging the app to the Trash. Then remove any associated configuration profile in your MDM or in Settings.
Temporarily, yes — which is why removal and reinstallation should happen in one session on a trusted network. On Windows, built-in protection typically re-enables automatically once third-party protection is removed. Do not leave a device in an unprotected state overnight.
That is what setup assistance covers. A specialist can stay on the call through removal, verify the device is clean, install and configure the replacement, and confirm the seat is correctly allocated. Book a session through the form on this page.
Still unsure which configuration fits your environment? Ask a specialist directly or call +1 (866) 674-9974.
A specialist stays on the call through cleanup, installation and configuration, and confirms the seat is correctly reassigned.