.msi. bach build --msi writes one from the same bach.toml, next to the setup file.
Not carried (and reported as
not in the MSI): [[migrate]], [updates], user data folders, component downloads, requirements other than a Windows build in a quiet install, a run step’s other exit codes, and elevated run steps in a per-user package. The texts Windows Installer shows itself are English.
The window
Open the.msi (double-click it, or remove it under Settings > Apps) and you get the same window as the setup file’s, not Windows Installer’s plain progress box: the same style and layout, the install folder, the options, the license, the requirements, “Repair” and the removal page, in the user’s language. The package carries a small copy of the setup program for it (about 10 MB).
The window asks the questions and then calls Windows Installer with the answers, so the install is a real one: the same files, shortcuts, registry values, upgrade rules and Settings > Apps entry as the table above, with a progress bar that follows Windows Installer’s own. Cancelling makes Windows Installer undo what it did. A machine-wide package asks Windows for administrator rights once.
A quiet install (msiexec /i ... /qn, /qb, Group Policy, Intune) never shows the window. It runs Windows Installer’s own install with the defaults and ADDLOCAL, so the license page and the requirements other than a Windows build apply only when the window is shown. Windows Installer’s log of a window’s run is %TEMP%\<app id>-msi.log, next to the setup log.
- The version has to be three numbers (
1.4.2; 255, 255, 65535 at most), no suffix. - Up to 2 GB and 32,000 files. Names are written in Windows-1252; other characters show as
?. - An app with
[access]can’t be an MSI. The package is x64 and isn’t signed by--sign: sign it withsigntool.