Your GPU driver is two months old. Windows Update quietly swaps it for a build from last year, and the next time you launch a game you’re back on an old branch with half the bug fixes missing. This is one of the most common driver complaints on Windows 10 and 11, and it has nothing to do with a broken driver. It’s Windows Update overriding your manual install.
Here is what’s actually happening and how to make it stop.
Why Windows Update keeps pushing that old driver
Windows Update maintains its own driver catalog, and it isn’t synced to the day with what NVIDIA, AMD, or Intel publish. When Microsoft’s catalog flags a newer package than what you have installed, it can install it during a routine update cycle. The catch: “newer” here means newer in Microsoft’s catalog, not newer than what you grabbed from the vendor. Those two numbers don’t always move in the same direction.
The result is a version that can sit several releases behind what the manufacturer offers, which means you lose performance improvements and bug fixes that shipped after Microsoft’s package was certified. Engadget calls out exactly this reputation problem: Windows Update is fine for hardware with no vendor software, but for GPUs it’s a poor source for the latest driver.
So the fix isn’t to fight Windows. It’s to tell Windows to leave your GPU alone.
The reliable fix: block driver updates through Group Policy
This is the method I use on every machine I care about. It’s a built-in Windows setting, no third-party tool required. It works on Windows 10 Pro and Windows 11 Pro, and it’s the one that survives reboots and feature updates.
Here’s the path:
- Press Win + R, type gpedit.msc, and hit Enter.
- Navigate to Computer Configuration > Administrative Templates > Windows Components > Windows Update > Manage updates offered from Windows Update.
- Find Do not include drivers with Windows Updates and open it.
- Set it to Enabled, then click OK.
Restart once. From now on, Windows Update will skip driver packages entirely and stick to OS patches. You install GPU drivers yourself, from the vendor, on your schedule.
Two caveats worth knowing. First, this setting blocks all driver updates through Windows Update, not just GPU. That includes chipset, printer, and peripheral drivers. In practice that’s fine, because vendor sites are the better source for those too. Second, if your machine is on Windows Home, gpedit.msc isn’t there. Skip to the registry method below.
Windows Home: the registry equivalent
No Group Policy editor on Home, but the same switch exists in the registry. Open regedit as administrator and navigate to:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate
If the WindowsUpdate key doesn’t exist, create it. Then create a new DWORD (32-bit) Value named ExcludeWUDriversInQualityUpdate and set its value to 1. Reboot. That mirrors the Group Policy toggle.
Back up the registry first if you’ve never edited it. A wrong key here won’t brick Windows, but it can leave Update behaving strangely until you undo it.
If a stale driver is already installed, roll it back first
Blocking future updates doesn’t fix the version Windows already pushed. You need to get off that old build before you block anything.
The clean sequence:
- Open Device Manager (right-click Start, pick it from the menu).
- Expand Display adapters, double-click your GPU.
- Go to the Driver tab.
- If Roll Back Driver is available and greyed-out, click it. That reverts to the previous package Windows saved.
- Restart.
If Roll Back is greyed out (common when the old package was cleaned up), head to your GPU vendor’s site and install the latest driver over the top. NVIDIA’s app, AMD Software: Adrenalin Edition, and Intel Graphics Software all detect your card and offer the current package. This overwrite is usually enough to get you onto the right branch, even if some leftovers remain.
Before installing, check the version in the Driver tab afterward to confirm it changed. Same number means the install didn’t take.
When a standard install isn’t enough: DDU
Sometimes Windows Update leaves debris that a normal reinstall won’t clear. Registry keys, shader cache folders, and orphaned driver packages can linger and cause conflicts. That’s when you reach for Display Driver Uninstaller (DDU), the free Wagnardsoft tool that scrubs every trace of NVIDIA, AMD, and Intel drivers.
Two rules from the DDU documentation that people skip and regret:
- Disconnect the internet before running DDU, or fully block Windows Update. Otherwise Windows can start reinstalling a driver mid-cleanup.
- Use Safe Mode if you want the most reliable result. Normal mode works, but the tool’s own guidance recommends Safe Mode for stability. If you do run it in normal mode, clean, reboot, then clean again.
DDU should not be your routine. It’s for stubborn cases: failed installs, a rollback that won’t stick, or a card that keeps reverting after you’ve already blocked updates. For a driver that just reinstalls itself once, the policy block plus a fresh vendor install is enough.
One nuance for laptop owners: recent DDU builds preserve manufacturer-specific driver extensions on Intel and Qualcomm systems by default. Removing those extensions can stop the GPU from starting and throw a Code 31 error, so leave the default alone unless you know why you’re changing it.
Verifying the block actually worked
Don’t assume. Check the version after the next Patch Tuesday.
Open Device Manager, get into the GPU’s Driver tab, and note the version string. Write it down. A week or two later, after Windows Update has run, check it again. If the number is unchanged, the block is holding. If it moved, something reactivated driver delivery, usually a feature update that reset policy or an OEM update utility running in the background.
For OEM machines, check the manufacturer’s own updater too. Dell, HP, and Lenovo ship their own update tools that can push graphics drivers independently of Windows Update. If you’ve blocked Windows Update but the version still shifts, that’s likely the culprit.
The short version
Windows Update isn’t malicious, it’s just working from a slower catalog. Block driver delivery through Group Policy or the registry, install GPU drivers from the vendor directly, and only reach for DDU when a normal overwrite won’t take. Keep a note of the version you’re running. If it doesn’t move on its own, you’re done.