Windows Firewall Control (WFC) by BiniSoft.org

These points are all now OK for me (the rest (not listed) is untested).

Thank you very much for the great update and have a nice weekend too!

Alpengreis

 

BUGS:

Build 4.4.1.0 (These issues were not occurring in 4.4.0.2).

A. In the WFC notification, Source and Remote contain same details.

Source should be local address and local port.



B. When specify local port in rule, applications cannot connect to network/remote address (test using SkyDrive). Delete all rules containing local port and then app connects.

 

I've made an outbound block rule for Windows Explorer across Domain/Public/Private. It was one of the first things I did when I saw WE in the Connections Log. The same with msiexec.exe in both system32/ and SysWOW64/

 

Windows Firewall Control v.4.4.1.1 - Quick fix

What's new:
- Fixed: Local source and remote IP address is the same in the notification dialog.

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

Have a great weekend,
Alexandru

 

Hello Alexandru, once again thanks a lot for the great updates.

When updating, I have not been asked to delete the certificates - and all 10 certificates are still there.
Win7, 64bit.

Enjoy your weekend

 

Later edit: It worked on my machines. I will test this more. Thank you for your feedback. You can manually delete ALL OF THEM them if their presence bothers you. They are not required anymore.

 

Can I delete them all - or is one of them still needed?

 

wfc.exe is set to launch at startup and both wfc.exe and wfcs.exe (v 4.2.1.0) are displayed as running processes in task manager on my win7 64 bit system. but i can't figure out how to display the program. when i click on either program, nothing appears. i suppose i'm missing something obvious. please advise.

 

Please use the dedicated forum topic instead of opening a new topic for this. Thank you for your understanding.
1. Try to install the latest version 4.4.1.1 and see if this behavior still occurs.
2. Check if Windows Firewall service is running.
3. Which icon is displayed in the system tray area for WFC ?

 

Just tried to update 4.4.1.1 over 4.4.0.1 and get the attached error.

Please advise.

 

Please go to that location and manually delete the file. It seems that the file is locked by another process. Then try to reinstall.

 

alexandrud
Thank you very much for the new update

 

[Bug] v4.4.1.0

I can no more open a rule such as ...



Then, after closing the rule manager and try to reopening, WFC crash.

Greetings,
Alpengreis

 

BUG:

Build 4.4.1.1

Sometimes secondary blacked-out WFC main panel appears after notification.

(Main panel is still present and normal.)

 

BUG:

Build 4.4.1.1

Previously reported issue persists: if include remote port in rule, then app cannot connect to network/remote address.

Used OneDrive (SkyDrive) to test.

If delete all rules with local port specified, then app connects.

 

Please export this rule and send it to me to import it. How do you define that remote address ? From WFwAS or from WFC ? The problem seems to be that protocol 34. I will fix this.

I can't reproduce this. Which steps do you do when this happens ? How to reproduce it ? Is it right after starting Windows ? Which .NET Framework version do you use ?

Please give more details. How does the rule that you create look like ? If you create a rule for a specific remote port and remote IP address, are you sure that the next time this program will use the same remote port and the same remote IP address ? In this case a new notification should be displayed.

 

Did anything happen in regards to firewall rules relating to applications installed in Sandboxie?

 

May I know is this a freeware? Thank You.

 

It is 'donationware'

 

Oh I see... So does it mean I wouldn't be able to use it if I do not donate?

 

You can still use it. If you do not donate then you won't be able to get notifications but everything else works.

 

And you receive a notification then, or not?

Also, please post your rule details here, else it's maybe too complicated to resolve this behaviour.

Note: local rules change (in much cases) very often (I don't use Skydrive, so I don't know there). This means: if you have an allow rule created with ONE local port and the local port changes, then it's clear, the program can not make a successful outbound traffic. But then, you should receive a notification.

 

I get white alert message windows and the main program's interface doesn't respond to user input. I have to uninstall the program to get Internet access on my machine again since the program doesn't function properly.

 

Hello Alpengreis,

After respond to initial notification, and set local port, app does not connect to network/remote address. New notification is generated after app tries new connection.

To solve problem I have create Allow rule that specifies no local port...which is what I normally do, but just testing WFC to see if including local ports works. Currently, it does not.

If I am not mistaken Alexandru uses W8.1 on one of his systems so he can verify this issue by testing it with OneDrive.