Malwarebytes Windows Firewall Control User Guide
Malwarebytes Windows Firewall Control User Guide
User Guide
Version 6.9.9.6
March 3, 2024
Notices .......................................................................................................................................................................................................................... 2
Third Party Project Usage ...................................................................................................................................................................................... 2
Sample Code in Documentation ........................................................................................................................................................................ 2
System requirements .............................................................................................................................................................................................. 5
Known limitations ..................................................................................................................................................................................................... 6
Program parameters ............................................................................................................................................................................................... 7
Keyboard shortcuts .................................................................................................................................................................................................. 8
Unattended installation ......................................................................................................................................................................................... 9
User interface .......................................................................................................................................................................................................... 10
Main Panel................................................................................................................................................................................................................ 11
Profiles tab .......................................................................................................................................................................................................... 13
Is it possible to allow LAN traffic when using High Filtering profile? ..................................................................................... 14
Notifications tab ............................................................................................................................................................................................... 15
How does the notifications system work? ......................................................................................................................................... 17
Windows Firewall notifications .............................................................................................................................................................. 18
How to stop entirely the notifications for a program?................................................................................................................. 19
Why there is no "Allow for now and ask me later" button? ....................................................................................................... 19
Options tab ......................................................................................................................................................................................................... 20
Rules tab .............................................................................................................................................................................................................. 22
How to allow connections only when I'm connected to my VPN?.......................................................................................... 23
How to find which firewall rule blocked or allowed a connection? ........................................................................................ 23
Windows Firewall Control recommended rules .............................................................................................................................. 24
Security tab ......................................................................................................................................................................................................... 26
Tools tab .............................................................................................................................................................................................................. 28
About tab............................................................................................................................................................................................................. 29
Rules Panel ............................................................................................................................................................................................................... 30
Does the program use a different set of firewall rules than Windows Firewall? ................................................................ 35
Can I create a rule for all the files from a folder? ........................................................................................................................... 35
How to allow a program to connect only to the local network? ............................................................................................. 35
How to allow programs located on mounted drives? .................................................................................................................. 36
How to allow Windows Store apps that have a different path after an update? .............................................................. 36
How to create a rule for a program which executes from the temporary folder? ............................................................ 36
Connections Log .................................................................................................................................................................................................... 37
• Windows 7
• Windows 8
• Windows 8.1
• Windows 10
• Windows 11
• Windows Server 2012
• Windows Server 2016
• Windows Server 2019
• Windows Server 2022
Windows Firewall Control is developed by using the Windows Presentation Foundation platform and requires .NET
Framework 4.8 or a newer version. It is recommended to install the latest .NET Framework version because newer
releases of the .NET Framework include speed improvements and also bug fixes.
• Windows Firewall service. Windows Firewall Control is not a firewall by itself and requires Windows Firewall to
be running.
• Windows Event Log service is required for logging purposes. If this service is not started, Malwarebytes Windows
Firewall Control service will fail to start.
• DNS Client service. This is required for the notifications system to work properly. If you use a router and this
service is stopped, the remote IP address of the blocked connections will be the IP address of the router instead
of the real IP address. Also, the log entries that are displayed in Connections Log will suffer from the same
problem. It is recommended to not disable this Windows service.
• Windows XP and Windows Server 2003 are not supported and were never supported because Windows Filtering
Platform was first introduced in Windows Vista.
• Windows Vista and Windows Server 2008 are not supported.
• Hyper-V Server free editions are not supported since they don't have a GUI. However, Windows Server with Hyper-
V role installed is supported since this operating system has a desktop and GUI applications are supported.
Windows 10/11
• The keywords Internet, Intranet, PlayTo Renderers, Remote Corp Network which can be set in the Remote
Addresses property of a rule from WFwAS are not visible in Windows Firewall Control. This is a problem caused
by Windows Firewall API which does not provide these values at all. Editing or duplicating such rules which have
these keywords set (for example, the rules from the default group named Cast to Device functionality) will
remove them. This problem is also visible when exporting/importing partial policy files because this info is
missing. However, when exporting/importing a full policy, this info is preserved.
-mp or -mainpanel
Open the Main Panel. This can be also achieved with a global hot key defined in the Options tab.
-rp or -rulespanel
Open the Rules Panel. This can be also achieved with a global hot key defined in the Options tab.
-cl or -connectionslog
Open the Connections Log. This can be also achieved with a global hot key defined in the Options tab.
-x or -exit
Close existing wfcUI.exe instance nicely by unsubscribing from system events and disposing the system tray icon.
-uninstall or -u
Launch the uninstall dialog. This works only if the program is not locked with a password. If the program is locked
with a password nothing will happen. In this case please unlock the program and then try again to uninstall it.
-en or -enablenotifications
Sets notifications mode to Display notifications if the current active profile is Medium Filtering profile.
-elm or -enablelearningmode
Sets notifications mode to Learning mode if the current active profile is Medium Filtering profile.
-dn or -disablenotifications
Sets notifications mode to Disabled if the current active profile is Medium Filtering profile.
The parameters can be used also in the Run dialog with the following syntax. Windows Firewall Control is registered
under the App Paths key from Windows Registry, so it can be launched by entering just the exe filename, without the
full path.
CTRL + TAB
Switch between the Rules Panel and Connections Log. If the other window is not yet displayed it will be opened.
F5 or CTRL + R
Refresh the firewall rules displayed in the Rules Panel or the log entries from the Connections Log.
CTRL + F
Move the focus to the search box in Rules Panel or Connections Log.
ENTER
Open the Properties Dialog for the selected entry in Rules Panel and Connections Log.
F1
Open the user manual. Available in Main Panel, Rules Panel, Connections Log, Notification Dialog.
CTRL + RIGHT
Switch to the next notification.
CTRL + LEFT
Switch to the previous notification.
CTRL + SHIFT + A
Create a generic allow rule for the current displayed notification.
CTRL + SHIFT + Q
Create a generic block rule for the current displayed notification.
CTRL + ALT + A
Create a temporary allow rule that expires on WFC restart, for the current displayed notification.
CTRL + ALT + Q
Create a temporary block rule that expires on WFC restart, for the current displayed notification.
CTRL + SHIFT + E
Add the file name from the displayed notification in the Notifications exceptions list.
-install or -i
This will launch the installation without asking the user any input. If the program is already installed and this parameter
is used, it will be ignored. The installer will install Windows Firewall Control into the default folder, which is
C:\Program Files\Malwarebytes\Windows Firewall Control.
-update or -u
This will automatically launch the update process without asking the user any input. If the program is not installed
and this parameter is used, it will be ignored.
-run or -r (optional)
When using the parameters -i or -u, the installer window will remain open when the process completes. Use this
parameter if you want to automatically launch wfcUI.exe and close the installer window.
-close or -c (optional)
When using the parameters -i or -u, the installer window will remain open when the process completes. Use this
parameter if you want also to close the installer window without executing wfcUI.exe.
-noshortcuts (optional)
When -install parameter is used, use this to disable the creation of Windows Firewall Control shortcuts on Desktop
and Start Menu.
-noautostart (optional)
When -install parameter is used, use this to disable the creation of Windows Firewall Control entry in the Startup list
of Windows.
-norules (optional)
When -install parameter is used, use this to disable the creation of Windows Firewall Control recommended rules.
To install Windows Firewall Control into a different folder than the default one, for example in C:\Program Files\
WFC, you can also specify a custom path:
To silently update Windows Firewall Control and automatically launch it, use the following syntax:
wfc6setup.exe -update -run or wfc6setup.exe -u -r
Pressing the left mouse button on the icon will launch the Main Panel window.
Pressing the right mouse button on the icon will open the context menu below.
Profiles
Can be used to switch between the filtering profiles of the application.
Main Panel
Can be used to launch the Main Panel window.
Rules Panel
Can be used to launch the Rules Panel window.
Connections Log
Can be used to launch the Connections Log window.
User manual
Can be used to open the online user guide. This context menu item is available only if the system tray application
can't connect to Windows Firewall Control service.
Request elevation
This context menu item is displayed only if the software runs under a standard user account and requires elevation.
Standard user accounts have limited read only access to certain settings and actions.
Exit
Can be used to exit the system tray application. This will close the process wfcUI.exe. This does not affect the process
wfcs.exe which is the background Windows service of Windows Firewall Control.
Main Panel is the main place where Windows Firewall Control can be configured. The first tab that is displayed is the
Dashboard tab which displays the state of Windows Firewall, the status of inbound and outbound connections and
the location to which Windows Firewall is located.
The following properties are saved when Main Panel window is closed and reused when the window is opened again:
• the size and the location of the window
• the vertical splitter position
This will open the lock dialog which can be used to lock the program. By locking the program the following items will
become unavailable:
Note that these will be unavailable even if Windows Firewall Control is closed. While the program is locked with a
password do not attempt to force the uninstall of Windows Firewall Control by using a 3rd party software because
you will not be able to access Windows Firewall interface any more. If you have forgotten your password, read the
topic The program is locked and I can't remember the password from the Troubleshooting section.
Recommendation: Before setting your password, you can view it in plain text by checking the Show password check
box. In this way you can be sure that you typed the password correctly.
While the application is in locked mode, instead of the default icons that reflect the profiles, the lock icons will be
displayed.
Filtering level
The filtering level specifies which connections should be allowed or blocked. Windows Firewall Control does not do
any packet filtering and this means it does not allow or block any connection. This is done by Windows Firewall based
on the firewall rules that are defined.
Inbound connections
In Windows Firewall inbound connections are by default blocked. A program can accept incoming connections only
if it has an explicit inbound allow rule that permits the incoming connections to it. Otherwise they are blocked if no
rule is defined. Changing the profile in Windows Firewall Control does not affect the filtering of inbound connections.
Outbound connections
When the profile is changed in Windows Firewall Control, only the outbound filtering capabilities of Windows Firewall
is changed.
The following profiles are available in the Profiles tab. The profile can be also changed from the context menu of the
system tray icon.
High Filtering
o All outbound and inbound connections are blocked. This profile blocks all attempts to connect to and from your
computer.
o Windows Firewall does not contain this mode. To achieve this, when this profile is set in WFC, two new firewall
rules are added to the firewall, named High Filtering profile - Block inbound connections and High Filtering
profile - Block outbound connections. These two rules are defined to block all connections for all programs.
These are two special rules and cannot be deleted from the Rules Panel. When the profile is switched to another
profile, these two rules are automatically removed.
No Filtering
o Windows Firewall filtering is turned off.
Revert profile
There are situations when the user may want to disable temporarily the firewall protection:
o While installing a new software without the hassle of creating a new firewall rule for the installer that may
download some files from the Internet.
o While debugging connectivity problems to see if the reason why a software can't connect is the firewall or the
software itself which can't connect.
Windows Firewall Control can set an internal timer which can revert the Medium Filtering or High Filtering profile
after a predefined period of time which can be set between 1 and 300 minutes. The timer is activated when the check
box is checked or when the profile is switched. In the example above, if the profile is switched after 20 minutes, the
timer will start again to count to 30 minutes. Also, if the process wfcUI.exe is restarted, this timer is considered to be
elapsed immediately because the program doesn't know how much time it was closed.
Let's say the local network uses IP addresses from the following IP range 192.168.0.1-192.168.0.254. We have to set
the remote IP addresses of these two rules with the following two IP ranges:
1.1.1.1-192.168.0.0,192.168.0.255-255.255.255.255
This means that the IP addresses from the excluded IP range 192.168.0.1-192.168.0.254 will not be blocked because
they are not contained in the block rule, meaning that the LAN traffic will be still allowed while any other connections
will be blocked.
The custom IP ranges defined for these two rules are reused when High Filtering is switched on and off until they are
updated again.
Notifications mode
The notifications mode sets which blocked connections will generate notifications that will be displayed to the user.
Since Windows Firewall Control displays notifications only for outbound blocked connections, the Connections Log
can be used to debug connectivity problems if an inbound rule is also required.
Display notifications
• A new notification is displayed for a blocked outbound connection if there is no matching firewall rule for the
program that was blocked. Read below what a matching firewall rule means.
Learning mode
• When this notification level is used and a digitally signed program is blocked, Windows Firewall Control will
automatically create an allow rule which will allow all connections of it. The program must retry the connection
in order to connect after the allow rule is created. Most programs have a reconnect mechanism which is triggered
automatically but some of them don't. If the program does not reconnect automatically, refreshing or restarting
the program will make it to try again to connect.
• If a blocked connection is generated by a program that is not digitally signed or the signature is not valid, a new
notification will be displayed to the user.
• It is not recommended to leave this notification level enabled for a long time. Use it for a limited period of time
to automatically have created allow rules for the programs that are digitally signed.
• If the program is in the notifications exceptions list, then a new outbound allow rule will not be created when
using this mode.
Disabled
• The notifications are not displayed to the user. The user has to create manually a new allow rule for each program
that he wants to allow to connect to the network.
• When the notifications are disabled and some programs are blocked, the Connections Log can be used to debug
connectivity problems. Use Connections Log to see the recently blocked connections. This will help to make an
idea of what rules are still required based on the processes that were recently blocked.
Notifications exceptions
Outbound connections of svchost.exe and System are generated by the operating system and are related to different
functionalities of the operating system, like: Core Networking, File and Printer Sharing, Network Discovery, Telemetry,
Windows Update, etc. Because svchost.exe is used by all Microsoft Windows services to connect to the network, it
may generate endless connections attempts in a very short period of time. Most users are interested in notifications
for their custom programs and don't want to be bothered with system notifications. For this reason, certain users may
want to disable the notifications of svchost.exe, System or the notifications of programs which are installed in a
certain folder.
Wildcards (*) are not supported. The current algorithm checks if the path of the program that was blocked starts or
ends with one of the strings defined in the notifications exceptions list.
This timeout can be set between 1 and 999 seconds. The timeout is automatically removed if the user moves the
mouse cursor over the notification dialog or if the timer is set to 0. If the computer is idle for a long period of time
and the user wants to see all notifications that have occurred while he was away from the computer, this timer can
be set to 0 to avoid the automatic closing of the notification dialog. However, this is not recommended. Programs
that were blocked in the past will be blocked in the future too since they have no rule. These notifications will be
displayed again.
A temporary rule can be set to expire when Windows Firewall Control is restarted, after 60, 10 or 5 minutes. There is
also this custom timeout which can be set between 1 and 60 minutes.
The notifications displayed by Windows Firewall Control are for outbound blocked connections and they work only
when Medium Filtering profile is used. When enabling Medium Filtering profile, the outbound filtering is enabled in
Windows Firewall and this means that all programs without an allow rule are blocked by default. The Connections
Log contains the entries filtered from the Security log of the system. The same entries are the source of notifications
displayed by Windows Firewall Control.
In the example above, all blocked connections that have the path starting with C:\Program Files\Intel or ending with
svchost.exe or System will not generate a new notification.
Adding a new notification exception can be done also from the notification dialog by pressing the small button on
the right (the one with the mouse image on it):
Please use with caution. Do not create such rules for System, Temporary or Downloads folder.
Shell Integration
This setting will add two new entries into the context menu of the executable files and the context menu of shortcuts
to the executable files.
Through these two context menu options, the user can create easily a new allow or block rule when browsing through
My Computer or from the desktop shortcuts. Multiple files can be selected but not more than 15 files. If more than
15 files are selected, the operating system hides these entries from the context menu. This setting is applied for all
user accounts.
When a new rule is created through the shell context menu, a confirmation dialog is displayed above the system
clock. If multiple files were selected, the confirmation dialog will be displayed only for the last selected file.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
This entry is available to all Windows user accounts and will launch the program for all user accounts.
Global Hot-Keys
The global hot keys are keyboard shortcuts that can be used from any program to launch a specific action. They can
be used while having no program open on desktop or while other programs are running and have the focus.
A special note for the global hotkey that toggles the profiles. There is a 2 seconds delay between the press of the
hotkey and the actual profile set. Each press starts a new delay of 2 seconds. This allows enough time to select the
desired profile before the actual profile is set. If you change the profile and the system tray icon does not show the
desired profile, press again until you stop on the profile you want to set. It will be set after 2 seconds.
User settings
Windows Firewall Control stores the program settings in Windows Registry. From the Options tab the user can:
The Rules tab can be used to specify some default properties for the newly created firewall rules and also for
importing and exporting purposes.
Rule direction
A firewall rule can be defined to allow outbound requests for a program which will allow it to connect to the Internet,
or can be defined to allow inbound requests which will allow the connection requests that are sent from the network
to your computer.
Outbound (recommended)
When creating a new firewall rule from Windows Firewall Control it will be created for outbound connections. These
kind of rules are required if you want to allow a program to connect to the network/Internet.
Inbound
When creating a new firewall rule from Windows Firewall Control it will be created for inbound connections. Avoid to
create these kind of rules because they allow your computer to be visible and accessible from the network/Internet.
Inbound rules are required when you want to be able to ping your computer from another computer or to make it
visible into the local network.
Rule location
Windows Firewall supports multiple simultaneously active profiles. Each network adapter card attached to a network
is assigned one of the following locations:
Domain
The domain location applies to a network when a domain controller is detected for the domain to which the local
computer is joined.
Private
The private location applies to a network when it is marked private by the computer administrator and it is not a
domain network.
Public
The public location applies to a network when the computer is connected directly to a public network, such as one
available in airports and coffee shops.
In order to support importing/exporting through files located on network shares, the import and the export are made
through temporary files which are created in the user temporary folder.
One way to find out which rule has blocked a connection is the following:
5. Open wpfstate.xml and do a search for the filterId value. From the search result, locate the displayData to find
out which filter allowed/blocked the connection.
<item>
<layer>
....
<displayData>
<name></name>
<description></description>
</displayData>
...
</layer>
</item>
• Web browsing. An allow rule for the web browser is still required.
• Network discovery - Discover other computers from your network and allow other computers to discover your
computer.
• Network printing - Allow printing on a printer from your network.
• PING other computers and respond to PING command.
• Windows time synchronization.
• Windows Updates, Windows Store access.
These rules are prefixed with WFC and can be easily distinguished in Rules Panel.
Secure Boot
Secure boot will attempt to set High Filtering profile when a system shut down event is detected by the program. The
network connections will be blocked at Windows start-up until the user manually changes the profile to another
filtering profile. While the High Filtering profile is enabled, when Windows Firewall Control is started, a notification
will be displayed informing the user about this.
*Depending on the number of running processes and the system load at shut down time, this feature may not work
if the operating system abruptly closes WFC service before it has time to react to system shut down event. This is
something which the operating system decides. If the shutdown takes longer than expected, the OS may decide to
kill existing Windows services without any prior notice. Not ideal, but WFC can’t change this OS behavior.
Secure Profile
In Windows, a software executed with administrative privileges can import a custom policy file and modify outbound
and inbound filtering settings of the firewall, or can even disable Windows Firewall. Windows Firewall Control can
prevent these external changes. When this feature is enabled, changing the filtering mode of Windows Firewall can
be done only through the Windows Firewall Control user interface, from the Profiles tab. This feature is automatically
disabled when Windows Firewall Control is uninstalled.
Secure Rules
In Windows, all programs executed with administrative privileges can add Windows Firewall rules. There is no way to
prevent this in Windows Firewall. One way to protect against this is to have UAC enabled which will inform the user
each time an application requires elevated privileges.
Windows Firewall Control is notified when a new firewall rule is added and can delete or disable any unauthorized
rule that is being added by other programs. Any rule which is created with the group name different than the defined
authorized group names is considered to be an unauthorized rule. Based on the user choice, these unwanted firewall
rules will be deleted or disabled. Disabling the rules instead of deleting them is useful for reviewing purposes because
the user has the opportunity to see which programs have this hidden behavior. Usually, a software should not add
The list of authorized groups contain the following predefined group names which can't be removed:
• Windows Firewall Control - This group name is used by default for all firewall rules created from Windows
Firewall Control.
• Temporary Rules - This group name is used when creating temporary rules from the notification dialog.
When Secure Rules is set to disable unauthorized rules, Windows Firewall Control will automatically disable these
rules and will add the "U - " prefix to the rule description. This applies to the newly created firewall rules and to
existing ones.
Allow Windows Store rules - Ensures that Windows Store apps are excluded from the logic of Secure Rules. The
firewall rules created when a new Windows Store application is installed will not be disabled or deleted.
System utilities
The existing shortcuts can be used to launch various system utilities. The following tools are available:
Event Viewer
This is a component of the operating system that lets administrators and users view the event logs on a local or
remote machine.
Resource Monitor
This is an utility from Windows that displays information about the use of hardware (CPU, memory, disk and network)
and software (file handles and modules) resources in real time. This utility can display the current active network
connections, which is a feature often requested by Windows Firewall Control users. This is already available and there
is no plan to implement this functionality in Windows Firewall Control.
Online services
The user can configure several online services that are used from the Notifications Dialog, Rules Panel or
Connections Log. Since there are not many alternatives for these online services, all of them are already defined and
the user can only choose which one to use. Custom providers can't be defined by the user.
Rules Panel offers an integrated an easier way to manage Windows Firewall rules. The firewall rules displayed are the
same firewall rules that Windows Firewall uses. There are three color codes used for the firewall rules: green rules
represent active allow rules, red rules represent active block rules, gray rules represent the rules that are disabled.
Disabled rules are not used until they are enabled. Invalid rules are displayed with red text color and temporary rules
are displayed with blue text color.
The following properties are saved when Rules Panel window is closed and reused when the window is opened again:
o the size and the location of the window
o the columns size, order and visibility
o the last values of the toolbox combo boxes
o the toolbox width
A special mention must be made for the Extended properties check box column. A rule with this check box checked
informs the user that the rule contains some extra properties which can't be configured from Windows Firewall
Control. These extra properties can be found for some Windows 10 firewall rules. These properties can be
imported/exported from Windows Firewall Control but they can't be modified.
Block
This action will change the selected rules to block connections. This menu item is disabled if the selected rule is
already a block rule.
Enable
This action will enable the selected rules. This menu item is disabled if the selected rule is already enabled.
Disable
This action will disable the selected rules. This menu item is disabled if the selected rule is already disabled.
Properties
This action will open the Properties dialog which can be used to customize an existing rule. This menu item is disabled
if multiple rules are selected.
Create duplicate
This action will create a new copy of each of the selected rules.
Delete
This action will delete the selected rules.
Add to group
This action will set the group name for the selected rules. The list contains all the group names from the current
existing firewall rules and all authorized groups names which are defined in the Security tab. The first entry is an
empty group name which can be used to unset the group name.
Authorize group
This action will add the group of the selected rule to the list of authorized groups names which are defined in the
Security tab and will enable the selected rule.
Toolbox controls
Blank rule
This will open the Create new rule dialog allowing the user to define a new rule from scratch.
Browse to allow
This will launch an open file dialog which will create a generic* allow rule for each of the selected files. The following
file types are supported: .exe, .dll, .bin, .setup, .scr, .tmp.
Click to allow
This will open a dialog which will wait for the user to click on a program's window in order to create a new generic*
allow rule for the program that was clicked.
Browse to block
This will launch an open file dialog which will create a generic* block rule for each of the selected files. Multiple files
are supported.
Click to block
This will open a dialog which will wait for the user to click on a program's window in order to create a new generic*
block rule for the program that was clicked.
Allow button
The same as the context menu item.
Block button
The same as the context menu item.
Enable button
The same as the context menu item.
Disable button
Malwarebytes Windows Firewall Control User Guide 34
The same as the context menu item.
Properties button
The same as the context menu item.
Delete button
The same as the context menu item.
*A generic rule means a rule for a program that is defined for all locations, all local and remote ports, all local and
remote IP addresses, all protocols. A custom rule means a rule that is customized with specific values.
Does the program use a different set of firewall rules than Windows Firewall?
Windows Firewall Control is not a firewall by itself. It is just a front end for Windows Firewall which makes things easier
and also adds some new extra features. The rules that you see in Rules Panel are the same rules that Windows Firewall
uses. These rules are applied even if Windows Firewall Control is not running.
How to allow Windows Store apps that have a different path after an update?
When a new version of a Windows Store application that you have installed is receiving an update, the path of the
executable file changes. Because Windows Firewall rules are applied per path basis, after such an update a new rule
is required. This can become very annoying especially if an application is updated very often. This is how Windows
Firewall works and this is not something that Windows Firewall Control can change.
o Create a rule that applies to all programs and set an empty group name for this rule. Setting an empty group
name is important for the next step.
o Launch Windows Firewall with Advanced Security (wf.msc) and edit your newly created rule.
o In the Programs and Services tab, press on the Settings button under the Application Packages group box,
select your specific application package and save the rule. Now you will have a working firewall rule, even if the
program gets updated and the path changes. Now, you can add this firewall rule in any Group you want.
Note: The rules with a group name set can't be modified from Windows Firewall with Advanced Security. Also, the
application package can't be set from Windows Firewall Control. You need to use both tools. However, when a
Windows Store app/game is installed it will automatically create the required firewall rules for its own package. If
Secure Rules is used, make sure that Allow Windows Store rules is checked so that these firewall rules are not
disabled/removed.
How to create a rule for a program which executes from the temporary folder?
Windows Firewall rules are applied per path basis, so even if you create a rule for an executable file, if this file is
executed from a different path (different folder or filename in the temporary folder), a new rule is required for each
file path. This is how Windows Firewall works and this is not something that Windows Firewall Control can change.
For this scenario the only solution is to use Low Filtering profile when such software is used. You may try to see if you
can configure this software to use only a specific port, for example 44444. Then you can create a rule that apply to all
programs but which allows only the connections for local port 44444. In this way you can define a working rule for
such programs.
The following properties are saved when Connections Log window is closed and reused when the window is opened
again:
o the size and the location of the window
o the columns size, order and visibility
o the last values of the toolbox combo boxes
o the toolbox width
Search rules
This action will open Rules Panel and will automatically search for rules defined for the path displayed in the Program
column.
Copy
This action will open a submenu which can be used to copy the details of the selected entry to clipboard. This can be
used when selecting multiple entries too. For example, to copy all remote addresses from 10 different entries.
*A generic rule means a rule for a program that is defined for all locations, all local and remote ports, all local and
remote IP addresses, all protocols. A custom rule means a rule that is customized with specific values.
Toolbox controls
There are several shortcuts available by clicking on the Program, Source, Remote, Process ID and the program Icon.
Just move the mouse cursor over them and check the info from the tool tips that will appear.
*A generic rule means a rule for a program that is defined for all locations, all local and remote ports, all local and
remote IP addresses, all protocols. A custom rule means a rule that is customized with specific values.
1. Make sure that our software is not blocked by your antivirus or by other security software that you use. Try to
temporarily disable them and see if the behavior changes.
2. Try to add wfcUI.exe and wfcs.exe into the white list (exceptions list, allowed list, etc) of your antivirus. Some self-
defense features, anti-executable programs, may block silently our software from execution. Some calls of WFC code
involve the use of system tools netsh.exe and auditpol.exe. Make sure that your antivirus don't block the execution
of command line programs that are executed in a CMD window.
3. If you have the possibility, try to install Windows Firewall Control on a different computer or in a virtual machine to
see if you can reproduce the same problem on multiple machines.
4. Try to uninstall and reinstall the latest version of Windows Firewall Control and check if the problem is solved.
5. Make sure that you have the latest version of .NET Framework installed. Windows Firewall Control requires .NET
Framework 4.6.2 or a newer version.
6. Please go to Event Viewer (execute eventvwr.msc). Under Applications and Service logs category, there is a
subcategory named WFC. There are logged all errors from Windows Firewall Control. If you see errors logged here,
from the right panel, use the button named Save all events as... to export a .evtx file and send it to us to check it.
7. Also in Event Viewer, under Windows Logs category, there is a subcategory named Application. Here are logged
all errors from all programs. Check in this log if there are error entries regarding the files wfcUI.exe or wfcs.exe. If
so, export a .evtx file of this log too and send it to us to check it. We can find here a .NET Framework problem that is
causing the problem.
8. If you use a program named Rivatuner Statistics Server, open it and set Application detection level to None.
Otherwise, this software may try to determine the FPS for WFC which uses the GPU to render the user interface.
When sending us an email please provide us as many details of the problem that you have. Write down the exact
steps that you did, make a screenshot of the error that you receive, specify your operating system, if it is a virtual
machine or a real machine, what other security software you use on the computer. Providing as many relevant details
of your scenario will increase the chances to reproduce the problem that you have on our test machines. Then we will
be able to provide a solution.
To report a problem regarding Windows Firewall Control send an email to [email protected]. Thank you.
To troubleshoot this, make a backup of your rules and then restore Windows Firewall default set of rules. Now you
should have only the default rules. Switch to Medium Filtering profile to enable outbound filtering in Windows Firewall
and start over with the creation of your rules. Do you see now the notifications ? If the answer is yes, then one or
more rules that you had in your previous rules set is responsible for the missing notifications. If you still don't see any
notifications, then this may be a symptom generated by software proxies.
If the rules are matching and you still receive duplicate notifications, it may be a symptom that Windows Firewall
filtering does not work correctly. This usually happens when a software proxy from a different security product is used
for filtering purposes. Windows Firewall is incompatible with software proxies, web filtering modules, NDIS drivers,
any filtering modules that intercepts network packets. They redirect the network traffic to the proxy and the problem
is that the traffic does not reach anymore the Windows Firewall filtering driver. In this case, Windows Firewall rules
do not apply correctly because the traffic appears to be made by the proxy, not by the original program. Try to disable
any software proxies, web filtering modules, NDIS drivers from the 3rd party security products that you use in order
to restore the filtering functionality from Windows Firewall. This incompatibility is between software proxies and
Windows Firewall, not an incompatibility with Windows Firewall Control which does not have any control over this
behavior. Known problems between Windows Firewall and various filtering modules were reported for: Avast
WebShield, Avira WebGuard, Kaspersky Internet Security, 360 Total Security, Symantec.
Another source that may cause duplicate notifications to be displayed can be a custom hosts file or a program like
PeerBlock that blocks IP addresses based on a blacklist. All blocked connections are logged in the Security event log
and will generate new notifications even if they weren't blocked by Windows Firewall. Also check your rules for
incompatible rules.
Please read also about the advanced notifications settings from the Notifications tab.
False positives are actually mistakes made by antivirus and sometimes antispyware programs. The companies that are
trying to protect our computers against the threats are under enormous pressure to get the malware identified and
a fix created that there isn't enough time except, for very basic testing, before they must release these identifications
and fixes. Add to this fact that the authors of the malware are also using the same program compilers and software
libraries that often a good program may get misidentified as a bad one. Typically, the protection programs quarantine
area that is made to safely hold a malware will allow you to restore these if you don't get impatient and empty it first.
If you report the false positive to your protection company, they will be able to correct their mistake. If users will not
What many people fail to realize with the subject of false positives... is that all antivirus and antispyware programs are
prone to these. This is because they must also try and detect unknown malware that has just been released also. Its a
case of trying to be safe and making a false detection instead of not being safe and letting the systems get infected.
Another issue that many do not understand and is why a good program may get detected as a malware after an
update is that the authors of the virus's and spyware also use the very same programs and code libraries that normal
program authors are using... So many times regular programs have some of the very same code that malware may
have.
The user has to ask themselves would they rather their protection program be a little bit paranoid and make a false
detection... or would they rather it miss a newly released malware and end up with an infected computer instead.
When the notifications system is used make sure that you can be notified about blocked connections of System
process. If System is added in the notifications exceptions list, then the notification will not be displayed.
To debug connectivity problems, when a software is being blocked, use the Connections Log to see the recently
blocked connections and make an idea of which rule is still required.
Similar to the event above, you can check the events below to find more info:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
1. Make sure that you don't have multiple places from where wfcUI.exe is executed. The program should be executed
only from the key above.
2. Make sure that wfcUI.exe is not blocked from being executed by a 3rd party security software, including Windows
Defender.
3. Please verify if the system tray icon is not displayed in the hidden icons area.
4. Check in Task Manager if the process wfcUI.exe is running but the system tray icon is missing or if the process is
not running at all.
5. Make sure that the Run this program as an administrator check box is not checked in the Compatibility tab of
wfcUI.exe file properties. When this check box is checked, UAC will prompt the user if he wants to allow the process
to be executed. This kind of user interaction is not allowed during the Windows startup, therefore the program will
be ignored and will not be started.
• Open the lock dialog that you normally use to unlock the program.
• Press on the following key combination on your keyboard: Ctrl + Alt + U
• The lock dialog should close after the key combination was pressed.
• Open the lock dialog again and unlock the program with the following password: binisoft
If the connections between the GUI part (wfcUI.exe) and the Windows service (wfcs.exe) is not possible, then the
icon of the tray application will display an exclamation mark.
A) The service did not start. Execute services.msc and check the status of Windows Firewall Control service. The
Startup Type should be Automatic and the Status should be Started.
B) The service did not start because it encountered an error during the startup. In this case it should be an error
logged about this in the event log. Please read the Troubleshooting section.
The system tray icon displays the profile but the context menu does not work
If the system tray does not launch the Main Panel when clicking on it and does not display the context menu on right
mouse click, check the logs from the B). This behavior is usually generated by a different security software which
blocks Windows Firewall Control.
Make sure that you have the latest version of .NET Framework installed. Windows Firewall Control requires .NET
Framework 4.8 or a newer version.
The system tray icon is not displayed even if the program appears in Task
Manager
Try to close the process wfcUI.exe from Task Manager and start it again. If the program appears in Task Manager
but not in the system tray, check the answers above.
Make sure that you have the latest version of .NET Framework installed. Windows Firewall Control requires .NET
Framework 4.8 or a newer version.
• the window is closed and at least one pixel of it was outside of the screen
• the screen resolution is changed
• a different DPI scaling is used
• the window is closed when a secondary monitor is used and the monitor is removed
1. To allow the Windows Mail application to connect and synchronize your email accounts, you must create an
outbound rule for svchost.exe.
2. To send an email you have to create an outbound rule for C:\program
files\windowsapps\microsoft.windowscommunicationsapps_17.6002.42251.0_x64__8wekyb3d8bbwe\hxmail.
exe
3. To be able to add a Google account you have to create an outbound rule for
C:\windows\systemapps\microsoft.accountscontrol_cw5n1h2txyewy\accountscontrolhost.exe and one for
C:\windows\system32\authhost.exe.
When the notifications system is used make sure that you can be notified about blocked connections of svchost.exe
process. If svchost.exe is added in the notifications exceptions list, then the notification will not be displayed.
To debug connectivity problems, when a software is being blocked, use the Connections Log to see the recently
blocked connections and make an idea of which rule is still required.
When the notifications system is used make sure that you can be notified about blocked connections of svchost.exe
process. If svchost.exe is added in the notifications exceptions list, then the notification will not be displayed.
To debug connectivity problems, when a software is being blocked, use the Connections Log to see the recently
blocked connections and make an idea of which rule is still required.
Make sure you don't have the revert profile enabled to automatically set High Filtering profile in Profiles tab.
When High Filtering is set, two new firewall rules are added to the firewall, named High Filtering profile - Block
inbound connections and High Filtering profile - Block outbound connections. These two rules are defined to
block all connections for all programs. When the profile is switched to another profile, these two rules are
automatically removed. Check in Rules Panel if you don't have multiple rules with these names.
For example, the user chooses to display recently blocked connections and no entries are shown. If recently there
were many allowed connections, they filled the entire log and older blocked connections were overwritten. In this
case there is nothing to display in Connections Log since there are no records of blocked connections.
• Increase the Security log size from Event Viewer. In the Event Viewer (execute eventvwr.msc) select the Security
category and from the right click context menu select Properties. In the dialog that opens, increase the
Maximum log size value. Note that an increased log size will make the Connections Log slower since more
entries will have to be processed. For best results regarding the performance, the default Security log size is an
optimal choice.
o Avoid using a different method or a specialized software to uninstall Windows Firewall Control because it will not
work properly. Windows Firewall Control uses a custom installer and other programs will not know how to
properly uninstall it.
o If the program is locked with a password, the uninstall will not be allowed by this method. In this case first unlock
the program and then try again to uninstall it. While the program is locked with a password do not attempt to
force the uninstall of Windows Firewall Control because you will not be able to access Windows Firewall interface
any more. If you have forgotten your password, read the following section The program is locked and I can't
remember the password.
If for some reason, the uninstall does not start by using the method described above, follow the next steps to manually
uninstall the program:
a) Close the process wfcUI.exe by exiting the Windows Firewall Control tray icon or by using Task Manager.
b) Run a CMD window with Administrator privileges.
c) Execute the following commands:
d) Delete manually the installation folder. Usually this folder is C:\Program Files\Malwarebytes\Windows Firewall
Control.
Now your system should be clean of any WFC installation. You can now start again a clean installation of the latest
version.