Forum Discussion
Solved
MSIX Packaging Tool Firewall Rule Failure
The Microsoft MSIX Packaging Tool:
Does not detect firewall rules added by the installer and add them as Desktop2 manifest entries.
Does not capture HKLM\Software\Services\CurrentControlSet\Ser...
- We tried Teamviewer, but it adds firewall rules as expected - in SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\FirewallRules
We tried, but couldn't find an app that writes firewall rules in:
SOFTWARE\Policies\Microsoft\WindowsFirewall\FirewallRules
Aniket_Banerjee
Microsoft
Microsoft
We tried converting UltraVNC in a test environment. MPT does detect the firewall, but it adds firewall rules to registry:
Computer\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\SharedAccess\Parameters\FirewallPolicy\FirewallRules instead of registry location you mentioned - HKLM\Software\Services\CurrentControlSet\Services\SharedAccess.
Maybe try TeamViewer. The package created by MMPT 2023.118 did not include a firewall entry in the manifest, but after installation I do see an entry under CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\FirewallRules\{guid}
The native installer is adding in the firewall rule properly, and it works natively, but when captured by the MMPT the package does not contain either any values under any SharedAccess key, and it is not in the Manifest as an extension. The result is that when you run the application from the MSIX package the end user is prompted for adding the firewall in. This isn't all that bad of an impact, but just nor right either.
The native installer is adding in the firewall rule properly, and it works natively, but when captured by the MMPT the package does not contain either any values under any SharedAccess key, and it is not in the Manifest as an extension. The result is that when you run the application from the MSIX package the end user is prompted for adding the firewall in. This isn't all that bad of an impact, but just nor right either.
- Aniket_BanerjeeWe tried Teamviewer, but it adds firewall rules as expected - in SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\FirewallRules
We tried, but couldn't find an app that writes firewall rules in:
SOFTWARE\Policies\Microsoft\WindowsFirewall\FirewallRules- OK. The original would have been against a much older MMPT, so it might have been addressed. Teamviewer is OK. It is not unheard of for an app developer to drop down local policies instead of direct configuration; I'll re-open if I run into it again with a publicly available app.
