Disable Symantec Endpoint Protection Chrome Extension (2024)

To disable or remove the Symantec Endpoint Protection (SEP) Chrome extension, you must first determine if your browser is "Managed by your organization." Because this extension is typically force-installed by IT administrators for security, standard removal methods may be grayed out. Method 1: Standard Disabling (Unmanaged Browsers)

If you have local administrator rights but do not have access to the SEPM console, you can use these methods: Stop the Symantec Service (Temporary):

Part 5: Troubleshooting – Why Does It Keep Coming Back?

You disabled the extension, rebooted, and it’s back. Here is why. disable symantec endpoint protection chrome extension

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

Disabling the Symantec Endpoint Protection Chrome extension can help resolve performance issues, compatibility problems, or false positives. While the extension provides valuable security features, it's sometimes necessary to temporarily disable it to ensure a smooth browsing experience. If you're experiencing issues with the extension, try disabling it using one of the methods outlined above. If you need to re-enable it, simply follow the same steps to toggle the switch back to the ON position. To disable or remove the Symantec Endpoint Protection

Alternatively, click Remove to delete it entirely from the browser. 2. Disable via Symantec Endpoint Protection Manager (SEPM)

Log in to the Symantec Endpoint Protection Manager (SEPM) console. Navigate to Policies and select Intrusion Prevention. Edit the active policy and locate the Windows Settings tab. Uncheck the option for Enable Browser Intrusion Prevention. Here is why

2. Problem Statement

The Symantec Endpoint Protection Chrome extension is installed by default to provide web threat protection (anti-phishing, malware scanning). However, it can cause conflicts with internal web applications, degrade browser performance, or interfere with single sign-on (SSO) flows. Currently, users cannot remove it because it is force-installed via the Windows Registry or Group Policy. Administrators require a controlled method to disable this extension without uninstalling the core SEP client.