Data, backups and portability

Errant Launcher is a portable app: all its data lives in a single folder next to the executable. This document explains where everything is stored, how to make backups, and how to move your collection between computers.

Contents

Where data is stored

On first launch the app creates an ErrantLauncher folder next to the exe file — for example, if the app is in D:\Tools\, the data will be in D:\Tools\ErrantLauncher\.

The app writes nothing to the Windows registry or user profile folders (Documents, AppData, etc.). The entire collection, settings and service files are only inside this folder.

Data folder contents

Path Contents
ErrantLauncher\sections\*.json Sections, categories and cards — one file per section
ErrantLauncher\settings.json Appearance and behavior settings: theme, language, tray, etc.
ErrantLauncher\state.json Window state, last opened section, launch counters
ErrantLauncher\custom-icons\ Icons you added or icons extracted from programs
ErrantLauncher\logs\ Local diagnostic logs (app.log, bootstrap.log)
ErrantLauncher\.backup\ Automatic backups of data files
ErrantLauncher\.mass-import-backups\ Copies created before mass import

The .backup, .mass-import-backups folders and the .import-staging service folder are hidden service directories; there is no need to delete them manually, but their contents should not be touched unnecessarily.

Backup

The app helps in two ways:

  1. Export configuration — the built-in feature ("Settings" → "Export configuration"): - Full backup — everything: sections, icons, settings and state; suggested file name — ErrantLauncher-Backup.zip; - Share collection — selected sections and icons, with favorite marks, but without settings; suggested file name — ErrantLauncher-Collection.zip.
  2. Copying the folder manually — with the app closed, copy the whole ErrantLauncher folder to a safe place. This is a complete snapshot of your data.

Additionally, the app itself creates copies in .backup\ during data operations and in .mass-import-backups\ before mass import — but that is insurance against a failure, not a replacement for regular backups.

Tip

Before major changes (mass import, relocation, update) make a "Full backup" via export — it is the easiest one to restore.

Moving to another computer

Method 1 — move everything:

  1. Close the app.
  2. Copy the exe file and the ErrantLauncher folder to the new computer or drive — together, keeping their relative positions.
  3. Run the exe in the new location.

Method 2 — move only the collection: use "Export configuration" in "Share collection" mode → "Import configuration" on another copy of the app (accepts .zip, .json and a configuration folder).

Note

About paths: cards referencing files by drive letter (D:\Tools\app.exe) work on the new computer only if the files exist there at the same paths. The mass import wizard warns about such cards. The launcher's own data does not remember drive letters — the data folder is found next to the exe.

Updating without data loss

There is no auto-update, but updating does not touch data:

  1. Close the app.
  2. Replace ErrantLauncher-x64.exe with the new version.
  3. Launch. The ErrantLauncher folder stays in place — all cards and settings are preserved.

Before reinstalling or uninstalling

  • Keep: the whole ErrantLauncher folder (or at least sections\, settings.json and custom-icons\ if you don't need the logs).
  • Uninstalling: delete the exe file and the ErrantLauncher folder. The app leaves no other traces in the system. You can additionally delete the temporary %TEMP%\.net\ErrantLauncher directories — they are created on every launch and are not cleaned automatically.
  • The "Delete all data" function in settings erases the contents of the data folder after two confirmations — use it only if you don't need a backup.

If files are unavailable

The app distinguishes between situations and behaves predictably:

Situation Behavior
Data folder is read-only "Read-only" mode: cards are visible and launch, changes are rejected with a notification and are not lost silently
Drive temporarily unavailable "No media" indicator; changes stay in memory and are saved after reconnection
Data folder cannot be read at all Unavailable storage message; the app closes
An individual data file is corrupt "File is corrupt" dialog: the file is ignored and not modified; you can delete it or keep it
File created by a newer version The file is read but not overwritten — updating the app is recommended
Several files for one section Contents are merged automatically, a notification is shown

Restoring from a backup

From an exported file: "Settings" → "Import configuration" → select the file → check the sections, settings, icons and favorites you need → "Import".

From a folder copy: with the app closed, replace the contents of the ErrantLauncher folder with the backup copy's contents.

After a mass import failure: the app reports the path of the copy created before the import (in .mass-import-backups\) — follow the hint in the error message: copy its contents over the data folder or repeat the import.

USB drive specifics

  • Running from USB is fully supported — it is a standard scenario.
  • Removing the drive while the app is running may terminate the process: always close the app before removal.
  • If the drive drops out and reconnects, the app detects the return and continues saving data.
  • On write-protected media, "Read-only" mode applies.
  • There is no absolute guarantee of card portability: if they reference local files of another computer, check card statuses after moving ("File missing", "Drive unavailable").

See also: User guide, System requirements.