UserAgent: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.109 Safari/537.36

Steps to reproduce the problem:
On a clean Windows 10 (v1511) computer with no third party software installed:

1. Deploy Chrome 48.0.2564.109 using the Google provided msi by assigning the application in a GPO Computer Configuration.
2. Turn on a targeted computer, and Chrome is installed.  Logon to see that Chrome installed perfectly.
3. Edit the GPO and add Chrome 49.0.2623.112 as an assigned application, set to REPLACE (uninstall) the Chrome 48 application created in step 1.
4. Reboot the targeted computer.
5. You'll see "Removing Chrome...", followed by "Installing Chrome..." -- as expected.
6. Logon to the computer.
7. Chrome is no longer installed.  This is in error.

What is the expected behavior?
Chrome should be installed.

What went wrong?
According to the logs, the uninstalls of v48 and google updater are successful, but the installation of v49 fails with error 1603.  This is because the DoInstall action fails with error -1606219999.

To uninstall Chrome, the msi launches an executable to perform the actual uninstallation.  That executable, in turn, launches the un/installer for google_updater.  I believe that the executable doesn't wait for the google_updater process to end and quits early.  This allows the Chrome installer to run out-of-order with the google_updater installer.

Since Google Update is in the process of being uninstalled, I think the Chrome installer detects this "bad state" and aborts the installation.

Did this work before? N/A 

Chrome version: 48.0.2564.109  Channel: stable
OS Version: 10.0.10586
Flash Version: Shockwave Flash 20.0 r0

I've tested this on several combinations of Chrome from v40-v49, and it fails consistently.

When it fails, the chrome_installer.log only lists uninstall events.  (The DoInstall action fails before writing any events?)

Workarounds (none are acceptable in our environment):
- Manually uninstalling Chrome using "Programs and Features" prior to the reboot prevents the problem.

- Rebooting the computer a second time results in Chrome being installed successfully (sometimes, but other times it fails to uninstall v48 even though Chrome is no longer installed).

- When creating the Chrome 49.0.2623.112 assigned application in GPO, set to UPGRADE the Chrome 48 application.

- Install another application the uses Google Update (such as Google Earth).  This prevents Google Update from being uninstalled.

- Modify the msi to add an artificial 30 second delay somewhere before DoAction.  This allows the google_updater process to exit before beginning the installation.  However, this causes the google_updater msi to fail with "Failed to grab execution mutex. System error 258."  This is probably OK since we are about to reinstall it, but who knows?

This issue is similar to  issue #381425 
 

Deleted: chrome_installer.log 448 bytes

chrome_installer.log 448 bytes View Download

Deleted: GoogleUpdate.log 39.0 KB

GoogleUpdate.log 39.0 KB View Download

Deleted: msi_chrome_install.LOG 120 KB

msi_chrome_install.LOG 120 KB View Download

Deleted: msi_chrome_remove.LOG 95.0 KB

msi_chrome_remove.LOG 95.0 KB View Download

Deleted: msi_updater_removal.LOG 85.4 KB

msi_updater_removal.LOG 85.4 KB View Download