Chrome MSI 64/32bit has the same ProductCode |
|||
Issue descriptionChrome MSI 64-bit and 32-bit has exactly the same ProductCode. According to Windows Dev Center article, applications must assign different product codes for 32-bit and 64-bit packages. https://msdn.microsoft.com/en-us/library/windows/desktop/aa370854(v=vs.85).aspx > The 32-bit and 64-bit versions of an application's package must be assigned different product codes.
,
Oct 8 2016
Matt: can u please triage this ?
,
Oct 10 2016
Giving them distinct product codes should be fairly easy; the ProductCode is generated at build time based on various inputs. Adding the build bitness as an input should not be a challenge. Is there a concrete problem caused by them having the same code? The two variants of Chrome cannot be installed at the same time.
,
Oct 10 2016
One problem caused by this is users cannot use ProductCode to programmatically detect which version is installed. No report of actual impact on the usage of Chrome browsers, hence the original priority P3.
,
Oct 10 2016
Can the ProductCode be used for that today? It changes for each release and we don't publish a list of ProductCodes anywhere, so it's a bit difficult for an enterprise to know the full set of all ProductCodes ever used.
,
Oct 11 2016
The change to using the same ProductCode for the two builds is an accidental byproduct of a change made to the official build system. It should not be too difficult to move back to distinct ProductCodes.
,
Oct 11 2016
Fixed with internal cl/135832258, which will be picked up by the next builds. |
|||
►
Sign in to add a comment |
|||
Comment 1 by kotah@chromium.org
, Oct 5 201612.7 KB
12.7 KB View Download
12.6 KB
12.6 KB View Download