Unable to install 68.0.3440.84 over 68.0.3440.75
Reported by
wainehau...@gmail.com,
Aug 2
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.87 Safari/537.36 Steps to reproduce the problem: 1. Install Google enterprise standalne msi 2. 3. What is the expected behavior? To install newest version of Chrome What went wrong? installer gives error the a newer version is already installed. Did this work before? No Chrome version: 68.0.3440.84 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: It seems the new msi thinks it is a downgrade from 75 and so will not install. Having checked the msi properties the upgrade code is the same, might this be a cause.
,
Aug 3
Thanks for filing the issue! As the issue seems to be related to "Enterprise" hence adding respective component and cc'ing @jmukthavaram for further inputs.
,
Aug 3
Thank you for flagging to correct team
,
Aug 3
Hi Greg, can you take a look at his bug please.
,
Aug 3
,
Aug 6
Hi. I'm unable to reproduce this using the x64 MSIs for the two versions indicated. Could you please provide the verbose msi log for the failing run? For example: msiexec /i googlechromestandaloneenterprise64.msi /l*vx msi.log Thanks.
,
Aug 7
As requested. So we get the issue on multiple machines. The previous version is already installed (68.0.3440.75)
,
Aug 8
Thank you for the log. The behavior you describe and the contents of the log are consistent with an attempt to downgrade from a newer version of Chrome to an older. While I am still unable to reproduce this, I believe I understand what Windows Installer is looking at when it decides whether the attempted install is to a newer version, the same version, or an older version. Would you please attach (or send me directly) the output of the following commands from a machine experiencing the problem: REM Check for Chrome's upgrade code: 96FDFD1C54952F233AE5EE499CC9C74F reg query HKLM\SOFTWARE\Classes\Installer\UpgradeCodes\96FDFD1C54952F233AE5EE499CC9C74F /s reg query HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UpgradeCodes\96FDFD1C54952F233AE5EE499CC9C74F /s REM Check for Chrome 68.0.3440.75's product code: 9EEA40537992B173AB0055CB4B671039 reg query HKLM\Software\Classes\Installer\Products\9EEA40537992B173AB0055CB4B671039 /s reg query HKLM\Software\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\9EEA40537992B173AB0055CB4B671039 /s REM Check for Chrome 68.0.3440.84's product code: 45C9CB4A9854C4A32871F90A20264F17 reg query HKLM\Software\Classes\Installer\Products\45C9CB4A9854C4A32871F90A20264F17 /s reg query HKLM\Software\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\45C9CB4A9854C4A32871F90A20264F17 /s
,
Aug 13
Hello, I have attached outputs of the commands you asked for. When running the last 2 commands it gave error that system could not find the registry key (reg query HKLM\Software\Classes\Installer\Products\45C9CB4A9854C4A32871F90A20264F17 /s reg query HKLM\Software\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\45C9CB4A9854C4A32871F90A20264F17 /s)
,
Aug 13
Thanks for those attachments. The "Version" value for Chrome 68.0.3440.75 in the keys listed in 3.txt and 4.txt should be 0x435c004b (67.92.75). In the listings you provided, it is 0x44000d70 (68.0.3440). It appears that either the 68.0.3440.75 Chrome MSI you started with was modified, or some state on the machines was modified after it was installed. If you switch the Version values back to 0x435c004b, you should be all set. I'm closing this out as WontFix since this doesn't seem to be an issue with the stock Chrome enterprise installer.
,
Aug 13
so we do use an mst to roll out the software, in our mst we do update the product version number to match the listed number in the chrome site. We have not had this issue before?
,
Aug 13
The Version field for Chrome's MSI is computed based on Chrome's W.X.Y.Z version as described here: https://bugs.chromium.org/p/chromium/issues/detail?id=67348#c62. Note that the Version you're setting it to for 68.0.3440.75 (0x44......) is higher than the true version (0x43......), so it makes sense that Chrome's MSI thinks that it's being downgraded. Also note that you're losing the build number entirely (.75 vs .84). Your path forward is to stop modifying the version number. Note that since issue 67348 was fixed, Chrome updates the DisplayVersion in the registry shortly after install/update, so Chrome's true 4-part version number is present in the registry and visible in the Programs and Features control panel. I hope this helps. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by swarnasree.mukkala@chromium.org
, Aug 2