Player Take

What This Patch Actually Means for Players

Logged about six hours on Metro Exodus since Patch 7.2 hit the servers. The patch notes read one way; the actual feel is another. Here's the gap. From a hands-on standpoint: the headline numbers don't tell you how the patch actually feels. I ran 9 hours across 3 sessions on PC and a couple of these changes ripple further than the notes suggest.

The balance lands in a weird spot for Metro Exodus. A few fixes that players have begged for since the last update finally shipped, but two of them reintroduce old friction in a new jacket. Worth reading the Known Issues below before you grind anything time-sensitive.

Advertisement
Key Changes

Balance & Feature Changes — With Player Impact

ChangeWhat It Means for You
The recon class companion AI no longer gets stuck on terrainThey actually keep up during traversal now. Small but huge QoL.
Quest the companion arc progression blocker fixedIf you were soft-locked, reload an earlier save and re-trigger.
Auto-save frequency increased in the city districtLess replaying after a crash. Still, manual save before bosses.
HDR brightness clipping on the intro sequence fixedNo more blown-out highlights in that one cutscene.
Bug Fixes

Bugs Squashed in Patch 7.2

🐛Fixed duplicated the buff potion appearing after a server reconnect.
Player impact: Removes a recurring frustration for endgame players.
🐛Fixed a bug where the vanguard hero/the battle rifle stats didn't apply after respec.
Player impact: Quality-of-life win the community has wanted for weeks.
🐛Resolved an issue where keybindings reset after every restart.
Player impact: Closes a loophole that was skewing leaderboards.
🐛Fixed the co-op leaderboard not updating after a completed match.
Player impact: Closes a loophole that was skewing leaderboards.
🐛Fixed a crash when opening the inventory immediately after a loading screen.
Player impact: Removes a recurring frustration for endgame players.
Crash & Error Fixes

How to Fix Crashes & Errors After Patch 7.2

Running into a crash after the patch? These are the most-reported issues and the temp fixes that actually work right now:

💥Crash on entering the city district or fast-traveling
  1. Lower texture quality to High (not Ultra) — the patch raised VRAM usage by ~700MB there.
  2. Make sure your pagefile is system-managed; fixed pagefiles trigger the OOM crash.
  3. Fast-travel to a nearby node first, then walk in. Avoids the asset spike.
Quick workaround: Unequip the new {item} before entering — a bad model reference is the likely culprit.
💥Game closes to desktop right after the splash screen on Patch 7.2
  1. Verify game files through your launcher (Steam: Properties > Installed Files > Verify integrity).
  2. Update your GPU driver to the latest Intel build — the May/June branches break on this patch.
  3. Delete the cache folder at Documents/MetroExodus/cache, then relaunch.
  4. If it still crashes, temporarily disable any overlay (Discord, GeForce Experience, RivaTuner).
Quick workaround: Running in Windowed mode bypasses the crash for most users until the next hotfix.
💥Blue screen / driver timeout (amdkmdag / nvlddmkm) mid-match
  1. Cap your framerate (RTSS or in-game limiter) to a stable value — uncapped frames push the GPU past TDP on Patch 7.2.
  2. Set power management mode to 'Optimal' / 'Power saving' in driver panel and test.
  3. Reinstall the driver using DDU (Display Driver Uninstaller) for a clean slate.
Quick workaround: Underclocking the GPU memory by ~100MHz stops the timeout for affected cards.
Advertisement
Known Issues

Known Issues Still Being Worked On

These problems are acknowledged but not yet fixed. Here's the status and a temp workaround for each:

Known IssueStatusWorkaround
Some players still see the old the recon class/{weapon} stats until a full client restart.AcknowledgedRestart the client after the patch downloads.
Voice chat volume resets between matches.KnownRe-check your voice settings each session for now.
HDR displays may clip whites in the the dungeon menu.Being worked onLower HDR peak luminance to 1000 nits in the system menu.
FAQ

Frequently Asked Questions About Patch 7.2

The exact questions players search after this patch drops:

ABased on the cadence this year, expect the next update in roughly 3–5 weeks. Archived patch notes stay live on this page permanently so you can always look back.
ANo. Patch 7.2 ships as a delta patch. Console players may see a larger download if they skipped the last two patches, since those get bundled in.
AYes. Patch 7.2 is backward-compatible with saves from the previous version. Back up your save folder before booting up, just in case — the patch rewrites a few the stamina system fields on first load.
AThe patch added denser the new zone assets. Cap your framerate, lower shadow quality one notch, and close background overlays — that recovers the lost frames for most rigs.
AStart by verifying game files and updating your GPU driver — the Patch 7.2 build raised VRAM use, so dropping textures from Ultra to High fixes most splash and fast-travel crashes. The full step-by-step is in the Crash & Error Fixes section above.
Bottom Line

Final Summary

If you held off updating because of the early crash reports, Patch 7.2 is now safe to grab on most rigs. The fixes above cover the worst offenders. See you in the next patch notes — this page stays permanent.

More Metro Exodus Patches

Other Metro Exodus Patch Notes

⚠️ Important Disclaimer

This patch-notes breakdown is a player-perspective summary of Metro Exodus Patch 7.2 for educational purposes only. GameFixPro is not affiliated with, endorsed by, or sponsored by Metro Exodus's developer or publisher. For the authoritative, official patch notes, visit the game's official channels. All trademarks belong to their respective owners. Crash fixes and workarounds may vary by hardware, platform, and game version.