One look at the comments on the announcement of Google Chrome 58 coming to the stable channel will tell you that everything isn’t as it should be. Several enterprise users appear to have had serious issues now that Google Chrome 58 is auto-migrating 64-bit Windows systems to the 64-bit version of Chrome.
Google Chrome 58.0.3029.96 for Windows, Mac, and Linux was updated on the stable channel on May 2, and the rollout will happen over the next several days and weeks. But some enterprise users found that the auto-migration to 64-bit Chrome was essentially breaking their browsers, only displaying the “Aw, snap” error message, and not even allowing them to open settings.
Per the comments, users have tried various methods to get it to work, and a manual installation of the 32-bit Google Chrome version appears to be one of the workarounds to the problem.
The real fix has since been identified, as follows:
The issues appear to be affecting businesses that use Citrix XenApp 6.5 on Windows Server 2008 R2, as recorded in Issue 717834:
Multiple users are reporting Aww snap after upgrading to 58.0.3029.96 ( (Server 08 R2 via Citrix Netscalers for remote connectivity, Server 2008R2 with Citrix XenApp 6.5.)
Fortunately, a fix seems to have been found for this major bug, which has been described here, in Issue 432595:
We believe we found the root cause of this issue. Can you please follow these steps and help us confirm/verify this is the case?
On Citrix XenApp 6.5 Google Chrome has to be added to the exclusion list for hooks injection to prevent issues with the 64 bit executables of the browser as documented in Citrix Article CTX107825.
To accomplish this, please create or update the string value with name ExcludedImageNames with the text chrome.exe,nacl64.exe in HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\CtxHook. This workaround is not needed with Citrix XenApp 7 or newer.
That’s a full day of panic for Enterprise users – not something that system administrators are going to be very happy about considering that many of them are responsible for thousands and thousands of users unable to open anything on Google Chrome 58 since the auto-update and migration to 64-bit.
Why did Google Chrome 58 Update to 64-bit in the First Place?
The Google Chrome team says that they did this to “improve stability, performance and security,” but it was certainly a shocker to several enterprise sysadmins who came in to work on Tuesday to find their browsers broken.
Thanks for visiting! Would you do us a favor? If you think it’s worth a few seconds, please like our Facebook page and follow us on Twitter. It would mean a lot to us. Thank you.
Source: Google Chrome Blog
