Repeat this process for the current user path if applicable: HKEY_CURRENT_USER\SOFTWARE\Policies\Google\Chrome\ExtensionInstallForcelist Restart Google Chrome for the changes to take effect. Method 3: Disable via macOS Terminal (Mac Users)
In practice, this means you can simply if you prefer, because SEP is no longer forcing its presence. Alternatively, if your organization still wants the extension but wants to manage it centrally, you can deploy it through your preferred management channel.
If you later re‑enable the option, the extension will be reinstalled automatically, though loading may take some time. disable symantec endpoint protection chrome extension
: Incompatibility between certain Chrome versions (like 78 and 79) and SEP can trigger the infamous "Aw, Snap!" error, rendering the browser unusable.
If your organization allows local modifications, you can disable the extension directly through the Google Chrome user interface. Open . Repeat this process for the current user path
Yes. If you want to retain the security benefits but the extension is causing performance issues, ensure that you are running the latest version of SEP (14.3 RU9 or newer). Later versions have improved the extension’s efficiency. Additionally, you can try removing other conflicting extensions or adjusting Chrome’s hardware acceleration settings.
You can use the Chrome ADMX templates to add a policy that explicitly blocks the SEP extension while leaving Browser Intrusion Prevention enabled. The extension can be blocked by its extension ID: pamolibmfebkknkdmfabpjebifbffbec . If you later re‑enable the option, the extension
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\ExtensionInstallForcelist