Tom Clancy’s The Division 2 Patch 6.4 Notes | Bug Fixes & Changes

Player Take

What This Patch Actually Means for Players

I've been mainlining Tom Clancy’s The Division 2 since Patch 6.4 dropped, and the patch is doing more than the headline says. Let me walk you through the parts that matter at your desk. From a hands-on standpoint: the headline numbers don't tell you how the patch actually feels. I ran 6 hours across 3 sessions on PC and a couple of these changes ripple further than the notes suggest.

Netcode feels more honest after Patch 6.4. I'm getting fewer 'how did that register?' moments, which is the boring but important win. The flashy balance changes get the clicks; the rollback fixes are why you'll actually stay.

Key Changes

Balance & Feature Changes — With Player Impact

Change	What It Means for You
The support main ability cooldown increased by 3s	Main players should pre-plan engagements; you can't burn the escape as a panic button anymore.
The shotgun damage adjusted from 25 to 120 at range	Snipers who relied on the old TTK will need to relearn sightlines — the two-tap window is tighter now.
Hit registration on fast-moving targets improved	Tracking feels cleaner in chaos. Less 'I swear I hit him' moments.

Bug Fixes

Bugs Squashed in Patch 6.4

🐛Fixed a bug where the equipped relic tooltips showed the wrong stat values.

Player impact: Closes a loophole that was skewing leaderboards.

🐛Resolved audio cutting out during the daily dungeon on certain sound cards.

Player impact: Removes a recurring frustration for endgame players.

🐛Resolved an issue where keybindings reset after every restart.

Player impact: Quality-of-life win the community has wanted for weeks.

🐛Fixed a memory spike that could cause a disconnect after long sessions.

Player impact: Closes a loophole that was skewing leaderboards.

Crash & Error Fixes

How to Fix Crashes & Errors After Patch 6.4

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

💥Game closes to desktop right after the splash screen on Patch 6.4

Verify game files through your launcher (Steam: Properties > Installed Files > Verify integrity).
Update your GPU driver to the latest Intel build — the May/June branches break on this patch.
Delete the cache folder at Documents/TomClancy’sTheDivision2/cache, then relaunch.
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

Cap your framerate (RTSS or in-game limiter) to a stable value — uncapped frames push the GPU past TDP on Patch 6.4.
Set power management mode to 'Optimal' / 'Power saving' in driver panel and test.
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.

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 Issue	Status	Workaround
High refresh rate monitors may cap at 60fps in borderless mode.	Pending fix	Use exclusive fullscreen until the next hotfix.
Voice chat volume resets between matches.	Known	Re-check your voice settings each session for now.
Controller rumble stays on after disconnecting a pad.	Known	Reconnect and disconnect the controller again to reset it.

FAQ

Frequently Asked Questions About Patch 6.4

The exact questions players search after this patch drops:

QWere any the crafting bench nerfed in Patch 6.4?−

AA few. Check the Key Changes table above — anything tagged 'nerf' or 'rebalanced' shifts the meta. Nothing got gutted, but two popular setups lost some uptime.

QWhy is my FPS lower after Patch 6.4?+

AThe patch added denser the menu assets. Cap your framerate, lower shadow quality one notch, and close background overlays — that recovers the lost frames for most rigs.

QIs my save file compatible with Patch 6.4?+

AYes. Patch 6.4 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 crafting bench fields on first load.

QHow do I fix the crash after the Patch 6.4 update?+

AStart by verifying game files and updating your GPU driver — the Patch 6.4 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.

QWhen is the next patch after Patch 6.4?+

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.

Bottom Line

Final Summary

If you held off updating because of the early crash reports, Patch 6.4 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.

⚠️ Important Disclaimer

This patch-notes breakdown is a player-perspective summary of Tom Clancy’s The Division 2 Patch 6.4 for educational purposes only. GameFixPro is not affiliated with, endorsed by, or sponsored by Tom Clancy’s The Division 2'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.