I recently shared my free Windows hardening tool, WinSystemHarden, on Indie Hackers. This post is a post-mortem of that discussion.
There’s no shortage of one-size-fits-all PowerShell scripts floating around, and they often end up breaking local printers or network shares. My goal was to build a simple GUI tool with 29 core rules. It captures snapshots of the registry and ACL permissions before making any changes, with one-click rollback.
V1.3 is live right now. After posting, I got some incredibly sharp feedback from other engineers. A handful of comments laid out blind spots I hadn’t considered at all. This is my unfiltered take on what I missed, and how I plan to fix it.
Deep Dive 1: The "Half-Bricked" State on Crash
One person asked a really good question: what happens if the machine crashes or loses power mid-rule application? Does rollback still work?
Honest answer: in the current V1.3 build, snapshots only live in memory until all rules finish applying successfully.…