How to fix Google Chrome not working with Symantec Endpoint

Matthew Adams
by Matthew Adams
Windows & Software Expert
Affiliate Disclosure

google chrome symantec
To fix various PC problems, we recommend DriverFix: This software will keep your drivers up and running, thus keeping you safe from common computer errors and hardware failure. Check all your drivers now in 3 easy steps:
  1. Download DriverFix (verified download file).
  2. Click Start Scan to find all problematic drivers.
  3. Click Update Drivers to get new versions and avoid system malfunctionings.
  • DriverFix has been downloaded by 0 readers this month.

In October 2019, users started posting on the Symantec support forum about an Aw Snap error that arises in Chrome when they start the browser.

The Aw Snap crash error isn’t something new. However, in this case, it occurs because Chrome 78 and 79 are not compatible with Symantec Endpoint Security software versions.

The incompatibility issue arises on any Windows platform that includes a Symantec Endpoint version that predates 14.2 RU2 MP1.

The issue largely pertains to Windows 2016 and Windows 10 RS1 platforms with SEP and Google Chrome browsers installed. Note, however, that Edge Chromium 78 and 79 are also incompatible with Symantec Endpoint Protection.


How can I fix Chrome’s incompatibility with Symantec Endpoint?

1. Update Symantec Endpoint Protection

Symantec’s official fix for SEP’s Chrome incompatibility is to update Symantec Endpoint to the latest 14.2 version.

You can get the latest patch update for Endpoint Protection (build 5569) from the RU2 MP1 client-only patches page. That page includes instructions for how you can download the latest patch and update the software with it.

SEP update download page google chrome not working with symantec


2. Deactivate Chrome’s renderer code

  1. Right-click Google Chrome’s desktop shortcut and select Properties.
  2. Select the Shortcut tab.
  3. Then enter the following line in the Target text box as shown directly below:
    • -disable-features=RendererCodeIntegrity Shortcut tab google chrome not working with symantec
  4. Select the Apply option.
  5. Click the OK button.

If you’re tired of Google Chrome’s incompatibilities, check out this article for some good alternatives


3. Edit the registry

  1. Press the Windows key + R hotkey, which opens Run.
  2. Input ‘regedit’ in the Open box and press Enter to open the Registry Editor.Registry Editor google chrome not working with symantec
  3. Go to this registry key: HKLM > Software > Policies > Google Chrome.
  4. Double-click the RendererCodeIntegrityEnabled DWORD on the right of the window.
  5. Change its value to 0 in the Edit Dword window.
  6. Click the OK option.

If you have issues opening the Registry Editor, check out this detailed guide for some quick fixes.


4. Launch Chrome with no sandbox

  1. Right-click a shortcut icon for Chrome on the desktop and select Properties.
  2. Click the Shortcut tab on the window that opens.
  3. Then add –no-sandbox to end of the Target box as belowTarget text box google chrome not working with symantec
  4. Select the Apply option.
  5. Click the OK button.

Edit Chrome’s exe file title

  1. Launch File Explorer with the Windows key + E keyboard shortcut.
  2. Open the folder that includes Chrome’s EXE file.
  3. Right-click Chrome’s EXE and select Rename.Rename option google chrome not working with symantec
  4. Enter Chrome as the new file title, but don’t change the EXE format at the end.

Those are a few of the resolutions confirmed to fix Google Chrome’s Aw Snap incompatibility error with Symantec Endpoint.

Remember, however, that you can always switch to browsers that don’t have any compatibility issues with Endpoint Protection, such as Firefox or Opera.

Which one of the many solutions listed above fixed the issue for you? Let us know by leaving a message in the comment scetion below.

This article covers:Topics:

There are no comments yet. Please leave a comment

add a comment

Leave a Reply

Your email address will not be published. Required fields are marked *