Even if it is easy to do this, it probably won't happen since the decision to make a new release must be now approved by a lot of people.
If you are running any software that takes a while to close, then the operating system will just kill the other processes in order to shut down....
Not really possible because the connection was already blocked, not paused. But, you can create a temporary allow rule which will get removed...
Please read the post below to understand what means all connections. It depends on the number of connections and on the size of the Security log....
The problem is that WFC development is currently very slow. I will take a look at these but I can't promise anything.
There is no progress. Microsoft did not bother to answer or to fix the issue in their code. WFC can't add a workaround either. I tried to parse...
Just a curiosity. It happens with WFC version 5.3.1.0 which is unsigned or with the digitally signed version 5.4.0.0 ?
WFC installer gives that warning if it finds another firewall registered in Windows Security Center. Do nothing but if you encounter connectivity...
I'm staying with WFC :) Most of WFC features were implemented many years ago and they are still working. As I mentioned before, if a critical bug...
I don't know, but Windows Firewall has control over outbound filtering since Windows Vista, so if they had this in plan, they would have done this...
It depends on your expectations. For the inability to prevent parent launching child, you already know my opinion. As for domain named based...
You are asking for something that Windows Firewall does not support and it has nothing to do with WFC. Windows Firewall does not support creating...
It would be a rule that will allow all connections for that specific application.
A release that fixes things will do the same steps: keeps settings, uninstall, install again. The problem with Windows Updates, especially large...
Create a new rule, the wizard opens. When asked to enter a path, use the "System" keyword (no quotes). Next, Next, Next. [ATTACH] Windows...
System is not system.exe, it is just System in Windows Firewall, it is a keyword. If Windows Firewall Notifier uses the same Windows Firewall...
Separate names with a comma.
