A small, technical fix from a routine code audit, worth explaining since it's the kind of bug that's invisible until it isn't.
Both features run a short Windows command (powercfg for the battery report, ipconfig for DNS) and were capturing its output, even though nothing in PurgeCore ever read that output. That's a classic trap: if a captured process ever writes more text than fits in Windows' small internal buffer, it can freeze completely, silently waiting for someone to read it, while PurgeCore waits for it to finish. Neither command was likely to print enough text to trigger it, but it's a real risk that shouldn't be sitting in the code regardless. Both no longer capture output they never use.
A small memory cleanup detail in the supporters list feature, no user-visible effect.
Free forever, no account, no trial.
Download for WindowsNo 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.