Chrome not updating sounds like a minor inconvenience, but running an outdated browser is a genuine security issue — Chrome updates patch vulnerabilities actively being exploited. Worth fixing properly. This fits into the wider topic we cover in our Google Chrome Errors.
Start with the obvious: three-dot menu → Help → About Google Chrome. This page triggers a manual update check. If it finds an update and installs it: done. If it shows an error code, that code tells you exactly what’s wrong. If it shows “Google Chrome is up to date” when you suspect otherwise: the installed version number is the truth — Chrome doesn’t lie about this.
Common error codes and what they mean
- Error 3 / Error 4: Can’t reach Google’s update servers. Usually a network, firewall, or antivirus block. Fix 1.
- Error 7: Download error — incomplete download or connection interrupted. Try again, or Fix 2.
- Error 12: Insufficient disk space. Check free space on C:.
- Error 11 or Error 13: Update installation failed — permissions or conflicting process. Fix 3.
Fix 1: Network or firewall blocking updates
Chrome downloads updates from dl.google.com and update.googleapis.com. If a firewall, security software, or corporate network blocks these domains, the update fails silently or shows Error 3/4.
Test: temporarily disable the antivirus or firewall → try the update again. If it works: add those Google domains to the security software’s exclusion list. For corporate networks where the proxy blocks Google’s update domains: Chrome updates need to be pushed through policy or the browser managed centrally rather than auto-updated.
Fix 2: Reinstall Chrome cleanly
When update mechanisms fail in ways that individual fixes don’t resolve: uninstall Chrome → download the latest installer from google.com/chrome → install fresh. This is the most reliable path when Chrome’s internal update system is broken. The fresh installer always gets the current version regardless of what’s wrong with the existing installation.
Before uninstalling: ensure Chrome sync is on (your account is signed in) so bookmarks, passwords, and extensions come back automatically after reinstall. The data lives on Google’s servers — the local Chrome installation is just the client.
Fix 3: Google Update service
Chrome updates run through a background service called GoogleUpdate. When this service is stopped or broken, auto-updates stop working silently — Chrome just doesn’t update even when connected.
Check: Win+R → services.msc → look for “Google Update Service (gupdate)” and “Google Update Service (gupdatem)” → both should be Running or set to Automatic/Manual. If either is Disabled: right-click → Properties → change Startup type to Manual → Start.
If the services don’t exist: Google Update wasn’t installed correctly or was removed. The reinstall approach (Fix 2) is more efficient than rebuilding the update infrastructure from scratch.
Fix 4: Permissions on the Chrome folder
Chrome installs to C:Program FilesGoogleChrome and updates this folder during patches. If permissions on this folder are incorrect — the current user account lacks write access — updates fail with Error 11 or 13. This happens most often after a user account change, a system restore, or a Group Policy change on corporate machines.
Check permissions: right-click C:Program FilesGoogleChrome → Properties → Security → verify SYSTEM and Administrators have Full Control. The Users group should have Read & Execute. If the update account (SYSTEM) lacks Full Control, add it back.
Fix 5: Chrome Enterprise vs Consumer
On corporate-managed machines, Chrome may be deployed through Group Policy with automatic updates disabled. The organisation manages updates centrally rather than allowing individual Chrome instances to self-update. This is intentional and can’t be overridden by users.
Check: navigate to chrome://policy/ in Chrome’s address bar. If “UpdatePolicy” or “Update” policies appear set to disabled: IT manages Chrome updates and the machine isn’t broken — it updates on their schedule. Report to IT if security updates are overdue.
Fix 6: Old system, not compatible with latest Chrome
Chrome occasionally drops support for older Windows versions. If the machine runs Windows 7, 8, or early Windows 10 builds: Chrome may be the latest version available for that OS, even if it’s not the latest Chrome overall. chrome://settings/help shows the version — if it says “This computer will no longer receive Google Chrome updates because Windows XP and Windows Vista are no longer supported,” the OS is the limitation, not the update mechanism.
For Windows 11: this shouldn’t be the issue — Chrome currently supports Windows 10 version 1809 and later.
When Chrome updates but then reverts
An update installs, Chrome restarts, and then shows the old version number again: a competing installation (Chrome Beta, Chrome Canary, or an enterprise deployment) may be reverting the production channel. Check for multiple Chrome versions installed: Settings → Apps → search “Chrome” — if Beta or Canary appear alongside the regular Chrome, that’s the source of confusion. Uninstalling the extra versions and reinstalling only the stable channel resolves it.
Our guide on Chrome startup and installation problems covers the profile corruption that sometimes accompanies update failures. For machines where multiple Google software products are having update issues simultaneously (Chrome, Google Drive, etc.), the GoogleUpdate service is the common infrastructure — the service troubleshooting in Fix 3 applies to all of them. Google’s Chrome update troubleshooting documentation covers the full set of error codes with their specific remediation steps and the update policy configuration for enterprise deployments.
Registry entries for GoogleUpdate
GoogleUpdate stores its configuration in the Windows registry. Corrupted or missing registry entries cause the update service to fail even when the service is technically running. The key location: HKEY_LOCAL_MACHINESOFTWAREGoogleUpdate → check whether this key exists and contains correct values.
If the key is missing or contains incorrect data: the cleanest fix is reinstalling Chrome from the official installer (Fix 2), which rebuilds all registry entries correctly. Manually recreating registry entries for GoogleUpdate is tedious and error-prone — the installer handles this more reliably.
Running the Chrome update manually via Command Prompt
If Chrome’s automatic update is failing but you need to force an update check immediately: administrator Command Prompt →
"C:Program Files (x86)GoogleUpdateGoogleUpdate.exe" /update /installedversion=chromeThis directly invokes the GoogleUpdate executable to check for and download Chrome updates. If it works from the command line but not through Chrome’s interface, the issue is Chrome’s own internal update trigger rather than the download mechanism — restarting Chrome and checking through Help → About again usually then works.
Proxy configuration blocking the update servers
Chrome uses the system proxy settings for its update connections. If a proxy is configured that doesn’t permit connections to Google’s update domains — a corporate proxy with Google filtered, a misconfigured home proxy left over from a VPN — updates fail without a clear error in Chrome’s interface. The About page shows “Checking for updates” indefinitely and then times out.
Test without proxy: Settings → Network and internet → Proxy → temporarily disable any configured proxy → attempt the Chrome update. If it updates without the proxy, the proxy is filtering Google’s update domains. Adding the domains to the proxy allowlist (dl.google.com, update.googleapis.com, clients2.google.com) resolves this for the update mechanism.
Date and time affecting update verification
Chrome verifies the update package’s signature using certificate timestamps. If the system clock is significantly wrong, the certificate validation fails and the update rejects the package as potentially tampered. This produces an update failure that looks like a download error rather than a clock error.
Verify the clock: right-click taskbar → Adjust date and time → Sync now. After synchronising, attempt the update. If the clock was wrong and is now corrected, the update should proceed normally.
Chrome background update vs user-triggered update
Chrome normally updates in the background when running, typically within 24 hours of a new release. The update downloads silently and applies on the next Chrome restart. If Chrome has been running continuously for days without a restart, it may have already downloaded an update that’s waiting to be applied — it will show the current running version until restarted.
The small update indicator: look for a small icon in the top-right area of Chrome (a circular arrow or an up-arrow) that appears when a pending update is waiting. Clicking it shows a “Relaunch to update” option. Chrome was already updated — it just needed a restart to complete. This is the most common reason for “Chrome isn’t updating” reports on machines where Chrome is kept open continuously.
Chrome installation integrity check
Chrome includes a built-in software reporter tool (Software Reporter Tool, also called “chrome_elf.dll” cleanup) that checks for software conflicting with Chrome’s operation. If conflicting software is detected, it can affect Chrome’s ability to update. Navigate to chrome://settings/cleanupTool (or Settings → Reset and clean up → Clean up computer) → Find → allow Chrome to scan for interfering software. Remove anything it finds. Then retry the update.
64-bit vs 32-bit installation mismatch
On 64-bit Windows systems, Chrome is available as both 32-bit and 64-bit. If the 32-bit version was installed on a 64-bit system (common for older installations), Chrome’s update mechanism may try to update to the 64-bit version and fail because the installation paths don’t match what the update expects.
Check which version is installed: chrome://settings/help → the version number line includes “(32-bit)” or “(64-bit)”. If 32-bit is installed on a 64-bit Windows machine: download the 64-bit installer directly from Google’s Chrome download page → uninstall the 32-bit version → install 64-bit fresh. The 64-bit version is more secure (full ASLR), uses hardware features better, and has a cleaner update path on 64-bit Windows.
Virus or malware blocking Chrome updates
Some malware specifically targets browser update mechanisms to prevent security patches that would detect or block the malware from being installed. If Chrome updates consistently fail and other approaches haven’t resolved it: run a Malwarebytes scan (full scan, not just quick scan). Malware blocking update mechanisms is a specific category that many general antivirus scans miss because the malware itself appears benign — it just prevents other software from being updated.
After a clean Malwarebytes scan: retry the update. If it now works: the malware was the cause and was cleared by the scan. If Chrome still won’t update after a clean malware scan: proceed with the reinstall approach, which gives Chrome a completely clean starting point regardless of what was blocking the update mechanism.
Chrome update stuck downloading for hours
An update that shows “Downloading…” in chrome://settings/help but never completes: the download is stalled. Cancel by navigating away from the page → return → try again. If it stalls repeatedly at the same percentage: the partial download is corrupted. Navigate to %temp% → delete any files starting with “chrome” that are recent → retry. Temp files from failed Chrome downloads prevent re-downloading the update package because Chrome finds the partial file and tries to resume it rather than starting fresh.
A quick checklist for diagnosing Chrome update failures without working through everything: (1) What does chrome://settings/help show — an error code or “up to date”? Error code → look it up specifically. Up to date → Chrome is correct, you may need a restart to apply a pending update. (2) Is a pending update waiting (small arrow/relaunch indicator in toolbar)? Restart Chrome. (3) Does the update work in a new Windows user account? If yes → the issue is specific to the current profile or user account permissions. (4) Does it work after disabling the antivirus? If yes → add Google’s update domains to exclusions. These four checks resolve most non-enterprise Chrome update problems without needing the more involved fixes.
How often Chrome should be updating
Chrome releases stable channel updates approximately every 4 weeks, with intermediate security patches (dot releases) between major versions. If chrome://settings/help shows the current version was released more than 6 weeks ago and shows no errors when checking for updates: there genuinely may not be a newer version. Google staggers rollouts — not every machine receives updates simultaneously. Check the Chrome release blog (googlechromereleaseblog.blogspot.com) to see the current stable channel version and compare to what’s installed. A version that’s one or two minor releases behind is normal; a version that’s multiple major releases behind (e.g., 10+ versions) indicates a genuine update failure worth investigating.
For machines that need Chrome updates but where the GoogleUpdate service keeps getting disabled (common when system optimisation tools or group policies disable non-Microsoft background services): set a monthly reminder to check chrome://settings/help and manually trigger an update check. The manual trigger (clicking “Check for updates”) always works even when automatic background updates are disabled, so long as the network and installation are healthy. It’s less convenient than automatic updates but keeps Chrome current without needing to fix the underlying service configuration. See also Windows 11 Not Updating for a related case.
One edge case that confuses people: Chrome installed from the Microsoft Store behaves differently from the standalone installer. Store-installed Chrome updates through the Store mechanism rather than GoogleUpdate. If the About page shows an update error that the GoogleUpdate service fix doesn’t resolve: check whether Chrome was installed from the Microsoft Store (Apps → Chrome → the publisher shows “Google LLC” but the source shows “Microsoft Store”). For Store-installed Chrome, updating through the Store itself (open Microsoft Store → search Chrome → Update if available) resolves the update without any of the GoogleUpdate service troubleshooting. You might also run into Google Chrome Not Updating.
