Frequently asked questions and troubleshooting

Contents

The app does not start

Possible causes: outdated Windows version; unsupported architecture; an already running instance; an unavailable data folder.

What to check:

  1. Windows must be 64-bit, Windows 10 (1607) or newer. Windows 7/8 and 32-bit systems are not supported.
  2. Look at the notification area (tray) — the app may already be running minimized.
  3. Check that the ErrantLauncher folder exists next to the exe and is readable.

What to try: move the exe file to a regular folder on a local drive (e.g. C:\Tools\) and run it again; check the ErrantLauncher\logs\bootstrap.log — it is created on launch failures.

Report to support: your Windows version, the exe file location, and the bootstrap.log contents if it exists.

SmartScreen warning

Cause: the executable is not digitally signed — expected for a beta version, not a sign of a problem.

What to check (recommended): the file's authenticity via its checksum. In PowerShell, in the app folder:

Get-FileHash .\ErrantLauncher-x64.exe -Algorithm SHA256

Compare the result with the string in the SHA256SUMS.txt file from the release package.

What to do: in the SmartScreen window click "More info" → "Run anyway". Disabling SmartScreen or other Windows protection is not required and not recommended.

Is .NET required?

No. The .NET runtime is built into the executable — the app runs on a clean Windows without .NET installed.

Note the downside of single-file delivery: on every launch the app unpacks its libraries into %TEMP%\.net\ErrantLauncher. The directories accumulate — you can delete them manually while the app is closed.

"Errant Launcher is already running"

Cause: only one instance of the app can run; a second launch shows this notification.

What to check: the notification area (tray) — the app may have been minimized there; if the running instance cannot be contacted, the app reports that separately.

What to try: close the process via the "Exit" tray menu or Task Manager and run it again.

"Read-only" mode and "No media"

Causes:

  • Read-only — the app has no write access to the data folder (protected media, permissions, quarantine).
  • No media — the data folder is temporarily unavailable (USB drive disconnected).

What happens: in read-only mode cards can be viewed and launched, but changes are rejected with a clear message. With "No media" changes stay in memory and are saved after the drive reconnects — the app reports "Drive reconnected".

What to check: whether the ErrantLauncher folder exists next to the exe; whether it has the "read-only" attribute; whether the drive with the same contents is connected.

"File is corrupt"

What happened: one of the data files (e.g. a section or settings file) cannot be read. The app ignores such a file and does not modify it — the rest of your data is safe.

What is offered: in the dialog — "Delete" the corrupt file or "Keep" it (for example, to try restoring it manually).

What to try: restore the file from a backup — from an exported archive via "Import configuration" or manually from .backup\/.mass-import-backups\ inside the data folder.

Running from a USB drive

Normal: this is a standard scenario — carry the exe and the ErrantLauncher folder together.

Typical problems:

  • The app terminated on removal — close it before removing the drive.
  • Cards do not launch on another computer — they reference files by local paths; check card statuses and paths.
  • Changes are not saved — see the "Read-only" mode section.

A command card leaves a console window

This is a feature, not a bug. Commands run with cmd /k or powershell -NoExit so the output stays on screen. Close the console window manually when you no longer need the result.

Also note: commands always run from the app's data folder — command cards have no separate working directory. If a command needs a different folder, start it with cd /d "path" (or specify the path inside the command itself).

Card shows "File missing" or "Drive unavailable"

Cause: the app checks the availability of card targets. Statuses:

Status Meaning
Available The target was found
File missing No file at the specified path
Source unavailable The folder/source cannot be read
Drive unavailable The disk/drive is not connected
Checking... Check in progress

What to check: whether the file exists at the specified path; whether the required drive is connected (especially after moving the launcher to another computer). You can fix the path in "Edit cards".

Mass import finished partially or with errors

Possible causes: duplicate paths and names, unavailable files, types disabled by filters, the candidate limit reached, write errors.

What to check: the import summary lists the reasons ("duplicate: card already exists", "name already used", "gone — file not found"). Notes on the results screen show what the filters cut: types, architectures, extensions, excluded folders.

What to try: adjust the filters and selection; use "Re-check" instead of a new scan.

If writing was interrupted: before the import a backup is created automatically (in .mass-import-backups\). The error message shows its path and the action to take: copy its contents over the data folder or repeat the import. Do not delete the data folder manually — it would destroy the backups too.

The window does not fit the screen

Cause: the app windows have a fixed size (content 1000 × 620 DIP, outer size 1028 × 648 DIP). If the screen work area is smaller — for example, low resolution combined with high Windows scaling — part of the window may go off the screen edges, including the top bar with the window buttons.

What to check: Windows scaling (Settings → System → Display → Scale) and screen resolution.

What to try: reduce Windows scaling or choose a higher resolution; if part of the window is off-screen — change the scaling and restart the app so the window re-centers.

Details: System requirements.

Updating and keeping data

Updating: there is no auto-update — replace the exe file while the app is closed; do not touch the ErrantLauncher folder.

Data after updating: preserved. If data files were created by a newer version of the app, the old version will read them but will not modify them — update the app.

Card sorting: the chosen sort order is kept only for the session — after a restart the default order applies. This is a known beta limitation, not data loss.

Where to find logs and how to report a bug

Logs: ErrantLauncher\logs\ next to the exe — app.log (working messages and errors) and bootstrap.log (launch failures). Logs are never sent anywhere automatically.

How to report a bug: step-by-step instructions, what to attach and where to write — in the document Support and bug reports.

Warning

Before sending a log, review it: it may contain paths to your files and folders.