Fix Chrome 79 crashes with Aw, Snap! error

The security feature built into Chrome 78 in Windows 10 caused problems for users running Symantec and other apps, Google recognized the issue and disabled the feature and asked affected users who received Aw, Snap! crash error messages when they launch Chrome to update their antivirus apps. Google recently re-enabled “Renderer Code Integrity” with the release of Chrome 79, and again, some users are experiencing browser crashes.

This time the feature will likely remain, now users need to ensure that the third party apps causing the issue are either updated or use the below methods to run Chrome v79 smoothly.

Here’s a little background on the new feature: To prevent antivirus and other third-party apps from injecting code into the Chrome browser, Google enabled the Renderer Code Integrity feature for Chrome in Windows 10, where apps that inject code into Chrome now cause browser to hit.

Chrome Community Manager Craig confirmed they shipped the new security feature with Chrome 79.

We’re following along to let you know that we plan to enable the underlying feature (Renderer Code Integrity) that resulted in the previous incompatibilities with the Chrome M79 release today.

It asks affected users to ensure their AVs are up to date and to contact antivirus companies to know their “compatibility times”. From now on, from the support topic in addition to Symatec Endpoint Protection PC Matic, Print Audit and Paulo Alt Traps, we can assume that other antivirus products such as Avast and McAfee are also causing this.

To avoid Aw, Snap! Chrome 79 crashes

I. Run Chrome with the following commadline swith

Chrome.exe --disable-features=RendererCodeIntegrity


II. Right-click the Chrome shortcut on the desktop, select “Properties”, click “open file location”, press F2 and rename “Chrome” to “chrom”.


III. Make this change to the registry.

1. Open the Run dialog box, type and run the command “regedit” without quotes

2. Navigate to HKEY_LOCAL_MACHINESOFTWAREPoliciesGoogleChrome

3. In the right pane, right-click New > DWORD (32-bit) Value to create a new key

4. Double-click it and enter the value name as “RendererCodeIntegrityEnabled” and the value data as 0.

RendererCodeIntegrityEnabled registry key

4. Restart Chrome.

Please note with the registry change above you added a new policy for Chrome, because of that you will see the message Managed by your organization or “your browser is managed” in the About pages and Chrome settings and menu, Firefox does too that and it’s completely normal.

Once your incompatible app receives an update for this issue, be sure to undo the above changes to benefit from the new protections offered by Chrome Browser.

Related Posts

Leave a Reply

Your email address will not be published.