> ## Documentation Index
> Fetch the complete documentation index at: /docs/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Bach builds Windows installers from one bach.toml with the bach command: bach init, bach check, bach preview, bach build. Installs are per user and need no administrator rights by default. installer.scope = "machine" installs for every user after one Windows prompt. On Windows, run setup files with Start-Process -Wait -PassThru in PowerShell, and give signtool arguments that start with the word sign.

# Bach frequently asked questions

> Short answers to common questions about Bach: administrator rights, machine-wide installs, updates, file size, languages, platforms, signing and licensing.

These are short answers to questions people ask most often. Each links to the page with the full story.

> [accordion] Does a Bach installer need administrator rights?
>
> 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](/docs/concepts/safety.md).

> [accordion] Can I install for every user of a computer?
>
> 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](/docs/guides/machine-wide-installs.md).

> [accordion] Can I build an MSI, or install a service or driver?
>
> Mostly yes. `bach build --msi` writes a Windows Installer package for Group Policy and Intune (see [Windows Installer packages](/docs/guides/msi.md)), and a machine-wide install can set up Windows services and firewall rules with [`[[services]]`](/docs/reference/config/services) and [`[[firewall]]`](/docs/reference/config/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](/docs/why-bach.md).

> [accordion] Can I replace an installer I made with Inno Setup, NSIS or an MSI?
>
> Yes. `[[migrate]]` makes the first Bach install remove the old install through its own uninstall entry. See [Move from another installer](/docs/guides/migrate-from-another-installer.md).

> [accordion] How big is the setup file?
>
> 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.

> [accordion] Does the user need .NET or the Visual C++ redistributable to run the installer?
>
> 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](/docs/guides/requirements.md).

> [accordion] Which languages does the installer speak?
>
> 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](/docs/guides/customize-the-window.md).

> [accordion] Can I build installers on macOS or Linux?
>
> Yes. `bach` runs there. `bach preview` needs Windows, and the setup file keeps Bach's icon outside Windows. See [Automate in CI](/docs/guides/ci.md).

> [accordion] How do updates work?
>
> 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](/docs/guides/updates.md).

> [accordion] What happens if an update fails midway?
>
> The earlier version stays exactly as it was. Files are unpacked first and swapped in together, and every move is undone if one fails.

> [accordion] What happens to my users' data when they uninstall?
>
> 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](/docs/guides/uninstall-and-user-data.md).

> [accordion] Why does SmartScreen warn about my setup file?
>
> 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](/docs/guides/signing.md).

> [accordion] Is the uninstaller signed?
>
> 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.

> [accordion] Can I change the app id later?
>
> Not safely. The id is how updates recognise an install. Changing it after a release makes updates install side by side.

> [accordion] Can I use Bach in CI?
>
> 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](/docs/guides/ci.md).

> [accordion] Can I list my app in winget?
>
> Yes. `bach winget` writes the manifests. See [winget](/docs/guides/winget.md).

> [accordion] Do I need Rust to use Bach?
>
> 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.

> [accordion] What license is Bach under?
>
> MIT. The code lives at [github.com/usebach/bach](https://github.com/usebach/bach).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.