Docs

Troubleshooting

The usual snags — the app won't start, the cursor won't cross, a game misbehaves — and how to report what's left.

The app won’t start

Nine times out of ten: the .NET 10 Runtime (x64) is missing. LBM runs on .NET and does not bundle it — install it from Microsoft and try again.

Windows SmartScreen may also block the installer on first run (it is not code-signed): choose More info → Run anyway.

The cursor doesn’t cross where I expect

  • Make sure LBM is actually enabled (bottom panel, or the tray icon).
  • Check your layout: the screens in the center panel must mirror your physical desk — sizes and vertical offsets. If a monitor reports a wrong physical size, correct it from the size view.
  • Clicks or scrolls landing oddly right at the moment of crossing were fixed in 5.5 — make sure you’re on the latest release.

A game or elevated app misbehaves

Fullscreen games with anti-cheat often run elevated and dislike global mouse hooks. Exclude the game in LBM: since 5.5, excluding an elevated game genuinely pauses the hook while it runs.

The daemon died / port conflicts

Since 5.5 the UI and the mouse daemon talk over a secure per-user local channel instead of a TCP port: no more port clashes with other software, a killed daemon restarts instantly, and the startup configuration survives crashes with automatic backup recovery. If you’re seeing these symptoms on an older version, update.

Clone mode and topology changes

Display topology changes (plugging/unplugging, clone mode) got safer handling in 5.5. If a topology change still confuses your layout, save your config and report it.

Reporting an issue

The magic move: copy config to clipboard (bottom panel) and paste it into a GitHub issue, along with what you expected and what happened. That config describes your exact display topology — it’s what makes your bug reproducible on another machine.