Chrome on Windows will block third-party apps that cause crashes

Software that injects code into Chrome will be phased out by 2019.

Google says that around two-thirds of Windows Chrome users use third-party applications that interact directly with the web browser, like antivirus or accessibility software. These apps have typically injected code into Chrome to work correctly, but people that use these kinds of code-injecting apps on Windows are 15 percent more likely to see Chrome crashes. To curtail this issue, Google will start blocking code injection apps from Windows Chrome in three phases, starting in July 2018.

Chrome 66, due out in April of next year, will start warning users after a crash, telling them that injected code is the culprit for their issues, and then helping them remove the specific software. In July 2018, Chrome 68 for Windows will start blocking code injected by third-party software. If that keeps Chrome from launching, the browser will restart and allow it, but will also request that the user remove the software. In January of 2019, Chrome 72 will block apps that try to inject code automatically, no questions asked (though some software will still be allowed, like accessibility software, input method editors and Microsoft-signed code).