Here's a workaround for Chrome crashes in Windows 10 build 10525

[Batu69]

Yesterday, Microsoft kicked off the second round of Windows 10 core updates with build 10525, providing you opted to "Get Insider builds" and have linked your Microsoft ID to the Windows Insider program. The next major update for Windows 10 is expected to ship in the fall as Wave 2 and Insiders will be providing feedback on that process before it happens.

Although Microsoft informed users of the "known issues" with Windows 10 build 10525, one particular issue that was overlooked relates to the 64-bit version of Google Chrome. Whenever the browser is launched in 10525, all tabs crash and you are presented with the following message:

No websites load and all plugins and extensions crash with the above message, reading: “Aw, Snap! Something went wrong while displaying this webpage. Closing the apps and tabs that you don't need may help by making more memory available.” Not cool.

Fortunately there are two workarounds. The first: reinstall the Chrome 32-bit version, this fixes the issue (Thanks Tom!); or, if you want to keep the 64-bit version - you will need to locate the shortcut to Chrome, by searching for it in the Start menu and opening the file location by right clicking on the Chrome entry.

Then right click on the shortcut which is shown in the folder and add on the end of the target path --no-sandbox as shown in the image above.

This is not a recommended way to run Chrome, as it could affect the stability of the app, but the issue has been reported to Google, and no doubt a fix will probably be a high priority for the company, as this affects all versions in the stable, beta and dev channels.

Should you use this workaround, keep an eye out for fix announcements and remember to remove the --no-sandbox flag once it is no longer an issue.

We will update this article once Google has both acknowledged the problem and announced a fix.

Source

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Windows 10 Build 10525 breaks Chrome; here's how to fix it

Chrome users who rush to install the latest build of Windows 10 have found that their favorite browser is broken. Build 10525 of Windows 10 prevents Chrome from working properly -- launch the browser and you'll be greeted by a series of notification saying that plugins have crashed.

Additionally, when attempting to visit any website, all that is displayed is an error message that reads "Aw, Snap! Something went wrong while displaying this webpage.

Closing the apps and tabs that you don't need may help by making more memory available". The compatibility issue has been reported to Google so a patch will be forthcoming soon, but in the meantime you can use this workaround.

It appears the problem only affected 64-bit versions of Windows, and it's not clear how many people have experienced the issue. The simple solution to getting Chrome up and running again is to use the --no-sandbox flag. This is not something that is normally recommended, as it brings Chrome processes out of their protected, sandboxed state, but as a temporary measure -- and to avoid having to switch browsers for too long -- it's fine.

• Right click on click on the desktop shortcut to Chrome and select Properties.
• Move to the Shortcut tab and click in the Target field.
• Type a space at the end of the path that appears in the field followed by --no-sandbox.
• Hit OK, and use the shortcut to launch Chrome.

You'll notice an information bar at the top of the screen that reads "You are using an unsupported command-line flag: --no-sandbox. Stability and security will suffer" but Chrome will at least be working once again.

Note the warning, and just hope that Google or Microsoft push out a fix soon.

Source