Fix & Adjust Automatic Updates in Google Chrome

Managing Google Chrome Updates: A Manual Guide

Google Chrome is designed to update automatically, ensuring users benefit from the latest security features and performance improvements. However, the automatic update mechanism can occasionally encounter issues. When this happens, manual intervention becomes necessary.

Although straightforward in concept, adjusting Chrome's update settings can be surprisingly complex. This guide provides a step-by-step walkthrough to resolve update problems.

Understanding Update Errors

A common error message encountered during Chrome updates reads: "Google Chrome or Google Chrome Frame cannot be updated due to inconsistent Google Update Policy settings." This indicates a conflict within the Google Update Policy configuration.

To resolve this, adjustments must be made using the Group Policy Editor. This allows for overriding the current update policy for the Google Chrome Binaries application.

Note: If your Google Chrome browser is currently updating without any issues, there is no need to proceed with the following instructions. Consider exploring our SysInternals Pro series for more advanced system administration topics instead.

Resolving Inconsistent Update Policies

The error message specifically directs users to utilize the Group Policy Editor. This tool enables administrators to configure and manage various settings for applications, including Google Chrome.

By accessing the Group Policy Editor, you can modify the update policy override for the Google Chrome Binaries application. This adjustment aims to resolve the inconsistency that is preventing Chrome from updating correctly.

Successfully modifying the update policy through the Group Policy Editor should allow Google Chrome to resume its automatic update process, ensuring you always have the most secure and optimized version of the browser.

Addressing the Need for Chrome Updates

Two key inquiries warrant consideration in this discussion: the rationale behind modifying the update function and the necessity for such intervention. While software updates inherently carry a degree of risk, maintaining a current web browser is crucial for minimizing vulnerabilities to zero-day exploits and security breaches.

Google Chrome, by default, handles updates automatically, often prompting a browser restart to implement them. However, since 2010, Chrome has incorporated advanced group policy settings designed to facilitate streamlined update management for network administrators within Windows enterprise environments. A challenge arises for individual users and businesses lacking a group policy system, as these settings can occasionally malfunction, disabling automatic updates. It's important to emphasize that the guidance presented here specifically addresses resolving Google Chrome update issues on Windows systems.

When automatic or manual updating is disabled, users will encounter a specific error message upon navigating to About -> Google Chrome or entering chrome://chrome in the address bar and attempting an update:

how-to-fix-and-adjust-automatic-updating-in-google-chrome-1.jpg

The complete error message reads as follows:

Update failed (error: 7) An error occurred while checking for updates: Google Chrome or Google Chrome Frame cannot be updated due to inconsistent Google Update Group Policy settings. Use the Group Policy Editor to set the update policy override for the Google Chrome Binaries application and try again; see http://goo.gl/uJ9gV for details.

For users unfamiliar with Windows administration or system management, this request can be daunting. Many individuals and home users can function effectively without ever needing to interact with the Group Policy Editor.

However, assistance is available. We have navigated the Group Policy Editor to provide a comprehensive guide to resolving the update issue.

Note: The Group Policy Editor is exclusively available on Windows Pro and higher editions (such as Windows 7 Pro, Enterprise, and Windows 8 Pro). Users with lower Windows versions (like Windows 7 Home) will need to directly modify the registry, a process we generally advise against. Review this tutorial to understand the changes, then consult the Google help file, Google Update for Enterprise, specifically the Registry Settings section, which details the necessary registry keys for manual editing.

Prior to proceeding, ensure you possess administrative privileges on the computer you intend to modify. Changes to the update policy require administrative access. Furthermore, if operating within a corporate network, verify with your IT department before making any adjustments. Even with administrative access, overriding existing Group Policy deployments may not be permitted.

Do you have administrative access and approximately 10-15 minutes to follow these instructions? If so, let's proceed with fixing Chrome.

Resolving Issues with Google Chrome's Automatic Updates

Attempting to rectify update problems by directly modifying the Windows Registry, involving alterations and deletions of registry keys, is a path we will not detail. Such direct registry manipulation is generally discouraged due to the potential for errors to escalate into significant system issues. Furthermore, utilizing the Group Policy Editor, as we will demonstrate, offers a future-proof solution, remaining effective even if Google Chrome's registry key usage evolves over time.

Simply downloading and attempting to install a fresh version of Chrome will not circumvent the issue. The new installation will still rely on the update servers, and the problematic policy will continue to obstruct the update process. This outlined method represents the most reliable approach to restoring regular, automatic updates.

The initial step involves obtaining the custom policy template for Chrome. Upon introducing Group Policy support to Google Chrome, Google provided a template encompassing all configurable Group Policy settings applicable to Chrome installations. You can download the template file from this link. For the time being, retain the downloaded file in your downloads folder, or archive it for future reference if you prefer.

Now, we will launch the Windows Group Policy Editor to install the custom Google Chrome template. This will allow us to modify policies without directly accessing the Windows Registry. Access the Group Policy Editor by opening the Run dialog (Windows key + R) and entering: gpedit.msc

how-to-fix-and-adjust-automatic-updating-in-google-chrome-2.jpg

With the Group Policy Editor open, navigate to the following path using the left-hand pane: Local Computer Policy -> Computer Configuration -> Administrative Templates. As illustrated in the image above, right-click on this entry and select "Add/Remove Templates...". Then, browse to the location where you downloaded the GoogleUpdate.adm template.

how-to-fix-and-adjust-automatic-updating-in-google-chrome-3.jpg

Verify that the template file appears in the Add/Remove window, as shown above, and then click the "Add" button. The custom Google Chrome policy is now successfully installed within the Local Group Policy Editor.

Configuring Automatic Updates for Google Chrome

Following the installation of a custom policy, locating the relevant templates within the Local Group Policy Editor is the next step. The precise location varies depending on the Windows version installed on your system.

Locating the Templates

Users of Windows XP, Windows 2000, and Windows Server 2003 should navigate to Administrative Templates -> Google -> Google Update.

For systems running Windows Vista, Windows 7, Windows 8, and Windows Server 2008 (and later versions), the path is Administrative Templates -> Classic Administrative Templates (ADM) -> Google -> Google Update.

All modifications will be performed within the Google Update section, as illustrated in the image above. Focus solely on this section and its sub-policies, leaving all others untouched. A total of six policies require adjustment.

Policy Adjustments

Navigate to the specified sub-folders and double-click each policy entry to modify its settings:

Google Update -> Preferences -> Auto-update check period override

Enable this override. The default check frequency is 1440 minutes, equivalent to every 24 hours. Should a specific need arise, this interval can be altered by adjusting the designated value.

Google Update -> Applications -> Update Policy

Set the policy override state to "Enabled". Ensure the option is configured to "Always allow updates"; switch to this setting if it is currently disabled. Alternative options, such as manual updates or automatic silent updates, are available, but maintaining "Always allow updates" is strongly advised for optimal browser security.

Google Update -> Applications -> Google Chrome -> Allow Installations

Enable this setting. No further configuration options are present.

Google Update -> Applications -> Google Chrome -> Update Policy Override

Toggle this to "Enabled". Similar to the previous application update policy, you can define the update frequency. The default should be "Always allow updates". Consistency between this setting and the prior policy change is crucial.

After implementing these changes, proceed to the following locations and replicate the exact settings for the Chrome Binaries:

Google Update -> Applications -> Google Chrome Binaries -> Allow Installations

Google Update -> Applications -> Google Chrome Binaries -> Update Policy Override

The configuration dialogs will mirror the previous screenshots, as you are simply duplicating the settings applied to Google Chrome for the Chrome Binaries.

Finalizing the Update

Upon completing all setting adjustments, close the Local Group Policy Editor and return to Google Chrome. Restart the browser and access Settings -> About Google Chrome. Initiate the update process by clicking the update button, and your Chrome installation will be refreshed.

Note: Should Chrome continue to fail updating despite correctly configured group policies, consult this Google support document. It details the location of potentially problematic registry keys that may require deletion in rare instances. Most users should be able to resolve update issues by adjusting the group policies alone, avoiding direct registry modification.