Windows Firewall - Export and Import a Specific Firewall Rule with Registry Editor

For those using WFC, the new version 6.9.9.3 is out
Change log:
- Fixed: Create WFC recommended rules does not work in the latest installer.
- Fixed: After installation 'Auto refresh on open' is set by default to true in Connections Log instead of false.
- Improved: Added read only access to Rules Panel, Connections Log and Notifications for standard user accounts.
- Improved: Run button will start WFC under the user account which started the installer instead of the elevated user account.
 
For those using WFC, the new version 6.9.9.4 is out
Change log:
- Improved: Request elevation button will not restart wfcUI.exe anymore. Instead, it will remove the read-only state from the current non-elevated executing instance.
- Improved: When a new rule is created by the experimental notification exception feature, Rules Panel will refresh if it is open.
 
For those using WFC, the new version 6.9.9.6 is out
Change log (same as 6.9.9.5):
- Fixed: When importing user settings the authorized groups list is not refreshed.
- Fixed: The experimental feature which auto creates allow rules for certain paths generates duplicate rules if a blocking rule prevents certain connections.
- Fixed: The tray icon does not offer any clue if the program runs in standard user mode or in elevated mode.
- Fixed: Learning mode tray context menu item remains disabled even after elevated rights are granted.
- New: Added a new WFC recommend rule for wwahost.exe which is required to reset a Windows PIN. Without this rule it is impossible to reset a Windows PIN.

Note that I consider important from the developer:
"The other rules which you created, to allow all connections, on any protocol, any port, for Dnscache service will not work. Service based rules must be more specific. Windows Firewall has some restrictions when it comes to allow connections for specific Windows services. DNS is supposed to work over UDP protocol. If you create a rule and set Any, this won't happen and the rule will be ignored. For example, inbound rules must be specific to a certain protocol. You will notice that none of the default Windows Firewall inbound rules are defined for Any protocol. This works only for outbound rules. And not always. Microsoft Windows services have some restrictions."
 
For those using WFC, the new version 6.9.9.7 is out
Change log:
- New: Added support for retrieving the friendly name for Name, Group, Description of Windows Store firewall rules.
- Fixed: When importing user settings with proxy config, the tray app wfcUI.exe crashes on startup.
- Fixed: It is not possible to remove the custom IP addresses/ranges from the High Filtering profile custom rules once they are set.
 
or those using WFC, the new version 6.11.0.0 is out
Change log (6.9.9.8):
- New: Added detection of invalid Windows Store rules. If a package is not found on the machine the rule will appear with red text in Rules Panel.
- Updated: The logic from previous version which detects the friendly name for Description property was reverted so that at least one column in Rules Panel contains the version of the package.

Change log (6.9.9.9):
- Fixed: Certain Windows Store firewall rules may show as invalid in Rules Panel when they are still valid.
- Improved: Notifications exceptions list is now sorted for uppercase entries first and then the others.

Change log (6.10.0.0):
- Improved: The export functionality was revised so that it does not stop if a rule is invalid. The invalid rule will be skipped and the others will be exported.
- Fixed: Exporting of the rules fails if one of the rules has the Description null.
- Fixed: Sorting of notifications exceptions list does not always work.

Change log (6.11.0.0):
- Fixed: Search functionality in Rules Panel does not include the Description property.
- Fixed: After creating a temporary rule from the notification dialog which includes multiple programs blocked, you must close the notification dialog otherwise all new rules are temporary.
- Improved: The algorithm for detecting invalid rules for Windows Store apps was updated to avoid false detections.
- Improved: The error handling and logging was enhanced on certain parts of code.
 
Last edited:
You must log in or register to reply here.
Back
Top