Support and error reports

Where to turn with questions about Errant Launcher and how to write an error report so the problem can be found and fixed quickly.


Support channels

Official project channels (the same links are inside the app — the "About" window; the channels work from the release publication):

Channel Address
Documentation Documentation on the site
Report an error GitHub Issues
Releases GitHub Releases

Before writing, check the FAQ and troubleshooting — many questions (SmartScreen, "Read-only", card statuses, window size) are already covered there.

How to describe an error

A good report answers three questions:

  1. What you were doing — reproduction steps, in order. For example: "opened Editor → Mass import → picked the D:\Tools folder → clicked 'Scan'".
  2. What you expected — "a list of candidates was supposed to appear".
  3. What happened — "the app closed" / "a message appeared …" — quote the message text verbatim or attach a screenshot.

What to attach to the report

Information Where to get it
App version "About" window (e.g. 1.0.0-beta.1)
Windows version and bitness Win+R → winver; architecture — in "Settings → System → About"
Display scale Settings → System → Display → Scale (if the problem is with display)
Where the app is launched from Path to the exe file; local disk or USB
Logs ErrantLauncher\logs\app.log and bootstrap.log — the ErrantLauncher folder is next to the exe file
Reproduction steps See above — the more precise, the better
Error message text Verbatim or a screenshot

Before sending a log, open it in Notepad and check the contents: logs may contain paths to your files and folders — remove anything you don't want to disclose.

What NOT to send

What to expect

This is a free independent project at the beta stage: there are no promises about response times, but every clearly described report helps ship the stable version faster. Watch the releases page — fixes arrive in new versions.