FileCobra Logo FileCobra
DriverStore Explorer — Clean Old Driver Packages from the Windows DriverStore for Windows PC Icon
Open Source v1.0.75 ✓ Checksum Published

Download DriverStore Explorer — Clean Old Driver Packages from the Windows DriverStore for Windows PC v1.0.75 for Windows PC

Open-source GUI (Rapr) that lists every driver package stored in the Windows DriverStore, shows size, date and provider, finds duplicates and old versions...

Technical Specifications & System Requirements

Developer lostindark (Teddy Zhang)
Platform & OS Windows 7 / 8 / 10 / 11
Package Size 0.8 MB
Architecture x64
Package Format ZIP Archive
Security Verification SHA-256 checksum published
SHA-256 Cryptographic Checksum Computed from the file we serve
a3c4a37a27b07981187f5932db48ddc4299eebe5a102a90f95d04aeb8afc2047
$ Get-FileHash .\driverstore-explorer-pc.exe -Algorithm SHA256

Software notes

The Bottom Line: DriverStore Explorer solves a problem Windows hides from you. The DriverStore grows silently every time a graphics, printer or network driver updates, because Windows keeps the previous packages in case a device returns or a rollback is needed. On a machine several years old, that folder can hold many gigabytes of versions nothing will ever use again, and Explorer gives you no safe way to see inside it. This tool turns an opaque system folder into a readable list where age, size and duplication are obvious. Used carelessly, it can also remove a driver you still need, which is why the honest advice is to delete old versions only, keep the newest package for every device, and export the driver list first. The interface is a dense grid that makes no attempt to teach, and deleting in-use packages requires the force option precisely because Windows resists it. None of that is a flaw in the tool so much as the nature of the job. For technicians cleaning a fleet image or an owner wondering where twenty gigabytes went, it is the standard open-source answer, and far safer than deleting DriverStore files by hand.

Features

  • Every driver package in the DriverStore is listed in one sortable grid with provider, class, version, date and size, so you can see at a glance which manufacturers and device types are consuming the most space.
  • Old and duplicate package detection marks entries that have a newer version of the same driver already present, which turns a risky guessing exercise into a short review list of sensible deletion candidates.
  • Deletion uses Windows' own driver package mechanisms and asks for administrator rights, and the list can be exported to a file first, so you keep a record of exactly what was removed from the machine.
  • The program is a small, portable open-source executable with no installer required and no background service, so a technician can carry it on a USB stick and run it only when needed.
  • A force-delete option exists for packages Windows refuses to remove normally, with clear separation from the normal delete path, which helps when a leftover package from uninstalled hardware will not shift.

Considerations

  • Deleting the wrong package can leave a device without a working driver, and the tool assumes you understand the difference between an old version and a current one before you start removing entries.
  • The dense, grid-based interface offers little guidance or explanation for beginners, and there is no built-in backup or undo for a package once it has been deleted.
  • It must run as administrator to delete packages, and some in-use drivers still resist removal without booting workarounds, so a cleanup occasionally cannot finish the job in one session.

How DriverStore Explorer — Clean Old Driver Packages from the Windows DriverStore for Windows PC Compares to Top Alternatives

HWMonitor ↗ vs DriverStore Explorer — Clean Old Driver Packages from the Windows DriverStore for Windows PC

HWMonitor reports live sensor data — temperatures, voltages and fan speeds — and never touches stored files or drivers. DriverStore Explorer does the opposite job: it manages driver packages on disk and reports nothing about how the hardware is running right now.

Best for:
CrystalDiskInfo ↗ vs DriverStore Explorer — Clean Old Driver Packages from the Windows DriverStore for Windows PC

CrystalDiskInfo reads the health status of your drives and warns about failing disks, but it cannot reclaim space from system folders. DriverStore Explorer frees space by removing stale driver packages and offers no information at all about disk health.

Best for:
Microsoft PowerToys ↗ vs DriverStore Explorer — Clean Old Driver Packages from the Windows DriverStore for Windows PC

PowerToys is a general collection of Windows productivity utilities such as FancyZones and PowerRename, aimed at everyday workflow. DriverStore Explorer is a single-purpose maintenance tool for one system folder, used occasionally by administrators rather than daily by everyone.

Best for:

About & Overview: DriverStore Explorer — Clean Old Driver Packages from the Windows DriverStore for Windows PC

DriverStore Explorer 1.0.75, widely known by its executable name Rapr, is an open-source utility by lostindark (Teddy Zhang) that makes the Windows DriverStore visible. Windows keeps a copy of every driver package ever installed, and old versions accumulate for years. The tool enumerates those packages in a sortable list with provider, version, date and size, highlights old and duplicate entries, exports the list, and deletes selected packages — with a force option for stubborn ones — running as administrator.

In-Depth: DriverStore Explorer — Clean Old Driver Packages from the Windows DriverStore for Windows PC

Inside the DriverStore: Why Windows Hoards Drivers

The folder at C:\Windows\System32\DriverStore\FileRepository is Windows' staging area for driver packages. When any device is installed — a GPU, a printer, a Bluetooth adapter, a virtual device created by software — its complete package of .inf file, catalogue and binaries is copied into the store, and Plug and Play installs the device from there rather than from your download. Keeping every version has a purpose: rollbacks work, a device reattached after a year finds its driver waiting, and Windows setup can repair an installation without media. The cost is accumulation with no housekeeping. A graphics driver updated monthly for four years leaves dozens of superseded packages, each potentially hundreds of megabytes, and printer drivers from hardware long since recycled sit beside them. Windows provides the pnputil command-line tool to enumerate and delete packages, and it works, but its output is a wall of text where matching an oem number to a device and version takes patience. DriverStore Explorer is essentially a careful graphical front end over the same mechanisms, adding sizes, dates, grouping and duplicate detection so a human can make decisions quickly and defensibly.

A Safe Cleanup Method That Avoids Regret

The order of operations matters more than the tool. Start by running the program as administrator and letting it enumerate the store, then export the full list to a CSV or text file and save it outside the machine being cleaned — that file is your only record once packages are gone. Sort by driver provider and date, and use the select-old-drivers function as a first pass: it marks packages superseded by a newer version of the same driver. Review that selection manually rather than trusting it blindly, paying special attention to storage, network and display drivers, where keeping the newest version is essential and where a mistake has the worst consequences. Delete in batches — one manufacturer at a time — and reboot before continuing, so any problem is attributable to a small change. Avoid force delete in a first session entirely; packages that resist normal deletion are usually in use, and the correct response is to identify the device, not to override the protection. Finally, measure the result by checking the DriverStore folder size before and after. This unglamorous routine is what separates a technician's cleanup from the forum stories about machines that lost their network adapter.

What This Tool Is Not: Updates, Backups and Driver Boosters

Confusion about categories causes most misuse. DriverStore Explorer does not find, download or update drivers — it never contacts a driver database and has no opinion about whether your current version is the best one. It is also not a backup tool: it can export a list of package names and versions, but it does not save copies of packages for later restoration, so a deleted version must be re-downloaded from the manufacturer if you change your mind. That separates it sharply from the commercial 'driver updater' category, which scans hardware, pushes downloads of variable quality and often charges subscriptions for doing it. Those tools solve a discovery problem; Rapr solves a storage and hygiene problem. The two meet only in that both touch the same folder. If your actual need is a missing or broken driver, the manufacturer's support page or Windows Update is the correct route, and deleting stored packages will not help you. If your need is reclaiming space on a small system drive or preparing a clean machine image for deployment, this is precisely the right instrument — narrow, transparent about what it removes, and free of the upsell machinery that surrounds most driver software.

How to Install & Verify DriverStore Explorer — Clean Old Driver Packages from the Windows DriverStore for Windows PC

STEP 1
Download Rapr

Get DriverStore Explorer 1.0.75 from the project's GitHub releases page and save Rapr.exe to a tools folder or USB drive.

STEP 2
Check the runtime

If Windows prompts for a .NET runtime on first launch, install the version requested; current Windows installs often already include a compatible one.

STEP 3
Run as administrator

Right-click Rapr.exe and choose Run as administrator, then wait while it enumerates every package in the DriverStore.

STEP 4
Export the driver list

Use the export option to save the complete package list to a file stored outside this PC, as your record before changing anything.

STEP 5
Select old drivers and review

Use Select Old Drivers, review the marked entries carefully keeping the newest package per device, then delete in small batches and reboot.

Related Windows PC Software & Alternatives

Floorp — Customisable Firefox Fork with Workspaces and Vertical Tabs for Windows PC icon
Floorp — Customisable Firefox Fork with Workspaces and Vertical Tabs for Windows PC 12.20.2 • Open Source
GSmartControl — S.M.A.R.T. Drive Health GUI for smartctl for Windows PC icon
GSmartControl — S.M.A.R.T. Drive Health GUI for smartctl for Windows PC 2.0.2 • Open Source
CapFrameX — Frametime Capture and Analysis Overlay for PC Games for Windows PC icon
CapFrameX — Frametime Capture and Analysis Overlay for PC Games for Windows PC 1.9.2.4 • Open Source
Geek Uninstaller for Windows PC icon
Geek Uninstaller for Windows PC 1.6.0.200 • Freeware
WinDirStat Disk Usage for Windows PC icon
WinDirStat Disk Usage for Windows PC /v2.9.3 • GPL v3
Driver Booster Pro: 1-Click Driver Updater & PC Game Booster icon
Driver Booster Pro 14.0.1.462 • Freeware

Frequently Asked Questions & Verification Guide

Is DriverStore Explorer — Clean Old Driver Packages from the Windows DriverStore for Windows PC free and open source?

Yes. DriverStore Explorer — Clean Old Driver Packages from the Windows DriverStore for Windows PC is completely free and open-source software. You can download and use it at no cost, and its source code is publicly available.

Is it safe to delete old drivers from the DriverStore?

Deleting old versions is generally safe when a newer version of the same driver package is present and working, because Windows uses the newest suitable package for its devices. The risk is removing the only package for hardware you still own, or the newest version by mistake. Work through the old-driver list rather than selecting everything, keep the latest package per device, and export the list before deleting. Creating a system restore point first is sensible on an important machine.

Why is my DriverStore folder so large?

Windows stores a complete copy of every driver package it installs and does not automatically remove earlier versions when a driver updates. Graphics drivers are the biggest contributors because each package is large and they update often, followed by printer drivers installed over years of hardware changes. The store also keeps packages for devices you no longer own. DriverStore Explorer shows the size per package, so you can see which category is responsible instead of guessing.

What is the difference between Delete and Force Delete?

Normal delete asks Windows to remove a package and Windows refuses if a device is currently using it, which protects hardware you are actively relying on. Force delete overrides that refusal and removes the package anyway. That can be necessary for a leftover package whose device is gone but still marked as used, and it can also break a working device if used on the wrong entry. Treat force delete as a last resort for entries you have identified with certainty.

Does DriverStore Explorer need installing?

No. The program is distributed as a portable executable (Rapr.exe) that you run directly, normally by right-clicking and choosing Run as administrator so deletion is available. It requires a suitable .NET runtime depending on the build you download, which recent versions of Windows usually provide or prompt for. Nothing is added to startup and no service is installed. That portability is why technicians commonly keep it on a tools drive.

Will deleting drivers free much disk space?

It depends entirely on the machine's history. A recently installed PC may hold only a few hundred megabytes of removable packages, while a system that has had years of graphics driver updates can release several gigabytes, occasionally much more. Sort the list by size and review the old-version entries to estimate your own figure before deleting. The tool reports sizes per package, so there is no need to guess.