How do I fix Google Chrome not working with Symantec Endpoint

Symantec Endpoint Protection (SEP) users were unable to take advantage of the new Chrome 78 features because their browser crashed on startup and refused to load pages.

Complaints about the bug popped up in droves on Reddit, in the comments section of the official Google Chrome blog, and more. Most of the complaints came from corporate environments where SEP is typically used.

Symantec representatives have already issued a newsletter confirming the problem and offering interim solutions to resolve it.

The developers write that the bug affects all SEP users running Windows 10 RS1, Windows Server 2012, and Windows Server 2016, as well as all Windows versions with SEP versions earlier than 14.2. Additionally, the problem affects the Microsoft Edge version of Chromium, but the updated browser is not yet available to the public.


Why doesn’t Google Chrome work with Symantec Endpoint?

Why doesn't Google Chrome work with Symantec Endpoint?

Browsers give us the ability to browse various topics 24 hours a day, 7 days a week. There are several security packages on the digital market that are popular with users. One such security software package is “Symantec Endpoint” developed by Broadcom Inc. However, when using this software, some users encounter various problems. One of the most common problems is the “Aw Snap” collision error. This error occurs when launching browsers, especially Google Chrome, and the main reason is incompatibility with the Symantec Software Edition Endpoint Security product.

These errors occur on various versions of Chrome, such as 78 and 79, and can occur on all Windows platforms, including Symantec Endpoint Edition, which is set to 14. 2 RU2 MP1. This error also occurs in different editions of Chrome, such as 78 and 79.


How do I solve Chrome’s incompatibility with a Symantec endpoint?

How do I solve Chrome's incompatibility with a Symantec endpoint?

Updating Symantec Endpoint Protection

The official solution to SEP incompatibility with Chrome is to update Symantec Endpoint to the latest version 14.2. The latest update for Endpoint Protection (build 5569) can be obtained from the RU2 MP1 client patch page. This page contains instructions on how to download the latest patch and update the software with it.

Disable Chrome rendering engine code
  1. Right-click the Google Chrome desktop shortcut and select Properties.
  2. Select the Shortcut tab.
  3. Then enter the following line in the Target text box, as shown in the figure below:
  4. -disable-features=RendererCodeIntegrity.
  5. Select the Apply option.
  6. Click the OK button.
Edit the registry
  1. Press the Windows + R key combination, which will open the Run command.
  2. Type “Regedit” in the Open field and press Enter to open the registry editor.
  3. Navigate to the following registry key: HKLM -> Software -> Policies -> Google Chrome.
  4. Double-click the DWORD RendererCodeIntegrityEnabled on the right side of the window.
  5. Change its value to 0 in the Edit DWORD window.
  6. Click on the OK option.
Running chrome without a sandbox
  1. Right-click the Chrome shortcut icon on your desktop and select Properties.
  2. In the window that opens, click the “Shortcuts” tab.
  3. Then add -no-sandbox to the end of the Destination field as follows.
  4. Select the Apply option.
  5. Click the OK button.
Change the name of your Chrome executable
  1. Launch File Explorer with the Windows keyboard shortcut + E.
  2. Open the folder where the Chrome EXE file is located.
  3. Right-click Chrome EXE and choose Rename.
  4. Type Chrome as the new file title, but don’t change the EXE format at the end.

Here are some of the confirmed solutions to fix the Aw Snap Error in Google Chrome with Symantec Endpoint. However, keep in mind that you can always switch to browsers that do not have Endpoint Protection compatibility issues.


Frequently Asked Questions

Go to the following registry key: HKLM -> Software -> Policies -> Google Chrome. Double-click DWORD Renderer Code Integrity Enabled on the right side of the window. In the Edit DWORD window, change its value to 0. Click the OK option.

  1. Go to the "Start" menu.
  2. In the search box, type "Run" or "Win R".
  3. In the "Run" menu, type "Smc -stop" and click OK.
  4. Symantec endpoint protection should now be disabled.

  1. Then open the add/remove programs :
  2. Select Symantec Endpoint Protection Manager.
  3. Select Edit.
  4. Click Next.
  5. Select Repair and click Next.
  6. Click Install and the repair will begin.

  1. Symantec Endpoint Protection Open.
  2. In the left pane, click Change Settings.
  3. In the components list, find Exceptions and click Customize Settings.
  4. Under Custom Exceptions, click Add -> Security Risk Exception -> Web Domain.
  5. Under Trusted Domain Exception, type *.
  6. Click OK.

Website | + posts

Mark Ginter is a tech blogger with a passion for all things gadgets and gizmos. A self-proclaimed "geek", Mark has been blogging about technology for over 15 years. His blog,, covers a wide range of topics including new product releases, industry news, and tips and tricks for getting the most out of your devices. If you're looking for someone who can keep you up-to-date with all the latest tech news and developments, then be sure to follow him over at Microsoft.