Microsoft released a new Insider build, the first one after the Windows 10 launch, and many users are now experiencing issues with the Google Chrome browser.
More specifically, each time you open the 64-bit version of Chrome in the latest build 10525 on Windows 10, all tabs crash instantly, displaying an error message. Closing the browser and opening it again will result in the same crash.
Google believes that there is indeed an issue and it is trying to resolve everything as soon as possible. The company wrote a brief message to ensure users that it is working on a fix.
"We have the problem confirmed and someone is working on it, so additional 'me too' comments are a distraction at this point. Please just star the issue if you want to convey that you are affected, and if we have any questions or need additional feedback we'll post a comment," stated the company.
Google further points out that users in the Windows 10 fast ring should expect this sort of issue since "disruptions and workarounds" are part of the fast ring experience.
While Google is working on solving the issues, however, users can also try a couple of workarounds to get Chrome going without hiccups. First of all, it appears that the problem only affects the 64-bit version of the browser, so the first workaround is to use the 32-bit version.
If, on the other hand, you're keen on using the 64-bit Chrome version, you can try a temporary fix to resolve the crashing issue in just a few steps. First, pin Chrome to the desktop. Go to the newly created shortcut, right-click on it and select Properties > No Sandbox > OK. From here on, you'll be able to continue only if you have administrative privileges.
The next time you launch Chrome, you'll see a warning message, but other than that, it should work normally without crashing. On the other hand, it's worth pointing out that this temporary fix for the 64-bit version of the browser doesn't do the trick for Canary builds for now.
As previously mentioned, these are just quick, temporary fixes to work around the issue, but it's still up to Google to properly resolve the problem. Considering that the company is aware of the issue and is working on it, it shouldn't take too long now for the 64-bit version of Chrome to work well with the Windows 10 build 10525.
