It happens to be the first preview build of the operating system, since Windows 10 was launched on July 29th.
Even though it isn’t much of an upgrade, it adds some new features like customizing the color of the Start Menu, Taskbar, Action Center and more. But there is something beyond that, which users didn’t anticipate.
What was thought to be a build which fixes bugs, instead caused a new one. And it is a massive bug. Windows 10 Build 10525 breaks the functionality of Google Chrome. The browser refuses to launch, and crashes immediately after you click on the icon to launch it.
So, if you are a Google Chrome user, who has upgraded to Build 10525, this must be incredibly annoying. Here is a bug tracker at the Chromium Project website (Chrome is based on Chromium), which mentions the very issue.
Google has not released an update to fix the issue, but fret not. Fortunately, there are some workarounds which you can try, courtesy Microsoft-News.
How to fix Google Chrome not working on Windows 10 Build 10525:
Method 1:
- If you are using the 64-bit version of Google Chrome, uninstall it.
- Head to Google Chrome’s webpage, and download a fresh copy of the browser’s 32-bit version and install it on your PC.
It should work, if it doesn’t, read on to try the other fix.
Method 2:
1. First, right-click on the Google Chrome shortcut on your desktop, and select Properties.
2. Click on the text-box, next to “Target”.
3. You will see a long file path, this is the location of the EXE, which the shortcut runs when it is clicked upon. At the very end of the file path, you will see a double quote”.
4. Press the space bar once, and copy the following command, and paste it in the textbox.
-–no-sandbox
For example, it should look like this: “C:\Program Files (x86)\Google\Chrome\Application\chrome.exe” –no-sandbox
5. Click on Apply, and then on OK, to close the properties window.
6. Now try running Chrome, and it will work.
You can try this even if you want to hang-on to Google Chrome 64-bit.
This will disable Google Chrome’s sandbox, so if you feel that is a bit risky, do not try it. Just delete the –no-sandbox, command line flag to restore it to the original state.
This should be considered a temporary workaround, until Microsoft rolls out a to fix for the problem. And it is unlikely that the Redmond Cpmpany will release this build in its current state to the Slow Ring members of the Insider Program.
