Troubleshoot Chrome MSI

Installation Issues

Installations behind a firewall time out and fail.

By default, Google Update attempts to check for an update on install, and fails at the firewall.

You can skip this check by passing the parameter "NOGOOGLEUPDATEPING=1" as follows:

msiexec /i GoogleChromeStandaloneEnterprise.msi NOGOOGLEUPDATING=1 /l*v log.txt
When installing the MSI over an existing MSI install, I get the error "More recent version exists."

If you left auto-updates on, it's possible that the version of the MSI you're trying to install is already outdated. If you already have the dev channel or beta channel installed, the MSI can't overwrite that because these channels will be on newer versions.

To see what the latest stable version of Chrome is for Windows, click here. You can download the latest version here.

I'm trying to repair an installation, but the repair is failing.

If you left auto-updates on, your installations have probably auto-updated to a later version. This is causing the repair to fail because you're already on a later version than the MSI.

You can download the latest stable MSI and use that for the repair instead.

When applying the MSI over a previous install, I get a message that a required program could not be run.

If you run the install with the /f flag (to run it as a minor upgrade), you'll get this error message:

There is a problem with the Windows installer package. A program required for this install to complete could not be run. Contact your support personnel or package vendor.

You need to instead run the install with the /i flag to run it as a major upgrade.

Version Issues

Are old or updated versions of the MSI available?

Old versions are not available. The latest stable version is always available here.

We release a new "major" version to the stable channel about every six weeks. We also update the stable channel between major updates if we have important crash or security fixes.

If you're looking to repair an existing MSI installation, and you left auto-updates on, you can repair with the latest stable MSI.

What if a user already has the consumer version of Chrome when I push out Chrome for Business?

There is only one version of Chrome on a machine at any given time. When the MSI notices that the consumer version of Chrome is already there, it will remove it and update the user's shortcuts. The next time the user launches Chrome, Chrome for Business is used.

This should look seamless to the user, but sometimes behaves inconsistently. You may want to uninstall the consumer version of Chrome before pushing out the MSI.

How can I remove the consumer version of Chrome from target machines entirely before pushing out Chrome for Business?

You can append these registry keys together with an additional parameter, and execute them:

HKEY_CURRENT_USER\Software\Google\Update\ClientState\{8A69D345-D564-463c-AFF1-A69D9E530F96}\UninstallString +
HKEY_CURRENT_USER\Software\Google\Update\ClientState\{8A69D345-D564-463c-AFF1-A69D9E530F96}\UninstallArguments + '--force-uninstall'

The command will end up looking something like this:

[Path to user's data directory]\setup.exe --uninstall --force-uninstall'
If I uninstall the consumer version of Chrome, will that wipe out the user's data?

No. User data is kept separate from the Chrome installation.

However, if the user was using a more recent version of Chrome, their profile data might not work in an older version of Chrome and they'll see a warning when they try to run it. You may want to verify that you're pushing out the latest stable channel version of Chrome.

I see a new version was just released, but my installs don't seem to be auto-updating.

We typically throttle updates the first few days after an update to watch stability rates and make sure we're pushing out a good update. Not all users will get the update immediately, so during this time you may see some machines auto-update while others do not.

If you require the most up-to-date version immediately, you may want to download the latest MSI and push it out manually.

Other Issues

I'm trying to set the default search provider, but it's not working.

The default search provider policy uses a different format for the search provider URL than the format you see when you open the options dialog. Using the options dialog format causes the policy to be ignored.

To denote the search keywords in the search URL, use {searchTerms} instead of %s. Using Google's search URL as an example:

Wrong: http://www.google.com/?q=%s

Right: http://www.google.com/?q={searchTerms}

Can I store my users' Chrome profiles on a roaming profile? Or sync them to a network drive?

Chrome user profiles are not backwards-compatible. If you try to use mismatched profiles and Chrome versions, you may experience crashes or data loss. This mismatch can often occur if a Chrome profile is synced to a roaming profile or network drive across multiple machines that have different versions of Chrome. We strongly encourage administrators and users to consider using Chrome Sync, which persists user settings across machines, instead of using roaming profiles at this time.

With that in mind, there are policies for controlling the location of the user profile and the cache: