Repository navigation
1.1.0, Where it is, on disk
Every package manager on this machine, read in one pass.
| Download | What it is |
|---|---|
DontLeaveUpdatesToFate-1.1.0-portable.exe |
Single file. Run it from anywhere, installs nothing. |
DontLeaveUpdatesToFate-1.1.0-setup.exe |
Normal installer: Start Menu entry, Add/Remove entry, installs to C:\Program Files\VagueDustin Enterprises. |
x64, Windows 10 1809 or newer. Both are unsigned: SmartScreen will show "Windows protected your PC" on first run; More info → Run anyway. SHA256SUMS-1.1.0.txt is attached if you would rather verify the download than trust it.
New in 1.1.0
Every row now shows where the package lives
The question the table could never answer was "which one is this, and where is it?". Now it does. Clicking a path opens Explorer with the folder selected; the row menu (⋯) adds Show in Explorer and Copy path. The location is searchable (type site-packages or Program Files to narrow the list) and it goes into every log export as a package inventory alongside the transcript.
No manager has a --where-is-it flag, so each is asked in the way it can answer: winget through the Add/Remove Programs registry read concurrently with the upgrade query, pip through one importlib.metadata pass per interpreter, Chocolatey and Scoop through their package roots, npm from the field it already reports, rustup and cargo from their homes.
Three rules keep it honest. Nothing is shown that is not actually on disk. MsiExec.exe /X{GUID} is not an install location, so uninstall strings pointing at a shared uninstaller are rejected outright. And a name that two different applications both claim (three .NET runtimes differing only by version) produces no answer rather than a confident wrong one.
Fixes
Four places disagreed about how many updates were waiting. A scan finding 78 packages, two of which had an unreadable installed version, showed "78 updates waiting" in the title bar, 76 in the tile below it, 78 across the sidebar counts, and 76 rows in the table. There is now one definition of "offered", used by all four, and the scan summary says how many were hidden and why.
Retrying a failure erased the run. "Retry 1 failed" started a fresh run, which blanked the 73 rows that had just succeeded. A retry now continues the run it belongs to. Related: the run counters are derived from the jobs rather than tracked alongside them, so they cannot drift again.
A cancelled run showed "Selected: 73". The tile's label and its number were decided by two different conditions.
Exported logs were timestamped in UTC while their filename was local time: the same instant, two clocks, one file. Everything is local now, with the offset named in the header.
Failures dropped their exit code when the cause was recognised from the text. An OBS upgrade that failed with 0x8A150111 reported only "Something is using this package": true, unsearchable, and indistinguishable from the same message raised by a different manager for a different reason.
The shortcut census ran before every run, unannounced. Enumerating four Start Menu trees and resolving every .lnk through COM takes seconds at both ends of a run, and forty pip upgrades cannot break a shortcut. It now runs only when the update includes a desktop installer, says so in the transcript, and can be switched off in Settings.
"Last scan" froze mid-scan: it was computed at render time with nothing to trigger a render, so it ticked four times in nineteen seconds and stopped. Also: Ctrl+R no longer fires while Settings is open, and Escape now clears the search box once the filter and the run are dealt with.
Licence
Free software under the GNU AGPL v3 or later, with absolutely no warranty. Copyright © 2026 VagueDustin Enterprises. The product name, the VagueDustin Enterprises name, and the crest and gold-navy identity are not covered by the code licence.