Windows Firewall Control (WFC) by BiniSoft.org

This is not a registered/unregistered thing. WFC is a system tray application from the beginning.

1. Are you sure it is not hidden like in the screenshot below ?



2. The process wfc.exe does appear in Task Manager after you close the Main Panel window ?

3. What Windows version do you use ?

 

Hi,

I'm on Win7 SP1 + KB3125574. WFC.exe is still present after the window close. The icon isn't hidden - it's set to show but on further inspection the problem might be my system. See attached. WFC is showing up as a battery icon and there are a few other entries that are not normally there. My system did crash after the install (not WFC related) so perhaps it's time for a rebuild.

Thanks for the reply.

 

Windows Firewall Control v.4.8.6.0

Change log:
- Fixed: The check of files on VirusTotal doesn't work anymore because the online provider accepts now only lowercase SHA256 hashes instead of uppercase.
- Updated: Added context sensitive help based on the selected tab in Main Panel and based on the focused window or dialog. Just use the F1 key almost anywhere to find useful information.
- Updated: The user manual topics were extended with new topics.

Note that the installer size was increased because the .chm file is also packed into the installer.

Download location: http://binisoft.org/download/wfc4setup.exe
SHA1: da9a949a602b127f8e08554cfa5eb8cabbc07776
SHA256: d27bd5deed48239c7afad5210ff528e4dea3924e60742c5ac66a796d1925de4f

Best regards,
Alexandru

 

Using 4.8.2 and all my rules disappeared on reboot. My last backup was a wfw file, apparently that extension doesn't work on the present release.

Any ideas why my rules vanished. Are they cached in a temp file/folder from which they can be recovered? Any way to force import my wfw backup file?

This is the second machine which lost all rules.. That's not expected or desired. I only noticed it when the notifications went crazy.

 

*.wfw is a Microsoft format and can be used since version 2.0 of WFC. It works to import it from WFC and also from WFwAS.

1. Do you see your rules in WFwAS ? They are the same rules. If you see them there but not in WFC, then check the filters from Rules Panel. I also thought twice in the past that the rules have disappeared but the problem was that I had no user created inbound rules. And for this reason the data grid was empty. Once I changed the filters the rules were displayed.
2. Did you enable Secure Rules ? Was is set to delete unauthorized rules or to disable them ?
3. Did you use TinyWall recently ?
4. Do you use a VPN software ? Some VPN programs import their custom rules set when launching the VPN and they restore your rules set when they are disconnected. Unfortunately, if the VPN software crashes, then your previous rules set is not restore back.

 

Updated to 4.8.6, no change. Just one rule (one that I added after things went sideways).

This may have been VPN related. I had to manually kill OpenVPN due to a connectivity issue, and then restarted it. It was sometime after all this happened that I noticed the rules disappearance. No Secure Rules or TinyWall.

When I tried to restore rules, only *.wfs was recognized.

However... on a whim I rebooted (after upgrading WFW) and after reboot all rules reappeared. I wish I had tried that on my other system, as I ended up starting my rule set from a fresh WFW install. So VPN must the culprit here. That's good to know since I've seen VPN connections re-ask for permissions under the VPN IP (10.*.*.*) which I has already setup for my fixed (non-VPN) IP.

 

Hi,

I updated WFC back arounf 15th Sept to 4.8.6.0 and today after reboot my PC I find that WFC was not putting up notifications when unauthorised apps tried to get onto the internet but were getting blocked. After looking around I noticed in the Notification section it said I was running an unregistered version. Why would WFC forget my registration details on a reboot.

I have had to back into my Account and generate a new Activation code. I hope it remembers it.

 

WFC does not work with VPNs? Like PIA?

 

I beg to differ. Works brillant with PIA for over 2 years

I just make sure all rules are PUBLIC to allow and to BLOCK DOMAIN & PRIVATE

eg, Torrent client is blocked for any protocol for DOMAIN & PRIVATE, and allow on PUBLIC
I also use Vuze for Torrents which can bind to the TAP adaptor (VPN Connection)


I also run a copy of Portable Firefox again with the same rules to only allow privacy browsing only on the VPN. For normal access I run a different copy of Firefox wo allow access over all conections. I just have to remember that if I am doing anything I suspect (ie torrent browsing, certain forums etc) I use the portable firefox.

 

I'm using Windows Firewall Control 4.8.6.0
OS: Windows 8.1 Pro (x64)

Many times I've checked WFC service, CPU usage is between 28% to 31%

 

wfcs.exe is the Windows service which does the heavy processing while wfc.exe is just a GUI application. The CPU usage is higher when the Connections Log is loading the entries or when a lot of connections are made and the Notifications System is enabled. For example if you use a torrent client with many active torrents. In other scenarios, it should stay between 0% and 1%.

From the Connections Log try to disable the logging for allowed connections. Do you see any improvement ?
Try to disable the Notifications System and see if the CPU usage is reduced.
Do you have this CPU usage all the time ?

 

Thanks alexandrud for reply.
Only sometimes I could see wfcs.exe using considerable CPU.
Also I noticed wfcs.exe CPU spike whenever I use WPS Office 2016.
When WPS office cloud service CPU usage spikes then wfcs.exe CPU usage spike as well. Not sure why.
Other times wfcs.exe CPU usage is very less.

Also I'm trying to block one specific ISP IP address via. WFC. As this specific IP address (from ISP) is injecting ads in my browser
I was checking Rules Panel but couldn't figure it out. Any ideas ?

 

I think ISP is injecting ads only when I visit http sites and not when I visit https sites
For DNS I have configured DNSCrypt.

 

Thanks SHvFI
Will keep searching for solutions to block these ads

 

Thanks guys, I tested and it worked perfectly.

 

Hi,

I have just noticed an issue with WFC and I do not understand.

I have setup a VirtualBox and installed Win7 (32bit)
I have put OpenVPN on the connection inside the VirtualBox.
I have WFC 4.8.6.0 installed

I have Vuze installed and configured to use the TAP connecion ie OpenVPN to PIA

I have 6 rules setup for Vuze in WFC, they are to allow UDP and TCP Outbound through the firewall on the PUBLIC connection, to block UDP and TCP Outbound through the firewall on the DOMAIN and PRIVATE connections and also to allow UDP and TCP Inbound on ALL connections

<?xml version="1.0" encoding="utf-8"?>
<!--Source='Windows Firewall Control', Type='Firewall Rules', Date='9/28/2016 1:47:40 PM'-->
<Rules>
<Rule Name="Vuze Launcher (In)" Group="Windows Firewall Control" Program="C:\program files\vuze\azureus.exe" Description="Inbound rule to allow Vuze Launcher" Location="4" Enabled="Yes" Action="Allow" Direction="In" LocalAddresses="" LocalPorts="" RemoteAddresses="" RemotePorts="" Protocol="6" ServiceName="" EdgeTraversal="0" Icmp="" InterfaceTypes="All" ApplicationPackage="" AuthorizedComputers="" AuthorizedUsers="" LocalUserOwner="" SecureFlags="0" />
<Rule Name="Vuze Launcher (In)" Group="Windows Firewall Control" Program="C:\program files\vuze\azureus.exe" Description="Inbound rule to allow Vuze Launcher" Location="4" Enabled="Yes" Action="Allow" Direction="In" LocalAddresses="" LocalPorts="" RemoteAddresses="" RemotePorts="" Protocol="17" ServiceName="" EdgeTraversal="0" Icmp="" InterfaceTypes="All" ApplicationPackage="" AuthorizedComputers="" AuthorizedUsers="" LocalUserOwner="" SecureFlags="0" />
<Rule Name="Vuze Launcher (UDP-Out) (Block)" Group="Windows Firewall Control" Program="C:\program files\vuze\azureus.exe" Description="Outbound rule to allow Vuze Launcher (UDP-Out)" Location="3" Enabled="Yes" Action="Block" Direction="Out" LocalAddresses="" LocalPorts="" RemoteAddresses="" RemotePorts="" Protocol="17" ServiceName="" EdgeTraversal="" Icmp="" InterfaceTypes="All" ApplicationPackage="" AuthorizedComputers="" AuthorizedUsers="" LocalUserOwner="" SecureFlags="0" />
<Rule Name="Vuze Launcher (TCP-Out) (Block)" Group="Windows Firewall Control" Program="C:\program files\vuze\azureus.exe" Description="Outbound rule to blockllow Vuze Launcher (TCP-Out)" Location="3" Enabled="Yes" Action="Block" Direction="Out" LocalAddresses="" LocalPorts="" RemoteAddresses="" RemotePorts="" Protocol="6" ServiceName="" EdgeTraversal="" Icmp="" InterfaceTypes="All" ApplicationPackage="" AuthorizedComputers="" AuthorizedUsers="" LocalUserOwner="" SecureFlags="0" />
<Rule Name="Vuze Launcher (UDP-Out)" Group="Windows Firewall Control" Program="C:\program files\vuze\azureus.exe" Description="Outbound rule to allow Vuze Launcher (UDP-Out)" Location="4" Enabled="Yes" Action="Allow" Direction="Out" LocalAddresses="" LocalPorts="" RemoteAddresses="" RemotePorts="" Protocol="17" ServiceName="" EdgeTraversal="" Icmp="" InterfaceTypes="All" ApplicationPackage="" AuthorizedComputers="" AuthorizedUsers="" LocalUserOwner="" SecureFlags="0" />
<Rule Name="Vuze Launcher (TCP-Out)" Group="Windows Firewall Control" Program="C:\program files\vuze\azureus.exe" Description="Outbound rule to allow Vuze Launcher (TCP-Out)" Location="4" Enabled="Yes" Action="Allow" Direction="Out" LocalAddresses="" LocalPorts="" RemoteAddresses="" RemotePorts="" Protocol="6" ServiceName="" EdgeTraversal="" Icmp="" InterfaceTypes="All" ApplicationPackage="" AuthorizedComputers="" AuthorizedUsers="" LocalUserOwner="" SecureFlags="0" />
</Rules>

If I drop the OPENVPN connection (ie disconnect the VPN) then run VUZE I would of thought all connection from VUZE would now be blocked from accessing the internet due to the WFC rules, however I am seeing some traffic through the firewall. See below for ALLOWED connections from the WFC Logging...

9/28/2016 1:43:32 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 58940 | 239.255.255.250 | 1900 | 17
9/28/2016 1:45:33 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54710 | 7f00:1:4e53:7067:8062:4186:100:e0 | 54709 | 6
9/28/2016 1:45:33 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54708 | 7f00:1:4e53:7067:8062:4186:100:e0 | 54707 | 6
9/28/2016 1:45:33 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54705 | 127.0.0.1 | 54535 | 6
9/28/2016 1:45:33 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54703 | 127.0.0.1 | 54535 | 6
9/28/2016 1:45:33 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 58940 | 239.255.255.250 | 1900 | 17
9/28/2016 1:45:33 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 58940 | 239.255.255.250 | 1900 | 17
9/28/2016 1:45:33 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 58940 | 239.255.255.250 | 1900 | 17
9/28/2016 1:45:33 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 58940 | 239.255.255.250 | 1900 | 17
9/28/2016 1:45:32 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 58940 | 239.255.255.250 | 1900 | 17
9/28/2016 1:45:31 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 1900 | 192.168.0.63 | 58940 | 17
9/28/2016 1:45:30 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 58940 | 239.255.255.250 | 1900 | 17
9/28/2016 1:44:33 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 58940 | 239.255.255.250 | 1900 | 17
9/28/2016 1:44:33 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 58940 | 239.255.255.250 | 1900 | 17
9/28/2016 1:44:33 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 58940 | 239.255.255.250 | 1900 | 17
9/28/2016 1:44:33 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 58940 | 239.255.255.250 | 1900 | 17
9/28/2016 1:44:32 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 58940 | 239.255.255.250 | 1900 | 17
9/28/2016 1:44:29 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 1900 | 192.168.0.63 | 58940 | 17
9/28/2016 1:44:29 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 58940 | 239.255.255.250 | 1900 | 17
9/28/2016 1:43:34 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54655 | 7f00:1:4e53:7067:a4d0:9485:100:e0 | 54654 | 6
9/28/2016 1:43:34 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54653 | 7f00:1:4e53:7067:a4d0:9485:100:e0 | 54652 | 6
9/28/2016 1:43:34 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54651 | 192.168.0.63 | 58940 | 6
9/28/2016 1:43:33 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54649 | 192.168.0.63 | 58940 | 6
9/28/2016 1:43:32 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 58940 | 239.255.255.250 | 1900 | 17
9/28/2016 1:43:32 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 58940 | 239.255.255.250 | 1900 | 17
9/28/2016 1:43:32 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 58940 | 239.255.255.250 | 1900 | 17
9/28/2016 1:43:32 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54646 | 192.168.0.63 | 58940 | 6
9/28/2016 1:43:32 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 58940 | 239.255.255.250 | 1900 | 17
9/28/2016 1:43:32 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54641 | 7f00:1:4e53:7067:a4d0:9485:100:e0 | 54640 | 6
9/28/2016 1:43:32 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54639 | 7f00:1:4e53:7067:a4d0:9485:100:e0 | 54638 | 6
9/28/2016 1:43:32 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54636 | 127.0.0.1 | 54535 | 6
9/28/2016 1:43:32 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54634 | 127.0.0.1 | 54535 | 6
9/28/2016 1:43:31 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54632 | 7f00:1:4e53:7067:a4d0:9485:100:e0 | 54631 | 6
9/28/2016 1:43:31 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54630 | 7f00:1:4e53:7067:a4d0:9485:100:e0 | 54629 | 6
9/28/2016 1:43:31 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54627 | 127.0.0.1 | 54535 | 6
9/28/2016 1:43:31 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54625 | 127.0.0.1 | 54535 | 6
9/28/2016 1:43:30 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54608 | 7f00:1:4e53:7067:a4d0:9485:100:e0 | 54607 | 6
9/28/2016 1:43:30 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54606 | 7f00:1:4e53:7067:a4d0:9485:100:e0 | 54605 | 6
9/28/2016 1:43:30 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54603 | 127.0.0.1 | 54535 | 6
9/28/2016 1:43:30 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54601 | 127.0.0.1 | 54535 | 6
9/28/2016 1:43:30 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54599 | 7f00:1:4e53:7067:a4d0:9485:100:e0 | 54598 | 6
9/28/2016 1:43:30 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54597 | 7f00:1:4e53:7067:a4d0:9485:100:e0 | 54596 | 6
9/28/2016 1:43:30 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54594 | 127.0.0.1 | 54535 | 6
9/28/2016 1:43:30 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54592 | 127.0.0.1 | 54535 | 6
9/28/2016 1:43:30 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54587 | 7f00:1:4e53:7067:a4d0:9485:100:e0 | 54586 | 6
9/28/2016 1:43:30 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54585 | 7f00:1:4e53:7067:a4d0:9485:100:e0 | 54584 | 6
9/28/2016 1:43:30 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54582 | 127.0.0.1 | 54535 | 6
9/28/2016 1:43:30 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54579 | 127.0.0.1 | 54535 | 6
9/28/2016 1:43:29 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54576 | 7f00:1:4e53:7067:a4d0:9485:100:e0 | 54575 | 6
9/28/2016 1:43:29 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54574 | 7f00:1:4e53:7067:a4d0:9485:100:e0 | 54573 | 6
9/28/2016 1:43:29 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54571 | 127.0.0.1 | 54535 | 6
9/28/2016 1:43:29 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54569 | 127.0.0.1 | 54535 | 6
9/28/2016 1:43:29 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54567 | 7f00:1:4e53:7067:a4d0:9485:100:e0 | 54566 | 6
9/28/2016 1:43:29 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 58940 | 239.255.255.250 | 1900 | 17
9/28/2016 1:43:29 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54561 | 127.0.0.1 | 54535 | 6
9/28/2016 1:43:29 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54559 | 127.0.0.1 | 54535 | 6
9/28/2016 1:43:29 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54556 | 7f00:1:4e53:7067:a4d0:9485:100:e0 | 54555 | 6
9/28/2016 1:43:29 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54553 | 127.0.0.1 | 54535 | 6
9/28/2016 1:43:29 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54551 | 127.0.0.1 | 54535 | 6
9/28/2016 1:43:29 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 52040 | 239.255.67.250 | 16680 | 17
9/28/2016 1:43:29 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54549 | 7f00:1:4e53:7067:a4d0:9485:100:e0 | 54548 | 6
9/28/2016 1:43:29 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54547 | 7f00:1:4e53:7067:a4d0:9485:100:e0 | 54546 | 6
9/28/2016 1:43:28 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54544 | 127.0.0.1 | 54535 | 6




So why am I seeing allowed outgoing connections through the firewall on the DOMAIN and PRIVATE connections This is what I do not understand. Any help would be really appreciated.


For comparrison here are the BLOCKED connections from the WFC Logging at the same time as above list.
9/28/2016 1:43:51 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 52518 | 209.222.18.222 | 53 | 17
9/28/2016 1:44:16 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 49001 | 67.215.246.10 | 6881 | 17
9/28/2016 1:44:14 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 1900 | 192.168.0.10 | 57061 | 17
9/28/2016 1:44:14 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 1900 | 192.168.0.10 | 57061 | 17
9/28/2016 1:44:09 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 53129 | 192.168.0.10 | 53 | 17
9/28/2016 1:44:08 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 52518 | 192.168.0.10 | 53 | 17
9/28/2016 1:44:01 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54677 | 192.168.0.36 | 49153 | 6
9/28/2016 1:44:01 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54676 | 192.168.0.36 | 49153 | 6
9/28/2016 1:44:01 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54675 | 192.168.0.36 | 49153 | 6
9/28/2016 1:44:01 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 53129 | 209.222.18.218 | 53 | 17
9/28/2016 1:43:59 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 52518 | 209.222.18.218 | 53 | 17
9/28/2016 1:43:58 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54671 | 192.168.0.69 | 49153 | 6
9/28/2016 1:43:58 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54670 | 192.168.0.69 | 49153 | 6
9/28/2016 1:43:58 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54669 | 192.168.0.69 | 49153 | 6
9/28/2016 1:43:52 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 53129 | 209.222.18.222 | 53 | 17
9/28/2016 1:43:48 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 53129 | 192.168.0.10 | 53 | 17
9/28/2016 1:43:47 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54666 | 192.168.0.36 | 49153 | 6
9/28/2016 1:43:47 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54665 | 192.168.0.36 | 49153 | 6
9/28/2016 1:43:47 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54664 | 192.168.0.36 | 49153 | 6
9/28/2016 1:43:47 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 52518 | 192.168.0.10 | 53 | 17
9/28/2016 1:43:45 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54663 | 192.168.0.69 | 49153 | 6
9/28/2016 1:43:45 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54662 | 192.168.0.69 | 49153 | 6
9/28/2016 1:43:45 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54661 | 192.168.0.69 | 49153 | 6
9/28/2016 1:43:44 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 53129 | 209.222.18.218 | 53 | 17
9/28/2016 1:43:43 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 52518 | 209.222.18.218 | 53 | 17
9/28/2016 1:43:41 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 1900 | 192.168.0.10 | 13795 | 17
9/28/2016 1:43:41 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 1900 | 192.168.0.10 | 13795 | 17
9/28/2016 1:43:40 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 53129 | 209.222.18.222 | 53 | 17
9/28/2016 1:43:39 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 52518 | 209.222.18.222 | 53 | 17
9/28/2016 1:43:38 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 53129 | 192.168.0.10 | 53 | 17
9/28/2016 1:43:38 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54658 | 192.168.0.69 | 49153 | 6
9/28/2016 1:43:38 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54657 | 192.168.0.69 | 49153 | 6
9/28/2016 1:43:38 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54656 | 192.168.0.69 | 49153 | 6
9/28/2016 1:43:37 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 52518 | 192.168.0.10 | 53 | 17
9/28/2016 1:43:36 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 53129 | 209.222.18.218 | 53 | 17
9/28/2016 1:43:35 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 52518 | 209.222.18.218 | 53 | 17
9/28/2016 1:43:34 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 53129 | 209.222.18.222 | 53 | 17
9/28/2016 1:43:33 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 53129 | 192.168.0.10 | 53 | 17
9/28/2016 1:43:33 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 52518 | 209.222.18.222 | 53 | 17
9/28/2016 1:43:33 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54648 | 192.195.77.54 | 80 | 6
9/28/2016 1:43:32 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54647 | 216.146.38.70 | 80 | 6
9/28/2016 1:43:32 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 53129 | 209.222.18.218 | 53 | 17
9/28/2016 1:43:32 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54644 | 52.206.15.209 | 443 | 6
9/28/2016 1:43:32 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54643 | 52.206.15.209 | 443 | 6
9/28/2016 1:43:32 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54642 | 52.206.15.209 | 443 | 6
9/28/2016 1:43:32 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 52518 | 192.168.0.10 | 53 | 17
9/28/2016 1:43:31 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 53129 | 209.222.18.222 | 53 | 17
9/28/2016 1:43:31 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 52518 | 209.222.18.218 | 53 | 17
9/28/2016 1:43:30 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54624 | 52.202.145.116 | 80 | 6
9/28/2016 1:43:30 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54623 | 52.202.145.116 | 80 | 6
9/28/2016 1:43:30 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54622 | 52.202.145.116 | 80 | 6
9/28/2016 1:43:30 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54621 | 52.202.145.116 | 80 | 6
9/28/2016 1:43:30 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54620 | 52.202.145.116 | 80 | 6
9/28/2016 1:43:30 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54619 | 52.202.145.116 | 80 | 6
9/28/2016 1:43:30 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54618 | 52.202.145.116 | 80 | 6
9/28/2016 1:43:30 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54617 | 52.202.145.116 | 80 | 6
9/28/2016 1:43:30 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54616 | 52.202.145.116 | 80 | 6
9/28/2016 1:43:30 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54615 | 52.202.145.116 | 80 | 6
9/28/2016 1:43:30 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54614 | 52.202.145.116 | 80 | 6
9/28/2016 1:43:30 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54613 | 52.202.145.116 | 80 | 6
9/28/2016 1:43:30 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54612 | 52.202.145.116 | 80 | 6
9/28/2016 1:43:30 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54611 | 52.202.145.116 | 80 | 6
9/28/2016 1:43:30 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54610 | 52.202.145.116 | 80 | 6
9/28/2016 1:43:30 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54590 | 52.206.15.209 | 443 | 6
9/28/2016 1:43:30 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54589 | 52.206.15.209 | 443 | 6
9/28/2016 1:43:30 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54588 | 52.206.15.209 | 443 | 6
9/28/2016 1:43:30 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54578 | 54.225.168.50 | 80 | 6
9/28/2016 1:43:30 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 52518 | 209.222.18.222 | 53 | 17
9/28/2016 1:43:29 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54565 | 216.58.213.68 | 80 | 6
9/28/2016 1:43:29 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54564 | 174.129.43.152 | 80 | 6
9/28/2016 1:43:29 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54563 | 216.58.213.68 | 80 | 6
9/28/2016 1:43:26 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54539 | 52.6.162.203 | 80 | 6
9/28/2016 1:43:24 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54538 | 52.206.15.209 | 443 | 6
9/28/2016 1:43:24 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54537 | 52.206.15.209 | 443 | 6
9/28/2016 1:43:24 PM | 3064 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 54536 | 52.206.15.209 | 443 | 6
So why am I seeing allowed outgoing connections through the firewall on the DOMAIN and PRIVATE connections This is what I do not understand. Any help would be really appreciated.

 

Are you sure that the Location changes immediately to Private when you disable the VPN connection ? If the Location is not changed immediately, then this might be the reason.

 

Windows Firewall Control v.4.8.7.0

Change log:
- Improved: The Notification dialog is now resizable.
- Fixed: Fixed unquoted service path which can be exploited at WFC service start-up for privilege escalation.

Download location: http://binisoft.org/download/wfc4setup.exe
SHA1: f3f02010d78a1f23c0a508ad56f5a177a3ac247f
SHA256: 996ef8b5c3f8645f9632de114b6084244d6dca1fdd10b8d3be2b4768f8dcab10

Best regards,
Alexandru

 

Hi,

I have just tried the following.
I rebooted the Virtual Machine and land on the desktop (Only using the standard bridged network connection in the VM. ie OpenVPN has NOT run and created the VPN)
I get the notification that WFC needs updating, so I updated to 4.8.7.0 (so ignore this bit)
I now run Vuze (using the same rules above) and these are the allowed connections from the WFC log. The network location is for the local LAN only in Network and Sharing Control Panel.
The IP address of this VM is 192.168.0.63. I have no idea where the IPv6 address are from as I only have IPV4 configured on Host, and IPv4 on LAN VM and IPv4 on OpenVPN (when running, which in this case it is not running on the VM)

9/28/2016 3:40:35 PM | 304 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 49211 | 127.0.0.1 | 49178 | 6
9/28/2016 3:41:19 PM | 304 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 58940 | 239.255.255.250 | 1900 | 17
9/28/2016 3:41:19 PM | 304 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 58940 | 239.255.255.250 | 1900 | 17
9/28/2016 3:41:19 PM | 304 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 58940 | 239.255.255.250 | 1900 | 17
9/28/2016 3:41:19 PM | 304 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 58940 | 239.255.255.250 | 1900 | 17
9/28/2016 3:41:18 PM | 304 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 58940 | 239.255.255.250 | 1900 | 17
9/28/2016 3:40:50 PM | 304 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 52040 | 239.255.67.250 | 16680 | 17
9/28/2016 3:40:40 PM | 304 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 49296 | 7f00:1::a4c0:9485:100:e0 | 49295 | 6
9/28/2016 3:40:40 PM | 304 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 49294 | 7f00:1::a4c0:9485:100:e0 | 49293 | 6
9/28/2016 3:40:40 PM | 304 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 49292 | 192.168.0.63 | 58940 | 6
9/28/2016 3:40:39 PM | 304 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 49291 | 192.168.0.63 | 58940 | 6
9/28/2016 3:40:38 PM | 304 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 58940 | 239.255.255.250 | 1900 | 17
9/28/2016 3:40:38 PM | 304 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 58940 | 239.255.255.250 | 1900 | 17
9/28/2016 3:40:38 PM | 304 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 58940 | 239.255.255.250 | 1900 | 17
9/28/2016 3:40:38 PM | 304 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 58940 | 239.255.255.250 | 1900 | 17
9/28/2016 3:40:38 PM | 304 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 49287 | 192.168.0.63 | 58940 | 6
9/28/2016 3:40:38 PM | 304 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 58940 | 239.255.255.250 | 1900 | 17
9/28/2016 3:40:38 PM | 304 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 49286 | 7f00:1::a4c0:9485:100:e0 | 49285 | 6
9/28/2016 3:40:38 PM | 304 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 49284 | 7f00:1::a4c0:9485:100:e0 | 49283 | 6
9/28/2016 3:40:38 PM | 304 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 49281 | 127.0.0.1 | 49178 | 6
9/28/2016 3:40:38 PM | 304 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 49279 | 127.0.0.1 | 49178 | 6
9/28/2016 3:40:38 PM | 304 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 49274 | 7f00:1::a4c0:9485:100:e0 | 49273 | 6
9/28/2016 3:40:38 PM | 304 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 49271 | 7f00:1::a4c0:9485:100:e0 | 49270 | 6
9/28/2016 3:40:38 PM | 304 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 49267 | 127.0.0.1 | 49178 | 6
9/28/2016 3:40:38 PM | 304 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 49265 | 127.0.0.1 | 49178 | 6
9/28/2016 3:40:36 PM | 304 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 49258 | 7f00:1::a4c0:9485:100:e0 | 49257 | 6
9/28/2016 3:40:36 PM | 304 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 49256 | 7f00:1::a4c0:9485:100:e0 | 49255 | 6
9/28/2016 3:40:36 PM | 304 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 49253 | 127.0.0.1 | 49178 | 6
9/28/2016 3:40:36 PM | 304 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 49251 | 127.0.0.1 | 49178 | 6
9/28/2016 3:40:36 PM | 304 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 49244 | 7f00:1::a4c0:9485:100:e0 | 49243 | 6
9/28/2016 3:40:36 PM | 304 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 49242 | 7f00:1::a4c0:9485:100:e0 | 49241 | 6
9/28/2016 3:40:36 PM | 304 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 49239 | 127.0.0.1 | 49178 | 6
9/28/2016 3:40:36 PM | 304 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 49237 | 127.0.0.1 | 49178 | 6
9/28/2016 3:40:36 PM | 304 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 49232 | 7f00:1::a4c0:9485:100:e0 | 49231 | 6
9/28/2016 3:40:36 PM | 304 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 49228 | 7f00:1::a4c0:9485:100:e0 | 49227 | 6
9/28/2016 3:40:36 PM | 304 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 49224 | 127.0.0.1 | 49178 | 6
9/28/2016 3:40:36 PM | 304 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 49220 | 127.0.0.1 | 49178 | 6
9/28/2016 3:40:35 PM | 304 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 58940 | 239.255.255.250 | 1900 | 17
9/28/2016 3:40:35 PM | 304 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 49218 | 7f00:1::a4c0:9485:100:e0 | 49217 | 6
9/28/2016 3:40:35 PM | 304 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 49216 | 7f00:1::a4c0:9485:100:e0 | 49215 | 6
9/28/2016 3:40:35 PM | 304 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 49213 | 127.0.0.1 | 49178 | 6
9/28/2016 3:40:35 PM | 304 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 49209 | 7f00:1::a4c0:9485:100:e0 | 49208 | 6
9/28/2016 3:40:35 PM | 304 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 49207 | 7f00:1::a4c0:9485:100:e0 | 49206 | 6
9/28/2016 3:40:35 PM | 304 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 49201 | 127.0.0.1 | 49178 | 6
9/28/2016 3:40:35 PM | 304 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 49198 | 127.0.0.1 | 49178 | 6
9/28/2016 3:40:35 PM | 304 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 49196 | 127.0.0.1 | 49178 | 6
9/28/2016 3:40:35 PM | 304 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 49195 | 127.0.0.1 | 49178 | 6
9/28/2016 3:40:35 PM | 304 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 52040 | 239.255.67.250 | 16680 | 17
9/28/2016 3:40:34 PM | 304 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 49191 | 7f00:1::a4c0:9485:100:e0 | 49190 | 6
9/28/2016 3:40:34 PM | 304 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 49189 | 7f00:1::a4c0:9485:100:e0 | 49188 | 6
9/28/2016 3:40:34 PM | 304 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 49186 | 127.0.0.1 | 49178 | 6
9/28/2016 3:40:34 PM | 304 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 49184 | 127.0.0.1 | 49178 | 6
9/28/2016 3:40:33 PM | 304 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 49183 | 127.0.0.1 | 31469 | 6
9/28/2016 3:40:29 PM | 304 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 49177 | 7f00:1::829:4386:100:e0 | 49176 | 6
9/28/2016 3:40:29 PM | 304 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 49175 | 7f00:1::829:4386:100:e0 | 49174 | 6
9/28/2016 3:40:29 PM | 304 | Vuze Launcher | C:\program files\vuze\azureus.exe | Out | 49173 | 7f00:1::829:4386:100:e0 | 49172 | 6

 

You are the best! Thanks!

 

hi
beautiful program , i want to install on my machines
a friend of mine does it use and she is so happy
may i ask you ?
is there a way to use wildcards like * for ip ?
and how can i backup all my w10/8/7 firewall rules ? are stored in the registry?
i want to backup them because in the past (lot time ago ) i have installed windows firewall control and it did mess up my firewall
thanks

 

Windows Firewall does not support wildcards, nor WFC. You can however define an IP range instead of using the *. For example to block 12.10.50.* you can set the following IP range in the remote IP addresses field: 12.10.50.0-12.10.50.255.

During the installation, WFC makes a backup of your rules which can be restored at uninstallation. Installing WFC will not mess up your firewall. The export and import functionality prior installing WFC can be achieved also from WFwAS user interface (wf.msc).

 

hi @alexandrud

but can i manually backup them ?

ps i said in the past i had problems, i could not forget after uninstalling it ,all the rules disapears and i had continue errors , at the end i had to restore an image , but it was lot time ago

are all there ?

Code:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\SharedAccess\Parameters\FirewallPolicy

thanks

 

@SHvFl thanks
just in case , i can stop the service and restore the reg file , can't I ?
thanks again!

 

do WFC include online license check or some kind of telemetry because i have some blocked connections from wfc.exe
on various ipv4 ip's and ipv6 ip's on port 80.

is there any way to display on svchost notifications real service name and not PID of services (services.exe) who call real service
because right now i have to split svchost services with own parameter to get the real service behind connection notification

and for further versions it will be nice to use custom URL's to do ip check