Driver updates are supposed to make your PC better. When they don’t—when your audio vanishes, Bluetooth flakes out, your GPU stutters, or you hit a blue screen—it’s maddening. The good news: you can almost always get back to a stable state with a clean rollback, and you can keep Windows from pushing the same bad driver again. Here’s a practical, no-drama guide to fixing it fast.
Bad drivers happen for a few common reasons: a vendor ships a buggy build, the update targets similar but not identical hardware, or it clashes with a specific app, antivirus, or overclocking tool. If the timing lines up—things were fine yesterday, you installed updates, now they’re broken—that’s your signal.
Typical symptoms: Crashes or BSODs, devices vanishing from Device Manager, stuttering and freezes, high CPU/DPC latency, or specific features failing (e.g., no mic input).
Good rollback candidates: Display/GPU, audio, Bluetooth, Wi‑Fi, storage, chipset, touchpads, and printer drivers.
Quick rule: If stability matters more than tiny performance gains, roll back immediately; you can test the newer driver later on your terms.
A few minutes of prep can save hours of frustration if you need a second attempt.
Create a restore point: Open Start, search “Create a restore point” > System Protection tab > your system drive > Create. Name it something obvious like “Pre-rollback”.
Note the device name and driver version: Win + X > Device Manager > right-click the suspect device > Properties > Driver tab. Screenshot or write down the Driver Provider, Date, and Version.
Map timing to symptoms: Check Settings > Windows Update > Update history > Driver updates to confirm what changed and when.
Download the last known-good driver: Grab the stable version from your device/OEM site (NVIDIA, AMD, Intel, Realtek, your laptop maker). Keep it handy in case Device Manager can’t roll back automatically.
Tip: If the system is unstable, disconnect from the internet before you start. That prevents Windows from immediately re-pushing the same driver while you’re mid-fix.
This is the fastest, cleanest route when Windows kept the previous driver package.
Open Device Manager: Press Win + X > Device Manager.
Find the failing device: Expand the relevant category (Display adapters, Sound, video and game controllers, Network adapters, Bluetooth, etc.) and double-click the device.
Open driver details: Go to the Driver tab to review Provider, Date, and Version.
Use Roll Back Driver: Click Roll Back Driver. Pick a reason (e.g., “Previous version performed better”). Let Windows revert and reboot if prompted.
Verify functionality: After restart, re-check the device’s Driver tab to confirm the earlier version. Test the app or workflow that was failing.
What if Roll Back Driver is greyed out?
No previous driver stored: Use Method 3 to manually pick an older driver or remove the bad one and install the known-good package.
Windows keeps reinstalling the same driver: Roll back, then immediately apply “Stop Windows from reinstalling the faulty driver” below before reconnecting to the internet.
If Device Manager can’t roll back or the issue is broader (multiple drivers or system instability), System Restore can return your whole system to a pre-update state without touching your personal files.
Launch System Restore: Press Win + R, type rstrui.exe, and press Enter.
Choose a restore point: Pick the point created before the driver update (Windows may have created one automatically). Click Scan for affected programs to see what will change.
Restore and reboot: Proceed with restore. The PC restarts and rolls back system files, drivers, and registry changes.
Confirm and test: After login, verify driver versions in Device Manager and test the problematic device.
If System Restore isn’t enabled:
Enable protection for next time: Open “Create a restore point” > select system drive > Configure > Turn on system protection > set reasonable Max Usage (5–10%). Create a manual restore point before major changes.
Open advanced startup: Hold Shift while clicking Restart from the power icon on the sign-in screen or Start menu.
Navigate to Safe Mode: Troubleshoot > Advanced options > Startup Settings > Restart, then press 4 (Enable Safe Mode) or 5 (with Networking).
Roll back in Safe Mode: Use Device Manager (Method 1) or the manual methods below. Safe Mode loads minimal drivers, lowering the risk of crashes.
When automatic rollback isn’t available, you can switch to a previously installed driver, or remove the bad package and install a known-good one.
Open the device’s driver dialog: Device Manager > device > Properties > Driver tab > Update Driver.
Choose local driver: Browse my computer for drivers > Let me pick from a list of available drivers on my computer.
Select the older version: Pick a prior version by date/provider. Click Next to install, then reboot and test.
This is precise and helpful when a vendor installer keeps “updating” back to the bad build.
Open an elevated terminal: Start > type “cmd” > Run as administrator.
List installed driver packages: Run:
pnputil /enum-drivers
Identify the target by Provider, Class, and Version, and note the Published Name (e.g., oem42.inf).
3. Uninstall the bad driver package: Run:
pnputil /delete-driver oem42.inf /uninstall
If the driver is in use, you can add /force but prefer a reboot then retry first.
4. Install a known-good driver:
If you have an older INF, install it:
pnputil /add-driver “C:\Drivers\GoodVersion\driver.inf” /install
Reboot and verify in Device Manager.
Notes:
GPU drivers: If problems persist, consider running the vendor’s clean install option. For stubborn graphics issues, a clean removal with a reputable tool like Display Driver Uninstaller (DDU) in Safe Mode can help—use cautiously and only from the official source.
Storage and chipset drivers: Be deliberate; removing the wrong package can affect boot or performance. Ensure you have a restore point.
Windows 11 Pro or higher (Group Policy):
Open Group Policy Editor: Win + R > .
Navigate to policy: Computer Configuration > Administrative Templates > Windows Components > Windows Update.
Enable the setting: Double-click “Do not include drivers with Windows Updates” > Enabled > OK.
Apply immediately: Run gpupdate /force in an elevated Command Prompt, or reboot.
Windows 11 Home (Registry):
Open Registry Editor: Win + R > regedit.
Create the policy key: Goto: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate
If WindowsUpdate doesn’t exist, create it.ExcludeWUDriversInQualityUpdate (DWORD, 32-bit) and set to 1.Caution: Be careful editing the registry. Export a backup of the key first (File > Export).
When you don’t want to block all drivers—just the bad one—hide it.
Use Microsoft’s “Show or hide updates” troubleshooter: Download the troubleshooter, run it, choose Hide updates, and select the offending driver. This prevents Windows Update from offering that specific package until you unhide it later.
Optional updates view: Settings > Windows Update > Advanced options > Optional updates > Driver updates. If the bad driver appears here, don’t select it. Hiding via the troubleshooter is more durable.
For devices that keep pulling the wrong driver, you can prevent installation by ID.
Find the hardware ID: Device Manager > device > Properties > Details tab > Property drop-down > Hardware Ids. Copy the most specific value (top entry).
Pro editions via Group Policy:
Open Group Policy Editor: .
Navigate: Computer Configuration > Administrative Templates > System > Device Installation > Device Installation Restrictions.
Enable restriction: “Prevent installation of devices that match any of these device IDs” > Enabled > Show > paste the hardware ID(s) > OK.
Reboot: Restart to enforce the block.
Use this tactically; you can disable the policy after you’ve installed the correct driver.
Small habits make driver mishaps rare—and easy to undo when they happen.
Prioritize OEM sources: Your laptop or motherboard vendor often tailors drivers for your exact hardware. Install those over generic ones unless you truly need a newer feature or fix.
Stagger big changes: Don’t update GPU, audio, and chipset drivers all at once. Change one, test for a day, then proceed. That isolates issues instantly.
Keep System Restore on: It’s lightweight insurance. Allocate 5–10% space for your system drive and create a restore point before driver or BIOS updates.
Snapshot versions before updating: Screenshot Device Manager’s Driver tab. If something breaks, you’ll know exactly what version to roll back to.
Disable automatic driver updates temporarily: When troubleshooting, exclude drivers from Windows Update and re-enable once you’ve stabilized on a good version.
Use clean installs for graphics drivers: NVIDIA and AMD installers both offer clean install modes that reset settings and replace components safely.
Watch optional updates: Check Settings > Windows Update > Advanced options > Optional updates periodically, but don’t install driver updates just because they’re listed. Only apply updates that solve a real problem you have.
Have offline installers ready: Save the last known-good driver installers locally. If a bad update kills your network, you won’t be stuck.
If you want the bare minimum path to stable, here’s the sequence that works most often:
Disconnect from the internet: Stop Windows Update from racing you.
Device Manager rollback: Properties > Driver > Roll Back Driver > reboot.
Block the reinstallation: Enable “Do not include drivers with Windows Updates” or hide the specific update.
Manual reversion if needed: “Let me pick from a list” to choose an older local driver, or use pnputil to remove the bad package and install a known-good INF.
Safe Mode or System Restore if unstable: Boot Safe Mode to perform the rollback, or restore to a point before the update.
When you’ve got the system calm again, reconnect and selectively update on your schedule.
For a step-by-step guide on manually installing updates, check out how to install Windows updates manually.
Yes. The easiest method is through Device Manager. Open the affected device’s Properties > Driver tab and select Roll Back Driver. This option is available when Windows has retained the previous driver.
A greyed-out button usually means Windows doesn’t have the previous driver package available. In that case, use Let me pick from a list of available drivers on my computer, install a known-good driver manually, or remove the faulty package with pnputil and install an older driver.
Compare the timing of the problem with your recent updates. Go to Settings > Windows Update > Update history > Driver updates and check what was installed. You can also open Device Manager > Properties > Driver to compare the provider, date, and version.
No. A normal Device Manager driver rollback does not delete your personal files. System Restore also generally leaves personal files untouched, although it can remove applications, drivers, and system changes made after the selected restore point.
Yes. Windows 11 Pro and higher editions can use the Do not include drivers with Windows Updates Group Policy setting. You can also hide a specific problematic driver update or, for persistent hardware-specific problems, use a hardware-ID installation restriction.
If Windows keeps reinstalling the faulty driver, temporarily disconnecting from the internet can help. It prevents Windows Update from immediately downloading another driver while you perform the rollback and stabilize the system.
Try Safe Mode. Hold Shift while selecting Restart, then go to Troubleshoot > Advanced options > Startup Settings > Restart and choose Safe Mode. Once Windows starts, use Device Manager to roll back or replace the problematic driver.
Not necessarily. Device Manager rollback is preferable when a single driver caused the problem because it makes a targeted change. System Restore is more useful when several drivers or system components became unstable after an update and you have a suitable restore point.
Yes. In Device Manager, open the affected device’s Properties > Driver > Update Driver, select Browse my computer for drivers, then Let me pick from a list of available drivers on my computer. You can also install a known-good INF package with pnputil.
It can be, but use caution. Confirm the Published Name, provider, class, and version before deleting a package. Be especially careful with storage, chipset, and other drivers that can affect system stability or boot. Creating a restore point first is recommended.
For persistent GPU problems, Display Driver Uninstaller (DDU) can be useful for a clean graphics-driver removal, typically from Safe Mode. It is more aggressive than a normal rollback, so it should generally be reserved for situations where the standard rollback or clean-install options don’t resolve the issue.
Create a restore point before major driver or BIOS updates, record your current driver versions, update one major component at a time, and keep known-good installers offline. For laptops and prebuilt PCs, prefer drivers supplied by the device manufacturer unless you specifically need a newer vendor release.
No. Optional driver updates don’t necessarily need to be installed simply because they’re available. If your hardware is working correctly, there may be little reason to replace a stable driver. Install an optional driver when it addresses a known issue, adds a feature you need, or is recommended for your specific hardware.
For most cases, use this order: disconnect from the internet → roll back through Device Manager → reboot and test → prevent the faulty driver from returning → manually install a known-good version if necessary. If Windows remains unstable, use Safe Mode or System Restore.