> ## 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.

# The installer window: every page and state

> A tour of the Bach setup window: requirement, license, ready, working, done and failed pages, update, reinstall and downgrade states, and keyboard use.

By default the setup window is one calm column: the logo, a heading, one line of copy, a card of choices and buttons at the bottom. [`[layout]`](/docs/reference/config/layout) can arrange it differently, for example beside a large picture. Pages rise in as they replace each other. This page describes every page and state you can meet, and which settings change them.

![The install page in light mode with the install location, a component, and desktop shortcut and start-with-Windows options](https://mintcdn.com/bach/Nejvqm3NCmw8u8dx/images/install-light.png?fit=max\&auto=format\&n=Nejvqm3NCmw8u8dx\&q=85\&s=cd71edab53dfda9f6780fd902884e2b2)

The first page of a fresh install, in light and dark mode.

## The pages in order

| Page | When it shows | What it offers |
| - | - | - |
| Requirement | Something the app needs is missing (see [requirements](/docs/guides/requirements.md)) | A button to the download, "Try again" and "Continue anyway" (for a requirement that is there although setup did not find it) |
| License | `installer.license` is set, and on an update only if the license changed | The terms in a card that scrolls, and "I agree" |
| Ready | The first page | The location, optional components, options and the main button |
| Working | While installing, updating or removing | An honest progress bar with step labels, and "Cancel" while the files are being unpacked |
| Done | After success | "Open", an optional website link, and "Close" |
| Failed | Something went wrong | A readable sentence, "Try again" and "Save support info" |

Requirements come first, then the license, then the ready page.

## The license page

The license sits in a card that scrolls smoothly and has a scrollbar along its right edge. Drag the bar, or click the empty track to move a page at a time. The text can be selected and copied: drag over it, double-click a word, triple-click a paragraph, or press Ctrl+A to select all and Ctrl+C to copy. Page Up, Page Down, Home and End scroll the card. Nothing is redrawn while the page is still, so a long license stays light on the processor and memory.

## The first page changes with what is on the computer

| Situation | Heading and button (English defaults) |
| - | - |
| No earlier install | "Install My App", button "Install" |
| The same version is installed | "Reinstall My App", button "Reinstall". Reinstalling keeps your data. |
| An older version is installed | "Update My App", button "Update". Keeps your data. |
| A newer version is installed | The downgrade page, which refuses to install over it |
| The setup file is damaged | The problem page, with a sentence about what is wrong |

When the same version is installed, the page also shows a **Repair** button next to **Reinstall**. Repair checks every installed file against the SHA-256 in the setup file, writes back the ones that are missing or changed, and redoes shortcuts and registration with the options the app was installed with. Nothing else in the folder and no user data is touched. It is the window's version of `--silent --repair`.

On an update the location row is fixed: updates always stay where they are. Every one of these texts can be replaced in [`[text]`](/docs/reference/config/text).

## The removal window

The uninstaller shows its own pages: "Remove My App", an unticked **Also delete my data** box when `[uninstall] data` is set, progress, and a last page that says whether data was deleted or kept. A feedback link ("Tell us why") appears when `uninstall.feedback_url` is set. See [The uninstaller and your users' data](/docs/guides/uninstall-and-user-data.md).

## When the app is still open

If the app is running, setup says so and does not replace files in use. The error page offers **Try again**, and a **Close and continue** button that asks the app to close the way Windows Update does. It may ask to save first. Nothing is killed. If the app will not close, the window says so.

## Errors

Errors are human sentences with a way forward. The most common ones have their own texts: the app is still open, a file is in use, another setup is running, the disk is full (with the needed and free size) and access was denied. "Access is denied" is reported as a file in use only while a running program really holds the file, which setup checks by trying to open it for writing. Otherwise the message names the file and gives Windows' own explanation (a read-only file, a permission, protection software), and the log records the raw error code. The rarer ones, such as a damaged setup file or a failed download, have texts too. The full list is in [`[text]`](/docs/reference/config/text).

## Cancelling

While an install or update unpacks its files, the working page has a **Cancel** button (Esc does the same). Until the files are moved into place nothing of the earlier version has been touched, so cancelling deletes what was unpacked and ends setup, leaving the folder as it was. Once the files start moving into place, which is the all-or-nothing step, the button is gone and the window cannot be closed until it is done. Removing an app cannot be cancelled. A setup that was killed instead (Task Manager, a power cut) leaves its unpacked files as `*.bach-new` next to their targets; the next run of the same setup file removes them.

## Support info

The failed page has a **Save support info** button. It writes one text file, `<app id>-support.txt`, to the user's desktop and shows it in Explorer. The file holds the app's name, version and id, Bach's version, the Windows build, the processor type, whether setup runs as administrator, the install folder, the free space on that drive, the sentence the window showed and setup's log. It holds none of the app's files and no access key, and the user's name and profile folder are replaced (`%USERPROFILE%` and `<user>`). Nothing is sent anywhere: the user decides whether to attach the file to a message to you. If the file can't be written, the button says so. The three texts are `support_save`, `support_saved` and `support_failed` in [`[text]`](/docs/reference/config/text).

## Choices on the first page

Rows of choices are whole click targets. Clicking anywhere on a row ticks or unticks its box, and a control inside a row never counts a click twice. See [Choices and components](/docs/guides/choices-and-components.md).

## Using the keyboard

The window works without a mouse:

| Key | What it does |
| - | - |
| Tab, Shift+Tab, arrow keys | Move through the choices, then the buttons |
| Home, End | Jump to the first or the last control |
| Space or Enter | Do what a click would |
| Enter with nothing focused | Press the page's main button |
| Escape | Cancel |
| Ctrl+C, Ctrl+A (license page) | Copy the selected text, select all of it |
| Page Up, Page Down, Home, End (license page) | Scroll the license |

A focus ring only shows once the keyboard is used, like the web's `:focus-visible`, so mouse users never see one.

In a Windows contrast theme (Settings › Accessibility › Contrast themes), edges, checkbox outlines, focus rings and secondary text turn to the full text colour, so nothing depends on a faint tint. With "Show animations in Windows" off, the window's motion holds still.

## Look and feel

* The window wears one of 14 [built-in styles](/docs/reference/config/style.md) (`installer.style`, Bach's own by default), and `[style]` changes its fonts, colours, corners and background.
* It is arranged by one of 10 [built-in layouts](/docs/reference/config/layout.md) (`[layout] preset`, the classic column by default), and `[layout]` changes its size, panel, spacing, buttons and animation.
* The window follows Windows' light or dark setting live, unless `installer.theme` fixes it. A few styles, such as `arcade` and `terminal`, start dark when `theme` isn't set.
* Your `accent` replaces only the primary colour: buttons, the progress bar and ticked boxes.
* Text is set in the style's font, Inter in Bach's own style. Long app names and long install paths wrap instead of clipping.
* By default setup never asks for administrator rights, so there is no UAC prompt. An app with `installer.scope = "machine"` asks Windows once, before this window opens (see [machine-wide installs](/docs/guides/machine-wide-installs.md)).

## See it yourself

```bash theme={"theme":{"light":"github-light","dark":"github-dark"}}
bach preview
bach preview --theme dark --lang de
bach preview --style aurora
bach preview --layout showcase
bach preview --uninstall
```


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