On a managed Windows computer, install Chrome without showing setup windows by running the Chrome Enterprise MSI through Windows Installer:
msiexec /i "GoogleChromeStandaloneEnterprise64.msi" /qn /norestartRun it from an elevated deployment context. Add verbose logging when you need evidence of what happened:
msiexec /i "GoogleChromeStandaloneEnterprise64.msi" /qn /norestart /L*v "C:WindowsTempChromeInstall.log"This method is intended for machine-wide, unattended deployment. The MSI must match the endpoint architecture and must not be older than a Chrome version already installed.
What the silent Chrome command does
msiexec is Windows Installer. The switches determine how the package is applied:
#1 Best Overall
- FOR HOME, WORK, & SCHOOL – With an Intel processor, 14-inch display, custom-tuned stereo speakers, and long battery life, this Chromebook laptop lets you knock out any assignment or binge-watch your favorite shows..Voltage:5.0 volts
- HD DISPLAY, PORTABLE DESIGN – See every bit of detail on this micro-edge, anti-glare, 14-inch HD (1366 x 768) display (1); easily take this thin and lightweight laptop PC from room to room, on trips, or in a backpack.
- ALL-DAY PERFORMANCE – Reliably tackle all your assignments at once with the quad-core, Intel Celeron N4120—the perfect processor for performance, power consumption, and value (2).
- 4K READY – Smoothly stream 4K content and play your favorite next-gen games with Intel UHD Graphics 600 (3) (4).
- MEMORY AND STORAGE – Enjoy a boost to your system’s performance with 4 GB of RAM while saving more of your favorite memories with 64 GB of reliable flash-based eMMC storage (5).
| Part | Purpose |
|---|---|
/i |
Installs the package that follows it. |
"GoogleChromeStandaloneEnterprise64.msi" |
The Chrome Enterprise MSI file. Use the actual path if it is not in the current folder. |
/qn |
Runs with no Windows Installer user interface. |
/norestart |
Prevents Windows Installer from restarting the computer automatically. |
/L*v "C:WindowsTempChromeInstall.log" |
Writes a verbose installation log. The folder must exist and be writable. |
Google’s Chrome deployment guidance also documents running the MSI directly with quiet and logging options. The important distinction is that an unattended command suppresses prompts; it does not remove prerequisites such as administrator rights, a compatible package, or enough disk space.
Before you run it
Download the managed package
Obtain the Chrome Enterprise Bundle or the Windows MSI from Google’s Chrome Enterprise download resources. The Enterprise package is the same Chrome browser used by consumers, with deployment and management controls intended for organizations.
Match architecture and version
- Use the 64-bit MSI for supported 64-bit Windows endpoints and the package that matches your target architecture.
- Do not push an MSI that is older than the Chrome version already installed. Google states that an older MSI cannot overwrite a newer installation.
- Keep the package in a local, trusted location or an authenticated distribution share. Do not ask every endpoint to download an installer from an unverified mirror.
Use an elevated context
A machine-wide MSI install normally requires administrative rights. In a test, open Command Prompt with Run as administrator. In production, use the deployment system’s device or system context and confirm that it can read the MSI and write to the log directory.
Run a silent install manually
- Copy the MSI to a test machine or make it available on a trusted share.
- Open an elevated Command Prompt.
- Change to the directory containing the package, or provide its full path.
- Run the quiet command:
msiexec /i "C:PackagesGoogleChromeStandaloneEnterprise64.msi" /qn /norestartFor the first pilot, use a log:
msiexec /i "C:PackagesGoogleChromeStandaloneEnterprise64.msi" /qn /norestart /L*v "C:WindowsTempChromeInstall.log"Because /qn hides the interface, the command window may appear to do nothing. Wait for msiexec.exe to finish and inspect the process exit code or log rather than expecting a wizard.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Batch-file example
A deployment batch file can capture the exit code for your management system:
@echo off
set "MSI=C:PackagesGoogleChromeStandaloneEnterprise64.msi"
set "LOG=C:WindowsTempChromeInstall.log"
msiexec.exe /i "%MSI%" /qn /norestart /L*v "%LOG%"
set "RC=%ERRORLEVEL%"
echo Chrome MSI exit code: %RC%
exit /b %RC%Return the Windows Installer code unchanged so the deployment console can distinguish success, a required restart, and a failure.
Rank #2
- Intel Celeron N4120: 4 Cores & Threads, 1.1GHz Base Clock, Up to 2.6GHz Boost Clock, 4MB Cache, Intel UHD Graphics 600. The perfect combination of performance, power consumption, and value helps your device handle multitasking smoothly and reliably with four processing cores to divide up the work.
- 14" HD Display: 14.0-inch diagonal, HD (1366 x 768), micro-edge, anti-glare. See your digital world in a whole new way. Enjoy movies and photos with the great image quality and high-definition detail of 1 million pixels.
- Memory & Storage: 4 GB LPDDR4x & 64 GB eMMC Storage. Adequate high-bandwidth RAM to smoothly run multiple applications and browser tabs all at once. An embedded multimedia card provides reliable flash-based storage.
- Ports:2 x USB 3.0 Type-A，1 x USB 3.0 Type-C，1 x HDMI，1 x Headphone Jack
- Chrome OS: Chromebook is a computer for the way the modern world works, with thousands of apps. Enjoy the seamless simplicity that comes with Google Chrome and Android apps, all integrated into one laptop. It’s fast, simple, and secure.
Deploy the MSI across Windows devices
Active Directory Group Policy
- Place the MSI on a share that computer accounts can read. Use a UNC path rather than a drive letter mapped only in your administrator session.
- Open Group Policy Management and create or edit a computer policy linked to the organizational unit containing the pilot devices.
- Add the MSI under the computer software-installation policy and point it to the UNC package path.
- Start with a small pilot OU. After the policy is applied, restart a test device if your policy configuration requires it.
- On the endpoint, run
gpupdate /forcewhen policy changes have not appeared, then verify Chrome and its policies.
Google lists Group Policy Management as a supported distribution mechanism for the Chrome Enterprise MSI.
Configuration Manager and other deployment systems
Microsoft System Center Configuration Manager and HP Client Automation are also named by Google as ways to distribute the package. In either system, define the install command as:
msiexec.exe /i "GoogleChromeStandaloneEnterprise64.msi" /qn /norestart /L*v "C:WindowsTempChromeInstall.log"Configure the package’s detection rule against the installed Chrome MSI or application version used by your organization. Keep detection and installation in the same architecture and version plan; otherwise a console may report success while repeatedly retrying the deployment.
Intune and other cloud management services
The deployment guidance summarized here specifically names Group Policy Management, HP Client Automation and Configuration Manager. Intune and other cloud tools change their packaging and detection screens over time. If you use one, package the Enterprise MSI according to your tenant’s current Win32 or line-of-business application workflow, preserve the quiet command, and validate detection on a pilot group before broad assignment.
Verify that installation and policies worked
Check the installer result
Use the deployment console’s result and the verbose log together. A zero exit code generally indicates success; a code indicating that a restart is required should be handled by your organization’s maintenance policy rather than forcing an unexpected reboot.
Check Chrome itself
- Open Chrome on a pilot endpoint.
- Visit
chrome://versionto confirm the installed version and executable path. - Visit
chrome://policyto inspect policies that should be managed. - If a Group Policy change is missing, run
gpupdate /force, restart Chrome, and check the policy page again.
The MSI installs the browser; policy settings are administered separately through the management system. Keeping those two functions separate makes it easier to troubleshoot whether a problem is installation, policy delivery, or policy precedence.
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 reinstallRank #3
- Storage: 16GB Flash Memory
- OS: Chrome OS
- Screen Size: 11.6"
Common failures and fixes
| Symptom | Likely cause | What to do |
|---|---|---|
| A setup window appears | The command was run without a quiet switch. | Use /qn and confirm that the deployment tool is executing the intended command, not launching the MSI interactively. |
| Access denied or error 1603 | The process lacks elevation, the package path is inaccessible, or another installation condition failed. | Run from an elevated context, verify read access to the MSI and write access to the log folder, then inspect the verbose log for the first failing action. |
| Error 1618 | Another Windows Installer transaction is already running. | Wait for the other installation to finish and retry; do not start multiple MSI transactions concurrently. |
| The command reports success but Chrome is not present | The wrong architecture, an incorrect detection rule, or a package launched in a different user context. | Check chrome://version, the MSI log, the package path, and the deployment system’s detection settings. |
| An older package will not replace Chrome | The installed browser is newer than the MSI. | Build the deployment from an MSI at least as new as the deployed Chrome version, then pilot it again. |
Policy is missing in chrome://policy |
Group Policy has not refreshed, the device is in the wrong organizational unit, or another policy has precedence. | Run gpupdate /force, confirm OU scope and computer targeting, restart Chrome, and review the policy page. |
| The log file is absent | The directory does not exist or the deployment account cannot write there. | Create the directory first or choose a writable system location, then rerun with /L*v. |
Pilot, reliability and operational guidance
Pilot before fleet rollout
Use representative hardware, Windows editions, existing Chrome versions, proxy settings and policy assignments in the pilot. Include at least one device that already has Chrome so you can verify the version rule and one clean device so you can verify first-install behavior.
Control restarts deliberately
/norestart keeps the installer from rebooting a user’s computer. It does not guarantee that every pending Windows operation can complete without a later restart. Schedule any required reboot through your normal maintenance window and communicate it separately.
Make logs useful but limited
Verbose logs are valuable during a pilot and incident investigation. They can contain paths, usernames, property values and deployment details, so store them with the same access controls used for other endpoint logs. After the package is stable, retain the logging level and retention period that your operational policy requires rather than collecting indefinitely.
Keep package and policy lifecycles separate
Chrome version deployment and browser policy changes have different rollback and testing needs. Version the MSI and policy configuration independently, document the target groups, and promote each change from pilot to broader rings only after checking the endpoint and policy views.
What changes on Mac and Linux?
The Windows MSI command does not apply to macOS or Linux. Google’s enterprise resources cover all three platforms, but each uses its own package and management workflow. Windows uses the MSI for managed machine installation. Linux policy documentation uses managed files under /etc/opt/chrome/policies/managed for browser applications and extensions. Use the platform-specific package and policy instructions rather than attempting to run msiexec outside Windows.
Or skip the browser setup
If your next task is taking a clean screenshot of a deployed site or an internal status page, ScreenshotNeo provides a single-request screenshot API and an MCP server for AI clients. It is separate from Chrome installation, but avoids maintaining your own headless-browser capture code.
Rank #4
- Processor and Memory Configuration: Features an Intel Celeron 3865U Processor with 4GB DDR4 Memory, Gigabit LAN, 802.11ac Wi-Fi and 32GB M.2 SATA SSD
- Android App Compatibility: Full support of Android apps from Google play on Chrome OS
- 4K UHD Graphics Display Support: Integrated Intel 4K UHD Graphics supports 2x monitors using HDMI and DisplayPort over Type C for compatibility with legacy Display connections like VGA and DVI
- Wireless Connectivity and File Sharing: Share files or stream your favorite media with Intel 802.11ac Wi-Fi, Bluetooth 4.2, and USB 3.1 Gen 1 Type a & Type C Ports
- Power Over Type C Technology: Power over Type C minimizes cable clutter and delivers power to monitors, projectors, and mobile devices
One GET request returns PNG, JPEG, WebP or PDF output:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpSee the ScreenshotNeo API documentation for request options. Before capture, it can accept the cookie or consent banner and remove 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 are not billed, and response headers identify the page verdict and billing result. Its MCP server exposes take_screenshot, get_page_info and capture_pdf to Claude, Cursor and other MCP clients.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsThe Free plan includes 1,000 screenshots each month with no card. Paid plans start at $5 for 3,000 screenshots; every feature is included on every plan. Create a free ScreenshotNeo account to try it.
FAQ
Can the MSI install Chrome for every user on a shared Windows computer?
The Enterprise MSI is intended for managed, machine-wide deployment. Test shared-device behavior in your own Windows configuration and confirm the resulting installation and policies on a pilot before assigning it broadly.
Should browser policies be embedded in the MSI?
No. Treat the MSI as the browser package and deliver management policies through Group Policy or your endpoint-management platform so each can be changed and audited independently.
Is a silent install reversible?
Yes, your management platform can remove or replace the deployed application, but the exact uninstall command and product identifier depend on the package and deployment system. Record the package metadata during pilot so rollback is deliberate rather than improvised.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Frequently Asked Questions
Can the MSI install Chrome for every user on a shared Windows computer?
The Enterprise MSI is intended for managed, machine-wide deployment. Test shared-device behavior in your own Windows configuration and confirm the resulting installation and policies on a pilot before assigning it broadly.
Should browser policies be embedded in the MSI?
No. Treat the MSI as the browser package and deliver management policies through Group Policy or your endpoint-management platform so each can be changed and audited independently.
Is a silent install reversible?
Yes, your management platform can remove or replace the deployed application, but the exact uninstall command and product identifier depend on the package and deployment system. Record the package metadata during pilot so rollback is deliberate rather than improvised.
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.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →
