Windows - Software - Uninstall Google Chrome

What the Chrome uninstaller does

This Automox Worklet™ detects and removes Google Chrome from Windows endpoints running both 32-bit and 64-bit operating systems. The Worklet searches the Windows Registry in multiple locations to identify Chrome installations, including the native registry hive and the 32-bit compatibility hive (Wow6432Node) on 64-bit systems.

The Worklet handles the uninstallation process by first stopping any running Chrome processes to prevent file lock errors. It then executes the Chrome uninstaller with system-level flags, supporting both MSI and EXE installation methods. The remediation script automatically relaunches in 64-bit PowerShell when necessary to maintain proper registry access and uninstallation on 64-bit endpoints.

The Worklet examines registry keys including HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall, HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall, HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall. exe -ArgumentList "/x $($version.PSChildName) /qn", "Stop-Process", and "Test-Path".

Why remove Chrome from endpoints

Organizations frequently need to standardize on approved software versions or switch to alternative browsers for compliance, security, or cost management reasons. Manually uninstalling Chrome from multiple endpoints consumes significant IT operations time, especially when users have cached data or customized settings that complicate the removal process.

This Worklet automates Chrome removal across your fleet, eliminating manual intervention and verifying consistent uninstallation across all endpoint architectures. By removing outdated or unapproved browser versions through Automox, you reduce security exposure from deprecated software and simplify endpoint standardization initiatives.

How Chrome uninstallation works

1. Evaluation phase: The Worklet checks the Windows Registry at HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall and HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall to determine if Google Chrome is installed. On 64-bit systems, it uses.NET registry classes to bypass 32-bit redirection and accurately detect both 32-bit and 64-bit installations. If Chrome is found, the endpoint is flagged for remediation.

2. Remediation phase: The Worklet stops all running Chrome processes to prevent file lock errors during uninstallation. It then executes the Chrome uninstaller with silent flags (--uninstall --multi-install --system-level --force-uninstall) for EXE installations, or the MSI uninstall command (msiexec /x) for MSI installations. The script validates the uninstall exit code and confirms successful removal before reporting completion.

Chrome uninstallation requirements

• Windows 7 or later (all supported Windows editions: XP through Windows 11)

• 32-bit or 64-bit architecture support

• Local administrator privileges required to access registry and execute uninstall commands

• Chrome uninstaller must be present (standard with any Chrome installation)

• No active Chrome user sessions during remediation (Worklet stops processes automatically)

Expected state after Chrome removal

After successful remediation, Google Chrome will be completely removed from the endpoint. The Worklet deletes the Chrome installation directory, registry entries, and all associated shortcuts from the Start menu and Desktop. Subsequent evaluation runs will report that Chrome is not installed.

The Worklet returns an exit code of 0 on success, indicating that uninstallation completed without errors. If users attempt to launch Chrome after remediation, they will receive a "program not found" error. To verify successful removal, check the Windows Registry at the locations mentioned in the evaluation phase or use the Programs and Features control panel to confirm Chrome no longer appears in the installed applications list.

How to validate uninstall google chrome changes

1. Run this Worklet on a pilot Windows endpoint and review evaluation output for uninstall 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 Get-ChildItem, Get-ItemProperty, Where-Object, then rerun evaluation for compliance.