Disable Symantec Endpoint Protection Chrome Extension -

To disable the Symantec Endpoint Protection (SEP) Chrome extension, you can use the standard browser settings if it is unmanaged, or advanced administrative tools like the Symantec Endpoint Protection Manager (SEPM) or Windows Registry if it is locked by an organization. 1. Disable via Chrome Extension Settings (Unmanaged)

• Chrome Enterprise/Cloud Management: set ExtensionSettings for extension ID to "blocked": true or set installation_mode.
• GPO: update ADMX for Chrome ExtensionSettings.
• MDM: push configuration profile.
• SEP Manager: push SEP client policy to disable browser integration if available.

Method 2: Enable through Chrome Group Policy disable symantec endpoint protection chrome extension

If it is locked, you cannot remove it permanently. However, developers often use this trick: To disable the Symantec Endpoint Protection (SEP) Chrome

Caveat: Managed policies or SEP clients can reinstall or re-enable the extension. Method 2: Enable through Chrome Group Policy If

• Push setting via enterprise management channel (MDM, GPO, Chrome Enterprise policies, or SEP management server).
• Use Chrome extension policy (ExtensionInstallForcelist / ExtensionSettings) or SEP client policy as applicable.

When you should NOT disable the extension

Before you pull the trigger, consider these scenarios where disabling SEP is a terrible idea:

1. Log into your SEPM console (usually https://<your_server>:8443/sepm).
2. Navigate to Policies → Web and Cloud Access Protection.
3. Edit the policy assigned to your workstation.
4. Look for the setting: "Enable Web Protection in Chromium-based browsers" or "Integrate with Chrome".
5. Uncheck this box.
6. Under the Browser Integration tab, set "Chrome Extension" to Disabled.
7. Save the policy and update the policy on the client (smc -stop then smc -start on the client, or wait for the next heartbeat).

Final Verdict

Disabling the SEP Chrome extension is possible, but how easy it is depends on whether your PC is managed by an IT department. For personal or unmanaged devices, Method 2 or 4 works perfectly. For managed devices, you may be stuck unless you have admin rights.