Latest Technology News

Aw, Snap! Something went wrong error on Google Chrome

Hello Friends

Hope you are doing well and enjoying all the posts.

Aw, Snap! Something went wrong error on Google Chrome

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.

Google Chrome version 78.0.x error “Aw, Snap! Something went wrong while displaying this web page.” when using a Symantec Endpoint Protection.

“Aw Snap” Crash on every page I try to open in Google Chrome.

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.

Symantec already officially accepted the issue on their support page.

This is due to the Symantec Application Control feature. 
Symantec Endpoint Protection (SEP) will need to be updated or removed. 


When launching Google Chrome version 78.0.x or later, the message “Aw Snap! Something went wrong while displaying this webpage.” is present if Symantec Endpoint Protection (SEP) 14.0 RU1 MP2 (14.0.3929.1200) or earlier is installed with the Application Control feature. This issue also affects Microsoft Edge Chromium version 78.0x with an error message of “Page cannot be displayed”.

Browser versions

  • Google Chrome 78.0.x (October 2019)
  • Microsoft Edge Chromium 78.0.x

SEP versions 14.0 RU1 MP2 (14.0.3929.1200) and older, including 12.1.

Error

In the Google Chrome browser:

Aw Snap! Something went wrong while displaying this web page.

In the Microsoft Edge Chromium browser:

Page Cannot be displayed.

In version 78.0.x of Google Chrome (chrome.exe) and 78.0.x of Microsoft Edge Chromium, Microsoft’s Code Integrity feature is enabled. Older versions of the SEP Application Control technology are not compatible with this feature in Chrome/Chromium. 

Cause

In version 78.0.x of Google Chrome (chrome.exe) and 78.0.x of Microsoft Edge Chromium, Microsoft’s Code Integrity feature is enabled. Older versions of the SEP Application Control technology are not compatible with this feature in Chrome/Chromium. 

Solution

Upgrade to SEP 14.2 or later

This issue is fixed in later versions of Symantec Endpoint Protection. To resolve this issue, download and install the latest version of Endpoint Protection from MySymantec.

If upgrading is not immediately an option, the incompatibility can be worked around by adding registry key for google chrome browser.Kindly make the registry changes(RendererCodeIntegrityEnabled to be added ) in machine key by group policy.

You can also add these registry setting manually in system if there are 2-3 users facing this issue. If there is high number of users then please go with gpo deployment.

HKEY_LOCAL_MACHINE\Software\Policies\Google\Chrome
DWORD (32-bit) Value name RendererCodeIntegrityEnabled to be added
Value Data = 0

Hope this solution will solve your problem .

So, that’s all in this blog. I will meet you soon with some other stuff. Have a nice day !!!

Recommended content

RODC Installation Guide- Step by step guide to install read only domain controller

RODC Filtered Attribute Set

Installing and configuring a RODC in Windows Server-2012

How to find the GUID of Domain Controller

Group Policy Understanding Group Policy Preferences

Group Policy Verification Tool GPOTool Exe

Group Policy Health Check on Specific Domain Controller

What is Netlogon Folder in Active Directory

How to Create Custom Attributes in Active Directory

How Can I Check the Tombstone Lifetime of My Active Directory Forest

How to Determine a Computers AD Site From the Command Line

How to Check the Active Directory Database Integrity

How to Check the Active Directory Database Integrity

Disabling and Enabling the Outbound Replication

DFS Replication Service Stopped Replication

What is Strict Replication Consistency

The replication operation failed because of a schema mismatch between the servers involved

Troubleshooting ad replication error 8418 the replication operation failed because of a schema mismatch between the servers

How to export replication information in txt file

Repadmin Replsummary

Enabling the outbound replication

Guys please don’t forget to like and share the post. You can also share the feedback on below windows techno email id.

If you have any questions feel free to contact us on admin@windowstechno.com also follow us on facebook@windowstechno to get updates about new blog posts.

How useful was this post?

Click on a star to rate it!

As you found this post useful...

Follow us on social media!

Was this article helpful?
YesNo

Vipan Kumar

He is an Active Directory Engineer. He has been working in IT industry for more than 10 years. He is dedicated and enthusiastic information technology expert who always ready to resolve any technical problem. If you guys need any further help on subject matters, feel free to contact us on admin@windowstechno.com Please subscribe our Facebook page as well website for latest article. https://www.facebook.com/windowstechno
Back to top button