Google Chrome 151.0.7922.76 offline installer now on Chocolatey

Google Chrome 151.0.7922.76 is now available as an offline installer package on Chocolatey, approved on 05 Aug 2026 and passing three automated checks, giving IT teams a scripted way to deploy the latest browser version without relying on Google’s web installer [1].

Package details and deployment options

The Chocolatey package uses Chrome’s MSI installer, automatically selecting the 64‑bit build on 64‑bit OSes and the 32‑bit build on 32‑bit OSes. It also respects existing 32‑bit installations on 64‑bit machines, updating only the 32‑bit copy if present [1]. The package includes PowerShell and batch scripts that expose enhanced exit codes (0, 1605, 1614, 1641, 3010) to signal success or required reboots, simplifying automated rollouts [1].

Enterprise rollout considerations

Because the package always pulls the latest Chrome release, organizations cannot pin older versions through Chocolatey; any checksum mismatch that arises when Google publishes a new installer will trigger an automatic update [1]. For larger enterprises, the documentation recommends proxying the Chocolatey feed through internal NuGet repositories (e.g., Nexus, Artifactory, ProGet) to cache the package and avoid external 404 errors [1]. This mirrors standard best practices for managing third‑party binaries in secure environments.

What to watch

• Next Chrome release cadence – Monitor Google’s official release notes for version 151.0.7922.77 or higher, which will replace the current package automatically.
• Enterprise policy updates – Watch for any changes in Chrome’s MSI deployment flags that could affect silent installs or update behavior.
• Security advisory timing – New CVE patches (e.g., the high‑severity CVE‑2025‑12725 in earlier builds) often arrive with browser updates; ensure the offline installer is refreshed promptly [2].

The availability of Chrome 151.0.7922.76 as a vetted offline installer removes a key friction point for large‑scale Windows deployments, but the automatic‑update nature means enterprises must stay vigilant about version drift and security patch timing.