The Windows Driver Store and Its On-Disk Footprint
An educational reference outlining why the Windows driver store grows over time and which vendor-documented utilities exist for managing its size.
How the Driver Store Accumulates Versions
Each time Windows installs a driver update, the previous version is preserved inside the driver store rather than overwritten. This is by design and is documented in the Windows Hardware Developer documentation driver-installation reference. The accumulation supports the rollback feature exposed in Device Manager.
Over a multi-year Windows installation, the cumulative size of preserved driver packages can range from a few hundred megabytes to several gigabytes. The exact figure varies with the number of devices and the frequency of vendor releases. This page is a general reference and does not advise any particular action on a particular machine.
Vendor-Documented Cleanup Utilities
The vendor documents two first-party utilities that interact with the driver store. The Disk Cleanup utility (cleanmgr.exe) includes a 'Device driver packages' category for removing superseded driver packages. The Plug and Play utility (PnPUtil.exe) provides a command-line interface for enumerating and removing driver packages, documented under the Windows Driver Kit reference.
For full syntax, supported switches, and behavioural notes on either utility, the authoritative source is the Windows Hardware Developer documentation. Third-party tools are not covered here, since this article is focused on the vendor's own documented surface.
Why Direct File Manipulation Is Discouraged
The C:\Windows\System32\DriverStore tree is tracked by Windows using package metadata and content hashes. Direct manipulation of files in that tree falls outside the vendor's documented surface and is not part of the supported management story. The PnPUtil and Disk Cleanup pathways exist precisely so that the package metadata stays consistent.
Removing driver packages also removes the associated rollback options, since rollback restores from the preserved copies in the driver store. This trade-off is described in the Windows Hardware Developer documentation for driver lifecycle management.
Quick Answers
Frequently Asked Questions
The questions readers send us most often on this topic.
By design — the previous version of each driver is preserved so that the documented rollback feature has something to restore from.
The Disk Cleanup utility (cleanmgr.exe) and the Plug and Play utility (PnPUtil.exe). Both are documented in the Windows Hardware Developer reference.
The Windows Hardware Developer documentation is the authoritative reference for the Windows driver store and its associated utilities.
Keep Reading
Related Overviews on PrintSoftDriver
Hand-picked articles that pair well with this one.
More Educational Driver Reading
Our knowledge section collects further plain-English background articles on how device drivers are organised on Windows, macOS, and Linux.