Fixed
Status Update
No update yet.
Comments
gr...@chromium.org
Hi Josh. I'm fairly sure that the old scripts used the bitness as one input to the product code generation. Could you check to see if this was lost in migration? Thanks.
pe...@google.com
wa...@google.com
ap...@google.com
Project: chromium/src
Branch: main
Author: Joshua Pawlicki <
Link:
Installer: Include architecture in MSI product code generation.
Expand for full commit details
Installer: Include architecture in MSI product code generation.
Compare to the old code at go/vsazt.
The effects of this change will not follow the normal waterfall process.
For this change to affect Google Chrome Stable releases:
1. A version of GoogleUpdater including this CL must be released.
2. Subsequently, the next Google Chrome MSI will pick up the change.
Fixed: 385086918
Change-Id: I88065ca30e9eebe0c759710637a052c50155d77f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6158413
Auto-Submit: Joshua Pawlicki <waffles@chromium.org>
Reviewed-by: Greg Thompson <grt@chromium.org>
Commit-Queue: Greg Thompson <grt@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1404063}
Files:
- M
chrome/updater/win/signing/msi_from_standalone.py
Hash: 0210bc069bfbce2c1f6146f849b355b8c726de5b
Date: Thu Jan 09 02:31:25 2025
al...@gmail.com
Hello,
This issue appears to still be in effect. The current available Chrome version, 132.0.6834.111, has ProductCode {00715A53-6C1B-35AC-BDC9-597DCF53D022} for both the 64-bit and 32-bit MSIs when retrieved fromhttps://chromeenterprise.google/download/ .
Thanks,
Alex
This issue appears to still be in effect. The current available Chrome version, 132.0.6834.111, has ProductCode {00715A53-6C1B-35AC-BDC9-597DCF53D022} for both the 64-bit and 32-bit MSIs when retrieved from
Thanks,
Alex
wa...@google.com
Sorry for the confusion, the fix has landed but it won't take effect on the current MSIs; it should be effective on the next release of Chrome.
Description
1. Download standalone MSI installers from
2. Check MSI Product Code (PowerShell or Orca, same results) of downloaded MSI
3. Compare to other release
First noticed this issue with 131.0.6778.109, persists through 131.0.6778.205
Description:
The 32-bit and 64-bit Enterprise MSI installers share the same MSI Product Code. This makes it much more difficult to distinguish between the two for something like an MECM detection method. This also seems to be causing MSI uninstalls to break entirely for any existing installations that had switched versions in the past (e.g. current 64-bit version that is an upgraded original 32-bit install in ProgramFiles(x86)). When uninstalled using either the MSI directly or through Programs and Features, a "There is a problem with this Windows installer package" error is reported.
Workaround:
When a machine is in the corrupted uninstall state, manually deleting content from ProgramFiles(x86) and attempting an 'upgrade' using a 64-bit MSI allows it to install and then uninstall without issue.