Skip to main content
These are short answers to questions people ask most often. Each links to the page with the full story.
Not by default. Installs are per user, into %LOCALAPPDATA%\Programs, and Bach only writes to the user’s own folders and HKCU, with no UAC prompt. An app asks Windows for administrator rights once only when it says so: with installer.scope = "machine", with elevated = true on one [[run]] step, or with an elevated [[migrate]]. See Safety rules.
Yes. Set installer.scope = "machine" and setup installs into %ProgramFiles% and HKLM after one Windows prompt. Background updates are off for such an app. See Machine-wide installs.
Mostly yes. bach build --msi writes a Windows Installer package for Group Policy and Intune (see Windows Installer packages), and a machine-wide install can set up Windows services and firewall rules with [[services]] and [[firewall]]. A setup file with services can’t be an MSI yet. Drivers and install-time scripts are not built in: a [[run]] step can start a program that does them, and for the rest use another tool. See Why Bach.
Yes. [[migrate]] makes the first Bach install remove the old install through its own uninstall entry. See Move from another installer.
A Bach setup file adds about 9 MB to your app, because it carries the installer window. The archive is compressed with zstd, and installer.compression trades size for build time.
No. The C runtime is linked in, so setup files start on a fresh Windows. Your app may need runtimes of its own. Declare them with requirements.
19: English, German, Dutch, French, Spanish, Italian, Portuguese, Polish, Russian, Turkish, Japanese, Korean, Simplified Chinese, Traditional Chinese, Swedish, Czech, Vietnamese, Indonesian and Hindi. It follows the user’s Windows display language. See Customize the window.
Yes. bach runs there. bach preview needs Windows, and the setup file keeps Bach’s icon outside Windows. See Automate in CI.
Running a newer setup file over an install updates it in place, and files the new version no longer ships are removed. Apps can also update themselves from an https feed, and bach build --patch-from can offer a smaller patch with only the files that changed. See Updates.
The earlier version stays exactly as it was. Files are unpacked first and swapped in together, and every move is undone if one fails.
It stays, unless they tick “Also delete my data”. Only folders you list in [uninstall] data, inside their profile, can be deleted. See Uninstall and data.
Windows warns about unsigned programs from publishers it does not know yet. Sign the file with signtool, or let bach build --sign do it. Signing is optional and needs a code-signing certificate. See Signing.
No, by design. It is written on the user’s computer from the signed setup file without the signature, because a signature only covers the exact file it was made for.
Not safely. The id is how updates recognise an install. Changing it after a release makes updates install side by side.
Yes. bach build exits with a non-zero code and a readable message on any problem. There is a GitHub Action. See Automate in CI.
Yes. bach winget writes the manifests. See winget.
No. Install it with the PowerShell or shell script, Scoop, npm (@usebach/cli) or a zip. Rust is only needed to build Bach from source.
MIT. The code lives at github.com/usebach/bach.