Windows Firewall Control (WFC) by BiniSoft.org

I don't have WFC installed right now. But from my experience adding NoVirusThank correctly did managed to keep the rules.

 

That's good.

 

I use Chrome Remote Desktop to access a PC that lives in my closet. It uses an auto-update feature and whenever it updates I can no longer connect until I click the notification to allow the new remoting_host.exe file. Is there any way to more permanently allow a specific file, even if it changes? (Yes I understand this is a potential security risk.)

 

A new path requires a new rule. This is how Windows Firewall works. Firewall rules are defined per path basis. Can you configure that software to use a specific port? If yes, then create a rule for a custom port (e.g: 45190) for all programs (no path set) and use that rule to connect to it. The changes that another software will try to use the same port are pretty low. Or disable the auto update from it, since it is just a remote desktop app, not an antivirus that needs constantly updates.

 

Does WFC tray icon, to be launched, needs particular executables?
I don't talk about WFC.exe, and I know netsh.exe is used by WFC.

 

OK then I guess Krusty didn't enable the Secure Rules feature.

 

No, but why do you ask? Did you encounter a failure scenario after removing certain file?

 

no, just using a security soft with custom blocks of LOLbins and it prevents the loading of WFC's tray icon (the service and notifications still work).
I know that blocking execution of Netsh.exe has impact on WFC but this ''issue'' is new, didnt happened before with the said soft. so i tought maybe a process related to WFC could be involved.
Only remediation is to remove the security soft.

 

Try to add wfc.exe in the exclusions list of that software. There can be certain apps that may block the loading of tray apps. However, since the notifications are displayed, but not the tray icon, it means the wfc.exe as a process is running, but it is prevented to register the tray icon into the existing tray icons.

 

That is weird, I added it, then decided to reset the exclusions list, readded wfc.exe , now it launches properly...

 

Well don't go installing the latest update today (KB4512941) build number to 18362.329 for W10 1903 users, that is if you want to keep using WFC...

 

Why? No problem noticed here so far.

 

Really no problems? Not even Cortana Search UI using a ton of CPU%...

 

No, but you're not alone - https://www.wilderssecurity.com/threads/bork-tuesday-any-problems-yet.370217/page-216#post-2852468

I don't know how you pinned it down to WFC though.

 

Never said WFC and SearchUI was related, only that you said you had no problems with this update, and the Cortana thing is hitting a lot of people.

Anyway WFC kept crashing since KB4512941, uninstalling KB4512941 stops WFC from crashing, guess I should mention I'm on 5.3.1.0 if that matters. Could also be releated to the new .NET update as well.

 

Actually, I just noticed one machine has this problem.

 

I will update my Windows 10 and I will check it out. I did not start my computer since Tuesday

 

Godspeed dude! Hope you find the issue I had with it, I'm a little worried that if I update again (which I'll eventually have to, come patch Tuesday) WFC will be competely inoperable, basically every time I opened the rule or connection log window WFC would crash, it started up fine with the shortcut but every time, again and again it would crash when you interacted with it, I did look at Event View and there were .NET errors I've never seen, sadly I cleared them without writing them down.

 

This is how things happen with beta versions of Windows. Not WFC's fault.

 

So an update. I decided to try this update again, since I guess I hate myself, and now afterwards WFC is behaving fine, no crashes. So maybe it's not an W10 'beta' issue, instead just a buggy update process on my end that worked the second try.

Funny enough though now O&O ShutUp10 doesn't start, gives me a .NET error when I try and run it. At least it's not WFC.

So don't go banging your head about my issue, it might have just been a one of.

 

I just upgraded from W7 with a working WFC to W10 - and now see this message when attempting to open the rules manager.

W10 also reset the rules, so no applications do not work unless I change the mode to low security.

Any ideas?
https://i.imgur.com/XCZ4NLj.png

 

Could be you need to install a newer version of .Net? 4.8 is the latest:

Code:

https://dotnet.microsoft.com/download/dotnet-framework/net48

 

Thanks!

I also had other applications complaining of similar issues, turns out I just needed be patient and and allow W10 to download updates (including dotnet updates) and it now works fine.

Thanks again for your reply.

 

WFC uses .NET Framework 4.5 or any version above. That error was a .NET Framework error, not a WFC error.