Fort Firewall 3.20.5 was released to fix a regression from version 3.20.4, where the "Clear Alerts" button failed to clear an underlying kernel driver flag, causing repeated notifications. The developer quickly addressed the issue after a user reported it on GitHub, managing to reproduce and patch the bug all within a single afternoon. This release also included a refinement to the Network Filter UI, showcasing the efficiency of a solo maintainer in handling bug fixes. Despite its strengths, including its own kernel driver and per-program control, users must disable Windows Memory Integrity to use Fort, raising concerns about security and trust in a solo project

Fort Firewall 3.20.5 Fixes Same-Day Bug, Lands After Single-Afternoon Patch

Fort Firewall 3.20.5 closing a regression from v3.20.4 where dismissing an alert stopped clearing the underlying kernel driver flag. A single user reported the issue on GitHub, the solo developer reproduced it, and shipped the fix all within one afternoon. The patch also tweaks the Network Filter UI, though its bigger story is how fast a lone maintainer can run a bug-fix loop. The free, open-source Windows firewall does demand you disable Windows Memory Integrity to run its kernel driver.

Fort Firewall 3.20.5 Fixes Same-Day Bug, Lands After Single-Afternoon Patch @ NT Compatible