Manage Chrome Browser updates (Linux)

Applies to Linux users who sign in to a managed account on Chrome Browser.

When you install Chrome Browser on Linux computers, the Google repository is also installed. The repository ensures that your system automatically keeps Chrome Browser up to date.

Step 1: Turn off Chrome Browser updates

To stop Chrome Browser auto-updating, take one of the following actions:

  • Create an empty repository before installing Chrome Browser:
    $ sudo touch /etc/default/google-chrome
  • Add the following line to /etc/default/google-chrome:
    repo_add_once=false
Step 2: Turn off Chrome Browser component updates (Optional)

Applies only to Chrome Browser components

Even if you turn off automatic updates for Chrome Browser, browser components won’t automatically stop updating, including Adobe® Flash®, Widevine DRM (for encrypted media), and the Chrome updater recovery component. If you want to stop these components from updating, disable the Chrome ComponentUpdatesEnabled policy.

Using your preferred JSON file editor:

  1. In your etc/opt/chrome/policies/managed folder, create a JSON file and name it component_update.json.
  2. Add the following setting to the JSON file to turn off component updates:
    {
    "ComponentUpdatesEnabled": "false"
    }
  3. Deploy the update to your users.
Note: This policy does not apply to all components. For a full list of exempted components, see ComponentUpdatesEnabled.
Step 3: Cache Chrome Browser updates to reduce bandwidth (Optional)

If your organization has an intermediate proxy cache set up on its network, you can use it to cache Chrome Browser updates. The updates downloaded from Google can be cached on most web-caching proxy servers. Proxy caches reduce bandwidth and improve response times by caching and reusing frequently requested webpages.

However, many proxy cache default settings aren’t optimal for Chrome Browser updates. To make sure that your proxy cache software can cache Chrome Browser updates, experienced IT administrators can configure the following settings:

  • Maximum file object size—The maximum individual file size that the proxy will cache. Updates are downloaded as one file, so make sure that the maximum file object size is at least 1 GB.
  • Cache directory size—Some web-caching proxy servers cache objects in memory. You can also configure  these servers to cache to disk. Ensure that the cache has adequate storage space, either in memory or on disk. Browsers retrieve objects cached in memory faster than on the hard disk.
  • URL settings—If the server allows you to add settings for particular domains, give preference to dl.google.com/* and www.google.com/dl/*. This is where devices get Chrome Browser updates.
  • Maximum object size in memory—Servers don't keep objects larger than the specified value in memory. This value needs to be set high enough to keep Chrome Browser updates in memory, but low enough to keep larger objects from hoarding the cache memory. Set the maximum object size in memory at a reasonable limit, such as 2,000 KB.
  • Cache space on disk—The total amount of hard disk space that the server can use to cache objects. If you have a large hard drive (more than 30 GB), you can increase the value to cache more objects.

Related topics

Was this helpful?
How can we improve it?