14 DAY TRIAL // One of the issues that users are experiencing with Windows 10 build 10525, which was released a couple of days ago, is that Google Chrome fails to work on some machines, and for the moment, there seems to be just one fix that actually exposes the application to stability and security risks.
In a statement posted on the Chromium board, Google confirmed the issue, explaining that it's already aware of the problem and is looking for more feedback in order to fix it.
At the same time, Google also explained that this kind of errors is something to be expected because Windows 10 build 10525 is not a final version of the operating system and some of the changes that Microsoft does could affect apps running on your computer.
Windows 10 in preview stage
“We have the problem confirmed and someone is working on it, so additional "me to" 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,” Google explained.
“Also, please remember that this kind of temporary breakage is expected for users on the Windows 10 fast ring. So, we definitely appreciate your assistance in tracking down these problems, but if you're not comfortable dealing with disruptions and workarounds, then the fast ring might not be for you.”
At this point, the easiest way to address the problem is to run the application with the –no-sandbox (right-click the Chrome shortcut, click Properties, and add the –no-sandbox flag at the end of the target code), but this isn't recommended because the app can be exposed to additional security and stability risks.
At the same time, we've heard that x64 users can install the x86 build to fix the problem, but since Google is already aware of the issue, a patch should be on its way.