Latest Chrome Canary build works well on Windows 10 build 10525

Reading time icon 2 min. read

Readers help support Windows Report. We may get a commission if you buy through our links. Tooltip Icon

Read our disclosure page to find out how can you help Windows Report sustain the editorial team Read more

Chrome users who recently installed Microsoft’s latest Windows 10 Insider build, 10525, may be experiencing some issues. A Chrome related bug on the Windows 10 Insider build surfaces for users specifically browsing with Google’s Chrome beta browser with 64-bit support.
Since the release of Windows 10 Insider build 10525, Windows and Chrome forums have populated with complaints of the 64-bit version hanging and or crashing when in use. Similar to the YouTube for Windows Phone situation, the Chrome team attempted to develop around Microsoft’s APIs for Windows 10, rather than using the costly official tools for Microsoft’s 64-bit systems. Understandably, the Chrome team chose to find a solution that did not cost $9,995 (the cost of Microsoft’s 64-bit tools) to implement. Unfortunately, for the Chrome team, without the official tools, the beta version of the Chrome browser fell victim to the new way Windows 10 manages memory.
Fortunately, the Chrome team has a solution in the works and is pushing an update through their Canary channel. The Canary channel is similar to the Windows 10 Insider program, in that it is a testing ground for future Chrome updates. The Chrome team has issued an update that carries “support for int 2e fallback system call stub in Win10” and as of right now; the update is currently working on the 64-bit Chrome Canary version 46.0.2489.0. There are probably still a few more days if not weeks of testing to be done before the beta channel lands the fix. Until the fix is pushed out to the Chrome beta channel, users on Windows 10 Insider build 10525 are encouraged to use the ‘no-sandbox’ version to avoid crashes.