SimpleWall 3.9.1 appeared on GitHub in July 2026, and people searching for it usually want two answers: is it worth installing instead of 3.8.7, and how do the custom rules actually work? Everything below comes from the project’s GitHub release notes, checksum files and README, checked on 17 November 2026. We have not installed 3.9.1 ourselves (Not tested yet), so no step here relies on screenshots or menu paths we have not seen.
The short answer
SimpleWall 3.9.1 is a pre-release. On 17 November 2026 the release GitHub marks as “latest” is still 3.8.7 from August 2025, even though the repository received commits as recently as 13 November. Most of the new things arrived in 3.9 (a longer rule limit, saner rules created from the log, profile paths with environment variables, fixes for log access and crashes); 3.9.1 adds network speed statistics, an option to keep blocked inbound packets out of the log, and a fix for repeated notifications. If you run a single admin workstation and those fixes matter to you, 3.9.1 is reasonable to try. For machines other people depend on, stay on 3.8.7 until the author promotes a 3.9.x build to stable.
3.8.7, 3.9 and 3.9.1 side by side
| Item | 3.8.7 | 3.9 | 3.9.1 |
|---|---|---|---|
| Release date on GitHub | 8 August 2025 | 21 July 2026 | 22 July 2026 |
| Release status | Stable, marked “latest” | Pre-release | Pre-release |
| Type, per the notes | Maintenance | Features | Maintenance |
| Builds listed in the .sha256 file | 32-bit, 64-bit, ARM64 | 64-bit, ARM64 | 64-bit, ARM64 |
| Installer size | 1.2 MB | 0.88 MB | 0.88 MB |
| Portable archive (bin.7z) | 0.94 MB | 0.78 MB | 0.78 MB |
| Rule length limit | Shorter (issue #809) | 1024 characters | 1024 characters |
| Network speed statistics | No | No | Yes |
| Option to exclude inbound blocked packets | No | No | Yes |
| Integrity files | .sha256 and installer .sig | .sha256 and installer .sig | .sha256 and installer .sig |
| Licence | Free, open source (GPL v3) in all three | ||
One detail for older hardware: the 3.8.7 checksum file lists a 32-bit simplewall.exe, while the 3.9 and 3.9.1 files list only 64-bit and ARM64. The release notes do not mention this change, so check the file list before you plan to roll 3.9.1 onto a 32-bit Windows install. The README lists Windows 7, 8, 8.1, 10 and 11 as supported.
What changed in 3.9
The 3.9 notes describe a feature release. The changes that affect daily rule work:
- Rules up to 1024 characters. A long list of addresses or ports separated by semicolons now fits in one rule (issue #809).
- Rules created from the network or log lists no longer include local IP addresses.
- Resolve network addresses is now on by default.
- Profiles save paths with environment variables. That makes a profile copied to another PC more likely to match the same programs.
- Fixes: saving a profile with a read-only attribute, log subscription returning “access denied”, a crash when loading the notification dialog, a disappearing search box, possible memory leaks.
What changed in 3.9.1
3.9.1 shipped one day after 3.9 as a maintenance release with four items: network statistics with connection speed, an option to exclude inbound blocked packets (useful when broadcast noise floods the log), a fix for repeated notifications, and an updated IGMP rule. If the same notification keeps coming back on 3.8.7, that is the bug this release addresses.
How SimpleWall rules work
SimpleWall writes its own filters to the Windows Filtering Platform. It is not a front end for Windows Firewall, and the two run independently. In the default configuration it blocks all applications, so the work is mostly deciding what to allow. Per-program allow and block decisions are made in the app lists and notifications; the rules editor is for anything more specific. It has two kinds of user rules:
- Global rules apply to every application, for example “block outbound SMB to the internet”.
- Special rules apply only to the programs you add on the rule’s Apps tab, for example “this backup agent may reach only the NAS”.
Remote and local fields accept the formats documented in the README. Separate several values with a semicolon:
| What you need | Syntax |
|---|---|
| Single addresses | 192.168.0.10; [fc00::1] |
| Address and port | 192.168.0.10:443; [fc00::1]:443 |
| Address range | 192.168.0.1-192.168.0.255 |
| Range with port | 192.168.0.1-192.168.0.255:80 |
| Subnet (CIDR) | 192.168.0.0/24; fe80::/10 |
| Ports and port ranges | 21; 80; 443; 49152-65534 |
A practical pattern for an admin PC: one special rule per sensitive tool (remote support, backup agent, update tool) with a narrow remote address list, plus a small set of global block rules for things nothing should do, such as outbound SMB beyond your own subnets. Keep each rule to one purpose: with 1024 characters a rule can hold a long address list, but small rules are easier to audit.
Blocklist instead of allow-list
The old blacklist mode was removed. The README describes how to rebuild it: in Settings, Rules, untick “Block outbound for all” and “Block inbound for all”, then create a user rule with the block action, any direction and empty local and remote fields, and assign it to the programs you want to cut off. Everything else is then allowed, which is weaker protection, so use it only where an allow-list is impractical.
Permanent, temporary and command line
When you enable filtering you choose permanent rules (active until you disable them) or temporary rules (reset at the next reboot). Temporary mode is the safe way to try a new rule set on a remote machine. The same choice is available from the command line: -install, -install -temp, -install -silent and -uninstall. Filters stay in place when SimpleWall is closed and even after it is uninstalled, until you press “Disable filters” or run -uninstall.
Should you upgrade?
- You hit repeated notifications, log “access denied” or the notification-dialog crash. Try 3.9.1 on that machine.
- You need rules longer than the old limit. 3.9.x.
- The PC runs 32-bit Windows. Stay on 3.8.7; the 3.9.1 checksum file lists no 32-bit build.
- Other people depend on the machine. Stay on the stable 3.8.7 for now.
Whatever you choose, compare the file hash with the release’s .sha256 list before running the installer with administrator rights, and export your profile first. Download and first-setup steps are on our SimpleWall page. If you are still choosing a firewall, see SimpleWall vs TinyWall, Comodo Firewall, GlassWire for traffic graphs, and our guide to free firewall software for Windows. The full rule reference is in the project’s README on GitHub.
FAQ
How do I use SimpleWall?
Run it as administrator, tick the programs and services you need in the app lists, then enable filtering. Answer the notifications for programs you missed, and add rules in the rules editor only where an app-level allow is too broad.
Does SimpleWall work on Windows 11?
The README lists Windows 7, 8, 8.1, 10 and 11, 64-bit and ARM64. We have not tested 3.9.1 on Windows 11 ourselves.
Does SimpleWall still support Windows 7?
Windows 7 is still in the README’s list. For Windows 7 the README names update KB3063858 as required. Dropped-packet logging works from Windows 7, allowed-packet logging from Windows 8.
Why does Windows Update stop working with SimpleWall?
Because everything is blocked by default, including services. Allow the update-related services, and check that the built-in blocklist is not set to block update endpoints.
Why does the network icon show an exclamation mark?
Windows checks connectivity with NCSI probes. The README’s first fix is to keep the NCSI system rule allowed; it is enabled by default.
Is SimpleWall safe to download?
Take it only from the author’s GitHub repository. Each release lists SHA-256 hashes, and the installer has a GPG signature (key ID 0x5635B5FD), so you can check a file before running it.







