New issue
Advanced search Search tips

Issue 767793 link

Starred by 1 user
Status: Assigned
Owner:
rogerta@chromium.org
Cc:
grt@chromium.org
ajha@chromium.org
kkaluri@chromium.org
pbomm...@chromium.org
ligim...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Task



Sign in to add a comment

Enterprise chrome 32-bit update installer tags "ap" in registry as "x64-stable"

Reported by jasonlvg...@gmail.com, Sep 22 2017 
UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0

Steps to reproduce the problem:
1. Install 32-bit Chrome on 32-bit Windows system
2. Update it by installing the installer at https://dl.google.com/tag/s/appguid%3D%7B8A69D345-D564-463C-AFF1-A69D9E530F96%7D%26iid%3D%7B03FE9563-80F9-119F-DA3D-72FBBB94BC26%7D%26lang%3Den%26browser%3D4%26usagestats%3D0%26appname%3DGoogle%2520Chrome%26needsadmin%3Dprefers%26ap%3Dx64-stable%26brand=GCEA/dl/chrome/install/googlechromestandaloneenterprise.msi
3. Check registry at HKEY_LOCAL_MACHINE\SOFTWARE\Google\Update\ClientState and look for the key with the expected update.

What is the expected behavior?
"ap" value of the key should not contain "x64". (Previously it was "multi-chrome")

What went wrong?
"ap" value of the key is now "x64-stable", even if the application and the OS are 32-bit.

Did this work before? Yes Some version around 52

Chrome version: 61.0.3163.100  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 27.0 r0

I manage updates for enterprise Google Chrome browser, and I need to decide which patch to apply to the system (32-bit or 64-bit). I used to be able to use the "ap" value but not anymore.
chrome.png
227 KB View Download

Comment 1 by jasonlvg...@gmail.com, Sep 22 2017 

Also, this post https://productforums.google.com/forum/#!msg/chrome/w93eUkzgkEo/0MYj9InRRYYJ suggests that there's no way to detect 32/64 bit Chrome via script, but I want to double check.

Comment 2 by ranjitkan@chromium.org, Sep 22 2017

Cc: kkaluri@chromium.org ajha@chromium.org

Comment 3 by ranjitkan@chromium.org, Sep 22 2017

Labels: Needs-Triage-M61

Comment 4 by gov...@chromium.org, Sep 22 2017

Cc: pbomm...@chromium.org ligim...@chromium.org

Comment 5 by georgesak@chromium.org, Sep 22 2017

Labels: -Needs-Triage-M61 Enterprise-Triaged
Owner: grt@chromium.org
Status: Assigned (was: Unconfirmed)
I think this has been fixed but I'll let grt@ confirm.

Comment 6 by jasonlvg...@gmail.com, Sep 25 2017 

Hi, I don't believe so as I still see it. More importantly, if one installs a problematic version, the "ap" value in the registry will have been updated as "x64-stable", therefore 32-bit and 64-bit applications will look the same in registry. How should I tell them apart please?

Comment 7 by grt@chromium.org, Sep 25 2017

Cc: grt@chromium.org
Owner: rogerta@chromium.org
No, it's not yet fixed. Roger has a CL underway that will fix this.

Comment 8 by jasonlvg...@gmail.com, Sep 29 2017 

grt@ allow me to repeat my question, may I know, then, if the problematic version has already been applied, how should I tell the 32-bit and 64-bit apart via registry?

Comment 9 by grt@chromium.org, Oct 4 2017

Labels: -Type-Bug-Regression Type-Task
There is nothing in the registry to indicate whether the installed Chrome is an x86 or an x64 build. Even with the fix we're discussing, the "ap" value is not guaranteed to provide this info. The most reliable thing would be to look at the bitness of the setup.exe file pointed to by the UninstallString value in the registry.
►

Sign in to add a comment