This project has moved. For the latest updates, please go here.


Windows Firewall Notifier does not require to be "installed", but rather unzipped and optionally activated if you want to use the outbound connection notifications (it must then be placed in a shared folder, like Program Files or alike). NOTE: Currently WFN writes its logfile to this directory, so the directory has to be writable. Program Files often isn't...!
If you want to enable the notifications, please launch the WFN.exe component, and then go to Notifications Options menu entry.
If not, no change will be made to your system and you can use it as a "portable" application.


Simply unzip and launch WFN.exe to have an overview of the currently open connections, to access the Windows firewall log (if enabled) and go through the existing rules.
Notifier.exe and RuleManager.exe are not meant to be used directly.


Please disable the notifications first through the corresponding menu; you can then safely manually delete the WFN files.

What WFN is not

WFN is not a full-featured firewall, but an extension build upon the Windows Filtering Platform (WFP). Basically, it enhances the Windows Firewall. The goal is to keep WFN as light-weight as possible, and to keep system resource usage down as much as possible.
This means that many 'advanced' features firewall products often boast with, cannot be offered by WFN. Additionally, the way WFN attaches to WFP means there are certain limitations that are important to note. For one, WFN cannot suspend a program so that an "Allow" rule can be created before the connection gets blocked: the Windows Firewall first blocks the connection attempt, and only then does WFN active. This means you'll have to retry the connection after making the rule.

Last edited Feb 20 at 5:43 PM by DanielPharos, version 8