Disable Symantec Endpoint Protection Chrome Extension Jun 2026

: Find the string value containing the SEP extension ID and delete it.

If you disable the extension but find it active again after a few hours or a system reboot, your device is bound by corporate compliance rules.

Wait for the client machines to check in ("heartbeat") to receive the updated policy.

If you are an IT administrator, or you have local admin rights on your company laptop, you can permanently disable the SEP Chrome extension across the entire machine. disable symantec endpoint protection chrome extension

Toggle the switch in the bottom-right corner of the card to the position.

Method 4: Enterprise Deployment via Group Policy (For IT Admins)

Press Windows Key + R , type regedit , and hit to open the Registry Editor. : Find the string value containing the SEP

The extension was introduced with SEP 14.3 RU2 for Google Chrome and with SEP 14.3 RU8 for Microsoft Edge, and it is now a standard component for organizations using these SEP versions. For the extension to function correctly, the SEP client must have the IPS component installed, and the LiveUpdate feature must be configured to download the necessary browser extension content (WebExt definitions) and IPS signatures.

If you have local administrator rights and need to temporarily disable the entire SEP client (including the browser extension) for troubleshooting, you can stop the Symantec Management Client service. Press on your keyboard to open the Run dialog. Type smc -stop and click OK .

This is the proper enterprise method. It prevents the extension from ever being pushed again. If you are an IT administrator, or you

You can bypass certain integrity checks by launching Chrome with the command: Chrome.exe --disable-features=RendererCodeIntegrity . For Individual Users (Mac) [DISCUSSION] Symantec Endpoint Protection | Page 64

If you disable the extension and find that it automatically turns back on after restarting Chrome or rebooting your computer, look out for these common causes:

Edit the existing GPO applied to your target organizational unit (OU) or create a new one.