The Windows Driver Store: A Reference Description
An educational reference outlining the protected folder used by Windows to track installed driver packages, as documented on the Windows Hardware Developer documentation.
An educational reference outlining the protected folder used by Windows to track installed driver packages, as documented on the Windows Hardware Developer documentation.
The driver store is a protected directory tree on Windows located at C:\Windows\System32\DriverStore\FileRepository. Each installed driver package is placed in its own subfolder, named after the originating INF file plus a content hash, so that successive versions of the same driver do not overwrite each other. This layout is documented in the Windows Hardware Developer documentation driver-installation reference.
Write access to the directory is restricted to the operating system itself. This is part of the vendor's documented design and ensures that the signature on each preserved driver package remains intact after installation.
Each driver update preserves the previous version inside the driver store, so the cumulative size of preserved packages grows with every vendor release that is applied. This behaviour is documented as part of the Windows driver lifecycle on the Windows Hardware Developer documentation and underlies the rollback feature exposed in Device Manager.
Two vendor-documented utilities — PnPUtil.exe and the Disk Cleanup utility (cleanmgr.exe) — provide the supported pathways for removing superseded driver packages. Direct file manipulation in the directory tree falls outside the vendor's documented surface and is not part of the supported management story.
The PnPUtil command 'pnputil /enum-drivers' is the documented mechanism for listing third-party driver packages currently registered in the driver store. The output includes the publisher, the install date, and the signature status of each package, as described in the Windows Driver Kit reference on the Windows Hardware Developer documentation.
Built-in Windows drivers are not enumerated by this command, because they are managed as part of Windows itself rather than as third-party packages. This article is a general background reference and does not advise any particular action on a particular machine.
The questions readers send us most often on this topic.
The vendor documents two utilities for this purpose: the Disk Cleanup utility (cleanmgr.exe) and the Plug and Play utility (PnPUtil.exe).
From a few hundred megabytes to several gigabytes, depending on the device count and the frequency of vendor releases applied over the lifetime of the installation.
The Windows Hardware Developer documentation is the authoritative reference for the driver store and the associated PnPUtil and Disk Cleanup utilities.
Hand-picked articles that pair well with this one.
Our knowledge section collects further plain-English background articles on how device drivers are organised on Windows, macOS, and Linux.