Windows Firewall Control (WFC) by BiniSoft.org

[Bug-Report (v4.2.0.2)]

Notification-System for ICMPv6 is broken ...

Reproducable preparation:
- OS = Win 7 x64
- WFC-Profile = Medium
- WFC-Notification-Level = High
- There is no exist (enabled) allow rule for this.
- There is no exist (enabled) block rule for this.

Enter the following Command in Command Prompt:

ping -6 google.ch

Notes:
- With ICMPv4 (ping), the notify works correct.

Regards,

Alpengreis

 

Not really broken, but missing. This was never supported. Only blocked connections on protocols TCP, UDP and ICMPv4 can generate notifications.

 

Oh, okay, sorry!

I had not noticed this.

Previously I needed not/barely IPv6 stuff. Now this has changed, since more and more comes with IPv6 support.

Can you support this protocol for notifications too?

Alpengreis

 

I guess, I could give it a try.

 

Awesome update alexandrud. Just a little heads up, the following bug fix that you made in v4.2.0.1 was in fact the fix for Secure Boot in my case...I always restarted my PC whenever I attempted testing this feature, so, it never triggered the Secure Boot, until now

Just wish the automatic switch to the medium filtering profile would come back...

 

I am trying to install GitHub for Windows. It is a click-once application. Windows Firewall Control is not allowing to connect to the internet. And there is no way I can manually add the program since program is ".application".

 

Use Low Filtering profile when installing this software. Windows Firewall Control does not block the installer, Windows Firewall does. Do you have notifications enabled ?

 

[Bug-Report (v4.2.0.2)]

Duplicate rules with change the allow/block-state after is broken resp. works not correct.

Reproducable with following steps:

1. Duplicate an ALLOW rule
2. Change this duplicated rule to BLOCK WITHIN RULE PROPERTIES WINDOW
3. Press REFRESH LIST

Now, the rule is set to ALLOW AGAIN, which is not desired.

The same behaviour is also vice versa.


[Crash-Report (v4.2.0.2)]

After long working in the Rule Manager window, WFC (at least the Rule Manager window) has crashed resp freezed. No reaction to key input, close (with mouse) was possible but after reopen, the window was much smaller and with white content.

This is the WFC-Log screenshot ...



And another one (without any reaction, even closing with mouse was not possible) ...



Maybe you can use the infos for debugging or something like that. Maybe it's unrepeatable ...

Regards,

Alpengreis

EDIT: More info for step 2
EDIT2: Added Crash-Report
EDIT3: Added Crash-Report no. 2

 

I do have notifications enabled set to Medium. But I am not getting notification.
I tried with low profile and also tried with no filtering.
May be something wrong with github setup. I will try on virtual machine and let you know.

 

I apologize. It was not firewall control. It was github application itself. I uninstalled completely and reinstall and it worked.

Thanks for your help and thanks for awesome product.

 

Windows Firewall Control v.4.2.1.0

What's new:
- New: Added a shortcut to Windows Firewall Control Panel applet in the Tools tab.
- Improved: The notification dialog was updated to contain more useful data. The Protocol selection is now a combo box which contains all supported protocols. The same applies for Direction selection.
- Improved: The notification dialog will display an (x86) indicator at the end of the file name for executable files executed from Program Files (x86) folder.
- Improved: Radio buttons for Direction and Action in Properties dialog were replaced with combo boxes.
- Fixed: Changing the action between Block/Allow in Properties dialog of a rule does not update the rule. After a refresh of the rules, the Action is the same.
- Fixed: Main Panel window does not stay on top of other windows when the activation dialog is displayed.
- Fixed: Program exits if the user starts Manage Rules, stops Windows Firewall service and then presses on the refresh button to query Windows Firewall rules.
- Update: The Main Panel was rewritten to load the tab items on demand, not all at once. Code refactoring.

New translation strings:
505 = Windows Firewall Control Panel applet
940 = Can't connect to Windows Firewall Control service

Installation notes: Just use the new installer to update to this new version.

Download location: http://binisoft.org/download/wfc4setup.exe
SHA1: 465bb83f612ed6952721ce79c14300634c1c5556

Have a great weekend,
Alexandru

P.S.: The list of new features is still open. Please share your feedback.

 

Thank you!

Running it now.

 

Awesome update! Liking the new notification dialog. Little suggestions about it:

- Widen the "Process ID" label to avoid the overflow indicator (...).
- Add an option to "Copy Name" by clicking the "Name" entry in the notification dialog.

​

 

I also use Windows 8.1 and the texts that I marked fit correctly. I will expand that text block, or I can rename the string "PID" instead of "Process ID". I will think about it. Regarding the Name, I will add the option to copy it to clipboard even if I'm not sure if this is helpful. This functionality already exists on the program icon, to copy the full path or the file name. In your case, it makes sense to search the web for hp.aioremote.exe but for I don't know if a search for PrinterControl4 will give you relevant results.

 

Alexandru,

with the new version, the process id is not showing on my PC.

Screensize: 1920x1080, zoom size 100% (standard)

 

It would be possible to create a real auto update, right now WFC doesn't check automatically for new updates and the updating process is manual although light, it would be wonderful no to bother about it a make the software able to autoupdate.

What about features like
anti-ARP spoofing, protocol Analysis, Filter loopback traffic and Fragmented IP traffic. Probably the only useful would be the loopback traffic filter. I guess this wont' be possible with WF
What about to give the option to create predefine templates for rules and ports?

Besides this is there a roadmap? Until now it looks like you are fixing bugs and adding features extremely quickly when these are requested in the forum, which is really admirable, I'm just wondering if you have some kind of roadmap.

 

Some people don't like software with "auto-home-call" function - so, IF integrate, then as CONFIGURABLE feature (Auto-Update-Check: On/Off) and Off by default.

 

Maybe could implements a schedule update task using task manager
which could make sure the updates could deliverer to end-users properly also the end users will keeps the WFC always up to date as well

 

It seems that the notification dialog has the old size. Execute: wfc -reset in the run dialog to reset the user settings. Or run regedit and delete the following key HKEY_CURRENT_USER\Software\BiniSoft.org\Windows Firewall Control\PlacementNotification. This will solve the problem you have described.

An auto update feature is possible, but we do not like programs that phone home and I tried to avoid this. For now, the user must check manually if an update is available. Clicking on the Check if a new version is available button once a month or two, is not that hard. But, I will think about it.

Features like anti-ARP spoofing, protocol Analysis, Filter loopback traffic and Fragmented IP traffic are not possible in WFC because it doesn't do any packet filtering. Adding templates for rules will increase the complexity of the software and this is not really desired.

The roadmap is not public.

 

An an option to auto purge invalid rules?

 

There is a button named Find invalid rules in Manage Rules window. This will select all rules defined for files that are not found anymore on your computer.

 

Holy crap, this is an awesome feature!

 

Indeed, that's true

 

Is this normal for these rules to be blocked?

 

This is a major bug.
These rules are optional and when you install WFC you have the possibility to create the WFC recommended rules or not. These block rules are created for privacy purposes because the connections covered by these rules are not requested by the user and they are encrypted. Nobody knows actually what information is sent from our computers to Microsoft servers. You can easily delete these rules if they don't suit your needs. Many users requested them and they were added in Windows Firewall Control.