Issue metadata
Sign in to add a comment
|
Chrome Version Architecture
Reported by
stoll.ni...@gmail.com,
Oct 2 2017
|
||||||||||||||||||||||
Issue description
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.79 Safari/537.36 Edge/14.14393
Steps to reproduce the problem:
1. Install Chrome x86
2. Use Ivanti Patch/SCCM to attempt patching Chrome
3. Updates Fail on x86 OS running x86 Chrome
What is the expected behavior?
previous to google's forced update of all chrome browsers to chrome x64, patching chrome worked fine.
What went wrong?
all versions of chrome show as 64-stable in the windows registry, even though they are 32bit installations on 32bit windows.
see registry key HKEY_LOCAL_MACHINE\SOFTWARE\Google\Update\ClientState\{8A69D345-D564-463C-AFF1-A69D9E530F96}\AP
it doesn't matter if we use the x86 or x64 MSI to install Chrome For Enterprise, they both show as 64-Stable in the registry. This is the only key available to determine the version of chrome that is installed, and is the key used by Ivanti Patch for SCCM (formerly shavlik patch) to determine which chrome patch to install. now that all installations of Chrome show as 64-Stable, they all try to install the the x64 patch only and fail, even on a x86 windows OS running 32bit Chrome.
Did this work before? Yes
Chrome version: 61.0.3163 Channel: n/a
OS Version: 10.0
Flash Version:
Please update this registry key appropriately for the 32bit Chrome installation, or add an additional key for use in determining which patches to apply to chrome
,
Oct 3 2017
Requesting dev team to take a look into it. Tagging with triage help label.
,
Oct 3 2017
,
Oct 3 2017
Thank you for reporting this. We are aware of the issue and are actively working toward a fix. I'll update this bug when the fix has shipped.
,
Oct 10 2017
32-bit MSI installers are now properly tagged and should no longer autoupdate to 64-bit builds.
,
Oct 10 2017
What is the version number that includes this update? I see the 61.0.3163.100 version is still the available download on the Chrome website and I see a version 62.0.3202.45 Beta
,
Oct 10 2017
The problem was with the way the installer was served by the download page. Any installers downloaded today will have the fix -- any downloaded prior to today will not.
,
Oct 10 2017
"The problem was with the way the installer was served by the download page. Any installers downloaded today will have the fix -- any downloaded prior to today will not." Can this be clarified? Is the version number going to remain 61.0.3163.100 or will there be a new public channel release today?
,
Oct 11 2017
There will not be a new release of Chrome for this. The actual build of Chrome itself did not change. The difference is in the tag appended to the MSI by the download page. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by nyerramilli@chromium.org
, Oct 3 2017