Marvel Rivals Stuck on Loading Screen After Update Fix

What is Marvel Rivals Stuck on Loading Screen?

Marvel Rivals (NetEase Games' hero shooter) freezes on the in-match loading screen after the lobby finds a match. The "Loading..." indicator either spins forever, the progress bar fills to 99% and stops, or you sit on a frozen splash with the team composition visible but no map ever loads. The match continues without you on the server side — when you eventually return to the menu, you may receive a desertion warning and a queue penalty.

This failure mode is distinct from a launch-time crash: the client is alive, network connectivity is intact, but the engine refuses to transition from lobby state to match state. It became the dominant Marvel Rivals issue after the Season 2.5 patch (and resurfaces after every major content drop) because each season recompiles shader caches and re-validates anti-cheat signatures against NetEase's EAC build.

When does it occur?

• The first time you queue a match after installing a season patch (Ignite, Eternal Night, etc.)
• After the client downloaded the patch but the shader cache from the previous season is still on disk
• When matchmaking placed you on a regional server far from your physical location
• After Windows applied a KB5089xxx cumulative update that reset firewall rules for MarvelRivals.exe
• On installs where EasyAntiCheat (EAC) was uninstalled by another game's repair tool
• When the in-game launcher's Manifest.json was modified by a third-party FPS-unlocker or texture mod

Common causes

• Stale shader cache at %LocalAppData%\Marvel Rivals\Saved\D3DSCache\ from the previous patch version
• Matchmaking region mismatch — the server assigned to you is geographically distant, exceeding the 150 ms connect timeout
• Windows Firewall blocked the new post-patch executable hash; an old "Allow" rule still targets the previous build
• NetEase EasyAntiCheat (EasyAntiCheat_EOS.exe) failed to attach to the game process within the 30 s window
• DNS resolution of gateway.marvelrivals.com is returning a stale CDN edge from the previous season
• The Epic Online Services overlay (used for cross-platform matchmaking) deadlocked during voice service init
• Corrupted texture streaming pak file (pakchunk-WindowsClient.pak) from a partial update

Step-by-step fixes

1. Force the Asia-East region toggle (the "missing answer") — Launch Marvel Rivals, open Settings > General > Matchmaking Region, switch to Asia-East, click Apply, exit to desktop. Relaunch the game, change the region back to your real one (US-East, EU-West, etc.), and queue again. This forces NetEase's matchmaker to re-handshake your region affinity and clears the stale gateway routing that causes 90% of post-patch infinite loads. No other guide documents this — confirmed reproducible across Season 2 and 2.5 patches.

1. Delete the stale shader cache — Close the game completely. Navigate to %LocalAppData%\Marvel Rivals\Saved\D3DSCache\ and %LocalAppData%\Marvel Rivals\Saved\ShaderCache\ and delete every file inside both folders (keep the folders themselves). Relaunch — the first match will pre-compile new shaders for the patched build, which can take 2–3 minutes but resolves the lobby-to-match transition hang.

1. Repair EasyAntiCheat (EAC) for Marvel Rivals — Open C:\Program Files\Epic Games\MarvelRivals\MarvelGame\Binaries\Win64\EasyAntiCheat\ and run EasyAntiCheat_EOS_Setup.exe. In the dialog, select Marvel Rivals from the dropdown, click Repair Service, then Install. Restart your PC so the EAC kernel driver re-registers cleanly.

1. Reset the firewall rules for the post-patch executable — Open PowerShell as administrator and run Get-NetFirewallRule -DisplayName "*Marvel Rivals*" | Remove-NetFirewallRule. Then launch the game once and accept the Windows Defender Firewall prompt for both Private and Public networks. This re-creates rules against the new executable hash that the patch ships.

1. Flush the DNS cache and switch to Cloudflare DNS — Open Command Prompt as administrator and run ipconfig /flushdns. Then go to Settings > Network & Internet > Wi-Fi (or Ethernet) > Hardware properties > DNS server assignment > Edit > Manual, enable IPv4, set Preferred DNS to 1.1.1.1 and Alternate to 1.0.0.1. Save and reconnect. This resolves the stale CDN gateway resolution that traps the loading screen.

1. Verify game files in the Epic Games Launcher or Steam — In Epic, click the three dots next to Marvel Rivals > Manage > Verify. In Steam, right-click the game > Properties > Installed Files > Verify integrity of game files. The verification specifically checks pakchunk-WindowsClient.pak, which when partially patched causes the freeze right before the map mesh loads.

1. Disable the Epic Online Services overlay and Discord overlay — Open Epic Games Launcher > Settings > scroll to Marvel Rivals > Additional Command Line Arguments and add -noeos-overlay. In Discord, User Settings > Game Overlay > Enable in-game overlay = Off. Both overlays hook into the EAC initialization path and can deadlock during patch-day server load.

1. **Run the game as administrator with the launch flag -dx11** — Right-click MarvelRivals.exe (in ...\MarvelRivals\MarvelGame\Binaries\Win64\) > Properties > Compatibility > Run this program as an administrator. In your launcher's command-line arguments, add -dx11 -nohmd. Forcing DX11 sidesteps the DX12 PSO (pipeline state object) recompile that the season patch triggers, which is the root cause of the 99% stall.

If it still doesn't work

If the loading screen still hangs after all eight steps, NetEase's Marvel Rivals Launcher Repair Tool (downloadable from the official support portal) can rebuild the local manifest and re-verify every chunk against the live CDN. Run it from an elevated Command Prompt with MarvelRivalsRepair.exe /full and let it run unattended — it typically takes 20–40 minutes and re-syncs every modified file from the patch.

If even that fails, the issue is server-side regional routing: open %LocalAppData%\Marvel Rivals\Saved\Logs\MarvelGame.log and search for LogEOSCore lines — a gateway timeout or region affinity mismatch entry confirms NetEase's matchmaker is sending you to a dead edge node. File a ticket at marvelrivals.com/support including your MachineId (visible in the log) and request a regional reset on your account. Marvel Rivals' [official help center](https://marvelrivals.com/help) tracks active patch-day server incidents — confirm the matchmaker is green before assuming the issue is client-side.