You roll back a bad GPU driver, reboot, and ten minutes later Windows Update quietly puts the busted one back. If that sounds familiar, you are fighting two separate mechanisms: the rollback you did in Device Manager, and the update pipeline that keeps re-offering the package. You have to address both. Here is the sequence I use on test machines, roughly in order of how much they interfere with normal use.
First, understand why it comes back
Device Manager’s “Roll Back Driver” button only restores the previous driver files on that device. It does not tell Windows Update to stop serving the newer package. On top of that, the newer package is often sitting in the local driver store, and Windows can re-stage it during the next update scan without downloading anything. So even offline, the reinstall can happen on the next boot.
That is the core of the problem. A rollback is a local file swap. An update is a policy question. You need to answer the policy question.
Pause updates while you work
Before touching anything else, stop the pipeline from firing mid-fix. Open Settings > Windows Update > Advanced options and pause updates. On Windows 11 this buys you up to five weeks depending on the edition and build. That is enough breathing room to do the rest cleanly without the package sneaking back in between steps.
This is not a solution, it is a hold. Do not skip it.
Remove the stale package from the driver store
Rolling back usually leaves the newer .inf files in the store. Windows sees them, matches them to your hardware ID, and can redeploy them on the next scan. Clear them out.
- Open Device Manager, find the device, right-click, Properties, Driver tab, and confirm the driver version you are actually running.
- Open an elevated Command Prompt or PowerShell and run
pnputil /enum-drivers. Look for the OEM number matching the newer package (the version you rolled back from). - Delete that package with
pnputil /delete-driver oemNN.inf /uninstall, substituting the actual number. If it refuses, add/force.
Be careful here. If you delete the wrong OEM package you can strip a working driver out from under a device mid-session. Note the OEM number before you type anything, and if you are not sure, take a System Restore point first.
Hide the specific update with the Microsoft troubleshooter
The cleanest way to block a single driver package without disarming updates for everything is the “Show or hide updates” troubleshooter, sometimes labelled wushowhide. Microsoft distributed it as part of the Windows Update troubleshooting tooling and it still works on current builds. Run it, choose “Hide updates,” tick the driver you do not want, and confirm. The package drops off the offered list until you unhide it.
It is clunky, the UI is dated, and Microsoft has made it harder to find over the years. It still does the job, and it does it without touching Group Policy. That is the trade I will take for a single stubborn driver.
Stop Windows Update from pushing drivers at all
If you want a broader hammer, Windows has a policy that tells it not to include drivers in update scans. This is what most people mean when they want to “stop automatic driver updates.”
- Press Win+R, type
gpedit.msc(Pro and Enterprise only). - In Group Policy, drill down through Computer Configuration, then Administrative Templates, then Windows Components, then Windows Update, then Manage updates offered from Windows Update.
- Enable “Do not include drivers with Windows Updates.”
On Home editions, gpedit.msc is not present by default. You can set the equivalent value under HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate if you know what you are doing, or use a third-party privacy/update manager. The catch is obvious: you also stop getting legitimate driver updates, including security-relevant ones. For a single bad GPU driver, wushowhide is the better tool. For a fleet of machines with a known-bad driver family, the policy is worth the trade-off.
Check the Optional updates page
Microsoft has been routing more driver packages through Settings > Windows Update > Advanced options > Optional updates. If your driver came in that way, you can simply deselect it there and it will not reinstall on its own. Worth checking before you do anything more drastic, because on some builds the package lives only in this list.
What usually does not work
Rolling back in Device Manager without clearing the driver store: the newer package stays staged and returns.
Uninstalling the device and scanning for hardware changes: Windows finds the same driver from the store or downloads it again.
Disabling the device: not a real fix, and it breaks whatever depends on that driver.
Editing registry keys you found on a forum post from 2014: half of them are for Windows 7 and do nothing on Windows 11, and a few can break the update service entirely if you get them wrong.
System Restore: it will roll back the whole system, including unrelated updates, and if the driver package is still in the store it can return anyway.
The sequence that actually holds
In practice, this order works with the fewest reboots and the least collateral:
Pause updates. Take a restore point. Confirm the current driver version in Device Manager. Run wushowhide and hide the offending package. Then clear the matching OEM package from the store with pnputil. Reboot. Confirm the version is still the one you want, and resume updates only after you are confident the package is not going to reappear. If it does, apply the “do not include drivers” policy as a fallback.
One caveat I will not paper over: hiding updates and editing policy are both supported, but Windows Feature Updates can reset some of these settings, and a future update may reintroduce drivers under a different package ID. Check the driver version again after any major Windows 11 build upgrade. It is annoying. It is also the reality of how Windows Update works, and I have not found a way around it that does not involve turning off updates entirely, which is its own bad trade.
The core lesson is that a rollback is not a decision, it is a snapshot. The decision is hiding the package or blocking the channel. Do one of those, and the driver will stay where you put it.
