Windows - Data Collection & Auditing - Enable Google Chrome Update Log

What the Chrome update logging enabler does

This Automox Worklet™ enables detailed local logging for Google Chrome updates on Windows endpoints. The Worklet implements Google's recommended logging configuration by creating a configuration file at C:\GoogleUpdate.ini and setting the IsEnabledLogToFile registry value under both 32-bit and 64-bit registry paths.

The Worklet configures verbose logging across six Chrome update components: utilities, services, core functions, network operations, and optional features. Log files are generated at C:\ProgramData\Google\Update\Log\GoogleUpdate.log and capture all Chrome update activity including successful updates, failures, and network communication details.

This diagnostic Worklet checks both 32-bit (HKLM:\Software\Google\UpdateDev) and 64-bit (HKLM:\Software\WOW6432Node\Google\UpdateDev) registry locations to accommodate different Chrome installation architectures. The Worklet only remediates endpoints where logging is completely disabled, preserving any existing logging configurations.

Why enable Chrome update logging

Chrome update failures can occur silently without clear error messages, leaving IT operations teams without diagnostic information. When endpoints run outdated Chrome versions due to failed updates, your organization faces increased security risk from unpatched vulnerabilities.

Enabling update logging provides visibility into why Chrome updates fail on specific endpoints. You can identify network connectivity issues, permission problems, corrupted update components, or proxy configuration errors that prevent successful updates. This diagnostic data is essential for resolving persistent update failures across your fleet.

The detailed logs include timestamps, component-level debugging information, and network communication details that help you troubleshoot complex update scenarios. Rather than manually enabling logging on individual endpoints, this Worklet deploys the configuration at scale and captures future update attempts automatically.

How Chrome update logging configuration works

1. Evaluation phase: The Worklet checks for the existence of C:\GoogleUpdate.ini and verifies the IsEnabledLogToFile registry value in both HKLM:\Software\Google\UpdateDev and HKLM:\Software\WOW6432Node\Google\UpdateDev registry paths. If either the configuration file or registry key exists with the correct value of 1, the endpoint passes evaluation.

2. Remediation phase: The Worklet creates C:\GoogleUpdate.ini with verbose logging configuration for all six Chrome update components (LC_UTIL, LC_SERVICE, LC_CORE, LC_NET, LC_OPT) set to logging level 6. It then creates the UpdateDev registry keys under both 32-bit and 64-bit paths if they don't exist, and sets the IsEnabledLogToFile DWORD value to 1. The configuration takes effect for all subsequent Chrome update attempts.

Chrome update logging requirements

• Windows endpoints with Google Chrome installed (workstations or servers)

• Administrator privileges to create files in C:\ root directory

• Administrator privileges to modify HKLM registry keys

• Available disk space in C:\ProgramData\Google\Update\Log\ for log file storage

• Endpoint restart recommended after remediation for configuration to take full effect

Expected Chrome update behavior after remediation

After remediation and an endpoint restart, Chrome will generate detailed update logs at C:\ProgramData\Google\Update\Log\GoogleUpdate.log. The log file will appear automatically when Chrome attempts its next scheduled update check or when you manually trigger an update.

You can verify successful configuration by checking for the GoogleUpdate.ini file in C:\ and confirming the IsEnabledLogToFile registry value is set to 1 in HKLM:\Software\Google\UpdateDev. The log file includes timestamps, shows time in log entries, appends to existing logs rather than overwriting, and outputs to both standard output and debug streams for comprehensive troubleshooting.

How to validate enable google chrome update log changes

1. Run this Worklet on a pilot Windows endpoint and review evaluation output for enable google chrome update log.

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 Test-Path, Get-ItemProperty, Write-Output.

4. Validate remediation effects from script operations such as Test-Path, New-Item, Out-Null, then rerun evaluation for compliance.