This error affects both consumers and business users. Here’s how one user describes this annoying 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. Symantec already officially acknowledged the issue on their support page. 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.
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.
Aw, Snap! Something went wrong error on Google Chrome
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.
Name *
Email *
Commenting as . Not you?
Save information for future comments
Comment
Δ
