Install Google Chrome

What the Chrome installer Worklet does

This Automox Worklet™ automates Google Chrome deployment on Windows endpoints. The Worklet detects the operating system architecture and downloads the appropriate installer version (x86, x64, or ARM64) to match your endpoint hardware.

The Worklet performs a machine-wide installation, making Chrome available to all users on the endpoint. It uses the MSI installer with silent installation flags, generating an installation log for troubleshooting.

Downloads come from the Automox software cache API, which maintains current Chrome versions. The installation includes a configurable timeout (default 300 seconds) to handle slow network conditions or large endpoints.

Why deploy Chrome through Automox

Browser standardization simplifies IT support and security management. Deploying Chrome through Automox provides consistent configuration across all endpoints regardless of whether users have local administrator rights.

The Worklet handles architecture differences automatically. You do not need separate policies for 32-bit, 64-bit, and ARM64 endpoints. One Worklet covers your entire Windows fleet.

After initial deployment, add Chrome to your Automox third-party patching policies to keep it updated automatically. This combination provides both initial deployment and ongoing update management.

How Chrome installation works

1. Evaluation phase: The Worklet queries the registry at HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for any entry with DisplayName matching Google Chrome. If Chrome is already installed, the Worklet exits without changes. Otherwise, it triggers remediation.

2. Remediation phase: The Worklet detects OS architecture using RuntimeInformation.OSArchitecture, selects the corresponding download URL from the Automox cache API, downloads the MSI to the WorkletCache directory, and executes msiexec.exe with /qn /norestart flags. Installation logs save to the cache directory for troubleshooting.

Chrome installation requirements

• Windows workstations or servers

• Internet connectivity to download from api.automox.com

• TLS 1.2 support for secure download

• Approximately 200 MB disk space for installer and installation

• Administrative privileges (provided by Automox agent)

Expected state after Chrome installation

After successful installation, Google Chrome appears in the Start menu and Programs and Features for all users on the endpoint. The browser version matches the latest available from Google at the time of installation.

The installer files are cleaned up automatically from the WorkletCache directory. Subsequent Worklet executions detect the existing installation and skip remediation. To keep Chrome updated, include it in your Automox third-party patching configuration.

How to validate install google chrome changes

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

4. Validate remediation effects from script operations such as Get-WorkletCache, Out-Null, New-Object, then rerun evaluation for compliance.

For technical validation, compare endpoint state to the Worklet evaluation logic and remediation flow for install google chrome. This supports repeatable software lifecycle workflows, faster change control review, and auditable compliance evidence.

Useful script references for this Worklet include evaluation operations such as Get-ItemProperty, Where-Object, Write-Output and remediation operations such as Get-WorkletCache, Out-Null, New-Object. Use these indicators to verify that endpoint changes match intended policy outcomes.

For technical validation, compare endpoint state to the Worklet evaluation logic and remediation flow for install google chrome. This supports repeatable software lifecycle workflows, faster change control review, and auditable compliance evidence.

Useful script references for this Worklet include evaluation operations such as Get-ItemProperty, Where-Object, Write-Output and remediation operations such as Get-WorkletCache, Out-Null, New-Object. Use these indicators to verify that endpoint changes match intended policy outcomes.