Purge installer folder

I do consulting, I produce and teach my own courses, I lecture and I present and my formal work title is senior workplace architect at Coligo in Stockholm, Sweden.

I'm also proud to be an Microsoft MVP since Follow me on twitter AndreasStenhall. I installed msizap. I had 40 gig in the installer folder. Lots of clicking but I have space to work now. Windows version failed on installation. WiCleaner worked flawlessly. Cleaned up 29 GB in 10 minutes. Thank you for your informative article! Thank you very much sir, really good and helpful article with clear instructions.

I found unused files taking up 50,8GB …imagine, I had to hit yes and ok for every single file to get rid of it! Absolutely worth it! Many thanks. My experience mirrored that of Maros.

Very helpful and straightforward instructions. Thank you. Lol I like how the main article has no mention of Patch Cleaner, but the comment section have hijacked it by only talking about Patch Cleaner. Patch Cleaner was actually only in development for about 9 months. PatchCleaner worked like a charm, 20 GB cleaned. I moved the files to an external hard drive just in case but damn! WICleanup was a rather awkward and clunky to use, but it definitely did find a lot of orphan files on my machine and allowed me to delete them.

Thanks for this article. Patch Cleaner found 45 GB of orphans! Why all the cumbersome solutions? Your solution is vastly more cumbersome than all of these, they are free and only take a matter of seconds to find what they are looking for. Your solution is paying for software and then waiting an hour for it to complete its task!

After using Patch Cleaner be prepared for an extremely long boot. I think mine is busy now for half an hour or so, though not stuck yet…. I have had to really scour my brain to remember all my old VAX commands when using the command prompt, so any suggestions will be most gratefully received. For nearly a year I have been working with a margin of about 3 GBs of space on my hard drive, it was so frustrating! To have this problem solved is fantastic.

Total disk usage was 61 GB, meaning over half my files were garbage!!! Good job Patch Cleaner! After doing some research, I realised that the Windows Installer sub-folder was the main culprit 28GB in size! However, it took me hours of research and banging my head against a brick wall , before stumbling across the positive feedback here for PatchCleaner.

I was absolutely amazed! Before, the sub-folder was 6GB in size but is now slightly over MB. Now, I have just under 60GB of available space. They are not duplicates. Delete one the other disappears. Patch Cleaner. It cleans the windows installer directory with one easy click. Patch Cleaner has found Fingers crossed my laptop will continue to work properly. I manually looked at the properties for a number of them and they are for programs that are listed as installed, and truly are installed.

I would NOT use it. MSIZap has similar problems, so be careful. Used PatchCleaner today to free 32 GB of a total 39,4 GB in my windows installer folder moved to external backup drive. What is left corresponds to installed applications. PatchCleaner was very user friendly and worked like a charm used version 1. Just moved 28 GB to another drive using Patch Cleaner.

Now I just have to verify that everything continues to work normally. Tried PatchCleaner today. Found over orphaned files Successfully moved them to another partition. Used PatchCleaner, freed up 16,9 GB! This is just sick. When I pulled it out of quarantine it was again flagged as a virus. I deleted the file. I tried to download it elsewhere but had same result. I looked a bit online and a few feel the original file has been swapped out for something evil from China since Please re-evaluate this file as it has been compromised.

What is your evidence that WICleanup has been compromised? Wow patch cleaner works like a charm. For an application to be removed, the application must know exactly what to remove from the system files , registry or what additional Custom Actions must be triggered during uninstall. Although an application is published on the machine and specific information can be found in the registry, the above-required information can only be obtained from the cached MSI. It fails in every case because the application is seen as already present on the machine.

The tricky part is that, when you empty your installer folder, the app still appears as installed in SCCM. The only option made available in the Software Center is for the user to uninstall the app only if you did not add a repair command on your application before you deployed it.

It can delete temporary files and system files, empty the Recycle Bin, and remove a variety of other items that you might no longer need. Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

You can simply use Disk Cleanup and clean up the unwanted files from WinSxS folder as well or you can remove the unwanted features directly from powershell. In-place upgrade from r2 to affect on spanned volume. But, ultimately the setting is applied. Using AD FS 3. Needs password authentication?