Windows Firewall Control (WFC) by BiniSoft.org

@alexandrud thank you for the news!

someone is addicted to sex someone on cocaine, I'm addicted to your WFC program.
I wish you good luck in life

 

You also mentioned a new project before ... I guess that's on hold with your familial and work responsibilities!?

 

For now, yes.

 

Will it be implemented too?

 

Hello, it would be good an option that does not let finish WFC from the task manager.

 

Hello,
How do I block an app for just a specific IP and port , but allow for the rest of the internet?

 

@popescu

Let us assume your desire is to block outgoing IP 200.200.200.200 on port 8000 for app c:\example.exe only and allow the rest for this app ...

- Block rule outgoing:
path = c:\example.exe
IP = 200.200.200.200
port = 8000

- Allow rule outgoing:
path = c:\example.exe
IP-ranges= 0.0.0.0-200.200.200.199,200.200.200.201-255.255.255.255,::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
ports = 0-7999,8001-65535

 

so," IP ::" is equivalent to IP ZERO??
The order of rules is important? (which one is on the top?)

 

@popescu

Ooops, sorry - the ranges were not correct, I corrected it already in my posting above ...

And yes :: is zero but only for IPv6 format! Means 0000:0000:0000:0000:0000:0000:0000:0000

So it's then in long format 0000:0000:0000:0000:0000:0000:0000:0000-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff for IPv6 which means ALL IPv6 addresses.

And NO, the order of rules is never important in the WFwAs.

 

On the one side, WFC is a GUI only and NOT a firewall ... on the other side to not to miss any notifications, it would be indeed sensefully.

However: I THINK that would change the current product too much also related to the upcoming Malwarebytes product with integrated "WFC" too and I assume that Alexandru will not implement it ... but let us wait for his answer ...

 

Thank you very much for the answer, yes you are right. I was referring to cases like using FRST which can terminate the WFC process and remove all firewall rules and when I reset the pc again all WFC notifications.
I guess if FRST can do that a Malware can do it too. Perhaps the most accurate expression would be that it cannot delete the WFC rules with other tools but this could be a problem too. Well that was my concern with WFC.

Translated with www.DeepL.com/Translator (free version)

 

You are welcome! A little help is also the password protect within WFC in the left corner below ...

 

Hi @ Wilders

I need some help please.

I am using Win 10 latest version Windows Firewall Control (Binisoft) and Aomei Backupper

When I try to "Check For An Update" in Aomei with the program open, the check grinds on and on and nothing happens even though I have allowed it from the Connections Log.

On the other hand if I go to Program Files etc to Auto updater and click on it, the check is almost instantaneous and is not blocked.

I believe the problem is due to the fact that Update checking from within the program generates a temporary folder containing the Update.exe. Whereas the Update.exe in the ProgramFiles does not generate a Temp Folder.

It generates it here C:\Users\***\AppData\Local\Temp\AomeiTempFolderWith.exe

Thus every time Update is started it generates a new folder.

How do you make a rule in WFC (Binisoft) for a constantly changing temp file with update.exe in it? Or is there any other way of resolving this issue?

Thanks

Terry

 

Not possible, new path = new rule. This is how Windows Firewall works. Wildcards are not supported.

 

Create a shortcut and check for updates. But there is no point in checking for updates for Aomei Backupper.

 

Hi Aldist

"But there is no point in checking for updates for Aomei Backupper."

Why?

Thanks to everyone?

Terry

 

Folk want a new version!

 

Last time I tried it with the secure profile activated, the rules of running WFC couldn't be deleted by FRST. Not so when WFC isn't running so I guess it's ok.

 

WFC: Question about Startup:

Recently started using WFC and finding it a very useful improvement over the "raw" Windows Firewall.

My quick question is about startup - on a couple of occasions (random) after booting up my pc the WFC tray icon was missing (not hidden).
The wfc process and wfcs service was running, but I couldn't get the Main Panel up.

So I've decided to try something different with startup settings.
In WFC's main panel, I will disable the "start automatically at user logon" check box.
Instead I will add a simple shortcut (admin priv) to "wfc.exe" in the Startup folder for all users.

I am assuming that starting "wfc.exe" will automatically initiate the "wfcs" service.

Not knowing too much about WFC, my question to those more knowledgeable is whether
there are any disadvantages to such a move?

 

WFC has two unrelated startup entries, for the GUI and for the service.

You can run the GUI in any way, this will not change anything, since the service starts separately, the GUI does not affect the start of the service.
https://www.wilderssecurity.com/threads/windows-firewall-control-4.347370/page-96#post-2590481

 

The GUI (wfc.exe) will attempt to start the service (wfcs.exe) only if it is launched with admin privileges. Anyway, wfc.exe should not be executed as administrator.

 

Thanks Aldist, some really key info - checked and yes I found the two registry entries mentioned.
Also a useful link - now I know how to raise the GUI when the service is running but for some reason the icon is not present in the tray. So missing icon should no longer be a big deal for me.

And thanks Alexandrud for your cautionary note - it was exactly the trap I fell into: set up the wfc.exe shortcut with Admin privileges.

My takeaway overall is then: If the WFC icon does not show in the tray after reboot, simply try command line "wfc -mp" to make it pop up.
And if I get tired of that, I can set "wfc.exe" as a Start Menu item with non-elevated privileges and see whether that produces the tray icon more consistently.

May I confirm: even if the tray icon is missing or the wfc.exe process is not started or has stopped, the wfcs service will still work as usual, generating notifications if notifications were configured to be in force?

 

WFC is just a GUI. Evenif wfc.exe or wfcs.exe are stopped, Windows Firewall rules will be applied. If the wfcs.exe service is started, but not UI wfc.exe, the notifications system will work, Learning mode too. However, wfc.exe is the one that displays the notifications. Even if the tray icon is not there, the notifications will be displayed. The problem that you have can be solved by restarting wfc.exe process. If the wfc.exe is set to run with administrative privileges, the tray icon may not be displayed during Windows startup. A .NET Framework reinstall/repair may fix this problem.

 

Is it possible for the windows firewall to block domain names?

 

Windows Brandmauer, therefore, Windows Firewall Control does not support address resolving, so only IP addresses, not domain names.