(A former version was having trouble with Microsoft’s phoning-home-functionality of Windows 8 whenever a known executable was started. For the created "WindowsFirewallNotifierTask" at the Task Scheduler I change the rule for new instances (properties -> settings) from parallel execution to enqueuing them. Just two notes on my own configuration which I slightly adapted from the default one:ġ. In this case the overhead for your daily security is absolutely zero (assuming that your Windows Firewall will be running anyway). You can disable the tool at every point in time (and even delete its directory) and still keep all created rules for your firewall configuration. Per click you can add an allow- or block-rule (or a temporary exception). This triggers a little tool to show the attempt to the user and ask for permission for later attempts. The WFN sets the outgoing connections to be blocked by default and schedules an event for every connection attempt which was blocked. The notifier itself is portable and does not need frequent security updates like other tools which are "online" themselves - since the important parts will be maintained by Microsoft. It does rely on the Windows Firewall which is indeed a complete firewall (at least in more current Windows versions) but is not preconfigured as one.īesides that, only the Windows Task Scheduler is needed. You can use the "Windows Firewall Notifier" ( or from several download portals).ĭon't get distracted by the "Beta"-hint in its version or the fact that there was no new release for some time now. There is still an answer for your question if someone else needs a very slim alternative:
0 kommentar(er)
