Wingetlywingetly
← All apps

Google Chrome Beta

by Google LLCv154.0.8037.17

Last updated

Try new features with Chrome Beta

Visit homepage

Install with winget

$ winget install --id Google.Chrome.Beta --exact --version 154.0.8037.17

Run in Command Prompt, PowerShell, or Windows Terminal. Prompts for any agreements.

Silent install command for Google Chrome Beta

Google Chrome Beta uses MSI (WiX). The silent install switches are /quiet /norestart.

One-line silent install (x64, machine scope)
msiexec.exe /i googlechromebetastandaloneenterprise64.msi /quiet /norestart

See the full silent install reference for Google Chrome Beta →

Built by Pckgr

For Intune admins

Stop chasing app updates. Pckgr patches them for you.

Automated application patching for Microsoft Intune. Pckgr keeps a curated library of 1,000+ apps continuously up-to-date in your tenant via Microsoft Graph - no manual repackaging, no chasing vendor sites.

Start free 30-day trial

No credit card required.

About

Feeling adventurous? Preview upcoming Google Chrome features before they’re released and give us feedback to make Chrome a better browser.

Installers · v154.0.8037.17

ArchitectureTypeScopeInstallDownload
x86MSI
WiX
machineDirect
x64MSI
WiX
machineDirect
arm64MSI
WiX
machineDirect

Copy a command tailored to that specific architecture, type, and scope - useful when winget would otherwise pick a different default.

Security

25 known CVEs via NVD

  • medium4.3Patched in wingetCVE-2026-87658affects before 153.0.8010.36Sep 9, 2026

    Information leak in Extensions in Google Chrome prior to 153.0.8010.36 allowed a remote attacker leveraging social engineering to obtain cross-origin data via a crafted Chrome extension. (Chromium security severity: Medium)

    Vendor advisory
  • low3.1Patched in wingetCVE-2026-87657affects before 153.0.8010.36Sep 9, 2026

    Use after free in V8 in Google Chrome prior to 153.0.8010.36 allowed a remote attacker who had compromised the renderer process to read memory inside the sandbox via a crafted HTML page. (Chromium security severity: Medium)

    Vendor advisory
  • medium5.4Patched in wingetCVE-2026-87656affects before 153.0.8010.36Sep 9, 2026

    Improper state validation in Safebrowsing in Google Chrome prior to 153.0.8010.36 allowed a remote attacker to bypass system access restrictions via a crafted HTML page. (Chromium security severity: Low)

    Vendor advisory
  • medium5.4Patched in wingetCVE-2026-87655affects before 153.0.8010.36Sep 9, 2026

    Clickjacking in Downloads in Google Chrome prior to 153.0.8010.36 allowed a remote attacker leveraging social engineering to spoof UI elements via a crafted HTML page. (Chromium security severity: Medium)

    Vendor advisory
  • critical9.6Patched in wingetCVE-2026-87654affects before 153.0.8010.36Sep 9, 2026

    Buffer overflow in ANGLE in Google Chrome on on Windows prior to 153.0.8010.36 allowed a remote attacker to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High)

    Vendor advisory
  • medium5.4Patched in wingetCVE-2026-87653affects before 153.0.8010.36Sep 9, 2026

    UI misrepresentation in FullScreen in Google Chrome on on Windows prior to 153.0.8010.36 allowed a remote attacker to spoof UI elements via a crafted HTML page. (Chromium security severity: Low)

    Vendor advisory
  • low3.1Patched in wingetCVE-2026-87652affects before 153.0.8010.36Sep 9, 2026

    Incorrect authorization in PushAPI in Google Chrome prior to 153.0.8010.36 allowed a remote attacker who had compromised the renderer process to bypass web origin policy via a crafted HTML page. (Chromium security severity: Medium)

    Vendor advisory
  • medium4.3Patched in wingetCVE-2026-87651affects before 153.0.8010.36Sep 9, 2026

    Incorrect authorization in Paint in Google Chrome prior to 153.0.8010.36 allowed a remote attacker to obtain cross-origin data via a crafted HTML page. (Chromium security severity: High)

    Vendor advisory
Showing 8 of 25. Source: NVD, updated 3h ago. Patch status is best-effort: NVD's fix version is compared against the latest version in winget, but the two version formats don't always align. Confirm with the vendor advisory before treating any specific build as safe.

See a CVE that affects your fleet? Push the patched version to Intune in one click with Pckgr - automated patching is the only way to keep up.

Related apps

  • Android StudioGoogle LLC
    Google.AndroidStudiov2026.1.4.7

    The official Integrated Development Environment (IDE) for Android app development.

  • Google ChromeGoogle LLC
    Google.Chromev153.0.8010.37

    The Fast & Secure Web Browser Built to be Yours

  • Android SDK Platform-ToolsGoogle LLC
    Google.PlatformToolsv37.0.1

    Android SDK Platform-Tools includes tools that interface with the Android platform, primarily adb and fastboot.

  • Google Chrome (EXE)Google LLC
    Google.Chrome.EXEv153.0.8010.37

    The browser built by Google

  • Google Chrome Beta (EXE)Google LLC
    Google.Chrome.Beta.EXEv154.0.8037.17

    Try new features with Chrome Beta

  • Google UpdaterGoogle LLC
    Google.GoogleUpdaterv152.0.7933.0

    An updater to keep Chrome (and certain other Google software) up to date.

More from Google LLC or browse beta, browser, chromium.

Frequently asked questions

How do I install Google Chrome Beta on Windows?
Open Windows Terminal, PowerShell, or Command Prompt and run: winget install --id Google.Chrome.Beta --exact --version 154.0.8037.17. winget downloads the installer from Google LLC and runs it. Requires Windows 10 (1809+) or Windows 11.
How do I install Google Chrome Beta silently for unattended deployment?
Add --silent and accept the agreements upfront: winget install --id Google.Chrome.Beta --exact 154.0.8037.17 --silent --accept-package-agreements --accept-source-agreements. This is the variant Intune, Configuration Manager, and other deployment tools should use.
What are the silent install switches for Google Chrome Beta?
Google Chrome Beta uses MSI (WiX). Run the downloaded installer with: msiexec.exe /i googlechromebetastandaloneenterprise64.msi /quiet /norestart. The silent switches are /quiet /norestart.
How do I uninstall Google Chrome Beta via winget?
Run: winget uninstall --id Google.Chrome.Beta --exact. Add --silent for unattended uninstalls. winget will use the registered uninstaller from Google Chrome Beta's Apps & Features entry.
Is Google Chrome Beta free?
Google Chrome Beta is distributed under Freeware. Refer to the publisher (https://www.google.com/chrome/beta/) for the full license terms - Wingetly itself does not charge for installation.
Does Google Chrome Beta work on Windows 10?
Yes, as long as your Windows 10 build supports winget (1809 or newer). winget ships with App Installer on Windows 10/11 and pulls Google Chrome Beta directly from the publisher.
How do I keep Google Chrome Beta up to date?
Run winget upgrade --id Google.Chrome.Beta --exact, or winget upgrade --all to update everything winget tracks. We index 1 version of Google Chrome Beta from microsoft/winget-pkgs.