New
#1
Enable/Disable Firewall Rules for 'Application Packages' using CMD?
Hi all,
I'm trying to use the CMD prompt command
Netsh AdvFirewall Firewall SET RULE name="name" NEW...
I'm trying to configure the Firewall Rules associated with the application packages found in "C:\Program Files\WindowsApps".
However, for some reason, the usual CMD syntax to SET an existing firewall rule simply returns the error:
No rules match the specified criteria
This used to work in older versions of Windows 10. However, it doesn't work in Version 1909.
Can someone explain how to use CMD Prompt to configure the pre-existing Firewall Rules that apply to Windows Apps?
EDIT:
The following command (using the Group= keyword) works:
Netsh AdvFirewall Firewall Set Rule Group="3D Viewer" New Enable=no works fine.
BUT
Netsh AdvFirewall Firewall Set Rule Name="3D Viewer" New Enable=no
returns 'No rules match the specfified criteria'.
EDIT #2
I have dumped the firewall rules to a .txt file.
The rules that won't edit with the CMD prompt Netsh command all have names similar to the following in the .txt file:
@{Microsoft.Microsoft3DViewer_5.1902.20012.0_x64__8wekyb3d8bbwe?ms-resource://Microsoft.Microsoft3DViewer/Common.View.UWP/Resources/StoreAppName}
When i supply these names under the Name= keyword field I still receive the No rules match the specified criteria error.
EDIT #3
Checking the Registry keys at:
HKLM\SYSTEM\ControlSet001\Services\SharedAccess\Parameters\FirewallPolicy\FirewallRules
Reveals that the rule I'm using as an example(3D Viewer) has the "name="field containing the above loooooong string from EDIT #2.
Changing that stringto "3D Viewer"makes the rule editable using the syntax I've supplied (netsh AdvFirewall Firewall Set Rule).
This doesn't solve my problem (now need to edit the registry keys for each of these 'broken' rule names) but it's a step in the right direction...
Last edited by Thelps; 27 Mar 2020 at 07:07.