- Chrome Version 78 Slow
- Chrome Version 78 Crashes
- Chrome Version 78
- Chrome Version 78 Crashed
- Chrome Version 78
Hello Friends
Hope you are doing well and enjoying all the posts.
Today we are going to provide the solution for 'Aw, Snap! Something went wrong while displaying this web page.' error as this will come in coming days once google chrome's released the next updates.This registry solution has been testing in test environment and registry fix able to resolved this issue.
Chrome OS is based on the underlying technology of the Chrome browser - this is why the version numbers of Chrome OS and Chrome Browser are always almost identical - eg Chrome OS v78 ships with Chrome Browser v78.
- The device you have runs on Chrome OS, which already has Chrome browser built-in. No need to manually install or update it — with automatic updates, you'll always get the latest version.
- Google Chrome updated to version 78 a few days ago and some users have been experiencing 'Aw, Snap!' Crashes instead of the promised features. This disruption occurs when launching the web browser.
SEP will cause Chrome/Edge 78 to break in coming days as Google Chrome's next update which is scheduled 22nd October 2019, would not work with Symantec Endpoint Protection (SEP) 14.0 RU1 MP2 (14.0.3929.1200)SEP version. Symantec has released an article for this which can be read further at location : https://support.symantec.com/us/en/article.tech256047.html
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:
In the Microsoft Edge Chromium browser:
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.
HKEY_LOCAL_MACHINESoftwarePoliciesGoogleChrome
DWORD (32-bit) Value name RendererCodeIntegrityEnabled to be added
Value Data = 0
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.
HKEY_LOCAL_MACHINESoftwarePoliciesGoogleChrome
DWORD (32-bit) Value name RendererCodeIntegrityEnabled to be added
Value Data = 0
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 onadmin@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!
Hello Friends
Hope you are doing well and enjoying all the posts.
Today we are going to provide the solution for 'Aw, Snap! Something went wrong while displaying this web page.' error as this will come in coming days once google chrome's released the next updates.This registry solution has been testing in test environment and registry fix able to resolved this issue.
SEP will cause Chrome/Edge 78 to break in coming days as Google Chrome's next update which is scheduled 22nd October 2019, would not work with Symantec Endpoint Protection (SEP) 14.0 RU1 MP2 (14.0.3929.1200)SEP version. Symantec has released an article for this which can be read further at location : https://support.symantec.com/us/en/article.tech256047.html
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.
Chrome Version 78 Slow
Error
In the Google Chrome browser:
In the Microsoft Edge Chromium browser:
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
Chrome Version 78 Crashes
Chrome latest version download 32 bit. 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.
HKEY_LOCAL_MACHINESoftwarePoliciesGoogleChrome
DWORD (32-bit) Value name RendererCodeIntegrityEnabled to be added
Value Data = 0
Chrome Version 78
Guys please don't forget to like and share the post. You can also share the feedback on below windows techno email id.
Chrome Version 78 Crashed
If you have any questions feel free to contact us onadmin@windowstechno.com also follow us on facebook@windowstechno to get updates about new blog posts.
Chrome Version 78
How useful was this post?
Click on a star to rate it!
