Many users who installed Chrome version 78 are experiencing the annoying ‘Aw Snap’ error. While the latest Chrome update brings a nice package of new features, such as new tab overlays, click-to-call or many more customization options, it basically makes the browser unusable for many.
This error affects both consumers and business users. Here’s how one user describes this annoying error.
When I open a google chrome tab, I get the “Aw Snap” crash error. Even when I click the 3 dots on the top right to go into the settings, any option I click will lead to another “Aw Snap” crash error. I have tried restarting my laptop, chrome, reinstalling, and checking for malware. All other recommendations for fixes require me to use the chrome menu, which as I said, I can’t even use without receiving another crash error.
As a quick reminder, as we previously reported, the same error affected Chrome Canary 78. Well, it seems that Google failed to fix the problem in the release version.
Symantec Endpoint Protection seems to be the culprit
Judging by user reports, it seems this problem is often caused by Symantec Endpoint Protection.
Google Chrome version 78.0.x error “Aw, Snap! Something went wrong while displaying this webpage.” when using a Symantec Endpoint Protection.
Symantec already officially acknowledged the issue on their support page.
When launching Google Chrome version 78.0.x or later, the message “Aw Snap! Something went wrong while displaying this webpage.” is present if any version of Symantec Endpoint Protection (SEP) is installed with the Application Control feature on Windows Server 2016. This issue also affects Microsoft Edge Chromium version 78.0x with an error message of “Page cannot be displayed”.
This happens because in Chrome 78 and Microsoft Edge Chromium 78, Microsoft’s Code Integrity feature is enabled. Unfortunately, as Symantec explains, the SEP Application Control technology is not compatible with this feature in Chrome/Chromium.
It is worth mentioning that this issue is affecting users who are relying on other cybersecurity products as well.
Not necessarily, I have a number of clients who aren’t using Symantec who also have this issue.
How to fix this problem
We already covered this Chrome error in an in-depth troubleshooting guide. Do check it out as it might help you to solve the problem — at least until an official solution is available.
If you’re using Symantec, and upgrading SEP is not an option, you can add an Application Control exception for Chrome.exe or MSEdge.exe.
Alternatively, you can switch to another browser. We recommend using UR Browser, a reliable privacy-focused browsing solution.