Problem: Windows 11 KB5066835 (Oct 2025) can tank PC gaming FPS and cause stutter—often with no single reliable fix

Published: 2026-01-23 12:00 (local time)

Quick Summary

A Windows 11 cumulative update (KB5066835, released 2025-10-14) has been widely linked to sudden frame-rate drops, stutter, and worse frame pacing in some games.
The impact appears inconsistent: some PCs/games barely change, while others see dramatic FPS loss.
NVIDIA issued a targeted hotfix driver (GeForce Hotfix 581.94, released 2025-11-19) specifically mentioning “lower performance” after KB5066835.
Microsoft’s KB notes don’t broadly acknowledge a general “FPS regression” as a known issue, so many players end up troubleshooting blindly.
Workarounds exist (hotfix driver, driver cleanup, toggling ReBAR, rollback strategies), but none are universal.

What’s happening

Since Microsoft released Windows 11 KB5066835 on October 14, 2025 (for Windows 11 24H2 and 25H2 branches), many PC gamers have reported that some games run noticeably worse right after installing the update: average FPS drops, 1% lows get uglier, and camera movement “feels” stuttery even when the FPS counter looks acceptable. Reports span different genres and engines, but the most publicized examples include major AAA titles where the regression is easy to benchmark and hard to ignore.

Coverage and community posts suggest the issue is most visible on systems using GeForce GPUs, but multiple reports indicate it may not be exclusive to NVIDIA hardware. The frustrating part is the unevenness: two PCs with similar specs may behave differently, and reinstalling drivers sometimes helps only temporarily.

Separately, Microsoft’s official KB entry for KB5066835 focuses on security and selected fixes (including a specific “gaming” input-related fix), but it does not clearly present a broad “post-update FPS regression” as a resolved/known issue. That gap is why this problem still feels like it has “few to no clear solutions” for affected players: the official Windows patch notes don’t line up with what many gamers observe in practice.

Likely causes (what research suggests)

OS/driver interaction triggered by KB5066835: NVIDIA’s own hotfix notes (as widely quoted by press and the NVIDIA community) explicitly reference reduced performance in some games after installing KB5066835, strongly implying an interaction between the Windows update and the graphics stack/driver behavior.
Configuration-dependent regression (not a single bug): Independent testing and user reports show wildly different outcomes depending on the game, resolution, and system configuration—pointing to a compatibility/performance path that only some setups hit.
Resizable BAR (ReBAR) sensitivity in some cases: Some reporting (including mainstream tech coverage) indicates that disabling ReBAR can reduce the regression for certain titles/systems, suggesting the update may have altered timing/CPU-GPU scheduling patterns that interact with ReBAR paths.
Driver state corruption or bad “upgrade path” residue: Community troubleshooting threads regularly show that clean driver installs (DDU) sometimes help, which supports the idea that the update can expose instability in existing driver states rather than purely introducing a new universal Windows bug.

Solutions & Workarounds

1) Install NVIDIA’s targeted hotfix driver (GeForce Hotfix 581.94) if you use GeForce

Who it helps: Windows 11 (24H2/25H2) PCs with NVIDIA GeForce GPUs affected after KB5066835.

Open NVIDIA’s official hotfix/support channel and download Hotfix Driver 581.94 (manual install).
Close games and overlays.
Run the installer, choose a clean install option if offered, then reboot.
Re-test the specific game/scene that regressed (use the same settings each time).

Risks/tradeoffs: Hotfix drivers are targeted releases with less validation than full WHQL drivers; they can solve one issue while introducing another.

Stop and contact official support when: Performance is still broken after the hotfix + reboot, or you encounter new crashes/black screens. Escalate to NVIDIA Support with your driver version, Windows build, and a reproducible benchmark scene.

2) Do a true “clean” GPU driver reinstall (DDU) to eliminate a corrupted driver state

Who it helps: NVIDIA/AMD users where performance regressed after the Windows update and persists across normal driver installs.

Download Display Driver Uninstaller (DDU) from its official source.
Disconnect from the internet (prevents Windows from auto-installing a driver mid-process).
Boot into Safe Mode, run DDU, remove GPU drivers.
Reboot normally, then install the latest stable GPU driver (or the NVIDIA hotfix if applicable).
Reboot again and retest.

Risks/tradeoffs: You’ll lose custom profiles/settings and may need to reconfigure G-Sync/FreeSync, color settings, and game profiles.

Stop and contact official support when: Clean install doesn’t change anything, or your PC becomes unstable outside games (freezes, driver timeouts).

3) Try disabling Resizable BAR (ReBAR) temporarily for the affected game(s)

Who it helps: Players seeing major FPS drops in specific titles after KB5066835, especially if coverage/community reports mention ReBAR sensitivity for that game.

Check if your motherboard BIOS has a Resizable BAR option (often under PCIe/advanced settings).
Disable Resizable BAR (and Above 4G Decoding only if your board requires that pairing), save and reboot.
Re-test the affected game(s).

Risks/tradeoffs: Some games benefit from ReBAR; disabling it can reduce performance in other titles.

Stop and contact official support when: You’re not comfortable changing BIOS settings, or you experience boot issues after changing PCIe/BIOS options.

4) Verify KB5066835 is installed, then decide: mitigate or roll back (if still possible)

Who it helps: Anyone unsure whether they’re actually on the problematic update path.

In Windows, open Settings → Windows Update → Update history and confirm KB5066835 installation.
If your system allows uninstalling the LCU, uninstall KB5066835 and reboot, then test performance.
If uninstall isn’t available (common after time passes), prioritize driver/hotfix mitigation instead.

Risks/tradeoffs: Rolling back security updates can increase risk exposure; also, uninstall may not be available on many systems.

Stop and contact official support when: You’re on a managed/work PC, or uninstall attempts fail—use Microsoft support channels and provide the KB number and OS build.

5) Reduce “variables”: disable overlays, capture tools, and frame-generation experiments while testing

Who it helps: Anyone diagnosing stutter/frame pacing issues.

Disable Xbox Game Bar capture features, Discord overlay, Steam overlay, and any third-party OSD tools.
Turn off experimental features one at a time (Frame Generation, Reflex, Anti-Lag, driver-level sharpening).
Re-test the same in-game spot for 2–3 minutes and compare.

Risks/tradeoffs: You may lose useful features (capture/party chat overlays) until the root cause is found.

Stop and contact official support when: The issue reproduces even with a clean environment and persists across multiple games.

Prevention (so it doesn’t come back)

Create a restore point (or full system image) before major Windows cumulative updates, especially on a “gaming-critical” PC.
Keep a known-good GPU driver installer archived so you can revert quickly if a new Windows patch + new driver combo goes bad.
Change only one variable at a time (Windows update, driver, BIOS setting) and benchmark a repeatable scene to avoid placebo fixes.
If you’re not impacted, avoid hotfix/beta drivers and wait for the next fully validated driver branch that incorporates the fix.

FAQ

Q: How do I know if I’m affected by KB5066835?
A: You’ll usually see an immediate change after the update: lower FPS, worse 1% lows, or new stutter in games that were previously stable. Confirm KB5066835 in Windows Update history.

Q: Is this definitely Microsoft’s fault?
A: Unclear. The strongest evidence is that the regression appears after a Windows update and NVIDIA issued a driver mitigation specifically naming that update. That suggests an interaction rather than a single-party “100% fault.”

Q: I installed the hotfix and nothing changed—what next?
A: Try a DDU-based clean install, then test with overlays off. If it’s game-specific, try ReBAR off as a test.

Q: Why does my FPS counter say ~60 but the game feels like ~30?
A: That’s often frame pacing (uneven frame times) rather than raw FPS. Stutter can persist even when average FPS looks normal.

Q: Should I uninstall KB5066835?
A: If uninstall is available and the regression is severe, it can be a useful A/B test. But it’s a security update, and uninstall may not remain possible—many users must mitigate instead.

Q: Will there be a permanent fix?
A: Typically, hotfix changes roll into later “standard” GPU driver releases, and Microsoft may also adjust future cumulative updates. Timing is uncertain.