InstallerClean 3.1.1
The anonymous report now says more about one of the reasons InstallerClean leaves installation packages alone.
The anonymous report
Before InstallerClean offers an installation package that no record names, it looks at each installation's cached copy of its installer to find out which program that copy belongs to, and so whether one installation is a second copy of another. Where a copy doesn't say and Windows can't confirm from the installation's own record that it's an ordinary installation, or where InstallerClean can't see all the installation packages of a possible second copy, it leaves alone the installation packages that no record names. The report now counts the cached copies it looked for and, for each installation whose copy didn't say and which Windows couldn't confirm, why the copy gave no answer and why Windows couldn't confirm it. Where a possible second copy stopped it instead, the report counts how many it checked and which step stopped it. Like everything else in the report it names no program, file or account, and the privacy policy lists what it holds.
The report is only ever sent from a PC's first finished run, and only if the "Send anonymous report" box is ticked on the screen InstallerClean shows when that run finishes.
The changelog has the full list.
Downloads
- InstallerClean-3.1.1-portable.exe (~64 MB) - The app as a single executable. No installation; run it directly.
- InstallerClean-3.1.1-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.
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.1.1 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.1.1-portable.exe: 0/68 ✨
- InstallerClean-3.1.1-setup.exe: 0/64 ✨
- installerclean-cli.exe: 0/62 ✨
Donate
Any small donation is much appreciated.