Unused driver cleaner

You may notice that over time, the folder begins to increase more and more and will fill the disk space. This will open up the Print Server Properties window as shown below. Next, select Remove, and the following window will be prompted. Method 2: Delete printer driver using Print Management — Launch the control Panel and navigate to the following and click on Administrative Tool as shown below. This will open up the Print Management window as shown below. You can use this command to add driver packages and remove them as described here.

To have this done, follow the steps below. This will expand the Disk Cleanup option. Click on Okay. As you can see, I also selected other option to clear. This is absolutely upto you. Now, the Disk clean up will delete all obsolete or unused driver versions. Note 1: AFter performing this operation, be aware that the Roll back driver button in Driver Properties tab of Device Manage will become inactive.

Note 2: You can also uninstall the printer driver via the Control Panel or Windows Settings through the uninstall program and features wizard.

Thus, a user can roll back to the previous driver version if the new driver is unstable a useful opportunity, as in the case of rolling back a Wi-Fi driver. However, Windows does not automatically clean and delete old driver versions, so as the time goes the size of disk space occupied by drivers becomes quite large.

In my case on my home laptop running Windows 7 installed almost 8 years ago , FileRepository folder occupies about 11 GB and contains over 5, files. In particular, over 20 Nvidia driver versions are stored here. In Windows 8 and Windows 10, easier ways to delete old drivers are used, these are described below. Get the list of all third-party drivers available in the system and export them to a text file.

To do it, run the following command in the command prompt with the administrator privileges:. Import this text file into Excel, and delete all odd data in a way that only the table containing the list of drivers in the repository is left. The table should contain the number of the driver in the system oemXXX. Sort this table by column B containing the name of the original INF file and column F driver installation date.

Among the drivers with the same name mark for removal all driver versions except the last one. Cleanmgr will delete all old unused driver versions. However, you should understand that the Roll back driver button in Driver Properties tab of Device Manage will become inactive.

How did you import from the txt file to excel? In terms of a third party device management application, Device Remover is probably the most advanced and feature rich free program available.

For some reason, the program is no longer developed and the official website has disappeared. The last available version is from so is new enough to work fine for most people. Both portable and installer versions can be downloaded. During the first run, you will be asked if you want to let the program run an optimize routine, allowing it should speed up the device detection and enumeration process.

Once loaded, devices can be viewed in a tree or list style, selectable from the tabs. A warning and confirmation window will appear to give you one last opportunity to back out.

Although the device removal procedure is quite simple, Device Remover is a powerful tool so other functions need to be handled with care. I liked the process of considering each item to remove not to remove.

Congrats for a great utility! USBDeview is more to my liking. I had over a hundred ghosts and It was a pain to select all the ghosts except a few which i will be using later on for removal.

But yes it does a little extra by showing us the ghosted services too. Thanks for all of your significant work. The portable devices section will probably have quite a few entries with phones, mp3 players etc. If you recognize the device or drive letter it uses, add that device only, make sure nothing else is selected for removal and try it.

The worst that can happen is the device will be re-detected when you reboot. Currently adding by class will enable all of them as will adding by device or wildcard. Is this what you mean?