Skip to main content
Bach installs for the current user and writes only to the user’s own folders and HKCU. An app that sets installer.scope = "machine" installs for every user instead and uses the matching machine-wide places, listed below. This page lists every place a Bach installer or the bach command touches, so you can audit or clean up with confidence.

On the end user’s computer

A machine-wide install

With installer.scope = "machine", everything above moves to the computer’s side: See machine-wide installs.

Temporary files during an install

  • Each chosen file is unpacked next to its target as <name>.bach-new, then swapped into place with the old file stepping aside as <name>.bach-old. These disappear when the install completes. While files move, a journal named .bach-update in the install folder lists them; if an update was cut short by a power cut or a crash, the next install, update or removal puts back what was half moved, and deletes the journal. An update that is run by the installed uninstall.exe renames it to uninstall.exe.bach-old, which is deleted once that process has ended.
  • In the names of these scratch files and folders (the log, the staged update folder, the online installer’s download folder, the uninstaller’s temp copy), a space in the app id is written %20: My App gives My%20App. No id can contain %, so My App and My-App never share a folder. Ids without a space are used as they are.
  • During removal of a per-user install, the uninstaller copies itself to the temp folder as <app id>-uninstall-<process id>.exe, and a hidden helper deletes that copy once it has exited. A machine-wide uninstaller runs elevated and removes from where it is, so no copy in the user’s temp folder is ever started with administrator rights. A hidden helper deletes uninstall.exe once it has exited.

On the developer’s computer

What Bach never touches

  • Anything outside the install folder, the data folders you list, the user’s shortcuts and the HKCU keys above.
  • Registry keys without the BachApp mark, and PATH entries other than its own.
  • Anything that needs administrator rights, unless the app asks for it with installer.scope = "machine" or an elevated step in [[run]].
See Safety rules.