Skip to main content
Bach reports every mistake as one sentence that names the thing at fault. This page lists the messages people meet most and what to do about each. Start with bach doctor: it says exactly what is missing.

When building

There is no network, or there is no release for this version. Put bach-setup.exe next to bach, or pass --runtime PATH, or set BACH_RUNTIME. Download the zip from the releases page if you need the file. If BACH_NO_DOWNLOAD is set, bach never downloads it. See Install Bach.
Build your app first, or fix [files] source and [app] executable. Both are relative: source is relative to bach.toml, and executable is relative to source.
Close the old setup file or the running app, then build again.
Preview needs Windows. Use bach check on macOS and Linux.
Give kind one of webview2, dotnet, vcredist, file or registry. file and registry need a name and an https url. See [[requirements]].
A [text] entry exists in only one language while the window speaks several. Add the other languages or limit installer.languages.
On macOS and Linux, app.icon is not applied. Build on Windows.

When installing

Raise version above the installed one, or pass --allow-downgrade on a silent run.
Close the app and press “Try again”, or press “Close and continue” to ask the app to close the way Windows Update does.
Install what it names with the button, then press “Try again”. A silent install exits with code 1 instead.
The window names the needed and free space. Free up room or install to another drive with the Location row, or --dir on a silent run.
The setup file is unsigned or the publisher is new. Sign the file.

When installing Bach itself

A package that was published only minutes ago can take a few minutes to appear everywhere. Wait and try again. If it still fails, check npm config get registry (it should be https://registry.npmjs.org/) and your proxy or company registry, then try the install script from Install Bach.
npm ran with --omit=optional (or --no-optional) and skipped the platform package that holds the program. Install again without that flag: npm install --global @usebach/cli.
Do not use sudo. Give npm a global folder of your own once, add its bin folder to your PATH, and install again: npm config set prefix ~/.npm-global.
Another copy comes first on your PATH, for example one from install.ps1. Run where bach (Windows) or which -a bach to see them, and remove the one you don’t want. npm uninstall --global @usebach/cli removes the npm copy.
It never writes into a folder it did not create. Set BACH_INSTALL_DIR to an empty folder.
Close any running bach, then run the script again.
Open a new terminal. The script adds its folder to your user PATH, which only new terminals see. In the same terminal, call it by its full path.
Nothing was installed. Check your connection and try again, or use the zip from the releases page.

Read the log

Every setup run writes %TEMP%\<app id>-setup.log, or the file you pass with --log. It names the steps and, when something fails, why. Read it instead of guessing, and attach it to a bug report.

Still stuck?

Open a bug report with a small bach.toml that shows the problem, the output of bach doctor, and the setup log. See Support.