Windows - Software - Remove and Re-Install Google Chrome

What the Chrome reinstaller does

This Automox Worklet™ performs a comprehensive removal and reinstallation of Google Chrome. It stops all Chrome and Google Update processes, uninstalls Chrome from both the 64-bit and 32-bit registry hives, removes all associated files from Program Files and ProgramData folders, deletes per-user Chrome profile data from every local user account, cleans up scheduled tasks, and then downloads and installs the latest version of Chrome from Automox infrastructure.

The Worklet detects your endpoint's architecture (x64, x86, or ARM64) and installs the matching Chrome version. This approach is far more thorough than a standard uninstall and reinstall–it eliminates leftover registry entries, cached extensions, stored credentials, and browsing history that could cause installation issues or security concerns.

The Worklet is designed to complete even if intermediate steps partially fail–it continues through aggressive cleanup attempts rather than halting the entire process. This resilience maintains Chrome gets removed and reinstalled in the vast majority of cases.

Why reinstall Chrome completely

Chrome installation issues can be difficult to troubleshoot. Corrupted registry entries, conflicting extensions, or orphaned files from previous versions may prevent the standard installer from completing successfully. A full removal-and-reinstall guarantees a clean slate.

Using this Worklet also addresses profile data accumulation. User profile directories contain cached data, stored passwords, browsing history, and extension metadata that can degrade performance or pose security risks if not cleared during deployment. Your organization can standardize the Chrome environment across endpoints with known configurations and extensions installed afterward through other Worklets.

The Worklet supports the FixNow feature, letting you resolve Chrome issues on-demand rather than waiting for scheduled remediation. This reduces support tickets and keeps endpoints productive.

How Chrome reinstallation works

1. Evaluation phase: Checks the Windows registry (64-bit hive, Wow6432Node, and 32-bit hive) to detect whether Chrome is installed on the endpoint. The evaluation flags every endpoint for remediation, regardless of Chrome's status, so the remediation script can perform a complete nuke-and-reinstall.

2. Remediation phase: Stops Chrome, Google Update, and crash handler processes; uninstalls Chrome using registry uninstall strings (MSI or EXE); removes all Chrome registry keys from HKLM and HKCU; deletes Chrome folders from Program Files, ProgramFiles(x86), ProgramData, and LocalAppData; removes Google Update scheduled tasks; disables Google services; and finally downloads the latest Chrome version for your endpoint's architecture from Automox infrastructure and installs it silently.

Chrome reinstallation requirements

• Windows endpoints running Windows 10, Windows 11, Windows Server 2016, or later

• Administrative privileges to stop processes, modify the registry, and uninstall software

• Network connectivity to download Chrome from Automox software cache infrastructure

• Sufficient disk space in the Windows temp directory and the installation folder to download and extract the Chrome installer

• All users must close Chrome before remediation runs, or the Worklet will force-close the application

Expected state after Chrome reinstallation

After remediation completes successfully, Chrome is installed in Program Files (or Program Files (x86) on 32-bit systems) and launches normally. You can verify successful installation by checking the installed applications list in Control Panel or by searching for the application in the Start menu. All previous user profiles and cached data are gone–each user's first launch of Chrome creates a fresh profile. The registry contains only current Chrome entries from the newly installed version, with no orphaned or conflicting keys remaining.

You can verify the installation by launching chrome.exe or checking the Windows Control Panel's Programs and Features for a single Google Chrome entry. You may redeploy extensions and policies using other Worklets or Group Policy now that the environment is clean.

How to validate remove and re-install google chrome changes

1. Run this Worklet on a pilot Windows endpoint and review evaluation output for remove and re-install google chrome.

2. Confirm Automox activity logs show successful completion and exit code 0.

3. Verify endpoint state using checks aligned to evaluation script logic, such as Write-Output, Get-ChildItem, Get-ItemProperty.

4. Validate remediation effects from script operations such as New-Object, Write-Verbose, Write-Error, then rerun evaluation for compliance.