Chrome 78 has now disabled renderer code integrity protection due to incompatibilities

In addition to Symantec’s Endpoint Protection, Google also found that the new Render Code Integrity Protection feature in Chrome 78 was incompatible with three other antivirus software. To further avoid a Chrome browser crash, Google has disabled the security feature and says it has stepped up efforts with third-party security companies to improve compatibility with the feature. Google said it would reopen the feature after the problem was resolved.

因不兼容问题 Chrome 78现已禁用渲染器代码完整性保护功能

Google released a stable version of Chrome 78 for Windows, Mac, and Linux platforms on October 22, 2019. The new version brings several features and improvements and is enabled by default on Windows 10 (version 1511 plus) systems.

The goal of the RenderEr Code Integrity Protection feature is ‘to prevent unsigned modules from being loaded into chrome’s renderer process’, but unfortunately encountered incompatibility on some systems.

The Chrome team has acknowledged the tab crash reports submitted by users and is wanted to share information in the Help Forum to better fix the problems that Chrome’s new security features may have caused third-party security software to fall wrong. This is particularly true with Symantec SEP (14.0.3929.1200 and earlier), so Google recommends that affected users update to version 14.2 plus as soon as possible.

Google recommends that other users disable Chrome 78’s Render Er Code Integrity protection feature if necessary.

(1) Right-click on the Chrome shortcut on your desktop and select Properties.

(2) Add the following command line at the end of the ‘Target’ field –disable-features-RendererCodeIntegrity

(3) Click on ‘App’ and restart Chrome 78.

Or replace the browser’s executable with the “Chrome.exe” from “Chrome.exe” as follows and see if it works.

C: sprogram Files (x86) \Google\Chrome\Application

Add a Comment

Your email address will not be published. Required fields are marked *