You installed windows-the-clean-way/”>a new GPU driver, rebooted, and now the screen flickers, a game crashes on launch, or Device Manager shows a yellow exclamation mark next to your adapter. The fix is usually the same one most people forget exists: put the old driver back. Windows keeps the previous version around for exactly this reason, and reverting is a two-minute job if you know where the button is.
Here is the safe order for rolling back a driver, what to do when the rollback option is greyed out, and how to keep a bad update from reinstalling itself behind your back.
Confirm the driver is actually the problem
It is easy to blame the driver for everything that goes wrong after a reboot. Before you touch anything, rule out the obvious. Did the problem start right after the update? Did Windows install something else in the same session? Pull up Windows Event Viewer and look for error messages tied to the device and timestamp. If the errors line up with the update, you have your culprit.
In Device Manager, a device with a real driver problem usually shows a yellow exclamation mark or a red cross over its icon. That is Windows telling you the device is not working properly. A graphics card that suddenly throws error Code 43 after an update is a textbook case. If your device looks clean in Device Manager and the issue is only in one application, the driver may not be the cause at all.
Roll back through Device Manager
This is the built-in method and it should be your first stop. Windows keeps the previous driver version on disk, so the rollback pulls from local storage. No internet needed.
- Press Windows + X and choose Device Manager. You can also press Windows + R, type
devmgmt.msc, and hit Enter. - Expand the category for the affected device. Graphics cards sit under Display adapters. Printers under Printers. Network gear under Network adapters.
- Right-click the specific device and choose Properties.
- Open the Driver tab.
- Click Roll Back Driver.
- Pick a reason when Windows asks, then confirm with Yes.
- Restart when prompted.
Save your open work before that restart. Windows needs to reinitialize the device with the older driver, and a clean reboot avoids a half-loaded state.
One thing to understand: rolling back only takes you to the version just before the current one. Windows keeps the previous driver, not the whole history. So if you have updated three times in a row, the rollback lands you on update number two, not the original factory driver. That is usually enough, but it is worth knowing before you click.
After the restart, go back into Device Manager, open the Driver tab again, and check the driver version number. It should read the older version. Then actually use the device. Launch the game, print a test page, open the app that was crashing. A version number alone does not prove the fix worked.
When the Roll Back Driver button is greyed out
A disabled rollback button means one thing: Windows does not have a previous version stored for that device. This happens on a fresh Windows install, after a clean driver install that wiped the old package, or when Windows Update replaced the driver without keeping a copy.
You still have options.
- Install the older driver manually. Go to the manufacturer’s site, find the previous release, download the installer, and run it. This is the most reliable path when the rollback button is dead.
- Use the built-in driver list. In Device Manager, right-click the device, choose Update driver, then Browse my computer for drivers, then Let me pick from a list of available drivers on my computer. If Windows still has an older INF cached, it shows up here.
- Use System Restore. Press Windows + R, type
rstrui, and hit Enter. Pick a restore point created before the update. This rolls back far more than one driver, so use it only when the targeted approach fails and you have a restore point to work with.
System Restore is the blunt instrument. It reverts drivers, registry changes, and installed software to an earlier state. If you installed something useful between the restore point and now, you lose it. Prefer the manual driver install whenever it applies.
Stop Windows from reinstalling the bad driver
Here is the part that trips people up. You roll back, everything works, and two days later Windows Update quietly pushes the same broken driver back in. You are right back where you started, wondering if you imagined the fix.
Prevention matters here. Configure Windows Update to notify you before installing driver updates rather than letting it act on its own. On Windows 10 and 11 the settings are buried, but the toggle exists under advanced update options. If you have just recovered a working system, treat that as the moment to tighten the setting.
The other habit worth building: create a restore point before any driver update. One click, and the next bad update becomes a ten-second problem instead of an evening of troubleshooting. For GPU drivers in particular, remember the version number you just rolled back to. Write it down somewhere. If the manufacturer’s latest release keeps breaking your setup, you will want to know which version to stay on.
What to do if the rollback itself goes wrong
Rolling back is low risk, but a reboot during the process, or an SSD hiccup, can leave the device in a strange state. If the rollback fails or the device drops off entirely, boot into Safe Mode. From there, Device Manager still works, and you can remove the device and its driver completely, then reinstall the version you want from a download you already have on disk.
For stubborn GPU issues where the standard rollback will not take, a full driver removal tool like DDU (Display Driver Uninstaller) does a deeper cleanup than Device Manager. Run it in Safe Mode, then install the older driver package fresh. This is heavier than a rollback and it is the right call when a normal rollback fails, not before.
The short version
Roll back through Device Manager when the button is available. Install the older driver manually when it is greyed out. Reach for System Restore or a deep uninstall only when the targeted route fails. And whatever you do, make sure Windows Update cannot silently reinstall the driver that broke your machine in the first place. That last step is what makes the fix stick.