When a new driver makes things worse
Sometimes a driver update adds no useful change for your setup and introduces a regression: a device stops responding, performance drops, or crashes begin. When Windows still retains the prior package, rolling back can return the device to that version and is a useful early test of whether the update caused the problem.
Confirm the driver is the cause
Before rolling back, make sure the timing lines up. Ask yourself:
- Did the problem start immediately after a driver update?
- Does the affected device match the driver you changed?
- Has anything else changed at the same time, such as a Windows update or new software?
If a driver update and the onset of the problem coincide, a rollback is a sound first move. If not, investigate other causes first.
Roll back through Device Manager
This is the primary method:
- Press Windows + X and open Device Manager.
- Expand the category and find the affected device.
- Right-click it and choose Properties.
- Open the Driver tab.
- Click Roll Back Driver.
- Choose a reason if prompted, confirm, and reboot.
Windows attempts to reinstall the retained previous version. Confirm the version and test the device afterward; rollback does not guarantee earlier behavior if firmware, settings, hardware, or another update also changed.
If the Roll Back button is grayed out
The button only works when Windows has a previous version stored. It is unavailable when:
- This is the first driver ever installed for the device.
- A cleanup removed the older package.
- Enough time or updates have passed that the prior version was cleared.
When rollback is not available, you have other paths.
Reinstall a known-good version manually
If you cannot roll back, download the specific earlier version from the manufacturer's official support site, if they still offer it, and install it over the current one. Many vendors keep an archive of previous releases. This effectively performs a manual rollback using a trusted source. Choose the exact version you know worked.
Use a restore point
If you created a restore point before the update, as recommended in our restore point guide, use it:
- Search for "Create a restore point" and open System Protection.
- Click System Restore.
- Pick a point dated before the driver change.
- Confirm and let Windows restart.
This reverts the driver along with any other system changes made since the snapshot.
When the device fails to load at all
If the bad driver causes a black screen, a boot loop, or a device you cannot even reach normally, use Safe Mode:
- Enter the Windows Recovery Environment by interrupting startup a few times.
- Go to Troubleshoot, Advanced options, Startup Settings, and restart.
- Choose Safe Mode.
- In Safe Mode, open Device Manager and roll back or uninstall the problem driver.
- Reboot normally.
Safe Mode loads minimal drivers, so a misbehaving one will not block you.
Prevent a repeat
Once you are stable again:
- Note which driver version caused the problem so you do not reinstall it.
- If Windows Update keeps pushing the bad version, pause updates temporarily while you wait for a corrected release.
- Stay on the known-good version until the manufacturer publishes a fix.
Know when to stop rolling forward
If several recent drivers for a device cause issues on your particular configuration but an older one behaves reliably, there may be no reason to update immediately unless a security advisory, application requirement, or publisher guidance applies. Document the version that works for your setup, and let a concrete need rather than novelty drive your decision.
