Windows Firewall Control (WFC) by BiniSoft.org

Same confirmation here, but only a few rules are imported. Opening the file with a text editor I can see there are many more rules in it.

Also 5.3.1.0 here. Probably not WFC fault, but the message is misleading. Guess WFC does not make any check to ensure the import was really successful.

 

FWIW ~ test....deleted four @ rules + Import Full policy 1.5.2018.wfw = four @ rules are back.

 

Try to import the file from command prompt by using netsh. Does it work or gives you an error? Wfw is Microsoft own format. It imports all or nothing. Make sure you don't have any filters active in Rules Panel so that you might see a different order. Make sure your file is not corrupted. Does it work with other exported files? The exported file is from the same operating system?

 

Has anyone else been getting WFC errors in their Event Viewer since updating to 1803? https://i.imgur.com/M04oI8e.png

 

Is the error affecting the operation of WFC? I'm getting ready to install 1803 so it would be helpful to know. TIA.

 

I'm not seeing any errors on my system. Are you using 5.3.1.0 - which fixes the problem with the status of secure rules and secure profiles on 1803?
https://www.wilderssecurity.com/threads/windows...#post-2752968

 

Yup I am on the latest version of WFC, and even with this error everything still seems to be functioning properly, this did not happen prior to 1803.

 

Curious. I will keep an eye on my logs and see if anything appears. Glad to hear it doesn't have any noticeable affect on WFC operationally.

 

It's reproducible for me every time, but it requires a reboot if you've cleared the logs already, once your PC starts up and you go to check the WFC logs, that error will pop up in Event Viewer, and if you hit "Refresh list" a new error pops up, this happens every time until you use WFC to "Clear log" once you've done that no more errors in Event Viewer until the next reboot.

 

@Special

Was the 1803 a clean install? If not, it COULD be help to de- and reinstall WFC.

 

No I updated to 1803 from Update & Security > Check for updates...

Has Alexandrud gotten any emails about this sort of thing, I doesn't seem to hurt anything, but if there is a fix on my end I'd like to fix the error message from showing in the Event Viewer.

 

Yes, I have those too. WFC 5.3.1.0 works normally. Clean 1803 install.

 

Some more details from the log:

Reading Security log failed.

Exception: System.ArgumentException: Index 31927 is out of bounds. at System.Diagnostics.EventLogInternal.GetEntryAt(Int32 index) at WindowsFirewallControl.Proxy.ProxyServer.GetLogConnections(Int32 logEntries, Int32 direction, Int32 eventId

 

Do you use any filter in Connections Log? Which settings do you use, the default ones? I will some more testing on this build in the next weeks. Currently I have only a tablet with me with Windows 8.1 which works fine with WFC 5.3.1.0.

 

No filters, just default settings + Auto refresh and Blocked connections only.

 

I just use defaults... https://i.imgur.com/L8pRhHU.png

Anyway glad I'm not crazy here, I hate when you're the only one having issues.

 

I reverted to 1709, way too many issues with 1803 (unrelated to WFC).

 

No issues with 1803, seems rock solid so far.

 

Same here with 5.0.2.0. Only unusual thing was that my WFC rules were resorted and network "IN" rules were re-enabled. Easy to fix.

 

I have upgraded Windows to 1803 and I am having the same crash trying to read the log. This make it inconvenient to use as the log is empty. Clearing the log does appear to make it work again for a while.

 

There is no "same" crash, if you are having crashes, then it's unique to you.

 

At the end of the next week I'll be home to my development machine and I will check the issues reported with Windows 10 version 1803. I am still on vacation and I can't test or fix anything on my Windows 8.1 tablet.

 

My money is on MS changing a name of Servicexyz to serviceXYZ.

 

Another 1803 here and indeed the "Reading Security log failed" error is making the Connections Log empty.

 

I know i said this before and really hope to not upset you but Please Please release 5.x or 4.x as Open Source Software so we can fix such things ourselfs.
Don't you think it's possible to talk these guys and tell them to open source at least an older version?
This would be so great since there is really no open source firewall control for Windows out there thats as usable as WFC.