Loader doesn't attach to Marvel-Win64-Shipping.exe

The Nimbus payload injects into Marvel-Win64-Shipping.exe — the actual game process, not the launcher wrapper. If you click Launch Game and Marvel starts but the overlay never appears (and isn't blocked by any of the overlay-not-showing causes), the loader is failing to attach to that specific process. Here's the diagnostic order.

Step 1: confirm the process actually spawned. Open Task Manager → Details tab while Marvel is running. Sort by name. You should see two Marvel processes:

• MarvelRivals.exe — the launcher / EAC wrapper, spawns first.
• Marvel-Win64-Shipping.exe — the actual game process, spawns 5-15 seconds later when the wrapper finishes the EAC handshake.

If only MarvelRivals.exe is present, the game never reached the actual launch stage — EAC is failing its handshake. See Step 5 below for the EAC-side fix.

Step 2: check the loader log for the attach attempt. Open %APPDATA%\Nimbus\logs\nimbus-loader-<latest>.log in Notepad. Search for Marvel-Win64-Shipping. You should see lines like:

```
[inject] waiting for Marvel-Win64-Shipping.exe
[inject] found PID 12345
[inject] OpenProcess OK
[inject] payload mapped at 0x7FF6...
```

If the log stops at waiting for Marvel-Win64-Shipping.exe and never advances, the loader's process-watch timer expired before the game spawned. Default watch window is 90 seconds; this expires if Marvel sat on the EAC handshake too long.

If the log says OpenProcess failed: ACCESS_DENIED, the loader wasn't elevated. Re-launch the loader as administrator.

If the log says OpenProcess failed: not found repeatedly, the game's process name has changed (rare, only happens during a major patch's pre-release builds) — wait for the next loader auto-update.

Step 3: fix the elevation case. Close the loader entirely (Task Manager → kill nimbus-loader.exe). Right-click nimbus-loader.exe → Run as administrator. Sign in. Click Launch Game again. The UAC prompt should appear; click Yes. If you don't see the UAC prompt this time, you may be skipping it because of a Windows auto-elevate policy — that path doesn't grant the privilege the loader actually needs. Pin the loader to Start with Run as administrator checked in *Properties → Advanced* so the UAC fires every time.

Step 4: fix the timeout case. If Marvel is slow to launch (older PC, HDD-mounted install, EAC handshake retrying), the default 90-second watch window can expire. The loader will surface "Waiting for game…" and eventually idle out. Workaround: click Launch Game first, wait until the loader's status pill reads Armed, then don't move on. Let the loader wait. If you launch Marvel manually in parallel (Steam → Play before the loader is armed), the timing race fails. Always let the loader drive the launch — it kicks Steam's steam://rungameid/2767030 itself.

Step 5: fix the EAC-side case. If Marvel-Win64-Shipping.exe never spawns at all, EAC is failing its handshake. Common causes:

• EAC service stopped. Open Services (Win+R → services.msc), find EasyAntiCheat, set Startup type to *Manual* and start it. (Don't set to *Disabled* — that breaks Marvel entirely.)
• EAC install corrupted. Re-run EasyAntiCheat_Setup.exe from Marvel Rivals\EasyAntiCheat\ and click Repair Service.
• Windows is asleep on a UAC prompt for EAC. Sometimes EAC's elevation prompt hides behind Marvel's splash. Alt-Tab to find it and click Yes.

Step 6: still failing. Grab the boot log via Settings → Export boot log to Desktop, and attach to a ticket at /dashboard/support. The log has the full process-watch timeline and pinpoints which step is failing in your specific case.