When troubleshooting hardware malfunctions, graphics instability, or peripheral connectivity issues in Windows 11, the graphical Device Manager is the standard diagnostic interface. However, Device Manager does not expose the underlying Windows Driver Store (located at C:\Windows\System32\DriverStore\FileRepository), where redundant, obsolete, and corrupted driver packages accumulate over time, consuming gigabytes of system disk space and occasionally triggering driver conflict loops.
Microsoft provides the native pnputil.exe (Plug and Play Utility) command-line tool to manage the Driver Store directly. Built into all editions of Windows 11, pnputil enables system administrators and power users to enumerate installed third-party drivers, export critical drivers before clean OS reinstalls, and forcefully delete malfunctioning packages. This guide covers essential commands, syntax structures, and best practices.
Launching Elevated Terminal in Windows 11
Because managing driver packages alters low-level system hardware configurations, pnputil requires administrator privileges:
- Right-click the Start button on the taskbar (or press
Win + X). - Select Terminal (Admin).
- Ensure your console is running elevated as Administrator.
Core Driver Management Operations
1. Enumerating Installed Third-Party Drivers
To list all third-party (OEM) driver packages currently registered in the Driver Store:
pnputil /enum-drivers
Each driver entry displays its Published Name (e.g. oem24.inf), Original File Name, Driver Class (e.g. Display, Net, System), Driver Date, and Version.
2. Filtering Drivers by Class
To view only network adapter drivers or display drivers:
pnputil /enum-drivers /class Net
pnputil /enum-drivers /class Display
3. Exporting All Third-Party Drivers for Backup
Before reinstalling Windows or migrating to a new storage drive, export every installed OEM driver into an offline backup directory:
# Create destination directory
mkdir C:\DriverBackup
# Export all drivers
pnputil /export-driver * C:\DriverBackup
This command extracts the complete INF, CAT, and SYS binaries into individual subfolders, allowing offline driver reinjection during future deployments.
4. Deleting Obsolete or Corrupted Driver Packages
When an updated graphics or chipset driver causes blue-screen crashes, delete the problematic package from the Driver Store using its published OEM identifier:
# Normal safe deletion
pnputil /delete-driver oem24.inf
# Force deletion if the package is flagged as active
pnputil /delete-driver oem24.inf /force /uninstall
The /uninstall flag instructs Windows to detach the driver from any connected hardware endpoints prior to package deletion.
Command Reference Table
| Command | Function | Recommended Context |
|---|---|---|
pnputil /enum-drivers |
Lists all OEM INF packages | Auditing hardware versions |
pnputil /add-driver *.inf /install |
Stages and installs driver batch | Automated fleet provisioning |
pnputil /delete-driver oemX.inf /force |
Purges driver from repository | Fixing rollback loops and BSODs |
pnputil /export-driver * <Path> |
Backs up all OEM drivers to disk | Disaster recovery preparation |
pnputil /scan-devices |
Scans system for PnP changes | Hot-plug peripheral detection |