ANAVEM
Languagefr
How to Enable Auto-Updates for Google Chrome Using Microsoft Intune

How to Enable Auto-Updates for Google Chrome Using Microsoft Intune

Configure automatic Chrome updates across managed Windows devices using Microsoft Intune by importing Chrome ADMX templates and setting up update policies to ensure security patches are applied automatically.

Evan MaelEvan Mael
March 28, 2026 15 min
mediumintune 7 steps 15 min

Why Configure Chrome Auto-Updates Through Microsoft Intune?

Managing Chrome updates across enterprise environments is critical for maintaining security and compliance. Manual updates create security gaps, while uncontrolled automatic updates can disrupt business operations. Microsoft Intune provides the perfect middle ground, allowing IT administrators to enforce automatic Chrome updates while maintaining centralized control and visibility.

Chrome receives frequent security updates, often multiple times per month. These updates patch critical vulnerabilities that could expose your organization to cyber threats. Without proper update management, devices running outdated Chrome versions become prime targets for attackers exploiting known security flaws.

What Makes Intune the Best Choice for Chrome Update Management?

Microsoft Intune integrates seamlessly with existing Windows device management infrastructure, providing policy-based control over Chrome updates without requiring additional software or complex scripting. By importing Chrome's ADMX templates, you gain access to the same granular controls available in traditional Group Policy environments, but with the flexibility of cloud-based management.

This approach ensures consistent update behavior across all managed devices, whether they're domain-joined, Azure AD-joined, or standalone workstations. The policy-driven method also provides audit trails and compliance reporting, essential for organizations with regulatory requirements.

What Will You Accomplish in This Tutorial?

You'll learn to download and import Chrome ADMX templates into Microsoft Intune, create configuration profiles that enforce automatic Chrome updates, and deploy these policies to managed Windows devices. By the end, your Chrome installations will automatically download and install security updates, keeping your environment protected against the latest threats while maintaining centralized IT control.

Implementation Guide

Full Procedure

01

Download Chrome ADMX Policy Templates

Start by downloading the latest Chrome ADMX templates from Google's official Chrome Enterprise site. These templates contain the policy definitions needed to manage Chrome through Intune.

Navigate to https://chromeenterprise.google/browser/download/ and locate the Policy templates section. Download the latest Policy templates ZIP file.

Extract the ZIP file to a local folder. You'll need these specific files:

  • chrome.admx - Chrome browser policies
  • Google.admx - Google application policies
  • GoogleUpdate.admx - Google Update service policies
  • Corresponding .adml files for your language (e.g., en-US folder)
Pro tip: Always download the latest templates to ensure compatibility with current Chrome versions and access to new policy options.

Verification: Confirm you have extracted the chrome.admx, Google.admx, and GoogleUpdate.admx files along with the language-specific .adml files in the en-US subfolder.

02

Import ADMX Templates into Microsoft Intune

Now you'll import the Chrome ADMX templates into Intune to make Chrome policies available for configuration.

Sign in to the Microsoft Intune admin center at https://endpoint.microsoft.com using your administrator credentials.

Navigate to Devices > Manage devices > Configuration. Click on the Import ADMX tab, then select + Import.

Upload the following files in this order:

  1. First, upload Google.admx and its corresponding Google.adml file
  2. Next, upload chrome.admx and its chrome.adml file
  3. Finally, upload GoogleUpdate.admx and its GoogleUpdate.adml file

For each upload, select both the .admx file and the corresponding .adml file from the language folder (e.g., en-US/Google.adml).

Warning: Ensure you upload matching language files. Mismatched ADML files will cause policy display issues in the Intune console.

Verification: After importing, refresh the page and confirm you see Google, Chrome, and Google Update folders under the Imported Administrative Templates section.

03

Create Chrome Auto-Update Configuration Profile

Create a new configuration profile to enforce automatic Chrome updates across your managed devices.

In the Intune admin center, navigate to Devices > Windows > Configuration. Click Create > New policy.

Configure the profile settings:

  • Platform: Windows 10 and later
  • Profile type: Templates > Imported Administrative Templates
  • Click Create

In the Basics tab:

  • Name: Enforce automatic updates for Google Chrome
  • Description: Configures Chrome to automatically download and install updates including security patches
  • Click Next

In the Configuration settings tab, navigate through the policy tree:

Computer Configuration > Google Update > Applications > Google Chrome > Update policy override

Configure the update policy:

  • Set the policy to Enabled
  • From the dropdown menu, select Always allow updates (recommended)
  • Click OK, then Next

Verification: Confirm the policy shows as "Enabled" with "Always allow updates" selected in the configuration summary.

04

Configure Profile Assignments and Scope

Assign the Chrome update policy to your target device groups and configure any necessary scope tags.

In the Scope tags tab, add any relevant scope tags for your organization's compliance requirements, or leave empty if not using scope tags. Click Next.

In the Assignments tab, configure your target groups:

  • Click + Add group under Included groups
  • Select your target device groups (start with a test group for initial deployment)
  • Choose Assignment type: Available or Required based on your deployment strategy
Pro tip: Start with a small test group to validate the policy works correctly before rolling out to all devices. This helps identify any conflicts with existing policies.

For production deployment, consider these assignment strategies:

  • Pilot group: 10-20 test devices for initial validation
  • Staged rollout: Deploy to departments or regions incrementally
  • Full deployment: All managed Windows devices

Click Next to proceed to the review screen.

Verification: Confirm your target groups are listed correctly and the assignment type matches your deployment strategy.

05

Deploy and Monitor the Configuration Profile

Review your configuration and deploy the Chrome auto-update policy to your managed devices.

In the Review + create tab, verify all settings:

  • Profile name and description are correct
  • Update policy is set to "Always allow updates"
  • Target groups are properly assigned

Click Create to deploy the policy.

Monitor the deployment status:

  1. Navigate to Devices > Configuration
  2. Find your "Enforce automatic updates for Google Chrome" profile
  3. Click on the profile to view deployment status
  4. Check the Device status and User status tabs for success/failure rates
Warning: Policy application can take 1-8 hours depending on device check-in schedules. Don't expect immediate results on target devices.

Force policy sync on test devices:

  • On the target device, open Settings > Accounts > Access work or school
  • Click on your work account > Info > Sync
  • Or use PowerShell: Get-ScheduledTask | Where-Object {$_.TaskName -eq "PushLaunch"} | Start-ScheduledTask

Verification: Check that the profile shows "Succeeded" status for your test devices within 2-4 hours of deployment.

06

Verify Chrome Auto-Update Policy Application

Confirm that the Chrome auto-update policy is properly applied and functioning on your managed devices.

On a target device, open Google Chrome and navigate to chrome://policy/ to view applied policies.

Look for the Chrome update policies:

  • Search for UpdatePolicy or scroll to the Google Update section
  • Verify UpdatePolicy shows:
    • Value: 1 (which means "Always allow updates")
    • Source: Platform
    • Status: OK

Test the update mechanism:

  1. Navigate to chrome://settings/help in Chrome
  2. Chrome should automatically check for updates
  3. If updates are available, they should download and prompt for restart
  4. If Chrome is current, you'll see "Chrome is up to date"

Verify update service status using Command Prompt:

sc query gupdate
sc query gupdatem

Both Google Update services should show STATE: RUNNING or STATE: STOPPED (normal when not actively updating).

Pro tip: Use chrome://policy/ as your primary verification tool. If policies don't appear here, the issue is with policy delivery, not Chrome configuration.

Verification: Confirm UpdatePolicy value is 1, Chrome checks for updates automatically, and the Google Update services are properly configured.

07

Troubleshoot Common Auto-Update Issues

Address common problems that may prevent Chrome auto-updates from working correctly on managed devices.

Policy Not Applying:

  • Check Intune policy assignment: Ensure the profile is assigned to devices, not users
  • Verify ADMX import: Confirm all three ADMX files (Google, Chrome, GoogleUpdate) imported successfully
  • Force device sync: Use Get-ScheduledTask | Where-Object {$_.TaskName -eq "PushLaunch"} | Start-ScheduledTask

Updates Still Blocked:

  • Check for conflicting Group Policies on domain-joined devices
  • Verify no local registry keys are overriding the policy
  • Test on a clean, non-domain device to isolate the issue

Chrome Not Updating Despite Policy:

Manually trigger an update check:

"C:\Program Files\Google\Update\GoogleUpdate.exe" /ua /installsource scheduler

Check Windows Event Logs for Google Update errors:

Get-EventLog -LogName Application -Source "Google Update" -Newest 10

Registry Fallback Method:

If policy-based updates fail, configure registry keys directly:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Update]
"UpdateDefault"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Update\Applications\{8A69D345-D564-463c-AFF1-A69D9E530F96}]
"Update"=dword:00000001
Warning: Registry modifications should only be used as a last resort. Always test on non-production devices first and create registry backups.

Verification: Run chrome://policy/ and chrome://settings/help to confirm updates are working after troubleshooting steps.

Frequently Asked Questions

How long does it take for Chrome auto-update policies to apply through Intune?+
Chrome auto-update policies typically take 1-8 hours to apply to managed devices, depending on the device check-in schedule with Intune. You can force immediate policy sync by going to Settings > Accounts > Access work or school > Info > Sync on the target device, or using PowerShell to trigger the PushLaunch scheduled task. The policy application time also depends on network connectivity and whether the device is actively being used.
What happens if Chrome auto-updates conflict with existing Group Policy settings?+
If there are conflicting Group Policy settings on domain-joined devices, the local Group Policy will typically take precedence over Intune policies. To resolve conflicts, you should either remove the conflicting GPO settings or ensure that Intune policies are configured with higher priority. You can test policy conflicts by checking chrome://policy/ to see which policies are active and their sources. For hybrid environments, consider using Group Policy preferences or configuring policy precedence through registry settings.
Can I control which Chrome versions get installed through Intune auto-updates?+
The standard Chrome auto-update policy through Intune will always update to the latest stable version and cannot be configured to target specific versions. However, you can use Chrome's TargetVersionPrefix policy to pin installations to specific major versions (like version 120.x.x.x). For more granular control, consider using Chrome Enterprise policies to configure update channels (Stable, Beta, Dev) or implement a staged update approach using different device groups with delayed policy application.
How do I verify that Chrome auto-updates are working correctly on managed devices?+
Verify Chrome auto-updates by navigating to chrome://policy/ on managed devices and confirming that UpdatePolicy shows a value of 1 with Source: Platform and Status: OK. Additionally, check chrome://settings/help to see if Chrome automatically checks for updates. You can also verify the Google Update services are running using 'sc query gupdate' and 'sc query gupdatem' in Command Prompt. Monitor the Intune admin center for policy compliance status across your device fleet.
What should I do if Chrome auto-updates fail despite correct Intune policy configuration?+
If Chrome auto-updates fail with correct Intune policies, first check for conflicting local policies or registry entries that might override Intune settings. Manually trigger updates using 'GoogleUpdate.exe /ua /installsource scheduler' from the Chrome installation directory. Check Windows Event Logs for Google Update errors and verify network connectivity to Google's update servers. As a fallback, you can configure registry keys directly under HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Update to force update behavior, though this should be a last resort after policy-based methods fail.
Evan Mael
Written by

Evan Mael

Microsoft MCSA-certified Cloud Architect | Fortinet-focused. I modernize cloud, hybrid & on-prem infrastructure for reliability, security, performance and cost control - sharing field-tested ops & troubleshooting.

Discussion

Share your thoughts and insights

Sign in to join the discussion