# LabyMod **Launcher** Bug Report
**Scope:** all Launcher-category incidents in the tracker (cumulative, 2026-06-07 → 07-01)
**Source:** #support, #general, #discussions · **Incidents:** 16 (8 active, 8 fixed)
**Launcher versions in window:** 3.0.6 → 3.0.10 · **Interactive view:** `bug-report-launcher-2026-07-01.html`

> Companion to the main report. This is the full launcher picture — every launcher incident, active and resolved — so the launcher dev has one place to work from.

---

## 🔴 / 🟠 Active — High

### [L-H01] Deleting an imported Modrinth instance wiped the whole .minecraft/saves folder ⚠️ data loss 🆕
- **(Crash)logs:** none (behavioral) · **Occurrences:** 1 · **OS:** Windows
- **Message Links:** https://discord.com/channels/260471731809026048/260478719695519746/1518999197464924262
- **Affected:** @Nobody · **Status:** needs-info

> "Als ich die Instanz später gelöscht habe, wurde jedoch offenbar auch der gesamte .minecraft/saves-Ordner gelöscht. […] der Ordner nicht im Papierkorb." — @Nobody, 2026-06-23

Imported a Modrinth instance, granted it access to the real `.minecraft/saves`, deleted the instance → the entire saves folder was deleted, permanently (not to recycle bin). Same family as the 3.0.6-fixed shared-directory deletion, but here it destroyed real worlds via the manually-linked path. **Fix direction:** instance deletion must never recurse into user-linked external directories, and deletes should go to the recycle bin / a trash staging area.

### [L-H02] Per-instance overlay hijacks schematics & mod folders ⚠️ REGRESSED
- **Occurrences:** 7 (2 new this window) · **OS:** Windows · **MC:** 1.21.x
- **Message Links:** https://discord.com/channels/260471731809026048/260478719695519746/1519049111679008848
- **Affected:** @Kn0cki, @The Rebirthed, @Tharson_, @RainerRainer75, @khalid7445, @Dark_Mandalor, @MYNTAX
- **Status:** regressed — was fixed in 3.0.7/3.0.8, now recurring

Litematica schematics & mod configs resolve to `instances\<uuid>\overlay\…` instead of `.minecraft`. Fixed in 3.0.7/3.0.8 (default instance runs in `.minecraft`, stale overlays cleaned up), but @Dark_Mandalor (06-23) reports schematics saving to the overlay folder again ("eigentlich war das ja fixed") and @MYNTAX (06-26) reports the Fabric mod folders no longer existing after closing MC (so mods can't be deleted). Overlay removal likely doesn't cover all content types / instance kinds.

### [L-H03] Launcher fails to start silently (no window, not in task manager)
- **(Crash)logs:** attachments/1519070185204617367_message.txt (`invalid_grant` refresh token + dbus) · **Occurrences:** 10 (3 new) · **OS:** Windows
- **Message Links:** https://discord.com/channels/260471731809026048/260478719695519746/1519872380393099435
- **Affected:** @The Rebirthed, @𝓜𝓪𝓾𝓿𝓲, @Zeesh, @cvhfvhcjx, @jaypredictable, @dj_pitgamer, @</3., @Simon, @MYNTAX, @Erika_bv
- **Status:** open — still recurring on 3.0.9 / 3.0.10

The longest-running launcher issue. Earliest evidence pinned an Electron `globalShortcut cannot be used before the app is ready` race (main process dies before any window exists → "nothing in task manager"). @jaypredictable's workaround (running the installer re-launches it) and @Erika_bv's (PC restart) point to a process-start/state race rather than a corrupt install. 3.0.9/3.0.10 added window-reappear/re-activation crash fixes but the cold-start case persists. **Ask:** `labymodlauncher-install.log` + `-error.log` captured immediately after a fresh failure.

---

## 🟡 Active — Medium / Low

### [L-M01] Stale imgui-java64.dll in %temp% breaks launcher start — *workaround*
- **(Crash)logs:** https://paste.labymod.net/raw/ivijuliyusozoyaqejaf · **Occurrences:** 1 · **Affected:** @Vanessa3209
- Launcher fails loading its imgui native; fixed by deleting `%temp%\imgui-java-natives\1.0.2\imgui-java64.dll`. Staff have a canned workaround → known recurring. The launcher should hash-check/overwrite its extracted natives (3.0.7's per-instance native fix covers *game* natives, not the launcher's own).

### [L-M02] Clean MC 26.1.2 instance takes ~1 min to launch (stall after Datafixer line)
- **Occurrences:** 1 · **Affected:** @moritz · **Message Links:** https://discord.com/channels/260471731809026048/260478719695519746/1513932541277503490
- Startup stalls after `291 Datafixer optimizations took 318 milliseconds`; much faster on Modrinth/vanilla on the same machine → launcher-side overhead (remap / verification / content sync).

### [L-L01] 'Start fullscreen' setting disables in-game fullscreen; 1.8.9 custom resolution gone
- **Occurrences:** 3 · **Affected:** @Kubii, @Kaktus, @Treggalin
- **Linked Ideas:** [#20999 — Starting window resolution doesnt apply [OPEN]](https://laby.net/ideas/20999)
- Northernside confirmed a launcher bug ("not supposed to turn it off in the game"), fix queued. Same window-geometry code path as the fixed borderless-fullscreen NPE. @Kaktus's 1.8.9 fullscreen pixelation is the lost custom-resolution control.

### [L-L02] Launcher doesn't remember window position (multi-monitor)
- **Occurrences:** 1 · **Affected:** @Niika (Arch Linux) — always opens on the 3rd monitor. Window geometry not persisted.

### [L-L03] labymodlauncher-install.log keeps appearing in Downloads (no opt-out) 🆕
- **Occurrences:** 3 · **Affected:** @Idrop200points, @Treggalin, @zlxne_
- Diagnostic log dumped to Downloads on every start; Northernside intends to remove it once the underlying Windows install issue is confirmed gone — still pending.

---

## ✅ Fixed (launcher)

- **Instances reset / instances.json corrupted on NTFS** (@Kaktus, @asdasf1z) → **3.0.9** (auto-recovery of corrupt instance list, "notably on NTFS") + **3.0.10** ("Recover Instances from Disk"). Verify recovery restores the mod list.
- **Silently reinstalls uninstalled mods** (@Jake) → **3.0.10** ("Fixed a race when quickly enabling/disabling mods that could leave a duplicate or stale disabled copy; installed mods now stay in a stable order").
- **Install/start error dialog** (`sdiufhisuhfiusfhuie`, @asdasf1z) → **3.0.10**, user-confirmed ("ja jetzt geht et").
- **Addon/mod install error dialog** (@Kaktus) → **3.0.8** ("crash when reading a corrupt or invalid addon/mod jar").
- **Fullscreen + explicit window size → NPE crash** (`BorderlessWindow.toggleFullscreen`, @King H-O, @_1z__) → **3.0.8**.
- **Standalone Forge 1.20.1 instance crash on start** (@ESK) → **3.0.7** (Forge manifest dedup / duplicate libraries).
- **Windows firewall prompt on every launch** (@The Rebirthed, @Gamerboy, @Timo) → **3.0.7** (communication server bound to the wrong interface).
- **AUR `labymodlauncher-bin`** (@Kawwabi) → confirmed working on **3.0.8**.

---

### Launcher themes worth a structural look
1. **Instance/content deletion safety** — L-H01 (saves wiped) + the 3.0.6 shared-dir fix + L-H02 overlay regression all touch how the launcher maps and deletes instance ↔ real game directories. A single "never delete outside the instance's own dir; recycle-bin everything" pass would close a whole class.
2. **Cold-start reliability on Windows** — L-H03 is 10 users over a month across 3.0.6–3.0.10; the Electron startup race + install-log-in-Downloads (L-L03) are the same "early startup on Windows is fragile" story.
3. **Window geometry** — L-L01 + L-L02 + open idea #20999 are one area (persist/restore window & resolution state).