← Back to blog

PurgeCore v1.11.5: Two False-Positive Bugs Fixed

2026

Fixed: browser cleanup could wrongly report a browser as open

The lock check used a single strict attempt to open each file exclusively. That's the right test in principle, but a single attempt could misfire on Windows Search indexing, antivirus real-time scanning, or a browser that just closed but hadn't released its SQLite journal file yet, none of which mean the browser is genuinely still open. It now retries a couple of times over roughly 300ms before concluding a file is actually locked. Files that are already free are unaffected, no added delay.

Fixed: the startup manager could keep showing a stale disabled state

Some programs re-add their own Run key entry the next time they start, a real, common safeguard many apps have against exactly this kind of tool disabling them. When that happened, PurgeCore kept trusting its own backup of "you disabled this" instead of the registry's actual current state, showing the item as disabled (or even listing it twice) when it had, in fact, come back on its own. The list now reconciles with the registry on every scan, so it reflects what's actually there rather than PurgeCore's last action on it.

Download v1.11.5

Free forever, no account, no trial.

Download for Windows

No commercial code-signing certificate yet, so Windows may show a brief "unknown publisher" warning on first run. The source is public on GitHub, and each release is published with a SHA-256 checksum you can verify.