Windows Firewall Control (WFC) by BiniSoft.org

ok so in SCU, v5.3.0 even with SecureRule enabled, WFC asks for Metro Apps' outbound connection.

 

@alexandrud

Thank you for the hard work & all the best!

 

I second this.

Compliments carrying this excellent software and effort all this time. Amazing!

Super support-time tested!

 

@alexandrud
i'm using 5.3.0.0 on Windows 10 x64 1803 (SCU) and can't seem turn off "secure rules" or "secure profile". If i untick either or both of them and close the gui, the next time i open the gui they are ticked again.
I've tried exporting the options to see if i can force the state of these settings, but if i open the settings file in notepad, there's no reference to "secure rules" or "secure profile", only "secure boot". it's as if these options don't exist!

i've uninstalled and reinstalled wfc but this has also made no difference.

 

These settings do not appear in the exported user settings file because they are external to WFC. They are not exported or imported. They have to be set manually.

I am still on version 1709 where this problem does not occur. On some 1803 systems, I had some reports that these two settings are not remembered correctly. It seems that WFC may enable these two settings when the Main Panel is closed on 1803 build. My recommendation is to use WFC version 5.0.2.0.

 

As always Alex, you have demonstrated integrity and honor!

Robert

P.S. I hope you made a ton of money. WFC has ALWAYS cost only $10 for this superlative product.

 

I can second that and his support was and is just GREAT

 

Now the party is over now, who knows what's next?
Take off the party hats and leave the room.
Was great, time to move on.

 

This is disappointing. Looks like I need to look elsewhere.

 

@alexandrud can you remove the 3 activations per day limit, it is annoying when you have multiple machines to downgrade...especially for people having different timezone than the server...

 

He already reported that he does not have the rights and access.

 

I can't do this anymore.

 

Kinda sad this is dead not even day zero into RS4, people who were like, it's just a front end for window firewall, it'll work for years, and now it seems to have this "game" breaking bug with secure rules already. Also FML, I bought my brother this for his new computer about 2 weeks before alexandrud made his announcement, well that won't get much use...

 

Yeah! another lifetime licence who dies before me...

 

This is a normal process. No one even hoped that the children and grandchildren of the developer would continue to activate the WFC

 

I expected it, remember my post? https://www.wilderssecurity.com/thr...-by-binisoft-org.347370/page-166#post-2749023

5.3.0 is Bin-ed, now let see how long v5.0.20 will last without issues.

 

You'd rather die and WFC to resume development? I guess that's generous.

 

That make sense. Thank you.

I've done some testing on my system and both settings (Secure Rules and Secure Profile) are actually working correctly in 5.3.0.0. Ticking and unticking these settings is enabling and disabling the protection of the relevant registry keys.

However, it appears that on 1803 on my system, WFC is unable to determine the real status of these two settings (I'm seeing a BUFFER TOO SMALL error for RegQueryKeySecurity in Process Monitor) and always shows them both as enabled in the Main Panel even if they're not.

Thankfully, the current protection status doesn't change when I close the Main Panel, exit WFC, restart the WFC service or reboot the PC.

Knowing all of this I'm happy to continue using 5.3.0.0 on 1803 for the time being.

 

I uninstalled WFC and will struggle with making my own outbound rules in Windows Firewall. I might reinstall it when the group who purchased Binisoft is revealed and only if it remains a standalone product. Hopefully, something else comes along...

@Antarctica
The count of my lifetime licenses is definitely dwindling. Lifetime is only as long as a developer continues development which could end at any time. Swallowed up into the abyss like the rest.

 

Good to know, thanks. Which keys are those? I'm not seeing something relevant on HKEY_CURRENT_USER\Software\BiniSoft.org\Windows Firewall Control.

 

These Windows Firewall keys, which are outside of the scope of WFC's registry entries:

Code:

HKLM\System\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\DomainProfile
HKLM\System\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\DomainProfile\AuthorizedApplications
HKLM\System\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\DomainProfile\GloballyOpenPorts
HKLM\System\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\DomainProfile\Logging
HKLM\System\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\FirewallRules
HKLM\System\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\PublicProfile
HKLM\System\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\PublicProfile\AuthorizedApplications
HKLM\System\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\PublicProfile\GloballyOpenPorts
HKLM\System\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\PublicProfile\Logging
HKLM\System\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\StandardProfile
HKLM\System\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\StandardProfile\AuthorizedApplications
HKLM\System\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\StandardProfile\GloballyOpenPorts
HKLM\System\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\StandardProfile\Logging

 

Your choice of course, but why? I will only stop using WFC if it actually stops working because of Windows 10 updates, or whatever.

Regarding lifetime licenses you are correct; "lifetime" has only ever meant for as long as developers continue development. The real question is value. I've gotten a lot of value out of WFC for a very affordable license.

 

@AmigaBoy

 

It depends on who the new owner is and whether or not bug and security updates continue. I don't have any trust in certain developers. For now, it gives me a chance to become better acquainted with Windows Firewall.

 

Can't wait to see who the new owner really is.