Issue with Google Chrome rendering after updates
We’ve all seen the all too familiar “Aw, snap!!” on a Google Chrome Tab. Well, the latest update makes that issue more likely than ever.
Issue:
Latest version of Chrome has a serious bug preventing all pages from loading in normal or incognito mode. The workaround at this time is to disable RendererCodeIntegrity which performs regular file integrity checks of executables to verify they have not been compromised.
Some articles suggest that it is related to only Symantec or other antivirus products, however we have confirmed this occurred on several off-domain systems without AV suggesting that the issue is more few websites that are skeptical are more than likely correct.
If you have any questions, contact support@phreedom.com
Workaround:
For Phreedom Clients:
Phreedom will be deploying this fix to all client systems with Chrome version 78 and setting our management system to also re-enable the RendererCodeIntegrity setting after Chrome version 81 which should release in ~3 months. This should happen automatically and require no end user intervention.
For non-Phreedom Users:
Have your IT person perform this update to your Windows 10 registry key at the command line.
REG ADD "HKLM\Software\Policies\Google\Chrome" /v RendererCodeIntegrityEnabled /t REG_DWORD /d 0
