For a machine-wide, unattended Chrome deployment, use the Google Chrome Enterprise MSI and call Windows Installer from an elevated PowerShell session:
$msi = 'C:Installgooglechromestandaloneenterprise64.msi'
$proc = Start-Process -FilePath 'msiexec.exe' -ArgumentList @('/i', $msi, '/qn', '/norestart', '/L*v', 'C:WindowsTempChromeInstall.log') -Wait -PassThru
if ($proc.ExitCode -ne 0) { throw "Chrome installation failed with exit code $($proc.ExitCode)" }
/qn suppresses all installer windows, /norestart prevents an automatic reboot, and /L*v writes a verbose log. Run PowerShell as administrator, or let a device-management agent execute it as SYSTEM.
What you need before running the command
- The current Chrome Enterprise MSI downloaded from Google’s official enterprise channel.
- An MSI architecture that matches the endpoint.
- A local or controlled network path such as
C:Installor a software-distribution cache. - Administrative rights, or an endpoint-management service that runs with system privileges.
- A test computer or pilot group before broad deployment.
Google documents the quiet pattern as msiexec /q /l GoogleChrome.msi. The /qn switch used above is the Windows Installer no-UI form commonly used by deployment wrappers. Always quote the MSI path when it contains spaces.
Install Chrome silently on one Windows computer
1. Download and validate the Enterprise MSI
Use the Chrome Enterprise MSI rather than the consumer installer EXE when you need machine-level deployment. Confirm that the package is newer than the Chrome version already deployed and that its architecture is appropriate for the device. Google warns that an older MSI cannot overwrite a newer deployed Chrome version.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstall#1 Best Overall
- 14" diagonal, 1366x768 resolution, HD BrightView LED, Glossy NON-TOUCH Display
2. Open an elevated PowerShell window
Start PowerShell with Run as administrator. If your management platform launches the script as SYSTEM, an interactive administrator window is not required.
3. Run the installer and check its result
$msi = 'C:Installgooglechromestandaloneenterprise64.msi'
$log = 'C:WindowsTempChromeInstall.log'
$proc = Start-Process `
-FilePath 'msiexec.exe' `
-ArgumentList @('/i', $msi, '/qn', '/norestart', '/L*v', $log) `
-Wait `
-PassThru
if ($proc.ExitCode -ne 0) {
throw "Chrome installation failed with exit code $($proc.ExitCode). See $log"
}
Write-Host "Chrome installation completed with exit code $($proc.ExitCode)"
-Wait keeps the script from reporting success before Windows Installer finishes, while -PassThru exposes the process exit code. Preserve the log path in your deployment system so a failed install can be diagnosed.
4. Verify the application
Launch Chrome from the Start menu or inspect the system installation directory:
Test-Path "$env:ProgramFilesGoogleChromeApplicationchrome.exe"
System-level Chrome normally resides under Program FilesGoogleChromeApplication. A user-level installation is under %USER DATA%GoogleChromeApplication. Installing from an MSI overrides a user-installed Chrome version when the MSI is newer; Google states, “Installing Chrome browser from an MSI overrides any version of Chrome browser installed by a user.”
Free tools Windows power users keep installed
One-click scans. No signup required.
Rank #2
- 1.1 GHz (boost up to 2.4GHz) Intel Celeron N5030 Quad-Core
- 4GB DDR4 System Memory; 128GB Solid State Drive
- 11.6" HD (1366 x 768) Multi-Touch Display
- Combo headphone/microphone jack - Noble Wedge Lock slot - HDMI; 2 USB 3.1 Gen 1
- Windows 11 Pro
Useful msiexec switches for deployment scripts
| Switch | Purpose | Typical use |
|---|---|---|
/i |
Install the specified MSI | /i C:InstallChrome.msi |
/q |
Quiet user-interface level | Google’s documented silent pattern |
/qn |
No user interface | Unattended deployment wrappers |
/norestart |
Do not restart Windows automatically | Managed endpoints where reboot policy is separate |
/L*v |
Verbose Windows Installer log | Incident diagnosis and pilot validation |
/x |
Uninstall an MSI package | Use only in a controlled removal workflow |
Do not add restart behavior casually. If your organization requires a reboot, schedule it through the device-management policy after the installer has returned a successful code.
Deploy to many computers
PowerShell through a management agent
Copy the MSI to each device or make it available from an authenticated distribution share, then run the script in the machine context. Use a deterministic local cache to avoid a network interruption halfway through installation:
$source = '\fileserverpackagesgooglechromestandaloneenterprise64.msi'
$msi = 'C:WindowsTempgooglechromestandaloneenterprise64.msi'
Copy-Item -Path $source -Destination $msi -Force
$proc = Start-Process msiexec.exe -ArgumentList @('/i', $msi, '/qn', '/norestart', '/L*v', 'C:WindowsTempChromeInstall.log') -Wait -PassThru
if ($proc.ExitCode -ne 0) { exit $proc.ExitCode }
exit 0
Secure the share and package permissions. A SYSTEM account may not have access to a user-mapped drive, so use a UNC path or stage the file locally first.
Active Directory Group Policy
Google supports MSI distribution through Active Directory Group Policy. Assign the package to computers, not individual users, when Chrome must be present before sign-in. Pilot the Group Policy on a test organizational unit, then use gpupdate /force on a test device to refresh policy.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Rank #3
- 256 GB SSD of storage.
- Multitasking is easy with 16GB of RAM
- Equipped with a blazing fast Core i5 2.00 GHz processor.
Configuration Manager, SMS, or another software-distribution platform
Microsoft System Center Configuration Manager, SMS, and other software-distribution tools can invoke the same MSI command. Configure the deployment as silent, wait for the process, collect the exit code, and retain ChromeInstall.log. Your platform’s detection rule should verify the installed Chrome executable or MSI product state rather than merely checking whether the script ran.
Version precedence and policy scope
Keep the Enterprise MSI current. Google warns that an older MSI cannot overwrite a newer deployed Chrome version, so a package that worked on one group can appear ineffective on a group with a more recent build. Maintain a package versioning process and test upgrades as well as first installs.
Device-level policies apply whether or not a user is signed in. User-level policies apply to particular signed-in users. Google provides policy templates for managed Windows PCs, and its Windows deployment guidance covers MSI rollout, Windows Group Policy, cloud policies, and staged testing. Chrome Enterprise Core is Google’s cloud-management option for managed Chrome deployments.
Test and validate a pilot
- Install the MSI on a representative test computer with the same Windows architecture, security controls, and connectivity as production devices.
- Confirm that Chrome launches and that the expected system path contains
chrome.exe. - Open
chrome://policyand verify that effective policies match the intended device or user scope. - Use
gpupdate /forcewhen testing Group Policy changes, then reopenchrome://policy. - Review the verbose MSI log and deployment exit code before expanding the assignment.
- Test an existing user-level Chrome installation and an upgrade from an older MSI.
Troubleshooting silent installs
No window appears, but Chrome is not installed
Check the PowerShell exit code and C:WindowsTempChromeInstall.log. Confirm that the MSI path exists, is readable by the execution account, and is not blocked by a network-share permission. A quiet installer intentionally provides no interactive error dialog.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteRank #4
- EFFORTLESS EVERYDAY PERFORMANCE: Powered by Intel Celeron N4020 processor and Windows 11 Home system, delivering reliable, low-power efficiency for daily tasks like document editing, email, online classes, and web browsing
- 15.6-INCH FULL HD DISPLAY: Enjoy immersive visuals on the 15.6" FHD (1920x1080) anti-glare screen with micro-edge bezels. Delivers clear details and comfortable viewing for long study sessions, working on spreadsheets, and video playback
- RESPONSIVE MULTITASKING & STORAGE: Built with 4GB LPDDR4 RAM and 128GB eMMC storage for smooth daily essential use. Expand your storage by up to 1TB via the integrated TF card slot to easily store movies, photos, and working files
- ADVANCED CONNECTIVITY: Outfitted with 2x Full-Featured Type-C ports for data transfer, fast charging, and dual-monitor output, alongside 2x USB 3.2 Gen1 ports and a 3.5mm audio jack for complete peripheral compatibility
- LIGHTWEIGHT & SILENT OPERATION: Slim and portable for effortless travel or commuting. Features a 1MP HD webcam for remote meetings, 38Wh battery with 45W Type-C fast charging, and a fanless silent design for peaceful work environments.
The script says the file cannot be found
Use an absolute path and quote it. Test with Test-Path $msi. Do not rely on a mapped drive when the script runs as SYSTEM; copy from a UNC path to a local cache first.
Access is denied
Run elevated or configure the management agent for device/SYSTEM context. Also check NTFS and share permissions on the MSI and log directory.
A newer Chrome is already present
Replace the package with a current Enterprise MSI. Google states that an older MSI cannot overwrite a newer deployed Chrome version. Do not force a downgrade unless your organization’s Chrome deployment policy explicitly supports it.
Group Policy has not applied
Run gpupdate /force, verify that the computer is in the targeted organizational unit, and check chrome://policy while signed in as the relevant user. Device and user policy scopes are different.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Best Value
- WINDOWS 11 | STABLE PERFORMANCE: Powered by Intel Celeron N4020 processor and Windows 11 system, this laptop delivers stable performance for everyday computing tasks. It supports web browsing, online learning, document editing, email communication, and basic office work with optimized power efficiency, providing a practical and reliable experience for essential daily use for daily use.
- 15.6” FHD IPS DISPLAY: Features a 15.6-inch Full HD IPS display with narrow bezels, offering wider viewing angles and clearer image details compared to standard panels. The improved screen-to-body ratio enhances visual experience for study, reading, document work, and video playback, making it suitable for both productivity and entertainment use.
- 4GB DDR4 + 128GB eMMC STORAGE: Equipped with 4GB DDR4 memory and 128GB eMMC storage for everyday basics such as browsing, documents, email, and online learning platforms. The built-in TF card slot supports storage expansion up to 1TB, giving you more flexibility for files, photos, videos, and daily documents. TF card not included.
- CONNECTIVITY & PORTS: Includes 1× TF card slot, 2× USB 3.2 Gen1 ports, and 2× full-featured Type-C ports (USB 3.2 Gen1). The Type-C ports support data transfer, charging, and video output, enabling flexible connection with external devices such as monitors, storage, and peripherals for daily work and study use.
- LIGHTWEIGHT DESIGN | ONLINE COMMUNICATION: Designed with a slim, portable profile, this laptop is easy to carry for school, commuting, and travel. A built-in 1MP front camera supports online classes, video meetings, remote communication, and everyday conferencing. The 3300mAh battery works with the low-power system design to support practical daily use, while thermal optimization helps maintain quieter operation during extended tasks.
The installer appears stuck
Look for a running msiexec.exe process and inspect the verbose log. Another MSI transaction, endpoint security scanning, or an unavailable source can delay completion. Because the example uses -Wait, your wrapper should allow a suitable management timeout and report failure if the process exits unsuccessfully.
Or skip the browser setup
If your goal is to capture pages after Chrome is available rather than manage the browser itself, ScreenshotNeo provides a website screenshot API and MCP server. It accepts a URL in one request and returns PNG, JPEG, WebP, or PDF. Before capture it accepts cookie/consent banners and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each step can be disabled. Bot checks, CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing, and responses identify the page verdict and billing status in X-Page-Verdict and X-Billed headers. Its MCP server includes take_screenshot, get_page_info, and capture_pdf for Claude, Cursor, and other MCP clients.
One-call examples
See the complete parameter reference in the ScreenshotNeo documentation.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp
import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
ScreenshotNeo includes full-page and element capture, device and viewport controls, dark mode, retina scale, PDF settings, custom CSS and JavaScript, waits, request blocking, headers, cookies, user agents, timezone and geolocation, transparent backgrounds, resizing, TTL caching, signed links, asynchronous webhooks, bulk capture, usage reporting, and an OpenAPI specification. Every feature is on every plan: 1,000 shots per month are free with no card; paid plans start at $5 for 3,000 shots. Create a free ScreenshotNeo account.
Recommended Free Tools
PowerShell deployment checklist
- Use a current Chrome Enterprise MSI and matching architecture.
- Run as administrator or SYSTEM.
- Use
/i /qn /norestartand a verbose/L*vlog. - Wait for completion and evaluate the exit code.
- Test policy scope at
chrome://policy. - Pilot before assigning the package broadly.
- Replace stale MSIs rather than attempting to overwrite newer Chrome builds.
Frequently Asked Questions
Can I run the MSI command from a non-elevated PowerShell window?
Only if a trusted deployment agent performs the operation with administrative or SYSTEM privileges; a normal user session generally cannot install Chrome machine-wide.
Does a silent MSI installation automatically reboot Windows?
Not with the example command: /norestart leaves reboot decisions to your management policy.
Where can I see why an unattended installation failed?
Open the verbose log at C:WindowsTempChromeInstall.log and correlate it with the PowerShell process exit code.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.

