IssueTracker

Forked from issue 382108340, which is about the bare MSI installer. This bug is about the enterprise bundle's embedded MSI installer. https://crbug.com/382108340#comment55 is relevant to this bug.

To reproduce: download https://dl.google.com/dl/chrome/install/GoogleChromeEnterpriseBundle64.zip, extract the MSI, and run in.

The MSI should error, due to O4 returning 70050, which is an error parsing the tag. I suspect it originates from here.

It looks like the enterprise bundle tags the MSI with brand=GCEB; this turns out to be problematic for O4. This tagged MSI will pass "brand=GCEB" as the tag on the command line to the standalone installer, along with the appargs appguid={8A69D345-D564-463c-AFF1-A69D9 E530F96}&installerdata=%7B%22distribution%22%3A%7B%22msi%22%3Atrue%2C%22system_level%22%3Atrue%2C%22verbose_logging%22%3Atrue%2C%22msi_product_id%22%3A%224B1A29D5-BC9F-32E0-8F5B-FF8755A3D6BF%22%2C%22allow_down grade%22%3Afalse%7D%7D, and appguid={8A69D345-D564-463c-AFF1-A69D9 E530F96}. But, the appguid from the appargs can't be found in the tag, so tag parsing fails.

This isn't a problem for the non-bundled MSI because it is completely untagged, so the standalone installer reads the tag information from its own signature instead of from the command line, and it has 8A69 there (this was injected while building the standalone installer).

Two possible solutions are:

1. Put an untagged MSI into the enterprise bundle. This should reduce the problem to the case of issue 382108340, and fewer execution paths are nice, but it will mean that installs of this type aren't allocated to GCEB.
2. Fix the tagged MSI in the enterprise bundle so that it includes the appguid in the tag.

Filed at P2 since our level of support for untagged bundle downloads is unclear, but I think this should be fairly quick to fix.