Windows Firewall Control (WFC) by BiniSoft.org

Thanks for the reply, will do that later & report back.

I have tried uninstalling v.4.0.2.2 & re-installing it again, but the same error still occurred.

After that, I have tried uninstalling v.4.0.2.2 & re-installing v.4.0.2.0. The error is no longer there when accessing the control panel.

 

Hello alexandrud,

I have tried installing v4.0.2.2 over v4.0.2.0, the same error appeared (before & after editing the regedit entries).

I have uninstalled v4.0.2.2 & installed back v4.0.2.0.

Let me know if you need me to try other methods.

Thanks.

 

What is the value of PlacementControlPanel key ? The crash occurs only when you try to open the Control Panel window ? My guess is that this has something to do with the new code that was implemented to avoid windows to open out of the screen.

 

W7 Pro 64
no problems with 4.0.2.2

Would it be possible to make the new Properties window resizable? Having to scroll is a bit more inconvenient than having 2 tabs, not much more, but resizing would be the best.

J

 

Yes. In the next version I will make it resizable.

 

Yes, only when opening the Control Panel.

Here is the screen print before updating from v.4.0.2.0 to v.4.0.2.2



The value after updating to v.4.0.2.2 & editing the registries, the new value

 

I understand that, but since it's system files I just wanted to double check

http://i.imgur.com/uL9RFcL.png

 

Odd. I have only integer values saved as coordinates. In your screenshot I see that you have double values. When it tries to convert back to integer, it fails. Do you use a custom DPI setting ? Maybe this is why on your computer the coordinates are saved as doubles. Anyway, I know what the problem is and I will provide a fix very soon.

 

Windows Firewall Control v.4.0.2.4 - Fast Update

What's new:
- Fixed: Control Panel window crashes on open if the DPI is different than the default value.
- Updated: Properties dialog from where a user can modify a rule is now resizable. Also, the position and state is saved on closing.

Installation notes: Just use the updater to update to the new version. That's all.

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

If you find any problems with this release please report them and I will fix them shortly. Also, if you have new features in mind, please share them and if it is possible I will implement them.

Thank you for your support and your feedback,
The developer

 

@alexandrud

Thank you for the update. Now the Windows Update works fine unter w8.1x64.

 

Nice work as always

 

Thanks alexandrud.

Yes I am using a custom DPI setting - 125%.

I have installed v.4.0.2.4 & it is working perfectly.

 

No problems here.

Thanks,
Robert

 

Alexandrud, when I open 'Manage Rules' then maximize the window and close it now sometimes it opens minimized...never did that before.

Robert

 

Just updated to v4.0.2.4, Windows Updates was still working fine with the old rule in place, so decided to disable all SVCHost rules except the old Windows Update rule; it turns out that rule on its own wasn't letting Windows Update check for updates. It was that rule along with the following Outbound rules, which were automatically created when I enabled the "Hyper-V" feature of Windows 8 on my Surface Pro:

Program: C:\windows\system32\svchost.exe
Name: Hyper-V - WMI (TCP-Out)
Group: @%systemroot%\system32\vmms.exe,-210
Description: Outbound rule for Hyper-V to allow remote WMI traffic. [TCP]
Location: ALL
Protocol: TCP, All Local Ports, All Remote Ports
Address: Any Local Address, Any Remote Address
Service: Windows Management Instrumentation

Program: C:\windows\system32\svchost.exe
Name: Hyper-V Management Clients - WMI (TCP-Out)
Group: @%ProgramFiles%\Hyper-V\SnapInAbout.dll,-211
Description: Outbound rule for the Hyper-V management clients to allow remote WMI traffic. [TCP]
Location: ALL
Protocol: TCP, All Local Ports, All Remote Ports
Address: Any Local Address, Any Remote Address
Service: Windows Management Instrumentation​

Kinda odd but, although their only difference is their name, group name and description (parts I thought don't affect the behaviour of the rule), having only one of them allowed (through Windows Firewall) alongside the old Windows update service rule results in Windows Update check failing with error code "80072EFD". Also, having both of them allowed and the old Windows update service rule blocked results in the same error code. In other words, all three of those rules need to be allowed in order for Windows Update to work...here's the old Windows Update service rule just for clarification:

Program: C:\windows\system32\svchost.exe
Name: WFC - Windows Update
Group: Windows Firewall Control
Description: Allow Windows Update to check and install new updates.
Location: ALL
Protocol: TCP, All Local Ports, All Remote Ports
Address: Any Local Address, Any Remote Address
Service: Windows Update​

Gonna keep my rules as they are until we find a way to narrow down the new Windows update rule.

 

Indeed, sometimes it does this. I will fix this. Thank you for reporting it.

 

Hi alexandrud,

two things ...

1) Could you expand the search function to all fields (for example search in Group-field)?

2) Since even local addresses can be defined, they should be visible in the Manager window.

Greetings,
Alpengreis (formerly SwissBIT)

 

1) No. The search is made in the Name and Program columns only, to easily find a specific program. For groups, many rules share the same group name and you can sort the data grid by that column to group them. The same apply to all the other columns.

2) Local Addresses and Description columns are already there. Right click on the data grid header and check them from the context menu to be visible. By default they are hidden because just a few users will actually use them and this is the reason why by default they are hidden.

 

Yes, I've often made it ​​with the Sorting. A search function would have been even better - but if it's technically not feasible ...

Ohh, how STUPID of me!

Thank you,
Alpengreis

 

Alexandrud, updated to 8.1 today. Seems like WFC doesn't work with it. Will you be updating it to be compatible with 8.1 real soon?

Thanks,
Robert

 

Please share your feedback. What does not work ? Latest version of WFC is compiled on Windows 8.1 and works fine on this new version of Windows.

 

Sorry did not know that.

So far:

1) Windows Update no longer connects (Original WFC rule).
2) Manage rules list not from latest event to last events like before (I do not mean alphabetized).

Robert

 

Changed in 'WFC-Windows Update' in 'Service' tab from 'Windows Update' to 'All' and now it works.

When I change it back to 'Windows Update' it returns 'wuauserv' (Windows Update Service) instead of 'Windows Update'. That's why the original rule does not work IMO.

Robert

 

The new rule for Windows Update is for svchost.exe for remote ports 80,443 on TCP protocol, without any service set. The old rule was set for Windows Update service (wuauserv is the short name, but they refer to the same thing). If you recreate the recommended rule, this is the rule that is created for Windows Update.

Regarding the second problem, WFC acts as usual, the latest entries (rules) are on top of the list. They do not appear this way on your machine when you first open Manage Rules window ?

 

No.

1) WFC alerts.
2) Create rule.
3) Open 'Manage Rules'.
4) Newly created rule first on list.
5) Thereafter, rules are from the bottom (original WFC install rules and then user made rules) not the latest entries like before.
6) Rules created yesterday and before are last.

Hope you know what I mean.

Thanks,
Robert