System requirements and compatibility

Errant Launcher is a portable app: it only needs a suitable Windows release and a little free space. Below are the confirmed requirements, recommendations and known limitations of the current beta version.

Contents

Minimum requirements

Parameter Requirement
Operating system Windows 10 version 1607 or newer
Architecture 64-bit (x64)
.NET Not required — the runtime is built into the app file
Installation Not required — a single executable
Administrator rights Not required to launch or run

Not supported:

  • Windows 7, 8 and 8.1 (a limitation of the .NET 8 platform used);
  • 32-bit Windows editions — no x86 build is provided;
  • ARM64 processors — there is no dedicated build; on ARM64 devices run the x64 version through the standard Windows emulation.

Installation and launch

There is no installer — the app ships as a single file ErrantLauncher-x64.exe.

  1. Copy the file to any folder: Documents, a separate directory on a disk, or a USB drive.
  2. Run it with a double click.
  3. On first launch, an ErrantLauncher folder is created next to the app file — it stores all cards, settings and service data.
Warning

SmartScreen warning. The executable is not digitally signed, so Windows may show a warning — this is expected for a beta version. How to verify the file: FAQ.

Display requirements

The app windows have a fixed size — it cannot be changed:

  • window content: 1000 × 620 DIP;
  • outer window size including the decorative shadow: 1028 × 648 DIP.

DIP is a logical unit of interface size, not physical screen pixels. The actual window size in pixels depends on the Windows scaling (for example, at 150% scaling the window takes about 1540 × 970 physical pixels).

For the interface to display fully, the screen work area (the screen without the taskbar) must fit the whole window. High scaling values reduce the work area in logical units and may require a higher screen resolution.

If the work area is smaller than the window size, part of the window when centered may end up off the screen edges, including the top bar with the minimize and close buttons.

Tip

In practice: on typical desktops (1920 × 1080 and above) at 100–150% scaling the window fits completely. On low-resolution screens with high scaling (for example, 1366 × 768 at 125–150%) the work area may not be enough — check the display on your screen at first launch.

Disk and access rights

  • Location. The app must be in a folder that allows reading; saving data also requires write access.
  • Writing. If the ErrantLauncher folder is read-only, the app opens in read-only mode: cards can be viewed and launched, but changes are not saved — a clear notification is shown about this.
  • Registry and profile. The app writes nothing to the Windows registry or user profile folders — all data lives only in ErrantLauncher\ next to the exe file.
  • Temp folder. On each launch the single-file app unpacks its libraries into %TEMP%\.net\ErrantLauncher. These directories accumulate and are not cleaned automatically; they can be safely deleted manually while the app is closed.

Running from a USB drive

The app is designed to run from removable media:

  • the whole package — the exe file and the ErrantLauncher folder — is carried over as is;
  • the drive letter may change between computers: data is looked up next to the executable, not by an absolute path.

Limitations:

  • removing the USB drive while the app is running may terminate the process — close the app before removing the drive;
  • if the drive is temporarily unavailable, the app reports "No media" and keeps changes in memory until it is reconnected;
  • cards referencing files by drive letter (for example, D:\Tools\app.exe) may not open on a computer where that letter does not exist.

Known compatibility limitations

  • Windows only; no macOS or Linux versions.
  • x64 only; no x86 or ARM64 builds.
  • The executable is unsigned — expect a SmartScreen warning.