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.
  • 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.
  • The problem also affects the Microsoft Edge version of Chromium, but the updated browser is not yet available to the public.
Updated April 2024This tool will stop these errors and fix common problems: Get it at this link
  1. Download and install the software.
  2. It will scan your computer to find problems.
  3. The tool will then correct the issues that were discovered.

Microsoft Edge Compatibility Problem

The Microsoft Edge browser may display error messages without any explanation of the problem, crash on startup, or won’t open at all in some cases. For example, you might not be able to load websites correctly or render pages very slowly. As well as problems syncing favorites, passwords, and other data, you could also face problems if you use it with a Microsoft account.

The new Chrome 78 features were not available to Symantec Endpoint Protection (SEP) users, as the browser crashed on startup and would not load.

Most of the complaints came from companies where SEP is typically used. Reddit posts about the bug also popped up in droves.

Symantec Endpoint Protection Manager Download

In this scenario, you send an email message with instructions for downloading and installing the client installation package to a list of specified users. The recipients follow the instructions and the client software is installed.

This error occurs when there are no pages to load in the browser, and you will receive an “Aw, Snap” message.

An interim solution for resolving the issue has already been offered by Symantec in their newsletter.

In order to resolve the Google Chrome compatibility issue, the latest version of Symantec Endpoint 14.2 must be installed. To update Endpoint protection, visit the patch page of RU2 MP1. The Endpoint patch must be installed and updated to ensure a better function.

Among other Windows versions with SEP versions earlier than 14.2, the bug affects all versions of Windows 10 RS1, Windows Server 2012, and Windows Server 2016. The updated version of Chromium, which is not yet available to the public, is also affected by the problem.


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.

Sepm Log4j

Remote code execution vulnerabilities exist in log4j, which is used by Symantec Endpoint Protection manager.

Please contact the software publisher if this version of C:/Users/Administrator/Downloads/Symantec Endpoint Protection Manager Console/bin/javaw.exe doesn’t work.

Chrome 78 and 79, as well as Symantec Endpoint Edition with 14.2 RU2 MP1, will display these errors on the various versions of Chrome.

Symantec Endpoint Protection Log4j

It exists because LDAP requests aren’t properly validated on the target system when processing LDAP requests.


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

Updated: April 2024

We highly recommend that you use this tool for your error. Furthermore, this tool detects and removes common computer errors, protects you from loss of files, malware, and hardware failures, and optimizes your device for maximum performance. This software will help you fix your PC problems and prevent others from happening again:

  • Step 1 : Install PC Repair & Optimizer Tool (Windows 10, 8, 7, XP, Vista).
  • Step 2 : Click Start Scan to find out what issues are causing PC problems.
  • Step 3 : Click on Repair All to correct all issues.


The majority of my time is dedicated to writing and managing content (as of recently I earned a bachelor’s degree in marketing from Gustavus Adolphus College) but I am also very passionate about studying cyber security as I can’t get enough of it.

If ChromeNativeMessaging.exe could not be started, the following warning is displayed:

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

Updating Symantec Endpoint Protection

It is recommended that you update Symantec Endpoint to the latest version 14.2 to fix the SEP incompatibility with Chrome issue. You can download the latest Endpoint Protection build (5569) on the RU2 MP1 client patch page. This page provides instructions on how to download and install the latest patch.

Disable Chrome rendering engine code

  1. You can access Google Chrome’s properties by right-clicking the shortcut on your desktop.
  2. Click Shortcuts.
  3. Below, you can see how you should add the following line to the Target text box:
  4. Disable features like RendererCodeIntegrity.
  5. Click on Apply.
  6. Then click OK.

Edit the registry

  1. Run is opened when you press Windows+R.
  2. To open the registry editor, type “Regedit” and press Enter.
  3. HKLM – Software – Policies – Google Chrome is the registry key where you can find it.
  4. You can enable renderer code integrity by double-clicking the DWORD RendererCodeIntegrityEnabled.
  5. The Edit DWORD window should be set to 0 now.
  6. Select OK.

Running chrome without a sandbox

  1. Choose Properties from the right-click menu when you are on your desktop.
  2. Choosing “Shortcuts” will open a new window.
  3. Add the following to the Destination field: -no-sandbox.
  4. Click on Apply.
  5. Then click OK.

Change the name of your Chrome executable

  1. By pressing Windows Key + E, you will be able to launch File Explorer.
  2. Chrome’s EXE file can be found in the Chrome folder.
  3. Choose Rename from the right-click menu when you are left-clicking Chrome EXE.
  4. Change Chrome’s title to Chrome, but don’t change its format to EXE.

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.


RECOMMENATION: Click here for help with Windows errors.

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.