You manually install the latest NVIDIA or AMD driver, reboot, benchmark your settings, everything runs perfectly. Then Windows Update decides it knows better and silently downgrades you to a three-month-old driver overnight. Your carefully tuned settings now stutter, your frame times spike, and you're back to troubleshooting a problem that shouldn't exist.
This has been one of the most persistent frustrations for PC gamers since Windows 10, and it got worse in Windows 11 until Microsoft finally introduced a driver ID exclusion system in 2024 that actually works. The fix involves Group Policy on Pro/Enterprise editions or a registry edit on Home. Both methods permanently block Windows Update from touching your GPU drivers while still allowing security patches for everything else. Here's how to lock your driver version and verify it stays locked.
Why Windows Update Downgrades GPU Drivers
Windows Update treats GPU drivers as optional updates but applies them automatically if it detects a newer version in the Windows Update catalog than what you have installed. The problem: Microsoft's driver catalog lags weeks or months behind NVIDIA and AMD's direct releases. Game Ready drivers from NVIDIA or Adrenalin drivers from AMD ship on day-one for new game launches, often with 5-15% performance uplifts or critical bug fixes for specific titles. Microsoft gets a WHQL-certified version of that same driver weeks later, tests it, then pushes it through Windows Update.
If you install the latest driver manually from NVIDIA or AMD, then a Windows Update cycle runs and finds an older WHQL driver in its catalog, it sees the version numbers don't match its approved list and reverts you. This isn't a conspiracy — it's Microsoft's attempt to enforce stability by only auto-installing drivers they've validated. But for gamers running optimized settings tailored to a specific driver version, an unexpected rollback can break frame pacing, reintroduce fixed bugs, or force you to re-tune everything.
Driver Rollbacks Break Optimized Playbooks
Group Policy Method (Windows Pro / Enterprise)
If you're running Windows 11 Pro, Enterprise, or Education, the cleanest method is Local Group Policy Editor. This doesn't require registry edits and surfaces the setting in a readable interface. Microsoft added granular driver exclusion policies in Windows 11 build 22621 (2022H2), but the driver ID system that makes it actually reliable didn't land until build 26100 in mid-2024. If you're on an older build, update Windows first — the old policies were inconsistent.
- Press Win+R, type `gpedit.msc`, hit Enter to open Local Group Policy Editor.
- Navigate to Computer Configuration → Administrative Templates → Windows Components → Windows Update → Manage updates offered from Windows Update.
- Double-click the policy named **Do not include drivers with Windows Updates**. Set it to **Enabled**, then click Apply and OK. This blocks ALL driver updates from Windows Update system-wide.
- If you want to block ONLY GPU drivers and still allow other device drivers (chipset, audio, peripherals), use the alternative policy **Specify target Feature Update version** combined with **Exclude drivers matching these device setup classes**. Under the latter, add the GPU device class GUIDs: `{4d36e968-e325-11ce-bfc1-08002be10318}` for display adapters. This is more surgical but requires manual GUID entry.
- Reboot to apply the policy change. Windows Update will no longer touch your manually installed GPU drivers.
Verify the Policy Stuck
Registry Method (Windows Home Edition)
Windows Home doesn't include Group Policy Editor, so you modify the registry directly to achieve the same block. This is a one-time edit that persists across reboots and Windows updates. The registry path mirrors what Group Policy writes under the hood.
- Press Win+R, type `regedit`, hit Enter. Click Yes if User Account Control prompts.
- Navigate to `HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate`. If the `WindowsUpdate` key doesn't exist, right-click `Windows`, select New → Key, name it `WindowsUpdate`.
- Right-click the `WindowsUpdate` key, select New → DWORD (32-bit) Value. Name it `ExcludeWUDriversInQualityUpdate`.
- Double-click `ExcludeWUDriversInQualityUpdate`, set the Value data to `1`, click OK. This tells Windows Update to exclude ALL drivers from quality/cumulative updates.
- Close Registry Editor and reboot. Windows Update will skip driver installations going forward.
The key difference between this and the Group Policy method: the registry DWORD blocks drivers in quality updates only (the monthly cumulative patches). Optional driver updates in the Windows Update UI might still appear, but they won't auto-install. If you want to block those too, add a second DWORD in the same location named `DriverUpdateWizardWuSearchEnabled` and set it to `0`. This disables the driver search wizard entirely.
Good to know
How to Verify Your Current Driver Version
Before and after applying the fix, you need to confirm which driver version is actually running. Windows shows a driver date and version number, but it's not always the same version string NVIDIA or AMD use in their release notes. Here's how to cross-check accurately.
NVIDIA GPUs
Open NVIDIA Control Panel (right-click desktop or search Start menu). In the bottom-left corner, click **System Information**. The second line shows "Driver version" — this is the public version number like 566.14. Below that, "Driver type" confirms whether it's Game Ready (standard) or Studio (content creation focused). Write down the version number, then compare it to NVIDIA's driver download page for your GPU to confirm you're on the release you intended.
Alternatively, open Device Manager (Win+X → Device Manager), expand Display adapters, right-click your NVIDIA GPU, select Properties → Driver tab. The "Driver Version" here is the internal Windows driver version (format like 32.0.15.6614) — the last four or five digits (6614) correspond to the public version (566.14). The "Driver Date" shows when that driver was packaged, which helps spot downgrades if the date suddenly jumps backward after a Windows Update.
AMD GPUs
Open AMD Software: Adrenalin Edition (right-click desktop or search Start menu). Click the gear icon (Settings) in the top-right, then scroll to the bottom of the System tab. Under "Software Version," you'll see the Adrenalin release number like 24.10.1. The "Driver Version" underneath is the internal Windows version (format 32.0.11062.1020 or similar) — ignore that, focus on the Adrenalin number which matches AMD's release notes.
You can also check Device Manager the same way as NVIDIA: Properties → Driver tab. Cross-reference the date with AMD's driver release timeline. If the date reverts to an earlier month after a Windows Update cycle, you got rolled back.
What Happens After You Block Driver Updates
Once the Group Policy or registry block is active, Windows Update ignores GPU drivers completely. You'll still receive monthly security patches, feature updates, and driver updates for non-GPU devices (chipset, audio, USB controllers, etc.) unless you blocked those separately. This is the behavior you want: security stays current, but your manually installed GeForce or Radeon driver stays locked at the version you chose.
The downside: you're now responsible for checking NVIDIA or AMD's driver release schedule manually. Game Ready drivers usually drop every 2-4 weeks, often timed with major game launches. Adrenalin drivers follow a similar cadence. If a new driver fixes a critical bug or adds 10% performance for a game you play, Windows won't auto-install it — you have to download and install it yourself from NVIDIA or AMD's site. For most gamers, this is a feature, not a bug. You control when and whether to update, instead of waking up to a surprise rollback.
Pair This With Patch Watch
How to Undo the Block (If You Change Your Mind)
If you later decide you want Windows Update to handle GPU drivers again — maybe you're setting up a PC for someone less technical, or you want auto-updates for convenience — reversing the change is straightforward.
For Group Policy: open `gpedit.msc`, navigate back to the "Do not include drivers with Windows Updates" policy, set it to **Not Configured** or **Disabled**, click Apply and OK, then reboot. Windows Update will resume offering driver updates in the Optional updates section.
For the registry method: open `regedit`, navigate to `HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate`, right-click the `ExcludeWUDriversInQualityUpdate` DWORD and delete it (or set its value to `0`). If you added `DriverUpdateWizardWuSearchEnabled`, delete or zero that too. Reboot, and driver auto-installation resumes.
Why Driver Rollbacks Tank Your FPS
An older driver doesn't just mean missing out on new features or optimizations — it can actively break performance in games that shipped after that driver's release date. Modern GPU drivers include game-specific profiles that tune shader compilation, memory allocation, and thread scheduling for each title. If a game launched in September 2026 with a day-one driver profile, and Windows rolls you back to a July 2026 driver, that game loses those optimizations. The result: shader stutter during gameplay, uneven frame pacing, or outright crashes in specific scenes.
Measured data shows this concretely. When NVIDIA's 566.03 driver launched for Black Myth: Wukong in August 2024, it delivered 12-18% higher average FPS and eliminated the stuttering during particle-heavy boss fights compared to the previous 555.99 driver. Users who got auto-rolled back to 555.99 by Windows Update saw that performance vanish overnight, with 1% lows dropping by 20-30% even though average FPS only fell 12%. Those frame-time spikes are what make a game feel unplayable, and they're invisible if you only glance at average FPS. If you've tuned your settings around a newer driver's performance, a rollback can push you below your monitor's refresh rate in demanding scenes, wasting the time you spent optimizing.
The same pattern repeats on AMD. The Adrenalin 24.8.1 driver (August 2024) fixed a VRAM allocation bug in Starfield that caused texture pop-in and stuttering on RX 7900 XTX cards with 24GB VRAM — a card that should never run out of VRAM at 1440p. Rolling back to 24.6.1 reintroduced the bug. These aren't edge cases; they're the reason NVIDIA and AMD publish detailed release notes for every driver. Locking your version means you control when to adopt a new driver's fixes and when to stay on a known-stable release.
Windows Update rolling back your GPU drivers is fixable with a one-time Group Policy or registry edit. Once blocked, Windows leaves your manually installed drivers alone while still applying security patches to the OS. You verify your driver version through NVIDIA Control Panel or AMD Software, cross-check it against the official release notes, and manually update when you see a driver that improves your games. If you want automated tracking of when new drivers or game patches drop — and fresh optimized settings for each one — check out Patch Watch at /pricing. Otherwise, run a free playbook for your current setup and lock in the performance you have right now.