Troubleshooting

The loader closed unexpectedly — what to send support

Where the diagnostic log lives, what to redact before pasting it, and what info opens a ticket fastest.

1 min readUpdated 2026-05-29

Two flavors of "loader closed unexpectedly":

**Flavor 1: Loader closed *after* you clicked Launch Game. This is expected behavior**, not a crash. The loader exits after arming the payload; Marvel Rivals starts on its own 5-15 seconds later. If the game does start, nothing's broken.

**Flavor 2: Loader closed *before* you clicked anything, or crashed mid-session.** This is a real issue. Steps to gather what we need:

1. Open %APPDATA%\Nimbus\ in File Explorer.
2. Inside is a logs\ folder. The most recent file is named nimbus-loader-<YYYYMMDD-HHMMSS>.log.
3. Open the log in Notepad. Redact your license key (any line containing KEY=) before sharing.
4. Open a ticket from your dashboard, category Install, and paste the redacted log into the body.

What to include in the ticket subject: the loader version (top-right of the loader window), the exact error text (if any), and what you were doing when it happened ("first launch ever" / "after a Marvel Rivals patch" / "after Windows Update").

With the log and a clear repro, median first reply on Discord is under 20 minutes.

Was this article helpful?

Related articles

Still stuck?

Discord is the fastest path — median first reply under 20 minutes. The chat widget in the bottom-right also works.