Windows\Installer folder cleanup. Clean msp & msi patches marked as superseded

On my SSD machine, the C:WindowsInstaller folder is massive and takes up about 15% of my total disk space.

Is there a way to clean up that folder without killing Windows 8.1/10? Tucking away the installers on the OS partition seems wasteful.

asked Jan 27, 2014 at 17:55

12 gold badges44 silver badges47 bronze badges

I created “PatchCleaner” to clean the windows installer directory of all orphaned files in one easy click. If you don’t trust the app to do the right thing, use the move feature to put them somewhere safe in case you need them back in the future. I have run it on multiple machines and saved up to 15Gb of space 🙂

Run PatchCleaner after windows updates to find newly orphaned files.

I recommend you use the Move action, and move the orphaned patches to external storage, just to be safe

Known Issues (full details on website)

answered May 28, 2015 at 13:45

1 gold badge13 silver badges6 bronze badges

This seems to have worked for me. This is a simplified set of instructions from http://www.kavoir.com/2012/07/how-to-free-up-c-drive-disk-space-in-windows-7-easy.html

Verification

As a verification, I ran a “repair” of my Microsoft Visio Professional 2013 install (took 4 minutes to process). This completed successfully. Windows update (with reboots) also ran successfully after making the above changes. I will write back if anything doesn’t work.

answered Apr 22, 2014 at 21:50

4 gold badges22 silver badges33 bronze badges

You can compress the folder. You will regain between 10 and 20% of the space.

answered Nov 26, 2014 at 10:46

6 silver badges2 bronze badges

answered Jan 27, 2014 at 19:17

30 gold badges178 silver badges245 bronze badges

How to safely(*) clear disk space on Windows 10(**)

(**) Targeting Windows 10 but similar steps may apply to other versions of Windows.

answered Oct 4, 2018 at 9:27

2 gold badges12 silver badges23 bronze badges

You can try a junction by copying the files to the new drive, then renaming the old installer folder temporarily, creating a junction from the default folder to the new. Then test things for a bit before deleting the renamed installer folder. Maybe install a bigger more complex program like visual studio, or adobe Photoshop, then uninstall it just to make sure all is well. But be forewarned, if anything goes wrong, you might not be able to install or re-install programs. Been there, done that. 🙂

answered Jan 30, 2014 at 10:43

1 gold badge14 silver badges24 bronze badges

answered Sep 26, 2015 at 22:52

I have delete the Installer folder and notice that.

I lost a lot of information’s that windows cache there. One it was the icons of the programs links. And many program links left with out an icon.

The size off all that directories are very small – so for me, you have to keep that directories with a GUID as name – and delete the rest.


Windows\Installer folder cleanup. Clean msp & msi patches marked as superseded

answered May 12, 2022 at 17:53

7 silver badges17 bronze badges

I noticed no ill effects: there are no new updates offered if you check for updates after running the script, so it doesn’t remove anything essential and Office still runs and can be serviced (add/remove components works).

Somewhat theoretical answer: if the MSPs are well designed, nothing should break just from running that script, unless you later uninstall patches (either manually or some automated process does it) in which case you’ll find out if the patches were well designed.

As Heath (MSFT) explains, if you remove superseded patches, what can happen is that if the “top patch” is then manually removed too, you’re left with a much older (and buggy) version of the app than you might expect. And my thinking is that in combo with the feature that some superseded packages may be non-uninstallable/”permanent” could break some apps; skip two paras for details how that could happen. (permanent is the keyword used in the .mum file.)

But before we get to that scenario, let me clarify something (which is a good way to see what’s going on): the superseded patches, while still present in the registry (that’s how that script finds them) are not shown at all (at least on Win 7) in the installed updates, unless they are also not marked as non-uninstallable/. ( I tested this myself, by modifying that script to not remove anything, but just list what it would do, and then checking the patches in the Control Panel.) But if you do uninstall a top patch, causing a superseded but uninstallable one to become unsperseded, it will pop back on that Control Panel list, when you refresh it. ( The writers of some 3rd party wix toolsets found this behavior pretty confusing.)

But there is actually a way to break an app with badly designed patches by uninstalling the intermediate/superseded ones: say you have files A and B, initially both at version 1.0. Patch X puts file A at ver 1.1, which is ok with file B at 1.0. Then patch Y puts file B at ver 1.1, which also compatible with A at 1.1, but incompatible with A at 1.0. But somehow this patch Y is made non-uninstallable, which can actually happen in a large number of ways. After those, you have patch Z which puts file A and B at 1.2. Then someone runs the script which uninstalls patch X (superseded), but can’t uninstall Y (superseded but non-uninstallable). And then they manually roll back patch Z, leaving exposed file A version 1.0 and B version 1.1 (from patch Y). And this breaks the app.

Admittedly, this kind of scenario probably does’t happen with MSFT apps for which they give a list of most recent MSPs (patches) that are safe to install by themselves, i.e. without all ancestor MSPs being installed. M S does this e.g. for Office 2016, but not for 2010 (although they even bothered to make a click-to-run version of 2010). And from my quick checks with the script, Silverlight bestows (a lot of) non-uninstallable (the script calls them “permanent”) but superseded patches, so such things do exist even in the MS realm. Actually Office 2010 has a few too, e.g.:

Microsoft Office Proof (Chinese (Traditional)) 2010 : Security Update for Microsoft Office 2010 (KB2760781) 64-Bit Edition is a permanent patch, run this script with /f to uninstall it

And Adobe Acrobat Reader DC also behaves pretty much like Silverlight, with a lot of non-uninstallable & superseded patches.

Also of some note, a fairly old MS document from the Vista days said that removing superseded stuff from %windir%Installer is a prerequisite for safe removal from from SxS (which is another source of bloat):

The only way to safely reduce the size of the WinSxS folder is to reduce the set of possible actions that the system can take – the easiest way to do that is to remove the packages that installed the components in the first place. This can be done by uninstalling superseded versions of packages that are on your system. Service Pack 1 contains a binary called VSP1CLN. EXE, a tool that will make the Service Pack package permanent (not removable) on your system, and remove the RTM versions of all superseded components. This can only be done because by making the Service Pack permanent we can guarantee that we won’t ever need the RTM versions.

So removing superseded stuff from %windir%Installer should also help with reducing the SxS size. Note that there are semi-automated ways that do the later (after some superseded patch really is uninstalled, using the API, not plain deletion, I suspect):

Package_for_RollupFix~31bf3856ad364e35~amd64~~7601.23642.1.0 superseded – uninstalled
2020-07-03 06:47:01, Info CBS

Also of some interest, someone else on that same MDL forum wrote a /ResetBase equivalent for Win 7. I haven’t tested it. The latter hack looks a lot more complicated than the simple script mentioned by the OP. It also “ships” with a full complement of dismcore.dll & etc. dlls from a (by now) old version of Win 7, so I’m skeptical it works well with the later servicing stacks.

:/>  Способы запуска программы от имени администратора в Windows 10

Learn how to clear up storage immediately

by Andrew Wafer

Updated on June 30, 2023


Windows\Installer folder cleanup. Clean msp & msi patches marked as superseded

We install many apps on Windows, and each of these gets updated every few months. Here, the OS stores the change in system information in a file to aid recovery in the Windows Installer folder, which might need a cleanup.

Can I clean up the Windows Installer folder?

The files are stored whenever an application is installed using the Windows Installer, and their size is usually small. But, over the course of time, as more apps are added and updated, the size of the Windows Installed folder increases.

Where exactly are Windows Installer files used? They come in handy when uninstalling an application or an update for it. Though experts recommend against deleting the files stored in the Windows Installer folder, if you run out of storage, try it.

Keep in mind that it’s safe to delete only the baseline cache:C:WindowsInstaller$PatchCache$

Don’t remove anything that’s located directly under:C:WindowsInstaller

This way, you can free up some space from your hard drive (especially if the space is already limited). Over time these patches might become quite numerous.

Remember, these are system files that are hidden by default, so you will have to directly paste the path in the address bar to access it. Another way is to enable hidden system files in Windows.

How can I cleanup the Windows Installer Folder?

The manual way for Windows Installer Folder cleanup works well, but you will have to first make the hidden protected operating system files visible.

Use a dedicated tool

PatchCleaner is the preferred tool for many when it comes to Windows Installer Folder cleanup. The best part, it automatically identifies which files can be safely removed and clears disk storage without putting the PC at risk, though it may sometimes be inaccurate.

Use a PC Optimizer software

Some software helps where it counts the most, in the performance of any PC, with optimization utilities that prevent a lot of unwanted damage from a system failure.

Fortect is a software program that specializes in Windows repair. It examines and diagnoses your damaged PC before repairing it using technology that not only restores your Windows Operating System but also reverses the damage done with a complete database of replacement files.

While you are clearing up storage space, find out how to reduce the size of the WinSxS folder.

Tell us the size of the Windows Installer folder on your PC and how much you were able to clear in the comments section below.

Cleanup remnant software files that bulk up your system

by Claire Moraa

Updated on May 17, 2023


Windows\Installer folder cleanup. Clean msp & msi patches marked as superseded

INSTALL BY CLICKING THE DOWNLOAD FILE

If you have ever installed a program and realized you didn’t need it or the app installation failed, you might be aware of the Windows Installer Cleanup utility.

This tool was available in earlier versions of Windows, but we show you how you can still download it in newer versions.

What does Windows Installer Cleanup Utility do?

Windows Installer Cleanup Utility is a tool that helps you to remove invalid registry entries and other system garbage. Such files can cause your PC to run extremely slow and other performance issues.

By using this utility, you can scan your computer for known issues and repair them. The utility also provides a way to uninstall programs that were installed on your computer by using Windows Installer technology.

Other beneficial purposes it may serve include:

How can I download the Windows Installer Cleanup utility?

Before you download the Windows Installer Cleanup utility, there are a few things to note:

Is it safe to delete the Windows Installer folder?

The Windows Installer folder is a hidden folder that contains all the Windows Installer data for your system. It can get pretty large if you have a lot of programs installed on your computer because it includes files and registry keys.

If you delete this folder, you’ll lose access to many applications. Instead of deleting the entire folder, we recommend performing a Disk Cleanup or finding other ways to free up space on your hard drive.

The good news is that other options are still available if you want to clean up your PC. Windows 11 has many built-in repair tools at your disposal. The program install and uninstall troubleshooter for Windows 11, for instance, is a replica of the Windows Installer Cleanup utility.

However, you may feel these tools are insufficient, so we recommend you reach out for uninstaller software. These tools will allow you to delete unnecessary files from your computer without worrying about causing future problems with your PC.

Let us know whether you still use the Windows Installer Cleanup utility and your experience thus far, especially in newer Windows versions.

Windows Installer Directory

When applications are installed and updated on the Windows Operating System a hidden directory “c:WindowsInstaller” is used to store the installer (.msi) files and the patch (.msp) files.

Generally these files are important as during updating, patching or uninstalling software it will use the .msi/.msp files. If you blanketly delete all the files in this folder, you will find yourself needing to rebuild windows.

Over time as your computer is patched and patched again, these installer files become outdated and orphaned. They are no longer required, but they can take up many gigabytes of data.

PatchCleaner

PatchCleaner identifies these redundant/orphaned files and allows you to either:

How it works

HomeDev has had many queries about how PatchCleaner works and if it can be trusted to do the right thing.

Its pretty simple. The windows operating system holds a list of current installers and patches, that can be accessed via WMI calls, (Windows Management Instrumentation ).

PatchCleaner obtains this list of the known msi/msp files and compares that against all the msi/msp files that are found in the “c:WindowsInstaller” directory. Anything that is in the folder but not on the windows provided list is considered an orphaned file and is tagged to be moved or deleted.

HomeDev cannot warrant that PatchCleaner will not find a false positive and delete a required patch which is why we have added the filter feature to filter and recommend using the move function, that way you can always copy the patches back if required. Please see the Known Issues List at the bottom of the page

CLI – Command Line Interface

As of verison 1.3, patch cleaner implements a CLI, (Command Line Interface).

The process will write the output to the console window and also logs the messages to the windows event log.

Malware

Given this is 100% free software I cannot justify the expense in doing this, so I do apologise for any extra clicks you may have to do to install PatchCleaner but I don’t think this will change any time soon.

If you don’t believe me, then how about trusting Softpedia where we have been given a 100% clean rating.

Check out the review here as well.

PatchCleaner on Softpedia

Known Issues

The installer that you download from the website is a self extracting 7z archive created as per my blog post (http://ntsblog.homedev.com.au/index.php/2015/05/14/self-extracting-archive-runs-setup-exe-7zip-sfx-switch/).

So you can actually open the .exe file with 7Zip and extract the files (setup.exe and PatchCleaner.msi).

I would then try running the PatchCleaner.msi file directly.

License

Yes the product is 100% free, but if you feel inclined please support via a donation either through the $ heart icon in the app or this link below

Version 1

Thats all the bugs fixed now.

Version 1.4.1.0 of PatchCleaner is a hotfix release due to a crash that was occuring on Windows 7 machines

:/>  Power shell и его возможности в уходящем году

Version 1.4.0.0 of PatchCleaner implements new functionality, including:

PatchCleaner now provides the details of:

There is a known issue in previous versions where PatchCleaner falsely identifies Adobe Acrobat Reader patches as not being required. Adobe do something proprietary when it comes to their automatic updating such that if PatchCleaner removes the “orphaned” patches from the installer directory, Adobe Reader automatic updates will no longer successfully install.

The exclusion filters feature allows you to add keywords that are used in “contains” filters to exclude patches that match these keywords. These “contains” checks are applied against the file title, subject, author and digital signature.

PatchCleaner is now pre-configured to exclude “Acrobat” which will exclude any Adobe Reader files from the set of orphaned files.

These exclusion filters are able to altered by you.

Any Adobe Reader patches that were copied back to “c:windowsinstaller” as part of step 4, will have been excluded from the set of orphaned files and will remain in the installer folder.

Version 1.3.0.0 of patch cleaner implements a CLI, (Command Line Interface).

This version contains some minor fixes, including:

Note: There have been no functional changes to the code

Since version 1.1.1.0, HomeDev has performed further testing, which involved testing with the latest round of windows updates.

All windows update patches installed with no issues being encountered.

Running patch cleaner after running a large set of windows updates recovered another 1GB of free space.

Hotfix for issue that was identifying false positives.

There was a bug that was falsely identifying a small number of patches as orphaned when in fact they were not. For example on a test computer it found 42 files worth 300MB of actual patch files that should have been retained.

If you used the move function the recovery process is:

I ran this for over a month with out any issues before releasing the first version of the product. It was only today that I had my first issue.

I appologise if this has caused any problems.

Fixes issue with move action crashing.

Added better error capturing around the move logic.

If you have crashes when attempting the move action it will be related to file system permissions. Try choosing a destination location that you have full control over.

First version of PatchCleaner.

Can you create a Command Line version of PatchCleaner?

Yes, we created a command line version of the PatchCleaner in version 1.3.0

I have upgraded to the latest version of PatchCleaner and it is crashing, what should I do?

Between version 1.3 and 1.4 there were changes made to the way PatchCleaner works.

It appears that a direct upgrade leaves some files from the pervious version behind and when the new version starts it fails to start throwing an error like:

FATAL PatchCleaner. App: An Unhandled Execption has occured System. IndexOutOfRangeException: Index was outside the bounds of the array.

Unrecoverable error, PatchCleaner uses vbScript and it appears that vbScript is not working on your computer.

Unrecoverable error, PatchCleaner uses vbScript  and it appears that vbScript is not working on your computer. ” Can’t find script engine “VBScript”. You will need to resolve this issue before running PatchCleaner

As the error suggests patch cleaner uses vbScript. It is used as the base technology for asking your computer what software and patches are required by your computer, as this is the fastest way to make the required “WMI” calls. Without a working version of vbScript on your computer PatchCleaner cannot work.

If you receive this error, it is because vbScript is broken on your computer.

This can be for various reasons, and google will be your friend to help resolve this.

Below is a link that people have used to help resolve the issue with vbScript on their computer:

Until you get vbScript working on your computer you will not be able to run patch cleaner.

To easlily test create a file called “test.vbs”, open it in notpad and enter this code:

Save it and double click, if you get a message box showing the above text then you have fixed your vbScript issue

Given this is 100% free software I cannot justify the expense in doing this, so I do apologise for any extra clicks you may have to do to install PatchCleaner but I have no plans to change this.

Hundreds of thousands of happy “customers” can’t be wrong, so just give it a go.

As of  October 2017 – softpedia has given PatchCleaner a 100% bill of health as verified as 100% clean.

Read about their review on Softpedia

I am having trouble installing/uninstalling PatchCleaner

Some people have encountered installaton challenges when attempting to install/uninstall PatchCleaner.

The installer that you download from the website is a self extracting 7zip archive created as per my blog post (http://ntsblog.homedev.com.au/index.php/2015/05/14/self-extracting-archive-runs-setup-exe-7zip-sfx-switch/). The idea behind this is to package both a Bootstrap setup.exe, along with the actual .msi.

If you run into problems installing, (or in some cases uninstalling and cannot find the .msi file), you can actually open the .exe file with 7Zip and extract the files.

Download and install a copy of 7Zip from 7Zip.org and right-click on the PatchCleaner.exe and choose extract here.

You will get 2 files, a setup.exe and a PatchCleaner.msi. The setup.exe is what is called a bootstrapper and it attempts to ensure that the pre-requisites are meet. The .msi is the installer itself.

Are you using Windows 10 for a long time without reformatting? If yes, you might have seen that the size of the folder C:WindowsInstaller is almost filled while you haven’t saved anything in this folder.

In fact, during normal operations, many unnecessary files get created in this folder. For this reason, you have to go with the Windows installer folder cleanup process. This will keep your computer system as fast as expected.

So, what are the cleaning processes? Let’s find out from below.

How to Delete Unnecessary Files of Windows Installer Folder?

Don’t assume that we are going to delete all files of the windows installer folder. It is because this folder contains important files for the accurate functioning of your computer system. If you delete them, you can’t work with your computer.

The below steps will allow you to do windows installer folder cleanup.

Symbolic Link Creation in order to save space in the Windows Installer folder

By default, the windows installer folder remains hidden. Even if you enable the “show hidden files and folders”.

Installer Folder Copying to Another Folder

Now, the Windows directory will have to installer folder in it. Choose another drive where you have to copy the whole windows installer folder.

For instance, you want to copy the installer from the “C” drive to the “D” drive. Simply copy the folder from C drive and Paste it to D drive.

The copying and pasting process may take longer depending on the installer folder size.

Tips: It would be best if you keep a copy of the installer folder to another drive or pen drive to avoid any unwanted situation.

Symlink creating using CMD

rmdir /s /q C:WindowsInstaller

Important note: The folder path needs to be replaced in the above command if the folder of Windows is at a separate path.

C:WindowsInstaller directory and the folder will get deleted entirely with the above command.

Great work! Windows installer folder shortcut is created now. And your compute C drive disk space is free too.

With the above solution, D drive will be the new location for any new request for windows installer folder files.

You might be interested in:  Windows 10 Startup Repair Not Working

How to Fix Windows Installer Package Problem

My C:WindowsInstaller folder has grown over 10 GB. I noticed that some *.msi and *.msp files are in C:WindowsInstaller but not the mentioned in the registry (e.g. I can see a file named “104a0288.msi” in C:WindowsInstaller but searching for “104a0288.msi” in the registry editor doesn’t bring any results). Can I safely remove those files?

:/>  Деактивация обязательной проверки подписи драйверов и Пошаговая инструкция по постоянному отключению проверки цифровой подписи драйверов (альтернативный подход №2) на Windows 10, 8.1, 8, 7?

I use Windows 7 SP1 x64 Ultimate.

asked Nov 2, 2014 at 18:32

The article below shows different ways to delete unused Microsoft Installer/Patch files from the Installer folder. It is a very good and descriptive article.

3 Ways to Safely Delete Unused MSI and MSP Files from Windows Installer Folder

In summary, these are the 3 ways:

First, I had trouble with the download link, so I found the utility downloadable here.

answered Mar 12, 2015 at 8:24

MsiZap only discovered one orphaned msi for a whopping savings of 100 MB. After that I tried PatchCleaner and cleaned up 20 GB.

PatchCleaner took about 20 minutes to parse the 30 GB of Windows Installer cache (seriously, MSFT, wtf) and then with one click was able to free up 20 GB.

answered Aug 5, 2017 at 21:13

3 silver badges5 bronze badges

C:WindowsInstaller is where Windows Installer stores cached copies of the setup packages (.msi) and setup patches (.msp) used for your currently installed programs. These files are required if you want to update, modify, or uninstall a program on your computer. Do not delete them blindly.

Sometimes you can end up with orphaned .msi or .msp files in this directory that do not get cleaned up appropriately. This typically happens when an installation fails. These can be removed with a tool called Msizap, but be aware it is not supported by Microsoft anymore.

“%PROGRAMFILES%Windows Installer Cleanupmsizap.exe” !g

I would honestly not worry about 10gb of installers sitting in there unless you are critical on hard drive space. It is more likely a sign that it’s time to reinstall Windows again to get your computer running as fast as it did on the day you bought it. 10gb is pretty typical for a 2+yr old install of Windows.

answered Dec 21, 2014 at 18:06

answered Nov 29, 2017 at 16:18

answered Jun 17, 2020 at 22:01

1 silver badge2 bronze badges

answered Nov 3, 2014 at 0:50

What is Windows Installer folder? Is it safe to delete files in this folder? This post of MiniTool would tell you how to safely free up space with the help of the Windows Installer cleanup utility.

On This Page :

About Windows Installer Folder

Windows Installer folder is a protected folder with System & Hidden attributes, which can be found under the Windows folder. When you install a program in Windows, its .msi setup package will be copied to the Installer folder.

The Installer directory is a cache location for installer data files of various applications installed on the PC. When you repair, uninstall, or reinstall the program via Apps & Features in Settings or Programs & Features in Control Panel, you are required to use the .msi package from the Windows Installer folder to do these operations.

Once the corresponding setup package (.msi or .msp) file isn’t found, Windows prompts the error “The installation source for this product is not available. Verify that source exists and that you can access it.”

Issues with the Installer Folder

However, you may find that the Installer directory grows and consumes a massive amount of hard disk space. This phenomenon often occurs and it can be seen in many forums or communities. Well, here is a true example.

Can You Delete All files in This Folder

The answer is negative because the Windows Installer folder contains important files for the accurate run of the system. If you delete these files, you can’t work with your PC. Actually, you should never delete the contents of the C:WindowsInstaller folder randomly.

Windows installer patches sometimes may get orphaned during the process of software uninstallation. When a program is uninstalled, the corresponding .msi package is left behind in the Windows Installer folder. Then these orphaned packages can be deleted.

Besides, many unnecessary files created during normal operations can also be removed. Based on the above fact, you can conduct a Windows Installer folder cleanup Windows 10 with the offered methods in this post.

Delete Orphaned. M SI Files via PatchCleaner


Windows\Installer folder cleanup. Clean msp & msi patches marked as superseded

Step 3: When the installation process ends, run it by double-clicking on its icon on the desktop. Then you can see the corresponding sizes of used, excluded, and orphaned files in the Installer folder.


Windows\Installer folder cleanup. Clean msp & msi patches marked as superseded

Step 4: You can click details behind each file category to see the detailed information if there are any files. For instance, here are the details of “in use” or valid program entries.


Windows\Installer folder cleanup. Clean msp & msi patches marked as superseded

Step 5: If there are any orphaned files on your computer, click details to learn the detailed information. Then you can either delete the orphaned setup package or move it to another folder and then delete it safely after a few days.

How to clean up Windows Installer folder safely? In addition to PatchCleaner, there are some other Windows Installer cleanup programs to do that.

Word Frozen: How to Solve It and Recover the Lost Data

Make Use of Windows Settings

Step 1: Open Settings by holding the Windows and I keys at the same time.

Step 2: In the Settings window, click System.

Step 3: Click Storage under the System tab, and then move to the right side of the window and tap Temporary files to continue.


Windows\Installer folder cleanup. Clean msp & msi patches marked as superseded

Step 4: Choose file types like Windows Update Cleanup and Downloads from the list, and then click on the Remove files option to execute the operation.


Windows\Installer folder cleanup. Clean msp & msi patches marked as superseded

Run Disk Cleanup

Disk Cleanup is a built-in utility on Windows devices. It can help you clean up system files safely. It is a free Windows Installer cleanup utility. You can free up space via Disk Cleanup using these steps.

Step 1: Open File Explorer by pressing Windows and E keys.

Step 2: Click on This PC in the left pane, and then find and right-click on the C drive and choose Properties.


Windows\Installer folder cleanup. Clean msp & msi patches marked as superseded

Step 3: Tap Disk Cleanup in the Properties window.


Windows\Installer folder cleanup. Clean msp & msi patches marked as superseded

Step 4: After you click on Clean up system files, the utility will immediately calculate the disk space that you can free up from the selected drive.


Windows\Installer folder cleanup. Clean msp & msi patches marked as superseded

Step 5: Choose files to delete and click OK to carry out the operation.


Windows\Installer folder cleanup. Clean msp & msi patches marked as superseded

Also read: How to Clean up Your Computer? Top 8 Methods for You

Find what is taking up your hard drive space with a professional disk space analyzer and then delete unused files or folders. MiniTool Partition Wizard is such a tool. Its Space Analyzer feature enables you to know what is exactly consuming your disk space.

Learn your hard disk usage and delete space-consuming and useless files with this free Windows Installer cleanup utility now!

MiniTool Partition Wizard FreeClick to DownloadClean & Safe

Step 2: Launch this app to enter its main interface.

Step 3: Click on the Space Analyzer feature in the top bar.


Windows\Installer folder cleanup. Clean msp & msi patches marked as superseded

Step 4: In the next window, choose C from the drop-down menu and click Scan. Then the program will automatically scan the selected drive.


Windows\Installer folder cleanup. Clean msp & msi patches marked as superseded

Step 5: After a while, you will receive the result. Expand the Windows folder to find the Installer folder. Likewise, you can expand the Installer folder to display its content. You can find the target files by using .msi or .msp file filters.


Windows\Installer folder cleanup. Clean msp & msi patches marked as superseded

Step 6: Right-click on the unused .msi or .msp files and click Delete (to Recycle Bin) or Delete (Permanently) based on your need.


Windows\Installer folder cleanup. Clean msp & msi patches marked as superseded