InstallerClean 3.2.0
InstallerClean no longer holds a file back for a day after it changes, and offers more of the files it held back for programs whose saved installer is missing or was never recorded.
- A file in
C:\Windows\Installerthat no installed program's records name is no longer held back for a day after it last changed. Instead, InstallerClean checks that it was last changed before the scan started, and that it could confirm Windows Installer had nothing in progress or waiting for a restart when the scan started - InstallerClean holds a file back if it changed after the scan started, and holds back all of those files if Windows Installer was busy as the scan started or the PC's clock went back during it, and says which it was
- If Windows Installer is busy at the check made just before a Move or Delete, nothing is moved or deleted, and the window and the command line say so as they do when it's busy at the click
- If InstallerClean can't check whether Windows Installer is busy, Move and Delete pause, with a banner in the window and an error on the command line
- A program with no saved installer in
C:\Windows\Installeris now checked against the installers it was installed from, where the registry agrees it has none, instead of holding back every spare copy of its installer and sometimes every installation package on the PC - Where a program's saved installer is missing, the spare copies in the folder that are a different package can now be offered, since Windows Installer ignores them, while a spare that is the missing installer is still kept
- A file that disappears as a Move reaches it is reported as no longer there, instead of as a file error
- The anonymous report now counts the files held back for each of these reasons, and, by the reason each was kept, the files held back because the program they belong to is still installed; like the rest of the report it names no program, file or account (the privacy policy lists what it holds)
The changelog has the full list.
Downloads
- InstallerClean-3.2.0-portable.exe (~64 MB) - The app as a single executable. No installation; run it directly.
- InstallerClean-3.2.0-setup.exe (~93 MB) - Installer. Adds InstallerClean and the command-line tool, with an Add/Remove Programs entry to uninstall.
- installerclean-cli.exe (~37 MB) - The command-line tool as a single executable, for scripting, scheduled tasks and deployment.
- InstallerClean-3.2.0-slim.exe (~6 MB) - The app as a single small executable, for a PC that already has the .NET 10 Desktop Runtime installed.
I haven't been releasing the slim version since 1.9.0, because one engine on VirusTotal, SecureAge, flags it. I'm releasing it again from now on, because it's certainly a false positive (I've reported it and I'm waiting to hear back from SecureAge), and a couple of people on Russian download sites said InstallerClean is too big. The slimmed down version only works if you already have the .NET 10 Desktop Runtime installed, but I hope it's useful for some people.
The apps are unsigned and freshly downloaded files carry the browser's mark, so on first run Windows SmartScreen will usually warn that the publisher is unknown. Click "More info", then "Run anyway".
Built with .NET SDK 10.0.112 from the v3.2.0 tag. The portable and the command-line tool are single-file builds published with compression on. Release builds are deterministic, so building that tag yourself, on that SDK and with those flags, gives you the same bytes and the same hashes for the portable and the command-line tool; the README's Checking the download itself section has the detail. The installer is a different case: Inno Setup packs it and stamps the build year into it, so don't expect its hash to match.
Build it yourself
VirusTotal
- InstallerClean-3.2.0-portable.exe: 0/70 ✨
- InstallerClean-3.2.0-setup.exe: 0/69 ✨
- installerclean-cli.exe: 0/70 ✨
- InstallerClean-3.2.0-slim.exe: 1/69 One false positive
Donate
Any small donation is much appreciated.