Protection Chrome Extension - Disable Symantec Endpoint

Stop:

sc stop smc
sc stop ccSvcHst

Start:

sc start smc
sc start ccSvcHst

In my case, the extension was:

If you’re an admin or an advanced user, you may want to disable just the browser component while keeping the main SEP client active for file and network protection.


If you want, I can:



If you want, I can:

Here’s a proper technical write-up on disabling the Symantec Endpoint Protection (SEP) Chrome extension.


Disabling the Symantec Endpoint Protection Chrome extension is straightforward for local users, but managed environments may enforce it persistently. Always consult your IT security team before disabling any endpoint security component, as it can expose the browser to web-based threats. disable symantec endpoint protection chrome extension


To disable the Symantec Endpoint Protection (SEP) Chrome extension, you typically need administrative access, as the software is designed to prevent unauthorized removal. Broadcom TechDocs For Managed Clients (via SEPM) If the extension is managed by the Symantec Endpoint Protection Manager (SEPM) , it is often forced via a registry key called ExtensionInstallForceList . To remove it: Disable Browser Intrusion Prevention : In the SEPM console, navigate to Policies > Intrusion Prevention . Disabling the "Browser Intrusion Prevention"

setting for the client group will automatically unload the extension from Chrome. Enable Third-Party Management : For version 14.3 RU9 or later , check the option "Enable third party management of extensions"

. This removes the force-install registry key, allowing you to manage or disable the extension using other tools like Active Directory GPO Google Admin Locking the State

: If the client shows a "Disabled" error after turning it off, select the padlock icon

next to the policy item in SEPM to lock the browser protection in its disabled state. Broadcom support portal For Individual Troubleshooting

If you are troubleshooting a specific machine and have the necessary permissions:

To disable the Symantec Endpoint Protection (SEP) extension in Google Chrome, the method depends on whether your computer is managed by an IT department (using policies) or if you have direct control over the client. For Managed Users (IT Administrators) If the extension was installed via the Symantec Endpoint Protection Manager (SEPM) Stop: sc stop smc sc stop ccSvcHst

, it is often "forced" and cannot be disabled within Chrome's settings. You must use a policy to remove it: Broadcom support portal Disable via Intrusion Prevention Policy : Open your SEPM console, go to Policies > Intrusion Prevention , and edit your policy. Uncheck the option for Enable Browser Intrusion Prevention Version Note : For clients on version 14.3 RU4 or newer

, disabling this policy will automatically unload or uninstall the extension from Chrome. Third-Party Management : Starting with

, you can enable "third-party management" in the IPS policy settings to manage the extension through Active Directory GPOs Google Admin instead of SEP. Broadcom support portal For Individual Users (Unmanaged Clients)

If you have administrative rights on your local machine and the extension is not locked by a central policy: Standard Extension Toggle Open Chrome and go to chrome://extensions/ Symantec Browser Protection toggle switch

Note: If the toggle is grayed out and says "Managed by your organization," you cannot disable it here. Stop the SEP Service (Troubleshooting Only) dialog (Win + R).

and hit Enter. This will stop all SEP services, which may automatically disable the extension's functionality, though it might not remove the icon from Chrome. Broadcom support portal Known Workaround for Chrome Errors

If you are trying to disable the extension because Chrome is not loading pages or crashing, some users fix this by modifying the Chrome shortcut: Right-click your Chrome shortcut > Properties field, add --disable-features=RendererCodeIntegrity to the end of the text string. Registry keys Start: sc start smc sc start ccSvcHst

to manually remove the forced installation entries for the extension?

If the extension is greyed out or cannot be turned off, it is controlled by Windows Group Policy. Standard users typically cannot disable this without removing the underlying policy.

Method 1: Symantec Client Interface (If Unlocked) Sometimes the extension can be toggled off directly from the SEP client software on the taskbar/system tray.

Method 2: Registry Modification (Windows Admin Only) Warning: This method requires Windows Administrator rights. Editing the registry can harm the OS if done incorrectly.

  • Look for an entry corresponding to the Symantec Extension ID. It usually looks like a string of random letters (e.g., nkcpopkkjcacjmlceahpemilmkgpgmog or similar).
  • Right-click the entry and select Delete.
  • Restart the Computer.
  • Upon restart, the extension should be removable via the standard Chrome extensions menu (chrome://extensions/).
  • Why it’s necessary, the risks involved, and three proven methods to turn it off.

    If you are reading this, you are likely frustrated. That small, shield-shaped icon in the top-right corner of your Google Chrome browser is causing chaos. Perhaps it is slowing down your page load times, blocking access to a legitimate internal company tool, consuming excessive RAM, or simply triggering false-positive security alerts.

    The "Symantec Endpoint Protection Web Protection" extension is installed silently when your IT department deploys Symantec Endpoint Protection (SEP) to your corporate laptop. While its intention is noble—to block malicious websites and phishing attempts—its execution can often feel like a digital straightjacket.

    Before we dive into the how, a crucial warning: Disabling this extension will expose your browsing activity to higher risk. Furthermore, on most managed corporate devices, your IT administrator has locked down Chrome policies. If the extension is greyed out or you see "Managed by your organization," you cannot disable it permanently without admin rights. However, for those on personal machines or legacy systems, here is everything you need to know.

  • Targeting & Scope
  • Enforcement & Delivery
  • User Experience
  • Security & Integrity
  • Auditing & Reporting
  • Rollback & Recovery
  • Notifications
  • Compliance Controls
  • Error Handling
  • API