If your frame rates dropped noticeably after installing a Windows update, you are not imagining it. Feature and cumulative updates routinely change graphics driver behavior, power plans, security features, and background services — and any of those can cost you performance. This guide walks through the most common causes, how to identify which one applies to you, and how to fix each one without breaking anything else. Every fix below is reversible, so you can roll back changes if something does not work as expected.
Most Common Causes
| Cause | Symptom | Likelihood |
|---|---|---|
| GPU driver replaced or reset by the update | FPS drop across all games; driver version changed in Device Manager | High |
| Power plan reset to Balanced | Lower clocks, worse performance on laptops and desktops alike | High |
| Hardware-accelerated GPU scheduling or Game Mode toggled | Inconsistent frametimes, stutter alongside lower averages | Medium |
| Core isolation / Memory Integrity enabled | Modest but measurable loss, mostly on older CPUs | Medium |
| Fullscreen optimizations or multiplane overlay changes | Alt-tab lag, stutter in borderless windowed mode | Medium |
| Windows Defender real-time scanning of game folders | Long shader loads, hitches when assets stream in | Low-Medium |
| Background update tasks still running | Drop only for a day or two after the update, then recovers | Low |
Diagnose Step by Step
1. Confirm the update actually changed something
Open Settings > Windows Update > Update history and note the exact KB number and install date. Then open your FPS overlay (Win+G for Game Bar, or your GPU vendor’s overlay) and compare against any pre-update numbers you recorded. If performance recovers within 24–48 hours, Windows was still finishing background indexing, .NET optimization, or defragmentation tasks — no fix needed.
2. Check your GPU driver version
Press Win+X > Device Manager > Display adapters, right-click your GPU, choose Properties > Driver, and note the version and date. If the date matches the update install date, Windows replaced your driver — usually with an older WDDM baseline. Compare against the latest version on NVIDIA, AMD, or Intel’s site.
3. Verify your power plan
Open Control Panel > Power Options (run powercfg.cpl from the Run dialog). Updates frequently reset the active plan to Balanced. Also check Settings > System > Power & battery on laptops — Power Mode may have reset from Best Performance to Balanced.
4. Inspect graphics and gaming settings
Open Settings > System > Display > Graphics > Change default graphics settings. Note the state of Hardware-accelerated GPU scheduling, Variable refresh rate, and Windowed games optimization. Also check Settings > Gaming > Game Mode. Updates can flip any of these.
5. Check Memory Integrity
Go to Windows Security > Device security > Core isolation details. If Memory integrity was switched on (updates occasionally enable it silently), it adds virtualization overhead to all memory operations, which hits older CPUs hardest.
6. Rule out thermals and residue
Run a monitoring tool such as HWiNFO64 and watch CPU/GPU package temperatures and clocks in-game. If clocks throttle below stock, clean out dust and recheck — but confirm throttling before assuming hardware fault. Also open Task Manager (Ctrl+Shift+Esc) and sort by CPU, disk, and GPU to see whether the update pushed a service into constant activity.
Fixes by Cause
Roll back or reinstall the GPU driver
What causes it: Windows Update delivers its own WHQL driver package, overwriting the vendor driver you installed.
How to check: Device Manager driver date (step 2 above) versus the release date of your last manual install.
What to do: In Device Manager, right-click the GPU > Properties > Driver > Roll Back Driver if available. If not, download the latest driver from your vendor, disconnect from the internet, run the installer with a clean installation option (NVIDIA) or Factory reset (AMD), and reconnect afterward. Alternatively, pause updates under Settings > Windows Update for up to five weeks to stop Windows from overwriting it again.
How to undo: Simply install a different driver version the same way; nothing here is permanent.
Restore your power plan
What causes it: Cumulative updates reset the active power scheme to Balanced.
How to check: Run powercfg /getactivescheme in Command Prompt or open Power Options.
What to do: Select High performance, or the Ultimate Performance plan (enable it with powercfg -duplicatescheme e9a42b02-d5df-448d-aa00-03f14749eb61). On laptops, set Settings > System > Power & battery > Power Mode to Best Performance while plugged in.
How to undo: Switch back to Balanced at any time in the same menu.
Re-tune GPU scheduling and Game Mode
What causes it: The update toggles Hardware-accelerated GPU scheduling (HAGS) or Game Mode to defaults that conflict with your setup.
How to check: Settings > System > Display > Graphics > Default graphics settings; compare against what you had before.
What to do: Toggle HAGS off (or on if it was previously on — its impact varies by GPU generation), then reboot. Test one change at a time in a demanding scene. Enable Game Mode if it was disabled; it prevents Windows Update from stealing resources mid-session.
How to undo: Flip the toggle back and reboot; changes apply instantly after restart.
Turn Memory Integrity back off
What causes it: The update enabled Core isolation’s Memory integrity feature without asking.
How to check: Windows Security > Device security > Core isolation details.
What to do: Toggle Memory integrity off and restart. Note this reduces security against certain kernel attacks — treat it as a tradeoff, not a free win, and consider leaving it on if your CPU handles the overhead fine.
How to undo: Toggle it back on and restart.
Disable fullscreen optimizations per game
What causes it: Updated flip-model presentation or multiplane overlay behavior causes stutter in borderless or fullscreen modes.
How to check: Symptoms include alt-tab delays and stutter despite healthy average FPS. Check Settings > System > Display > Graphics for per-app entries.
What to do: Browse to the game’s .exe, right-click > Properties > Compatibility tab, check Disable fullscreen optimizations, and apply. Test both with and without — the impact differs by engine and GPU.
How to undo: Uncheck the same box.
Exclude game folders from real-time scanning
What causes it: Defender re-scans game executables and streamed assets after the update re-indexed your drives.
How to check: Open Windows Security > Virus & threat protection > Protection history; heavy scanning activity coinciding with gameplay is the tell.
What to do: Under Virus & threat protection settings > Exclusions > Add an exclusion > Folder, add your main Steam library folder (e.g., C:\Program Files (x86)\Steam\steamapps) and any other game install roots. Only exclude trusted, legitimate game directories.
How to undo: Remove the exclusion from the same list.
When to Replace or Reinstall
If you have worked through every fix above and performance is still degraded, escalate in this order. First, uninstall the problem update: go to Settings > Windows Update > Update history > Uninstall updates, pick the KB installed right before the drop, and remove it. Then pause updates so it does not reinstall immediately.
Second, use Settings > System > Recovery > Go back if the update was within the last 10 days — this rolls back a feature update while keeping your files.
Third, consider a clean GPU driver pass with Display Driver Uninstaller (DDU) in Safe Mode if rollbacks and reinstalls from within Windows have failed; corrupted driver leftovers from a botched update are rare but stubborn.
Last resort: an in-place repair install — run Setup.exe from a Windows 11 ISO mounted in File Explorer, choose Keep personal files and apps, and let it repair system components without deleting anything. Only a full reset (Settings > System > Recovery > Reset this PC) should follow if the repair install also fails, and back up first.
FAQ
How long should I wait before troubleshooting?
Give it 24–48 hours. Windows schedules maintenance tasks like search indexing and .NET optimization right after updates, and these can hammer the disk and CPU temporarily. If FPS is still low after two days of normal use, start with the driver check.
Will uninstalling the update break anything else?
Cumulative updates can be uninstalled safely from Update history > Uninstall updates, and Windows will simply offer the next patch later. Servicing-stack updates and some security patches cannot be removed — if the KB is greyed out, use the “Go back” recovery option instead.
Does pausing updates leave me exposed?
Pausing for a short window (1–5 weeks via Settings > Windows Update > Pause updates) is a reasonable way to stop a bad GPU driver package from reinstalling while you test. Just set a reminder to resume, since delayed security patches do accumulate risk over time.
My FPS is fine but stutters got worse — same causes?
Mostly yes, but weight the causes differently. Stutter points more toward HAGS, fullscreen optimization/overlay behavior, and Memory Integrity than toward power plans or drivers. Toggle those one at a time and test in the same in-game location for a fair comparison. By 2026 standards, frametime consistency matters as much as average FPS, so use an overlay that shows both.
