Share this article

Improve this guide

How to fix Google Chrome not working with Symantec Endpoint

3 min. read

Updated onOctober 4, 2023

updated onOctober 4, 2023

Share this article

Improve this guide

Read our disclosure page to find out how can you help Windows Report sustain the editorial teamRead more

In October 2019, users started posting on theSymantec support forumabout an Aw Snap error that arises inChromewhen they start thebrowser.

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 andGoogle Chromebrowsers 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?

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 theRU2 MP1 client-only patches page. That page includes instructions for how you can download the latest patch and update thesoftwarewith it.

2. Deactivate Chrome’s renderer code

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

3. Edit the registry

If you have issues opening the Registry Editor, check out thisdetailed guidefor some quick fixes.

4. Launch Chrome with no sandbox

Edit Chrome’s exe file title

Those are a few of the resolutions confirmed to fixGoogle 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.

[wl_navigator]

More about the topics:Google Chrome Errors

Matthew Adams

Windows Hardware Expert

Matthew is a freelancer who has produced a variety of articles on various topics related to technology. His main focus is the Windows OS and all the things surrounding it.

He is passionate about the tech world, always staying up-to-date with the latest and greatest. With an analytical view, he likes problem-solving, focusing on errors and their causes.

In his free time, he likes to read and write about history and tries to always develop new skills.

User forum

1 messages

Sort by:LatestOldestMost Votes

Comment*

Name*

Email*

Commenting as.Not you?

Save information for future comments

Comment

Δ

Matthew Adams

Windows Hardware Expert

He is passionate about everything surrounding Microsoft’s OS, focusing on troubleshooting guides & tips for everyday problems.