Microsoft recently released the first Windows 10 post-RTM build for insiders, but it is still far from bug-less. Reportedly, a lot of users of Google Chrome who are testing the latest build 10252 said that the browser just crashes, for no particular reason.
According to various reports, the 64-bit version of Google Chrome doesn’t work in Windows 10 build 10252. On the other hand, the 32-bit version works just fine. You can try it yourself, just run the 64-bit version of Google Chrome, and you’ll probably get a crash report and a bunch of error messages.
So, why does this happen? Google Chrome uses a special technology called “sandbox,” which isolates the browser’s processes in order to reduce the vulnerability of the browser, and reduce a chance for malicious software to get to your computer. “Cutting through the noise, it looks like the sandbox is breaking in the Win10 10525 previews for 64-bit Chrome,” said Justin Schuh, a Google software engineer, in one of his messages on the Chromium bug tracker.
Apparently, some aspects of the latest Windows 10 build conflict with the sandbox technology, which prevents Google Chrome from working on build 10252 of Windows 10 for Insiders. So, if you want Google Chrome to work, you’ll need to disable the sandbox feature.
To disable the sandbox technology in your Google Chrome browser, do the following:
- Right-click on your Desktop shortcut of the Chrome browser and go to Properties
- Go to Shortcut tab and click on the Target: field
- Type space at the end of the path in Target: filed and enter the following: –no-sandbox
- Click OK, and use that shortcut to launch Google Chrome
This should restore the functionality of Google Chrome in Windows 10 build 10252, but it takes some risks with it. Namely, when you disable the sandbox feature of your Chrome browser, it will become more vulnerable, and potential malicious content will find easier way to enter your computer through the Google Chrome browser.
But, if you don’t want to mess with your security in the Chrome browser, you can switch to the 32-bit version, or maybe try another browser, until Microsoft comes up with the solution. And, since this issue is now widely reported, I’m sure that Microsoft’s developers will start working on the solution, along with the fixes for other bugs from Windows 10 build 10252.
If you’re still having issues on your PC or you simply want to avoid them for the future, we recommend you to download this tool (100% safe and tested by us) to fix various PC problems, such as file loss, malware and hardware failure.
If you have any other Windows 10-related issues you can check for the solution in our Windows 10 Fix section.