Fix: Google Chrome Enterprise 58.0.3029.96 breaks on XenApp 6.5 / Windows Server 2008 R2 – UPDATE

Fast published to help everyone else, so sorry for any typos or grammatical errors! ty

On Tuesday the 2nd May 2107 Google published a new update for Google Chrome Enterprise 58.0.3029.96. After this update, nearly all of our XenApp 6.5 customers informed us, that Google Chrome stopped working for them. The browser itself opens, but it never displays any content:

I took a while to figure it the problem. In the first place I found two Google discussion, the first Link led me to the second link:

https://chromereleases.googleblog.com/2017/05/stable-channel-update-for-desktop.html

https://productforums.google.com/forum/#!topic/chrome/ptsYxZLowxM;context-place=forum/chrome

That’s where I found the important hint:

Some more info, we were running 32bit Chrome and according to this https://chromereleases.googleblog.com/2017/05/stable-channel-update-for-desktop.html Chrome is automatically updating to the 64 bit version for users running a 64 bit OS with 4 GB RAM or more.

For some reason I’m not aware of yet, the x64 version of Google Chrome Enterprise doesn’t work on all or nearly all of our XenApp 6.5 servers. I did a quick test of uninstalling Chrome and reinstalling Google Chrome Enterprise x86 which resolved the problem immediately!

So long story short, I built a package for PDQ Deploy and will also tell you the manual steps I did to resolves our issues:

1. %SYSTEMROOT%\System32\taskkill.exe /f /im chrome.exe
2. MsiExec.exe /qn /norestart /X{69BDE82E-C14F-3309-9813-E5F4E6111920}
3. MsiExec.exe /qn /norestart /X{A4690197-328E-3732-A460-124D6900D9C5}
4. msiexec.exe /i "googlechromestandaloneenterprise-58.0.3029.96.msi" ALLUSERS=1 /qn /norestart /log output.log

I have also the PDQ XML file for you:

FIX_Google_Chrome_Enterprise_58.0.3029.96.xml (1469 downloads )

I hope I could help anybody!

Alternate Download Link: https://files.meinekleinefarm.net/f/d5fddd53cd/

UPDATE: Thanks to a users comment below this article, we now know, that the root cause are the api hooks from XenApp 6.5, see the following links for a further explanation:

http://1reddrop.com/2017/05/03/google-chrome-58-migration-64-bit-major-issues-enterprise-users/

https://support.citrix.com/article/CTX107825