MSIX Dependencies

%3CLINGO-SUB%20id%3D%22lingo-sub-1868551%22%20slang%3D%22en-US%22%3EMSIX%20Dependencies%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1868551%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3CBR%20%2F%3E%3CBR%20%2F%3EI've%20tried%20to%20create%20an%20MSIX%20package%20which%20has%20a%20dependency%20for%20another%20MSIX%20package.%20As%20far%20as%20i%20know%2C%20if%20you%20manually%20deploy%20an%20MSIX%20package%20that%20has%20a%20dependency%2C%20the%20dependency%20must%20be%20manually%20installed%20before%2C%20because%20the%20main%20MSIX%20package%20does%20not%20know%20where%20the%20dependency%20is%20(makes%20sense).%3CBR%20%2F%3E%3CBR%20%2F%3ESo%20i%20started%20to%20make%20an%20.appinstaller%20file%20which%20contained%20the%20%3CDEPENDENCIES%3E%20element%20so%20that%20the%20installation%20could%20first%20install%20the%20dependency%2C%20and%20afterwards%20the%20main%20MSIX.%20Inside%20the%20element%2C%20the%20URI%20is%20set%20to%20an%20UNC%20path.%3CBR%20%2F%3E%3CBR%20%2F%3EWhen%20i%20try%20to%20install%20the%20package%20via%20the%20.appinstaller%20file%2C%20the%20following%20error%20occurs%3A%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%221.png%22%20style%3D%22width%3A%20814px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F232399iA93DEE8404D35F72%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%221.png%22%20alt%3D%221.png%22%20%2F%3E%3C%2FSPAN%3E%3CBR%20%2F%3E%3CBR%20%2F%3ELooking%20through%20the%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fuwp%2Fschemas%2Fappinstallerschema%2Felement-dependencies%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3Edocs%3C%2FA%3E%20about%20this%2C%20i%20can%20see%20that%20my%20package%20name%20is%20declared%20correctly.%20However%2C%20my%20appinstaller%20file%20was%20missing%20the%20dependency%20ProcessorAchitecture%2C%20which%20was%20X64%20(in%20some%20cases%2C%20i%20see%20that%20the%20AppInstaller%20is%20looking%20for%20the%20_native%20version%20by%20default).%3CBR%20%2F%3E%3CBR%20%2F%3EAfter%20placing%20the%20ProcessorAchitecture%20to%20X64%20in%20the%20.appinstaller%2C%20i%20tried%20the%20installation%20again%2C%20but%20this%20time%20with%20the%20following%20error%3A%3CBR%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%222.png%22%20style%3D%22width%3A%20814px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F232401i1C71398ACF3E70A3%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%222.png%22%20alt%3D%222.png%22%20%2F%3E%3C%2FSPAN%3E%3CBR%20%2F%3E%3CBR%20%2F%3EI%20then%20went%20and%20manually%20tried%20to%20install%20the%20dependency%20first%20(from%20my%20local%20pc)%2C%20and%20then%20the%20MSIX%20package%20(without%20the%20.appinstaller%20file).%3CBR%20%2F%3E%3CBR%20%2F%3EThe%20dependency%20is%20installed%20on%20the%20system%2C%20as%20the%20Get-AppxLog%20suggests%3A%3CBR%20%2F%3E09%2F11%2F20%20-%20Mon%209%3A45%3A32%20PM%20613%20Performance%20summary%20of%20Deployment%20Add%20operation%20on%20Package%3CBR%20%2F%3ECaphyon.SampleApplication_2.0.0.0_x64__4crez2cfzhms2%3A%3CBR%20%2F%3EOverall%20time%3A%205329%20ms%3CBR%20%2F%3EGap%3A%2016%20ms%3CBR%20%2F%3EEnqueue%20cost%3A%20109%20ms%3CBR%20%2F%3EDequeue%20delay%3A%200%20ms%3CBR%20%2F%3EGap%3A%2016%20ms%3CBR%20%2F%3EBundle%20processing%20cost%3A%200%20ms%3CBR%20%2F%3EIndexing%20cost%3A%2063%20ms%3CBR%20%2F%3EResolve%20dependency%20cost%3A%2015%20ms%3CBR%20%2F%3EGap%3A%2016%20ms%3CBR%20%2F%3ECheck%20approval%20cost%3A%20297%20ms%3CBR%20%2F%3EEvaluation%20cost%3A%202843%20ms%3CBR%20%2F%3EHardlinking%20evaluation%20cost%3A%202750%20ms%3CBR%20%2F%3EStage%20required%20cost%3A%2079%20ms%3CBR%20%2F%3EFlushing%20and%20closing%20files%20cost%3A%200%20ms%3CBR%20%2F%3EGap%3A%2015%20ms%3CBR%20%2F%3EMachine%20register%20cost%3A%2063%20ms%3CBR%20%2F%3EStage%20user%20data%20cost%3A%200%20ms%3CBR%20%2F%3EGap%3A%2031%20ms%3CBR%20%2F%3ERegistration%20cost%3A%20359%20ms%3CBR%20%2F%3EGap%3A%2016%20ms%3CBR%20%2F%3ERepository%20commit%20transaction%20cost%3A%201328%20ms%3CBR%20%2F%3EGap%3A%2031%20ms%3CBR%20%2F%3EData%20flush%20cost%3A%200%20ms%3CBR%20%2F%3EPost%20DeStage%20repository%20commit%20transaction%20cost%3A%200%20ms%3CBR%20%2F%3ERemaining%20cost%3A%2032%20ms%3CBR%20%2F%3E%3CBR%20%2F%3EBut%20when%20i%20try%20to%20install%20the%20main%20package%20it%20appears%20it%20doesn't%20detect%20the%20dependency%3A%3CBR%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%223.png%22%20style%3D%22width%3A%20814px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F232403i9A65E8F766DC81AD%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%223.png%22%20alt%3D%223.png%22%20%2F%3E%3C%2FSPAN%3E%3CBR%20%2F%3E%3CBR%20%2F%3EThe%20AppxManifest%20file%20seems%20to%20be%20ok%20according%20to%20the%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fuwp%2Fschemas%2Fappxpackage%2Fuapmanifestschema%2Felement-packagedependency%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3Edocs%3C%2FA%3E%3A%3CBR%20%2F%3E%3CDEPENDENCIES%3E%3CBR%20%2F%3E%3CTARGETDEVICEFAMILY%20maxversiontested%3D%22%26quot%3B10.0.19041.0%26quot%3B%22%20minversion%3D%22%26quot%3B10.0.17763.0%26quot%3B%22%20name%3D%22%26quot%3BWindows.Desktop%26quot%3B%2F%22%3E%3CBR%20%2F%3E%3CPACKAGEDEPENDENCY%20minversion%3D%22%26quot%3B2.0.0.0%26quot%3B%22%20name%3D%22%26quot%3BCaphyon.SampleApplication%26quot%3B%22%20publisher%3D%22%26quot%3BCN%3DTestCert_2020-3-25_14-56-53%26quot%3B%2F%22%3E%3CBR%20%2F%3E%3C%2FPACKAGEDEPENDENCY%3E%3CBR%20%2F%3E%3CBR%20%2F%3EThe%20dependency%20has%20a%20publisher%20specified%20and%20it's%20signed%2C%20so%20it%20doesn't%20fall%20in%20the%20framework%20category%2C%20and%20the%20dependency%20version%20is%20equal%20to%20the%20minimum%20version%20specified%20here.%3CBR%20%2F%3E%3CBR%20%2F%3EIn%20the%20end%2C%20i%20managed%20to%20install%20the%20main%20MSIX%20and%20dependency%20in%20the%20following%20order%3A%3CBR%20%2F%3E1.%20Manually%20install%20the%20dependency%20first%3CBR%20%2F%3E2.%20Install%20the%20main%20app%20via%20the%20.appinstaller%20file%20from%20the%20URI%20share%3CBR%20%2F%3E%3CBR%20%2F%3ESomehow%2C%20it%20then%20detects%20that%20the%20dependency%20is%20installed.%20If%20i%20try%20to%20uninstall%20the%20main%20MSIX%20package%20and%20leave%20the%20MSIX%20dependency%20on%20the%20system%2C%20and%20then%20try%20to%20reinstall%20the%20main%20MSIX%20manually%20from%20my%20PC%2C%20the%20same%20error%20code%20as%20mentioned%20earlier%20appears.%3CBR%20%2F%3E%3CBR%20%2F%3EI%20couldn't%20find%20any%20additional%20error%20codes%20other%20than%200x80070057%2C%20which%20is%20specified%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fwin32%2Fappxpkg%2Ftroubleshooting%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3Ehere%3C%2FA%3E%20that%3A%3C%2FTARGETDEVICEFAMILY%3E%3C%2FDEPENDENCIES%3E%3C%2FDEPENDENCIES%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%22One%20or%20more%20arguments%20are%20not%20valid%20If%20you%20check%20the%20AppXDeployment-Server%20event%20log%20and%20see%20the%20following%20event%3B%20While%20installing%20the%20package%2C%20the%20system%20failed%20to%20register%20the%20windows.repositoryExtension%20extension%20due%20to%20the%20following%20error%3A%20The%20parameter%20is%20incorrect.%3CBR%20%2F%3EYou%20may%20get%20this%20error%20if%20the%20manifest%20elements%20DisplayName%20or%20Description%20contain%20characters%20disallowed%20by%20Windows%20firewall%3B%20namely%20%7C%20and%20all%20%2C%20due%20to%20which%20Windows%20fails%20to%20create%20the%20AppContainer%20profile%20for%20the%20package.%20Please%20remove%20these%20characters%20from%20the%20manifest%20and%20try%20installing%20the%20package.%20%22%3CBR%20%2F%3E%3CBR%20%2F%3EAm%20i%20missing%20something%20here%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1942599%22%20slang%3D%22en-US%22%3ERe%3A%20MSIX%20Dependencies%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1942599%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F287679%22%20target%3D%22_blank%22%3E%40alexmarin89%3C%2FA%3E%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWould%20you%20please%20share%20your%20*.msix%20applications%20that%20are%20causing%20this%20error.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThank%20you!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1951059%22%20slang%3D%22en-US%22%3ERe%3A%20MSIX%20Dependencies%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1951059%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F449344%22%20target%3D%22_blank%22%3E%40Roy_MacLachlan%3C%2FA%3E%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20placed%20the%20msix%20packages%20and%20appinstaller%20file%20in%20a%20zip%20and%20uploaded%20it%20here.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

Hi,

I've tried to create an MSIX package which has a dependency for another MSIX package. As far as i know, if you manually deploy an MSIX package that has a dependency, the dependency must be manually installed before, because the main MSIX package does not know where the dependency is (makes sense).

So i started to make an .appinstaller file which contained the <Dependencies> element so that the installation could first install the dependency, and afterwards the main MSIX. Inside the element, the URI is set to an UNC path.

When i try to install the package via the .appinstaller file, the following error occurs:

1.png

Looking through the docs about this, i can see that my package name is declared correctly. However, my appinstaller file was missing the dependency ProcessorAchitecture, which was X64 (in some cases, i see that the AppInstaller is looking for the _native version by default).

After placing the ProcessorAchitecture to X64 in the .appinstaller, i tried the installation again, but this time with the following error:
2.png

I then went and manually tried to install the dependency first (from my local pc), and then the MSIX package (without the .appinstaller file).

The dependency is installed on the system, as the Get-AppxLog suggests:
09/11/20 - Mon 9:45:32 PM 613 Performance summary of Deployment Add operation on Package
Caphyon.SampleApplication_2.0.0.0_x64__4crez2cfzhms2:
Overall time: 5329 ms
Gap: 16 ms
Enqueue cost: 109 ms
Dequeue delay: 0 ms
Gap: 16 ms
Bundle processing cost: 0 ms
Indexing cost: 63 ms
Resolve dependency cost: 15 ms
Gap: 16 ms
Check approval cost: 297 ms
Evaluation cost: 2843 ms
Hardlinking evaluation cost: 2750 ms
Stage required cost: 79 ms
Flushing and closing files cost: 0 ms
Gap: 15 ms
Machine register cost: 63 ms
Stage user data cost: 0 ms
Gap: 31 ms
Registration cost: 359 ms
Gap: 16 ms
Repository commit transaction cost: 1328 ms
Gap: 31 ms
Data flush cost: 0 ms
Post DeStage repository commit transaction cost: 0 ms
Remaining cost: 32 ms

But when i try to install the main package it appears it doesn't detect the dependency:
3.png

The AppxManifest file seems to be ok according to the docs:
<Dependencies>
<TargetDeviceFamily MaxVersionTested="10.0.19041.0" MinVersion="10.0.17763.0" Name="Windows.Desktop"/>
<PackageDependency MinVersion="2.0.0.0" Name="Caphyon.SampleApplication" Publisher="CN=TestCert_2020-3-25_14-56-53"/>
</Dependencies>

The dependency has a publisher specified and it's signed, so it doesn't fall in the framework category, and the dependency version is equal to the minimum version specified here.

In the end, i managed to install the main MSIX and dependency in the following order:
1. Manually install the dependency first
2. Install the main app via the .appinstaller file from the URI share

Somehow, it then detects that the dependency is installed. If i try to uninstall the main MSIX package and leave the MSIX dependency on the system, and then try to reinstall the main MSIX manually from my PC, the same error code as mentioned earlier appears.

I couldn't find any additional error codes other than 0x80070057, which is specified here that:

 

"One or more arguments are not valid If you check the AppXDeployment-Server event log and see the following event; While installing the package, the system failed to register the windows.repositoryExtension extension due to the following error: The parameter is incorrect.
You may get this error if the manifest elements DisplayName or Description contain characters disallowed by Windows firewall; namely | and all , due to which Windows fails to create the AppContainer profile for the package. Please remove these characters from the manifest and try installing the package. "

Am i missing something here?

2 Replies

Hi @alexmarin89,

 

Would you please share your *.msix applications that are causing this error.

 

Thank you!

Hi @Roy_MacLachlan,

 

I've placed the msix packages and appinstaller file in a zip and uploaded it here.

 

Thank you