Google Chrome And Windows 10 Build 10525: It’s Not Working

Google Chrome and Windows 10 appear to have fallen out with each other. But no one is  forcing anyone to use Microsoft’s new Edge browser….just yet. 

Microsoft released the new preview of version Windows 10 build 10525 to Windows Insiders earlier this week, and it was jumped on by large swathes of users eager to get their mittens on the latest version Windows 10.

If you’re running Windows 10 at the moment and are reading this post using Google Chrome, but have no idea what a “Windows Insider” is, then this in all likelihood does not affect you; so go make some coffee, come back, relax, and then read on.

The idea behind the Windows Insider program is that Microsoft allows users to be voluntary guinea pigs to new builds of Windows 10, and help Microsoft to iron out things that just don’t work before the average Windows 10 user is allowed to have it. This allows Microsoft to test things for free, and in turn,  the Insiders get to play with the new stuff before anyone else. The original Insiders program was supposed to end with the official release of Windows 10 back in July, but due its success, will now be kept going indefinitely.

Improvements and bugs are to be expected in the “preview builds,” and the new build, 10525, has not proved to be an exception. So far the most noticeable bug has been to do with the Google Chrome 64 bit version of its browser. Opening the 64 bit version of Google Chrome in Windows 10 build 10525 will give users an error message, and then just crash instantly.

The boffins in Google have been inundated with people reporting the error, but have confirmed that ‘someone is working on it,’ going as far as to say that “additional “me to” comments are a distraction at this point.”

Aside from not knowing the difference between ‘to’ and ‘too,’ it’s safe to say that Google will have the issue resolved sooner rather than later.

There are workarounds for Google Chrome 64 and Windows 10 build 10525, but the best bet presently is to either use the 32 bit version of Chrome, or shift to another browser like Firefox…or dare I say it even Edge on a temporary basis.