Stop binaries in a folder from phoning home.
Creates Windows Firewall rules to block inbound + outbound network traffic for every executable inside a directory you pick.
Grab the latest portable build: BlockAll.exe (~69 MB, self-contained — no .NET runtime install required).
Double-click. Accept the UAC prompt. That's it.
Recursively walks a folder, finds every file matching a configurable set of extensions (*.exe, *.dll, *.js, *.swf, *.api, *.ocx by default), and creates two Windows Firewall rules per file — one inbound, one outbound — across all three profiles (Domain / Private / Public).
Uses direct INetFwPolicy2 COM access; orders of magnitude faster than New-NetFirewallRule. Thousands of rules per second on a warm firewall service.
- Folder picker + drag-drop a folder anywhere onto the window.
- Live progress bar with ETA and rules-per-second readout.
- Session history persisted to
%LOCALAPPDATA%\BlockAll\history.json— every block run is recorded. - One-click Undo for any past session.
- Hash-pinning (SHA-256 per file): a Verify command flags any file an installer has swapped out from under your rules.
- Firewall snapshot taken before every session (
netsh advfirewall export) as a defensive backup. - Re-scan: catches up missing rules and picks up new files added since the last run. Works across machines.
- Portable session file: each run drops
BlockAll-session.json+BlockAll-summary.txtinto the target folder. Copy the folder to another machine and re-scan there — same rules, no extra setup. - Explorer right-click integration (opt-in): adds "BlockAll this folder" to the folder context menu.
- Double-click
BlockAll.exe. Accept the UAC prompt. - Click Browse…, drag a folder onto the window, or paste a path into the box.
- Adjust the extension list if you want.
- Click Block.
Rules appear in wf.msc (Windows Defender Firewall with Advanced Security) under group name BlockAll-<8-char-id> — two rules per file (-IN and -OUT).
To remove the rules later, right-click the session in the history grid and choose Undo.
Click Block on a folder that already has a BlockAll-session.json and you'll be asked:
It looks like this directory has already been scanned. Would you like to re-scan it?
- Yes — top up missing rules and add any newly-discovered files.
- No — start a fresh session (replaces the existing summary).
- Cancel — bail.
Copy the target folder (with the BlockAll-session.json in it) to the second machine. Open BlockAll there, point it at the folder, click Block, choose Re-scan. Same rules get created.
Requires the .NET 8 SDK.
cd src/BlockAll
dotnet publish -c Release -o ../../distOutput: dist/BlockAll.exe — single-file, self-contained, ~69 MB.
- Requires Administrator (firewall rules need elevation; the manifest self-elevates on launch).
- Tested on Windows 10 22H2 and Windows 11.
- Rules apply to all three firewall profiles (Domain, Private, Public). Direction is always inbound + outbound.
- BlockAll does not phone home, does not touch the network, and stores nothing outside
%LOCALAPPDATA%\BlockAll, the target folder, and the Windows Firewall ruleset.