DriverStore Explorer

What the tool exposes

DriverStore Explorer, usually shortened to RAPR, exposes the Windows driver store, the repository under System32 that holds every driver package Windows has ever staged. Device Manager shows you the driver currently bound to a device; it does not show you the six earlier versions of the same package still occupying disk space, nor the packages left behind by hardware you removed years ago. This tool lists all of them with the provider, class, version, date, signed status and size, so the total footprint of stale driver packages becomes a number you can act on rather than a suspicion. It can delete a selected package, force-delete one that is in use, export a package to a folder, and install a package from an .inf file.

How the workflow fits together

The executable is portable and needs no installation; it requests elevation because the driver store lives in a protected location. The list can be sorted and filtered, and the columns that matter most are the size and the publishing status. A package marked as currently in use should not be removed unless you are deliberately replacing it, and the tool marks those so they can be excluded with one command. Old versions of a graphics or chipset driver are the usual target: they can consume hundreds of megabytes each, and removing them frees space and can shorten the list of candidates that Windows Update considers. Exported packages are useful on machines that must stay offline and receive a driver from a known-good source.

Configuration, limits and trade-offs

Export writes the full package including the .inf and the binaries, which is the form that pnputil and the Windows installer expect. Force deletion bypasses the in-use check and will leave a device without a working driver if the package is the one currently bound to it, so a restore point taken beforehand is cheap insurance; System Restore does include the driver store. Two limits are worth knowing before you start deleting. First, the tool manages packages, not the driver files that were installed into System32\drivers by an old-style installer, so some leftovers persist. Second, and more important, the tool removes packages but always removes them for the whole machine, so a package shared by two identical devices disappears for both.

Who should choose something else

Anyone who only needs to roll a single device back one version can use Device Manager's Roll Back Driver button and the driver package properties dialog, which is enough for a one-off fix. Someone chasing a general slowdown or disk-space problem should check the actual sizes first, because stale drivers are rarely the largest consumer and a disk-usage analyser will find the real culprit in a minute. And if the goal is to keep a fleet of machines updated rather than to prune one, a package-management or imaging workflow that reinstalls a known driver set is more predictable than manual deletion, which is difficult to audit after the fact.