guide · static export
PC

Roll Back a Bad Driver with PnPUtil

Name the package that broke the machine, remove it properly, install the previous version and stop Windows from offering it again.

by@guidox updated:10/31/26 time:30 min level:Intermediate tested on:Windows 11 24H2 works on:Windows 10, Windows 11 tools:Command Prompt as administrator, Device Manager
TL;DR

Use **Device Manager > Driver > Roll Back Driver** first, then remove the package with `pnputil /delete-driver oemXX.inf /uninstall` and install the known-good version with `/add-driver /install`.

Before you start

Requirements

  • Admin rights
  • The previous driver package
  • Thirty minutes
Step by step

Instructions

01

Confirm the driver is the suspect

Sort the signed drivers by date and compare with the day the problems started. The newest package on the list is the first one to look at, not the only one.

Get-CimInstance Win32_PnPSignedDriver | Sort-Object DriverDate -Descending | Select-Object -First 10 DeviceName,DriverVersion,DriverDate
02

Try the built-in rollback first

Device Manager keeps the previous package for that device and restores it in one click. It is the least invasive option because nothing gets deleted.

Device Manager > device > Properties > Driver > Roll Back Driver
⚠ warningThe button only exists while the older package is still on disk. A disk cleanup or a later update removes it and the button greys out.
03

Find the package name when there is no rollback

pnputil lists every third-party package with its oem number, provider and version. That oem file name is what every later command needs.

pnputil /enum-drivers
tipMatch the provider and the version, not the device name. One vendor often ships several packages.
04

Remove the package

Deleting the driver package removes the files and the registry entries and reverts the device to the inbox driver that ships with Windows.

pnputil /delete-driver oem42.inf /uninstall /force
⚠ warningForce removes a package that is still in use. The device may lose its function until the reboot finishes.
05

Install the version that worked

Adding a package from a folder writes it into the driver store and installs it on the matching device in the same step.

pnputil /add-driver D:\driver\setup.inf /install
06

Stop the same build from returning

Windows Update offers drivers again after a while. An exclusion keeps driver deliveries out of quality updates while security patches keep arriving.

reg add HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate /v ExcludeWUDriversInQualityUpdate /t REG_DWORD /d 1 /f
tipThis blocks automatic driver delivery only. A manual check for updates still offers the package if it is important for security.
Troubleshooting

Common issues

Roll Back Driver is greyed out

No previous package remains. Remove the current one with pnputil and install an older build from the vendor.

delete-driver fails with access denied

The console is not elevated, or the device is running. Reboot and repeat the command.

The device disappeared after removal

Expected until the inbox driver binds. Scan for hardware changes in Device Manager, then reboot.

The bad driver comes back after a week

Windows Update offered it again. Set the exclusion or hide that particular update.

FAQ

Frequently asked

Does deleting a package break the device?

It falls back to the generic driver that ships with Windows. Video and audio keep working with fewer features until you install another package.

Where do these oem files live?

In C:\Windows\INF as oemNN.inf, paired with a matching .pnf file that you never edit by hand.

How to undo this

Reinstall the removed package with pnputil /add-driver, or let Windows Update offer it again. The exclusion value is undone by setting it back to 0 or deleting it.

Changelog · 1 entry
  1. 2026-10-31
    First version
Interactive version: checklist, feedback, related guides →

Free · no account needed · tracks your progress