Everything worked yesterday. Then Windows Update installed a new driver overnight, and now your WiFi drops, your audio crackles, or your screen flickers. The driver update giveth, and the driver update taketh away — and Windows 11 gives you a built-in undo button for exactly this situation. Rolling back a driver takes about two minutes when the option is available. This guide covers all three rollback paths: the one-click Device Manager rollback, System Restore for when the button is grayed out, and manual reinstall of the older driver for stubborn cases. Just as important, we’ll show you how to stop Windows from ‘helpfully’ reinstalling the bad driver tomorrow. If you want to compare versions before deciding, our driver version check guide shows how to read what’s installed. Rollback is also the correct response when a manual driver update you installed yourself goes wrong — same buttons, same process. And if Windows keeps pushing driver updates you don’t want, our guide to disabling automatic driver updates is the permanent fix.
Why this happens
- Windows Update installed a buggy driver. The classic trigger — an automatic driver update breaks previously working hardware.
- Manual update to an unstable release. You installed the newest driver yourself and it’s worse than what you had.
- OEM driver replaced by generic. Windows swaps your laptop maker’s tuned driver for a Microsoft generic that lacks features.
- Driver conflict after major Windows upgrade. Feature updates reshuffle drivers and break previously stable combinations.
- Partial or interrupted update. The new driver half-installed, leaving the device in a broken intermediate state.
- Rollback button grayed out. No previous driver stored — happens after clean installs or long-ago replacements.
- Windows re-installs the bad driver. You roll back, and Update pushes the same bad driver again overnight.
- Multiple devices affected. A chipset or platform update breaks several devices at once, needing coordinated rollback.
How to fix it
Work through these in order — diagnose first, then act.
Fix 1: Use the Device Manager rollback button
The one-click undo — works when Windows kept the previous driver, which it usually does for update-initiated changes.
- Open Device Manager (Windows + X) and find the misbehaving device.
- Right-click → Properties → Driver tab.
- Click ‘Roll Back Driver.’ If it’s grayed out, skip to Fix 2.
- Select a reason (e.g., ‘Previous driver worked better’) and click Yes.
- Restart the laptop and verify the device works — check the Driver tab to confirm the older version/date is active.
Fix 2: Restore via a System Restore point
When the rollback button is grayed out, a restore point from before the update achieves the same result system-wide.
- Search ‘Create a restore point’ → System Protection tab → System Restore.
- Choose ‘Choose a different restore point’ to see the full list with dates.
- Pick a restore point dated before the driver problem started.
- Click ‘Scan for affected programs’ to preview what else will revert — drivers and system files only, not documents.
- Confirm and let it run; the laptop will reboot. Verify the device works afterward.
Fix 3: Manually install the older driver
The most reliable method when neither rollback nor restore is available — you supply the known-good driver yourself.
- Find the previous working version: check the driver date in Device Manager, or recall when the device last worked.
- Download that older driver from your laptop maker’s support site (their driver archives list versions and dates).
- In Device Manager, right-click the device → Uninstall device, checking ‘Attempt to remove the driver for this device.’
- Restart, then install the downloaded older driver package.
- Verify the version in the Driver tab matches what you intended — then immediately do Fix 4 so Windows doesn’t ‘fix’ it.
Fix 4: Block Windows from reinstalling the bad driver
Rollback is pointless if Update re-pushes the same driver overnight. This is the step everyone forgets.
- Download Microsoft’s ‘Show or hide updates’ troubleshooter (wushowhide) and use it to hide the specific driver update.
- Alternatively, open gpedit.msc → Computer Configuration → Administrative Templates → Windows Components → Windows Update → Manage updates offered from Windows Update → enable ‘Do not include drivers with Windows Updates.’
- On Windows 11 Home (no gpedit), set the registry: HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate → DWORD ExcludeWUDriversInQualityUpdate = 1.
- Verify over the next few days that the driver version stays put.
- Revisit this policy when you actually want a driver update — blocked means blocked.
Fix 5: Roll back graphics drivers with DDU when needed
GPU drivers sometimes resist normal rollback; Display Driver Uninstaller gives you a clean slate to install the older version.
- Download DDU and the older GPU driver version you want (NVIDIA/AMD/Intel archives).
- Disconnect from the internet so Windows can’t interfere mid-process.
- Boot into Safe Mode and run DDU → ‘Clean and restart.’
- Install the older driver package, choosing Custom/Clean install if offered.
- Reconnect to the internet and confirm stability under load before re-enabling automatic updates.
Fix 6: Handle multi-device breakage after feature updates
Major Windows upgrades can break several drivers at once — prioritize and work systematically.
- List every broken device in Device Manager (yellow icons) before changing anything.
- Start with the most critical: network (to stay online), then display, then audio.
- Roll back each via Device Manager where possible; use manual reinstall for grayed-out ones.
- Consider rolling back the entire feature update: Settings → System → Recovery → ‘Go back’ (available for 10 days after the upgrade).
- Document which driver versions work — future you will thank present you. Microsoft’s Windows support pages document the recovery options if you need a refresher.
Fix 7: Verify stability and document the working setup
Rollback isn’t done when the device works — it’s done when it stays working.
- Use the laptop normally for a day with the rolled-back driver, exercising the previously broken function.
- Confirm Windows Update hasn’t re-offered the bad driver (check Update history).
- Write down the working driver version and date from Device Manager’s Driver tab.
- Create a fresh System Restore point labeled with the working configuration.
- If the device breaks again later, you’ll know exactly which version to return to.
Closing
Driver rollback is Windows’ built-in apology mechanism — use it promptly when an update breaks things, then block the bad update so the apology sticks. Two minutes of rollback plus five minutes of prevention beats hours of fighting a driver that never worked.
