Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
Software
Browsers
Chrome & Chromium
How To Fix "Aw Snap!" Crash in Google Chrome 78
Message
<blockquote data-quote="DDE_Server" data-source="post: 841416" data-attributes="member: 65727"><p><img src="https://www.bleepstatic.com/content/posts/2019/10/24/Google_Chrome_Symantec.jpg" alt="" class="fr-fic fr-dii fr-draggable " style="" /></p><p>Google Chrome updated to version 78 a few days ago and some users have been experiencing "Aw, Snap!" crashes instead of the <a href="https://www.bleepingcomputer.com/news/software/chrome-78-released-with-doh-trial-tab-hover-cards-and-more/" target="_blank">promised features</a>.</p><p>This disruption occurs when launching the web browser on systems with an outdated version of Symantec Endpoint Protection (SEP).</p><p><span style="font-size: 22px"><strong>Incompatibility problem</strong></span></p><p>Since the release of the newest Google Chrome on Tuesday, a large number of users started to complain that they could not use it.</p><p>When starting Chrome, users would see the "Aw Snap!" message specific to a page crash.</p><p><img src="https://www.bleepstatic.com/images/news/u/1100723/AwSnap.png" alt="" class="fr-fic fr-dii fr-draggable " style="" /></p><p>Most of the reports came from users that did not have the latest version of Symantec Endpoint Protection installed. An investigation from both Google and Symantec confirmed this to be true.</p><p>In a blog post on Thursday, Symantec explains that the problem is an incompatibility between the <a href="https://www.symantec.com/content/dam/symantec/docs/data-sheets/endpoint-application-control-en.pdf" target="_blank">Application Control</a> technology in its product and Microsoft's Code Integrity feature enabled in Chrome browser.</p><p>Microsoft Edge Chromium is also impacted by this issue but the browser has not been officially released so the user base affected is limited.</p><p><span style="font-size: 22px"><strong>The solutions</strong></span></p><p>Symantec <a href="https://support.symantec.com/us/en/article.tech256047.html" target="_blank">details</a> that systems affected by this problem are Windows Server 2012, 2016, and Windows 10 RS1 with any version of SEP installed. </p><p>Any other Windows operating systems running a version of SEP older than 14.2 are also impacted. On these, updating to the latest SEP should fix the issue.</p><p>A workaround exists for all other cases and it consists of adding an Application Control exception for the Google Chrome and Microsoft Edge Chromium executables (Chrome.exe and MSEdge.exe).</p><p>An alternative to this is to run Chrome with the Code Integrity feature disabled, which can be achieved in two ways:</p><p>Chrome.exe –disable-features=RendererCodeIntegrity</p><p>or by setting a registry key to 0:</p><p>Key: HKLM\Software\Policies\Google\Chrome</p><p>Name: RendererCodeIntegrityEnabled</p><p>Type: DWORD (32-bit)</p><p>Value: 0</p><p>Since a swarm of users reported the "Aw Snap!" crash problem, Google investigated as well, its <a href="https://support.google.com/chrome/thread/17555930?hl=en" target="_blank">conclusion</a> being that an update to SEP 14.2 or above would do away with the incompatibility.</p><p>Disabling the protection in Chrome through the <a href="https://cloud.google.com/docs/chrome-enterprise/policies/?policy=RendererCodeIntegrityEnabled" target="_blank">RendererCodeIntegrityEnabled</a> policy in the browser is listed as a solution, too, albeit not a recommended one because it's purpose is to protect the browser process.</p><p>Some users already <a href="https://www.reddit.com/r/chrome/comments/dmif5z/aw_snap_chrome_no_longer_works_if_you_have_older/" target="_blank">reported</a> that updating SEP to the latest version allowed them to use Google Chrome as before.</p></blockquote><p></p>
[QUOTE="DDE_Server, post: 841416, member: 65727"] [IMG]https://www.bleepstatic.com/content/posts/2019/10/24/Google_Chrome_Symantec.jpg[/IMG] Google Chrome updated to version 78 a few days ago and some users have been experiencing "Aw, Snap!" crashes instead of the [URL='https://www.bleepingcomputer.com/news/software/chrome-78-released-with-doh-trial-tab-hover-cards-and-more/']promised features[/URL]. This disruption occurs when launching the web browser on systems with an outdated version of Symantec Endpoint Protection (SEP). [SIZE=6][B]Incompatibility problem[/B][/SIZE] Since the release of the newest Google Chrome on Tuesday, a large number of users started to complain that they could not use it. When starting Chrome, users would see the "Aw Snap!" message specific to a page crash. [IMG]https://www.bleepstatic.com/images/news/u/1100723/AwSnap.png[/IMG] Most of the reports came from users that did not have the latest version of Symantec Endpoint Protection installed. An investigation from both Google and Symantec confirmed this to be true. In a blog post on Thursday, Symantec explains that the problem is an incompatibility between the [URL='https://www.symantec.com/content/dam/symantec/docs/data-sheets/endpoint-application-control-en.pdf']Application Control[/URL] technology in its product and Microsoft's Code Integrity feature enabled in Chrome browser. Microsoft Edge Chromium is also impacted by this issue but the browser has not been officially released so the user base affected is limited. [SIZE=6][B]The solutions[/B][/SIZE] Symantec [URL='https://support.symantec.com/us/en/article.tech256047.html']details[/URL] that systems affected by this problem are Windows Server 2012, 2016, and Windows 10 RS1 with any version of SEP installed. Any other Windows operating systems running a version of SEP older than 14.2 are also impacted. On these, updating to the latest SEP should fix the issue. A workaround exists for all other cases and it consists of adding an Application Control exception for the Google Chrome and Microsoft Edge Chromium executables (Chrome.exe and MSEdge.exe). An alternative to this is to run Chrome with the Code Integrity feature disabled, which can be achieved in two ways: Chrome.exe –disable-features=RendererCodeIntegrity or by setting a registry key to 0: Key: HKLM\Software\Policies\Google\Chrome Name: RendererCodeIntegrityEnabled Type: DWORD (32-bit) Value: 0 Since a swarm of users reported the "Aw Snap!" crash problem, Google investigated as well, its [URL='https://support.google.com/chrome/thread/17555930?hl=en']conclusion[/URL] being that an update to SEP 14.2 or above would do away with the incompatibility. Disabling the protection in Chrome through the [URL='https://cloud.google.com/docs/chrome-enterprise/policies/?policy=RendererCodeIntegrityEnabled']RendererCodeIntegrityEnabled[/URL] policy in the browser is listed as a solution, too, albeit not a recommended one because it's purpose is to protect the browser process. Some users already [URL='https://www.reddit.com/r/chrome/comments/dmif5z/aw_snap_chrome_no_longer_works_if_you_have_older/']reported[/URL] that updating SEP to the latest version allowed them to use Google Chrome as before. [/QUOTE]
Insert quotes…
Verification
Post reply
Top