Installation failed: system failed to register the windows.firewall extension
yay opened this issue · comments
When I'm running the msixbundle from here https://github.com/M2Team/NanaZip/releases/tag/1.2 on Windows 11 build 22622.575 I get the following error message:
App installation failed with error message: error 0x800706D9: While processing the request, the system failed to register the windows.firewall extension due to the following error: There are no more endpoints available from the endpoint mapper.
. (0x800706d9)
I have most security features completely disabled on this machine, including Windows Defender, Firewall, VBS, etc.
Is this just how the msi installer works or is it something that you're trying to do on your side in the install script?
I have run the following commands to disable the security features mentioned:
bcdedit /set hypervisorlaunchtype off
and
https://privacy.sexy/
Privacy Over Security -> ✔️ Disable Windows Defender
Search Services in your start menu and start it, make sure the Windows Defender Firewall service exists and is running.
Otherwise, you may have to enable the Defender, and now the firewall seems to be a part of it, IDK.
NanaZip doesn't use the extension of windows.firewall and declare the capability about internet.
But it is certain that AppX/MSIX packages can't be installed in some modified versions of Windows. Also, NanaZip can't hack AppXSVC (AppX Deployment Service) and installation is completely managed by the system.
I have run the following commands to disable the security features mentioned:
bcdedit /set hypervisorlaunchtype offand https://privacy.sexy/ Privacy Over Security -> ✔️ Disable Windows Defender
I glanced the commands which will change system files(move, rename...) and their permissions. It is possible that this is the reason of AppXSVC broken.
I think NanaZip need support unpackaged mode to deal with some special system environment. (#169 )
Thank you for looking into this! Unpackaged mode would work, if menu integration (and cleanup) can be done outside of the installer.
We can quite easily make a MSI installer with WiX, but menu integration is quite a complex ordeal. From my testing it doesn't look like you can integrate into the Windows 11 context menu without involving sparse MSIX (which is also a complex ordeal by itself; might as well install the MSIX proper). The current shell extension also needs some fixes in order to work with the classic context menu using traditional installation.
e: Scratch that, there might be another way to register the shell extension. I'll try that and see how it turns out.
e: I managed to make a working MSI setup for NanaZip with the following Wix snippet:
https://gist.github.com/dinhngtu/2be7222068241f6b0801e448dd8c442c
The downside is that loading strings from package resource is broken for the shell extension, so I temporarily patched the shell extension to use the normal LoadString instead.
It also remains to see if this method works on Windows 11.
It looks like Windows Terminal has suffered the same issue. Maybe enable Windows Firewall will solve the issue.
Kenji Mouri
According to the following comment from Microsoft employee, this is not the issue of NanaZip.
We hope you subscribe this issue to get further information about EXE Installer and discuss there.
- #169
- Original posted by @MouriNaruto in #209 (comment) at 2022-09-03T21:38:54Z
NanaZip will provide exe installer (You can see the empty reversed NanaZipInstaller project in the current stage.) after NanaZip is modernized by XAML Islands.
Kenji Mouri
- Original posted by @MouriNaruto in #209 (comment) at 2022-09-03T21:38:54Z
Workaround: According to the following comment from Microsoft employee, installing for all users may obviate internet access. Please see ReadMe.md#MSIX-Package. Although NanaZip won't provide an offline license provisioning file, but the command include -SkipLicense parameter.
Also, the related issues have been closed in Windows Terminal repo.
To sum up, We are sorry to close this issue. Thanks for your support and understanding.