Google says that about two-thirds of the users of Windows Chrome make use of third-party applications that directly interact with the web browser such as antivirus or accessibility software. These apps have normally injected code into Chrome for it to work correctly. However, people that make use of these kinds of code-injecting apps on Windows are fifteen percent more likely to experience Chrome crashes. To fix this issue, Google will begin blocking code injection apps from Windows Chrome in three phases, starting from July of next year.
Chrome 66 is scheduled to be released in April 2018. It will begin warning users after a crash, informing them that injected code is the culprit for the issues they experience. It will then help them remove the specific software. In July of next year, Chrome 68 for Windows will begin blocking codes that are injected by third-party software. If that blocks Chrome from launching, the browser will restart and enable it. However, it will also ask that the user eliminate the software. In January of 2019, Chrome 72 will prevent apps that attempt to automatically inject code, no questions asked (even though some software will still be allowed, such as input method editors, Microsoft-signed code, and accessibility software).