Windows Firewall is incompatible with software proxies, web filtering modules, NDIS drivers, any

filtering modules
that intercept network packets. These modules may redirect the network traffic to their proxies and
the traffic will
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. This
incompatibility is between
software proxies and Windows Firewall itself, not an incompatibility with Windows Firewall
Control which does
not have any control over this behavior.
•
The notifications system is incompatible with old versions of some encryption programs
(BoxCryptor, TrueCrypt)
because they encrypt the file paths and the real paths can't be determined by Windows Firewall
Control. If you
use such security programs you have to try for yourself if this problem applies to your configuration
or not.
•
Due to multiple system configurations and software installed there may be incompatibility
problems. Please
report them and help to improve Windows Firewall Control.
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.