Issue metadata
Sign in to add a comment
|
Legacy Browser Extension 5.0 not working on Windows XP
Reported by
blacksta...@gmail.com,
Oct 5 2017
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 5.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.112 Safari/537.36 Steps to reproduce the problem: 1. Install Google Chrome Enterprise with LBS 4.0 2. Chrome gets updated and updates LBS to 5.0 3. When Chrome runs and executes LBS 5.0 users are getting an error that the executable is not a valid Win32 application. What is the expected behavior? The LBS extension 4.0 works OK but it gets automatically updated and renders our browser switching policies unusable, this happens since september 27 when the extension was updated to 5.0 What went wrong? The LBS extension got update to version 5.0 from version 4.0 and it seems that the compilation has an issue with Windows XP, either it wasn't compiled with support for this platform or something else happened. The LBS 5.0 x86 version is working correctly on Windows 7 (x64). Did this work before? Yes 4.0 Chrome version: 49.0.2623.112 Channel: stable OS Version: 5.1 (Windows XP) Flash Version: Shockwave Flash 22.0 r0 AFAIK LBS version 4.0 was operating normally. We have gotten many support calls from users that couldn't work normally after the update. Please correct the anomaly for the x86 version of the legacy extension (msi installation).
,
Oct 6 2017
,
Oct 9 2017
Julian, would you take a look (or route accordingly)? Thanks!
,
Oct 9 2017
Unfortunately XP is not a supported platform for Chrome and LBS (or Windows for that matter) anymore. Our internal build infrastructure has also now completely removed support for XP which used to be possible until recently.
You can try to stay on v4 by using Google Update's policies to disable auto-updating the LBS application by creating the registry key
"HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Update\Update{00EBA25B-97AB-475A-BD68-C3B6C9E94260}" as DWORD with value 0.
None of those components are supported on XP anymore though and as such are not guaranteed to work and using outdated software and os is a security threat to your organization! Therefore apart from this advice I am closing this bug as WontFix.
,
Oct 10 2017
Thank you for your response, this is the workaround we've been doing since the version 5.0 change. To be more precise we are disabling the "Google Update" services as they are not applying any more for this product and as far as I'm concerned other Google products too for the windows XP platform.
Would you like to inform us about the mentioned registry key's function please? {HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Update\Update{00EBA25B-97AB-475A-BD68-C3B6C9E94260}, what does it do actually?
With regards,
George Simos
,
Oct 10 2017
This key will disable the automatic update functionality only for the Legacy Browser Support feature without touching anything else. However XP is as you say not a supported platform for any other product so disabling updates completely is just as good.
,
Oct 10 2017
Thank you for the clarification and for the time you have invested to assist us! Have a nice day. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by blacksta...@gmail.com
, Oct 5 2017