Note: In managed installs the “Remove” button is often disabled.
Warning: Only do this if you understand registry editing. Backup first.
This prevents Chrome from loading the extension altogether.
If you cannot disable the extension directly in Chrome, the next best option is to tell the SEP desktop client to stop injecting the plugin. This is the "proper" way to do it without hacking Chrome flags. disable symantec endpoint protection chrome extension
For Symantec Endpoint Protection 14.x (or newer):
Important: You may need to enter an administrator password if your IT team has set one. If you don't know it, you cannot proceed.
On macOS:
You disabled the extension, rebooted, and it’s back. Here is why.
| Action You Took | Why It Failed |
| :--- | :--- |
| Turned off toggle in chrome://extensions | SEP client syncs policy every 30 minutes and re-enables it. |
| Deleted registry keys | SEP client recreates them on service start. |
| Uninstalled SEP client | You likely lack admin rights; UAC prompt blocked you. |
| Removed Chrome profile folder | SEP client detects missing folder and re-injects the extension. |
The golden rule: If the SEPM policy says "Force Install," the extension will return unless you override the policy at a higher level (local GPO or registry override as shown in Part 2, Method 2). Note: In managed installs the “Remove” button is
Feature Name: SEP Browser Extension Toggle Description: A configuration setting allows IT Administrators to disable or remove the "Symantec Endpoint Protection" browser extension from Google Chrome (and other supported browsers) on managed endpoints. Target Audience: System Administrators, Security Operations Teams.
Provide administrators the ability to disable the Symantec Endpoint Protection (SEP) Chrome extension across managed endpoints from a centralized admin console, with options for temporary disable, scheduled disable, per-group targeting, audit logging, and user opt/override controls. This feature is designed for enterprise environments where extension conflicts, troubleshooting, or staged rollouts require controlled disabling of the browser extension.