Forum Discussion
MSIX Instal AppxManifest error 0x80070002
Hi Michael,
Thank you for reporting this issue. We are tracking a bug with regards to path tokenization but it looks like you already tried using the detokenized path and you hit another error. What is the error that you are seeing?
It would be great if you can file a feedback item using the "report a problem" button from the MSIX Packaging Tool settings > feedback tab and attach the full logs and your installer.
You can find the logs at %localappdata%\packages\Microsoft.MsixPackagingTool_8wekyb3d8bbwe\LocalState\DiagOutputDir\
Thanks,
Peyman
Hello Peyman,
i changed two times the [{System}] to VFS\SystemX86\, following error message by 99% at instal:
Fehler bei der App-Installation. Fehlermeldung: AppxManifest.xml(2560,12): Fehler 0x80080204: Das Paket "Word2003_1.0.0.0_x64__0axtw1mbg53sp" kann nicht registriert werden. Das TypeLib-Element erfordert mindestens ein untergeordnetes Win32Path-Element oder Win64Path-Element. (0x80080204)
Any Idea?
Best Karsten
- Michael MüllerNov 19, 2018Copper Contributor
After Edit the Manifest.xml we have the Log Issue:
[Warning] Unable to detect publisher name from provided certificate: System.Security.Cryptography.CryptographicException: Das angegebene Netzwerkkennwort ist falsch. bei System.Security.Cryptography.CryptographicException.ThrowCryptographicException(Int32 hr) bei System.Security.Cryptography.X509Certificates.X509Utils._LoadCertFromBlob(Byte[] rawData, IntPtr password, UInt32 dwFlags, Boolean persistKeySet, SafeCertContextHandle& pCertCtx) bei System.Security.Cryptography.X509Certificates.X509Certificate.LoadCertificateFromBlob(Byte[] rawData, Object password, X509KeyStorageFlags keyStorageFlags) bei MsixPackagingTool.ViewModel.Common.ViewModelBase.ValidateCertificatePassword(Byte[] certBytes, SecureString password) [19.11.18 18:10:38] [Warning] Unable to detect publisher name from provided certificate: System.Security.Cryptography.CryptographicException: Das angegebene Netzwerkkennwort ist falsch.
- Michael MüllerNov 20, 2018Copper ContributorWe have to put second time the certifictae in the field by editing the package manifest . Is there a problem by read the certificate in MSIX?
The certificate is up to date.
regards karsten- Peyman ZanjaniNov 20, 2018Microsoft
Hi Michael,
Looks like you are hitting an access violation error with com interface registrations, we are working on a fix and will let you know when it becomes available.
For now, try editing the manifest manually to workaround this by setting the version number to 1.5 on com:interface elements that don't have VersionNumber defined using package editor.
<com:Interface Id="000208d4-0000-0000-c000-000000000046">
<com:TypeLib Id="00020802-0000-0000-c000-000000000046" VersionNumber="1.5" />
</com:Interface>
<com:Interface Id="0002441c-0000-0000-c000-000000000046">
<com:TypeLib Id="00020802-0000-0000-c000-000000000046" VersionNumber="1.5" />
</com:Interface>
With regards to certificate, that is by design. Every time a package is modified in any way the signature goes away and you need to provide the certificate to sign the package again.
- Peyman