> ## 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 check: validate bach.toml and list the files

> bach check [CONFIG]: reads a bach.toml, lists every file and option the installer would carry, and reports mistakes and warnings in plain sentences.

`bach check` reads a `bach.toml` and lists what the installer would install, without building anything. Run it after every config change.

```bash theme={"theme":{"light":"github-light","dark":"github-dark"}}
bach check
bach check path/to/bach.toml
bach check --app-version v1.4.0
```

| Argument | Default | Meaning |
| - | - | - |
| `CONFIG` | `bach.toml` | The config file |
| `--app-version VERSION` | `app.version` | Check with this version instead of `app.version`, as a release tag like `v1.4.0` does for `bach build`. A leading `v` is dropped. |
| `--profile NAME` | main build | Check this [profile](/docs/reference/config/profiles.md) of the config instead of the main setup file. [`bach profiles`](/docs/reference/cli/profiles) lists them. |
| `--strict` | off | Treat any warning as an error: the command exits with code 1. `BACH_STRICT=1` does the same, which suits CI. |

## What it reports

* **Every file** the installer will install, after `exclude` and components are applied.
* **The summary** also shown by `bach build` and `bach inspect`: publisher, program, number and size of files, install folder, options, components, link schemes, file types, languages, license, your own texts, requirements, shortcuts, update feed and data folders.
* **Mistakes** as one sentence naming the setting at fault. Unknown settings are an error.
* **Warnings** on lines starting with `warning:`. A typical one: a `[text]` entry given in only one language while the window speaks several.

Treat every warning as something to fix or to mention to your team. In a pipeline, `bach check --strict` makes sure nobody ships one by accident:

```console theme={"theme":{"light":"github-light","dark":"github-dark"}}
$ bach check --strict
...
warning: installer.path_folder is "bin", but no installed file is in it.
error: bach.toml has 1 warning, and --strict treats it as an error: fix it, or run without --strict.
```

## Works everywhere

Unlike `bach preview`, `bach check` also runs on macOS and Linux.

See [Write your bach.toml](/docs/guides/write-bach-toml.md).


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