
For example, if you already have Chrome Stable installed in %ProgramFiles%, running mini_installer.exe directly will be a no-op. Similarly, if there is already a per-machine canary/dev/beta/stable version installed in %ProgramFiles%, the corresponding per-user installation will be blocked.

Include -verbose-logging on the command line to make the log very verbose (and possibly informative).

If installation is failing for some reason, you can see why in %TMP%\chromium_installer.log. Per-user installs are blocked if a per-machine install is already present. You can use -system-level for a per-machine install into %ProgramFiles%. This folder contains files to build mini_installer.exe, the Windows installer for Chromium.īy default, running mini_installer.exe will do a per-user install of Chromium into %LOCALAPPDATA%\Chromium\Application.
