I'm using Netlimiter with its great Blocker firewall. It's only the one firewall(comodo is one) that actually stops any, to connect outside. Somethin like this: Windows Firewall Control, -VLC( or malware) wants to connect outside, WFC prompts, want you block or not. Too late, connection was made Fort firewall, -VLC(or malware) connected to the server However, Netlimiter Blocker; stops it. Completely.
You are most likely referring to DNS, which is generally allowed in firewalls for obvious reasons, but can be blocked and allowed only per app, then you would also get a prompt.
I have to disagree with the highlighted part. When WFC displays a notification, the connection was blocked, not allowed, so it can't be too late. The connection is blocked, not paused, therefore the software must retry the connection.
Yeah pretty much, also can see how apps are coded these days, 20 years ago if an app tried to connect to the net, it was polite, it would wait 30 seconds, then try again "once", then wait again or hard fail. Now if e.g. Office365 has updated itself (in a new version path, the idiots), I see the local port rapidly rise on the notification as its trying repeatedly rapidly, as if it thinks the situation will change if it does that. WFC handles this really well, barely any CPU usage, one of the alternative WF products, would fall over in this situation.
Yes, I have also not seen any connections being made, when apps are being blocked by SpyShelter, WFC and TinyWall, so I'm not sure what topicstarter means.
