Downloads:

1,174

Downloads of v 6.0.2.0:

951

Last Update:

17 Apr 2019

Package Maintainer(s):

Software Author(s):

  • Alexandru Dicu

Tags:

windowsfirewallcontrol Windows Firewall Control WFC binisoft malwarebytes

windowsfirewallcontrol (Install)

6.0.2.0 | Updated: 17 Apr 2019

Downloads:

1,174

Downloads of v 6.0.2.0:

951

Maintainer(s):

Software Author(s):

  • Alexandru Dicu

windowsfirewallcontrol (Install) 6.0.2.0

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

To install windowsfirewallcontrol (Install), run the following command from the command line or from PowerShell:

>

To upgrade windowsfirewallcontrol (Install), run the following command from the command line or from PowerShell:

>

To uninstall windowsfirewallcontrol (Install), run the following command from the command line or from PowerShell:

>

NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://chocolatey.org/api/v2. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to https://chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade windowsfirewallcontrol -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade windowsfirewallcontrol -y --source="'STEP 3 URL'"
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode

- name: Ensure windowsfirewallcontrol installed
  win_chocolatey:
    name: windowsfirewallcontrol
    state: present
    version: 6.0.2.0
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'windowsfirewallcontrol' do
  action    :install
  version  '6.0.2.0'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: windowsfirewallcontrol,
    Version: 6.0.2.0,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller windowsfirewallcontrol
{
   Name     = 'windowsfirewallcontrol'
   Ensure   = 'Present'
   Version  = '6.0.2.0'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'windowsfirewallcontrol':
  provider => 'chocolatey',
  ensure   => '6.0.2.0',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install windowsfirewallcontrol version="6.0.2.0" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved by moderator gep13 on 08 May 2019.

Description

Windows Firewall Control - Managing Windows Firewall is now easier than ever

Program Overview

Windows Firewall Control is a powerful tool which extends the functionality of Windows Firewall and provides new extra features which makes Windows Firewall better. It runs in the system tray and allows the user to control the native firewall easily without having to waste time by navigating to the specific part of the firewall. This is the best tool to manage the native firewall from Windows 10, 8.1, 8, 7, Server 2016, Server 2012. Windows Firewall Control offers four filtering modes which can be switched with just a mouse click:

High Filtering - All outbound and inbound connections are blocked. This profile blocks all attempts to connect to and from your computer.
Medium Filtering - Outbound connections that do not match a rule are blocked. Only the programs that you allow can initiate outbound connections.
Low Filtering - Outbound connections that do not match a rule are allowed. The user can block the programs he doesn't want to allow initiating outbound connections.
No Filtering - Windows Firewall is turned off. Avoid using this setting unless you have another firewall running on your computer.

Windows Firewall Control doesn't do any packet filtering and does not block or allow any connection. This is done by Windows Firewall itself based on the existing firewall rules.
Program Features

√ Notifications of outbound blocked connections.
√ Learning mode that automatically allows digitally signed programs.
√ Create temporary rules which are automatically deleted when they expire or on program restart.
√ Intuitive user interface which is easy accessible through a system tray icon.
√ Full support with standard user accounts. Elevated privileges are required only at installation.
√ Disable the ability of other programs to tamper Windows Firewall rules and state.
√ Integrated support of creating, modifying and deleting Window Firewall rules.
√ Multiple and easier ways of creating new rules in Windows Firewall.
√ Lock feature which can disable the access to the settings of the program and Windows Firewall.
√ Shell integration into the right click context menu of the executable files.
√ Automatically display invalid rules for programs that do not exist any more.
√ Possibility to find and display duplicate firewall rules.
√ Merge multiple similar rules or duplicate existing ones.
√ View recently allowed and blocked connections and create new rules from the Security log.
√ Import and export of partial sets of rules.
√ Protection to unauthorized uninstallation.
√ Possibility to restore previous settings at uninstallation.
√ Global hot keys are supported and various shortcut keys are available.
√ Integrated multi language support in 29 languages.
√ And many, many more. Just try it out.

System Requirements

√ Microsoft .NET Framework version 4.5 or a newer version.
√ Compatible with all x86 and x64 versions of Windows 10, 8.1, 8, 7, Server 2016, Server 2012.
√ Windows Firewall service is required to be enabled for Windows Firewall Control to run.
√ DNS Client service is required to be enabled for the notifications to work properly.
Known Limitations

√ Windows Firewall is incompatible with software proxies, web filtering modules, NDIS drivers and any other security software that may redirect the traffic from Windows Firewall to their own filtering module.
√ Due to multiple system configurations and software installed there may be incompatibility problems. Please report them and help us to improve Windows Firewall Control. Thank you for your support!


tools\chocolateybeforemodify.ps1
Start-Process 'sc.exe' -Verb "runas" -ArgumentList 'stop wfcs'
tools\chocolateyinstall.ps1
$ErrorActionPreference = 'Stop';
$toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"

$packageArgs = @{
  packageName   = $env:ChocolateyPackageName
  fileType      = 'exe'
  url           = 'https://www.binisoft.org/download/wfc6setup.exe' 
  File          = "$toolsDir\wfcsetup.exe"
  silentArgs    = ''
  validExitCodes= @(0)
  softwareName  = 'Malwarebytes Windows Firewall Control*'
}

Get-ChocolateyWebFile @packageArgs

[bool] $update = $False
[array]$key = Get-UninstallRegistryKey -SoftwareName $packageArgs['softwareName']
if ($key.Count -gt 1) {
    $update = $True
}

if ($update -eq $True) {
    Write-Verbose "[$($packageArgs['softwareName'])] Update WFC"
    Start-Process $toolsDir\wfcsetup.exe -Wait -Verb "runas" -ArgumentList '-u -c'
} else {
    Write-Verbose "[$($packageArgs['softwareName'])] Install WFC"
    Start-Process $toolsDir\wfcsetup.exe -Wait -Verb "runas" -ArgumentList '-i -c'
}


Remove-Item $toolsDir\*.exe -ea 0 -force
tools\chocolateyuninstall.ps1
$toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"

$ErrorActionPreference = 'Stop';
$packageArgs = @{
  packageName   = $env:ChocolateyPackageName
  softwareName  = 'Malwarebytes Windows Firewall Control*'
  fileType      = 'exe'
  silentArgs    = ''
  validExitCodes= @(0)
}

[array]$key = Get-UninstallRegistryKey -SoftwareName $packageArgs['softwareName']

if ($key.Count -eq 1) {
  $key | % {
    $packageArgs['file'] = "$($_.UninstallString)"
    [array]$str = $packageArgs['file'] -Split " -"
    $packageArgs['file'] = $str[0]

    Start-Process $packageArgs['file'] -ArgumentList '-uninstall' -Verb 'runas'
    Start-Process autohotkey -Wait -ArgumentList '.\uninstall-windows-firewall-control.ahk' -WorkingDirectory $toolsDir
  }
} elseif ($key.Count -eq 0) {
  Write-Warning "$packageName has already been uninstalled by other means."
} elseif ($key.Count -gt 1) {
  Write-Warning "$($key.Count) matches found!"
  Write-Warning "To prevent accidental data loss, no programs will be uninstalled."
  Write-Warning "Please alert package maintainer the following keys were matched:"
  $key | % {Write-Warning "- $($_.DisplayName)"}
}
tools\uninstall-windows-firewall-control.ahk
#SingleInstance ; Ensure only one instance at a time
#Persistent ; Ensure the script persists until an ExitApp
SetWorkingDir %A_ScriptDir%  ; Ensures a consistent starting directory.

CoordMode, Mouse, Client ; All used coordinates are now relative to the upper left corner of the active Window and thus should work for everyone.

WinWaitActive, Malwarebytes Windows Firewall Control
Click, left, 46, 197 ; chooses the third selection box which preserves the stored firewall rules. This enables a quick reinstallation without the loss of most settings.
Sleep 4000 ; Waits for 4s to allow the user to choose another option.
Click, left, 433, 292 ; presses the next button to start the Deinstallation.
WinWaitActive, Malwarebytes Windows Firewall Control
;Waits until the Deinstallation is completed successfully.
While(WinExist("Malwarebytes Windows Firewall Control")){
	Sleep 200
}
ExitApp
tools\wfcsetup.exe.ignore
 

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
windowsfirewallcontrol (Install) 5.4.0.0 223 Wednesday, November 14, 2018 Approved
Discussion for the windowsfirewallcontrol (Install) Package

Ground Rules:

  • This discussion is only about windowsfirewallcontrol (Install) and the windowsfirewallcontrol (Install) package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or windowsfirewallcontrol (Install), or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus