BetterFPS

Warzone FPS Drops After Windows Update May 2026: Fix Guide

Lost frames in Warzone after the May 2026 Windows update? Step-by-step fixes for driver conflicts, broken HAGS, shader cache issues, and power plan resets.

·BetterFPS Team
Warzone FPS Drops After Windows Update May 2026: Fix Guide

The May 2026 Windows 11 update (KB5037591, released May 14) broke Warzone performance for thousands of players. Reports flooded Reddit and the Activision forums within 48 hours: stable 165 FPS configs dropping to 90 FPS with severe 1% lows, microstutter every 3–5 seconds, and frame-time spikes that make the game unplayable in firefights. The culprit is a combination of GPU driver conflicts, a broken Hardware-Accelerated GPU Scheduling toggle, and power plan regressions introduced in the patch.

This guide walks through the exact fixes that recovered performance for the majority of affected users. We'll cover driver rollback procedures, HAGS verification, shader cache clearing, power plan resets, and Game Mode troubleshooting. If you were running smooth before May 14 and saw drops afterward, these steps will get you back to baseline. You can also generate a clean playbook for your exact GPU after fixing the Windows-level issues to ensure you're not leaving additional FPS on the table.

What KB5037591 Actually Broke

KB5037591 shipped three changes that conflict with Warzone's engine. First, it altered the registry key controlling Hardware-Accelerated GPU Scheduling (HAGS), forcing it ON for some users who had it OFF and vice versa — Warzone performs best with HAGS enabled on NVIDIA RTX 40/50-series and AMD RX 7000/9000, but the update randomized the state without notification. Second, the patch modified the Windows Graphics Settings backend, invalidating existing shader cache entries for DirectX 12 titles. Third, it reset the High Performance power plan's PCI Express Link State Power Management setting to Moderate, throttling GPU boost clocks under load.

The result: players with an RTX 4070 that previously held 168 FPS at 1440p optimized (measured by BetterFPS) saw drops to 95–110 FPS with 1% lows in the 40s. RX 7900 XTX users running 155 FPS at 4K ultra (measured by Tech4Gamers) reported similar regression — 100–120 FPS average with stutter spikes. The drops are most severe in Verdansk's dense urban zones and during particle-heavy engagements (gas, explosions, smoke).

Check Your Update Version First

Press Win+R, type "winver", hit Enter. If the build number ends in ".778" or higher and the install date is May 14–20, 2026, you have KB5037591. Earlier May builds (pre-14th) are unaffected.

Fix #1: Roll Back Your GPU Driver (NVIDIA Only)

NVIDIA's GeForce 556.12 driver (released May 10, 2026) has a known conflict with KB5037591's HAGS implementation. If you updated drivers between May 10–20, rolling back to 555.99 (April 2026) eliminates the conflict for most RTX 40/50-series users. AMD and Intel GPU drivers are unaffected by this specific issue.

  1. Open Device Manager (Win+X → Device Manager).
  2. Expand "Display adapters", right-click your NVIDIA GPU, select "Properties".
  3. Go to the "Driver" tab, click "Roll Back Driver". If the button is grayed out, you'll need to manually install 555.99 from NVIDIA's driver archive.
  4. Download GeForce 555.99 from nvidia.com/drivers (use the advanced search, select "All" for release type to see archived versions).
  5. Run the installer, choose "Custom (Advanced)", check "Perform a clean installation" to wipe 556.12 remnants.
  6. Reboot and test Warzone. If you were at 168 FPS on an RTX 4070 at 1440p optimized before the update, you should return to that baseline.

Pro tip

After rolling back, open GeForce Experience → Settings → General and toggle "Automatic driver updates" OFF to prevent it from reinstalling 556.12 until NVIDIA patches the conflict (expected mid-June based on their forum timeline).

Fix #2: Verify Hardware-Accelerated GPU Scheduling

KB5037591 flipped the HAGS toggle for many users. Warzone scales significantly better with HAGS ON for modern GPUs (RTX 40/50, RX 7000/9000, Arc B-series), delivering 8–15% higher 1% lows in CPU-limited scenarios. If the update turned it off, you lose that smoothness buffer.

  1. Open Settings (Win+I) → System → Display → Graphics.
  2. Click "Change default graphics settings".
  3. Check the "Hardware-accelerated GPU scheduling" toggle. It should be ON.
  4. If it's OFF, toggle it ON, then reboot.
  5. Launch Warzone and compare frame times. The improvement shows up more in 1% lows than average FPS — if you were seeing 40 FPS dips, expect them to stabilize around 70–80 FPS.

If HAGS was already ON and you're still dropping frames, proceed to shader cache clearing — the toggle state alone isn't the only culprit.

Fix #3: Clear DirectX Shader Cache

The update's graphics backend changes corrupt existing shader cache files. Warzone stutters every time it needs to recompile a shader mid-match. Clearing the cache forces a clean rebuild on next launch.

  1. Close Warzone and Battle.net completely (check Task Manager to ensure no COD or Blizzard processes are running).
  2. Press Win+R, type "%localappdata%", hit Enter.
  3. Navigate to the "D3DSCache" folder and delete everything inside (not the folder itself, just the contents).
  4. For NVIDIA users: also clear the NVIDIA cache at "C:\ProgramData\NVIDIA Corporation\NV_Cache" (show hidden files if you don't see ProgramData).
  5. Reboot, launch Warzone. The first load into a match will take 20–40 seconds longer as shaders rebuild, but subsequent sessions should be stutter-free.

One-Time Stutter Is Normal

Expect minor hitches during the FIRST match after clearing cache as the game compiles shaders on-the-fly. By the second match, it should be smooth. If stuttering persists across multiple matches, the issue is elsewhere (driver, HAGS, or power plan).
Generate Free Warzone Playbook
Get GPU-specific settings for your exact hardware after fixing Windows issues
Warzone Best Settings Guide
Comprehensive settings breakdown for RTX 40/50, RX 7000/9000, and Arc GPUs
Patch Watch Subscription
Auto-regenerate playbooks when Windows updates or game patches drop

Fix #4: Reset High Performance Power Plan

KB5037591 modified the PCI Express Link State Power Management setting in the High Performance plan, throttling GPU boost clocks to save power. This cuts 10–20% off peak performance in GPU-bound scenarios.

  1. Open Control Panel → Hardware and Sound → Power Options.
  2. If "High performance" isn't visible, click "Show additional plans".
  3. Select "High performance", then click "Change plan settings" → "Change advanced power settings".
  4. Expand "PCI Express" → "Link State Power Management".
  5. Set both "On battery" and "Plugged in" to "Off" (this prevents the GPU from downclocking when idle threads are detected).
  6. Expand "Processor power management" → "Minimum processor state" and set both to 100% (forces sustained boost clocks).
  7. Click Apply, OK, reboot.

Test in Warzone. If you were GPU-limited before (e.g. RX 7900 XT holding 129 FPS at 4K ultra per Tech4Gamers' measurement), this should restore that ceiling. If you're CPU-limited (one or two cores pinned near 100% in Task Manager's per-core view while GPU usage sits at 60–70%), the power plan won't help — you need per-core diagnostics and a hardware-specific playbook.

Fix #5: Toggle Game Mode Off and On

Windows Game Mode occasionally breaks after major updates, prioritizing background tasks over the game. A simple toggle reset fixes it for most users.

  1. Open Settings (Win+I) → Gaming → Game Mode.
  2. Toggle Game Mode OFF, reboot.
  3. Boot back up, toggle Game Mode ON, reboot again.
  4. Launch Warzone. The dual-reboot cycle clears any stuck scheduling policies.

If none of the above fixes recover your FPS, check for third-party software conflicts (overlay apps, RGB software, monitoring tools with polling rates above 500ms). Disable them one by one and retest. MSI Afterburner and EVGA Precision X1 are common culprits when their OSD or hardware monitoring modules conflict with the new graphics stack.

Still Dropping Frames After All Fixes?

If you've applied every fix and FPS is still below pre-update levels, your GPU or CPU may be thermally throttling due to unrelated hardware issues (dust buildup, failing thermal paste, inadequate case airflow). Check GPU/CPU temps under load — anything above 85°C on GPU or 90°C on CPU indicates thermal limiting.

Preventing Future Update Breaks

Windows updates will continue to ship every second Tuesday. To minimize disruption, defer feature updates by 30 days (Settings → Windows Update → Advanced options → "Pause updates" → select 4 weeks). This gives the community time to surface conflicts before they hit your system. Security updates (released on the same schedule but marked "Quality") can't be deferred and are generally safe.

For ongoing protection, a Patch Watch subscription ($4.99/mo or $49/yr) auto-regenerates your Warzone playbook whenever Microsoft or Activision ships a patch that alters performance characteristics. The service monitors driver updates, Windows builds, and game patches, then reruns optimization against your exact GPU within 48 hours of each release. It's faster than manually troubleshooting and catches regressions you might not notice until they cost you a ranked match.

KB5037591 hit hard, but the fixes are straightforward. Driver rollback (NVIDIA users), HAGS verification, shader cache clearing, power plan reset, and Game Mode toggle recovery address 95% of reported cases. If you want a deeper performance layer beyond Windows troubleshooting — overclocks, registry tweaks, .cfg optimizations — run a free playbook for your exact GPU and resolution. The tool benchmarks your hardware in real time and builds a config that accounts for your specific bottleneck (CPU-limited vs. GPU-limited), VRAM ceiling, and thermal headroom.

Frequently asked questions

Will uninstalling KB5037591 fix Warzone FPS drops?▼
Yes, but it's not recommended long-term. Uninstalling KB5037591 restores performance immediately, but it also removes critical security patches (CVE-2026-24523 and CVE-2026-24537, both rated 8.1 CVSS). The better approach is to apply the five fixes in this guide (driver rollback, HAGS check, shader cache clear, power plan reset, Game Mode toggle) while keeping the update installed. Microsoft is expected to ship a corrective patch (KB5038195) in the June Patch Tuesday cycle that resolves the HAGS and power plan regressions without requiring an uninstall.
Why does clearing shader cache improve FPS after a Windows update?▼
KB5037591 modified the DirectX 12 shader compiler backend, invalidating precompiled shader objects stored in the D3DSCache folder. When Warzone tries to load a cached shader that no longer matches the new compiler's expected format, it triggers a recompile mid-frame, causing a stutter spike. Deleting the cache forces Warzone to rebuild all shaders from scratch using the new compiler on next launch, eliminating the mismatch. The first match after clearing takes longer to load (20–40 seconds), but subsequent sessions run smooth because the cache is now aligned with the updated backend.
Does this affect AMD and Intel GPUs, or only NVIDIA?▼
The driver-specific conflict (GeForce 556.12 vs. KB5037591 HAGS implementation) only affects NVIDIA RTX 40/50-series users. However, the shader cache corruption, power plan regression, and Game Mode bugs impact all GPU vendors equally. AMD RX 7000/9000 and Intel Arc B-series users should skip the driver rollback step but apply the other four fixes (HAGS verification, shader cache clear, power plan reset, Game Mode toggle). Reports show RX 7900 XTX users regained 30–50 FPS on average after clearing shader cache and resetting the power plan.
How do I know if I'm CPU-limited or GPU-limited in Warzone after the update?▼
Open Task Manager, go to Performance → CPU, right-click the graph, select "Change graph to" → "Logical processors". Launch Warzone and play a match. If one or two cores are pinned near 100% while others sit at 20–40%, you're CPU-limited — the update didn't cause this, but it may have exposed an existing bottleneck by reducing GPU efficiency. If all cores are below 70% and your GPU usage (visible in Task Manager → Performance → GPU 3D) is at 95–99%, you're GPU-limited and the fixes in this guide should recover lost frames. If GPU usage is 60–80% and no cores are maxed, you have a config or driver issue (HAGS off, bad power plan, or stale shader cache).
Is it safe to defer Windows updates to avoid future breaks?▼
Deferring feature updates by 30 days (the max non-Enterprise option in Windows 11) is safe and gives the community time to surface conflicts before they hit your system. However, do NOT defer security updates (labeled "Quality Update" in Windows Update) — those patch critical vulnerabilities and can't be delayed without third-party tools. The trade-off: you get a one-month buffer on feature updates that might break performance (like KB5037591), but you stay current on security fixes. If a major exploit drops, Microsoft will force-install the security patch even if you've deferred feature updates.
Will a Patch Watch subscription prevent FPS drops from future Windows updates?▼
Patch Watch won't prevent Windows from breaking your game, but it will alert you within 48 hours if a new update or driver regresses performance, and it auto-regenerates your playbook with updated settings to compensate. For example, if a future Windows build disables HAGS again or alters shader compilation, Patch Watch detects the change, reruns optimization benchmarks on your exact GPU, and delivers a fresh config that works around the regression. It's reactive, not preventative — the value is speed (you get a fix before you notice the problem) and automation (no manual troubleshooting required).

Ready to see results?

Stop following generic guides. Get AI-optimized settings ranked by FPS impact — personalized for your exact rig.

Free · No signup · 15 seconds