SOLVED

Understand load behaviour of modification packages

%3CLINGO-SUB%20id%3D%22lingo-sub-308072%22%20slang%3D%22en-US%22%3EUnderstand%20load%20behaviour%20of%20modification%20packages%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-308072%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3CBR%20%2F%3EI'm%20looking%20for%20a%20description%20of%20load%20behaviour%20in%20msix%20packages.%3C%2FP%3E%3CP%3ESample%3A%20Simple%20app%20loads%20help.txt%20from%20%25programfiles%25%5Cdemo%3C%2FP%3E%3CUL%3E%3CLI%3EMain%20msix%20contains%20help.txt%20in%20vfs%2C%20it%20loads%20every%20time.%3C%2FLI%3E%3CLI%3EMain%20msix%20doesn't%20contain%20help.txt%20in%20vfs.%20If%20help.txt%20exists%20on%20a%20local%20system%20(native)%2C%20it%20loads%20from%20here.%3C%2FLI%3E%3CLI%3EMain%20msix%20doesn't%20contain%20help.txt%20in%20vfs%2C%20but%20help.txt%20is%20in%20modification%20package%20(modi1.msix)%2C%20it%20loads%20from%20modi1%20vfs.%3C%2FLI%3E%3CLI%3EMain%20msix%20doesn't%20contain%20help.txt%20in%20vfs%2C%20but%20help.txt%20is%20in%20a%202nd%20modification%20package%20(modi2.msix)%2C%20it%20loads%20from%20modi1%20vfs%3C%2FLI%3E%3CLI%3EMain%20msix%20doesn't%20contain%20help.txt%20in%20vfs%2C%20but%20help.txt%20is%20in%20a%203nd%20modification%20package%20(alpha.msix)%2C%20it%20loads%20from%20alpha%20vfs%2C%20because%20names%20order%20is%20the%20relevant%20feature.%3C%2FLI%3E%3C%2FUL%3E%3CP%3EIs%20this%20correct%3F%3C%2FP%3E%3CP%3Ethanks%20and%20kindly%20regards%3C%2FP%3E%3CP%3EAndreas%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-325085%22%20slang%3D%22en-US%22%3ERe%3A%20Understand%20load%20behaviour%20of%20modification%20packages%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-325085%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Dian%2C%20it%20works.%20I've%20forgotten%20%22IgnorableNamespaces%3D%22rescap6%22%26gt%3B%22%20in%20the%20manifest.%20thx.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-323942%22%20slang%3D%22en-US%22%3ERe%3A%20Understand%20load%20behaviour%20of%20modification%20packages%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-323942%22%20slang%3D%22en-US%22%3E%3CP%3ESure%2C%20but%20installation%20fails%3A%3C%2FP%3E%3CP%3E-------------------------------%3C%2FP%3E%3CP%3Eadd-appxpackage%20%3A%20Fehler%20bei%20Bereitstellung.%20HRESULT%3A%200x80080204%2C%20Das%20Manifest%20des%20Appx-Pakets%20ist%20ung%C3%BCltig.%3CBR%20%2F%3EFehler%200xC00CE014%3A%20%C3%9Cberpr%C3%BCfungsfehler%20bei%20App-Manifest%3A%20Das%20App-Manifest%20muss%20gem%C3%A4%C3%9F%20dem%20Schema%20g%C3%BCltig%20sein%3A%20Zeile%2010%2C%3CBR%20%2F%3ESpalte%206.%20Hinweis%3A%20Das%20festgelegte%20Schema%20f%C3%BCr%20MaxVersionTested%20erkennt%20keine%20XML-Felder%20mit%20dem%3CBR%20%2F%3E%3CA%20href%3D%22http%3A%2F%2Fschemas.microsoft.com%2Fappx%2Fmanifest%2Ffoundation%2Fwindows10%2Frestrictedcapabilities%2F6-Namespace%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttp%3A%2F%2Fschemas.microsoft.com%2Fappx%2Fmanifest%2Ffoundation%2Fwindows10%2Frestrictedcapabilities%2F6-Namespace%3C%2FA%3E.%20Stellen%20Sie%3CBR%20%2F%3Esicher%2C%20dass%20MaxVersionTested%20richtig%20angegeben%20ist.%20Ursache%3A%20Der%20Inhalt%20des%20Elements%3CBR%20%2F%3E'%7B%3CA%20href%3D%22http%3A%2F%2Fschemas.microsoft.com%2Fappx%2Fmanifest%2Ffoundation%2Fwindows10%2Frestrictedcapabilities%2F6%7DModificat%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttp%3A%2F%2Fschemas.microsoft.com%2Fappx%2Fmanifest%2Ffoundation%2Fwindows10%2Frestrictedcapabilities%2F6%7DModificat%3C%2FA%3E%3CBR%20%2F%3EFehler%200xC00CE014%3A%20%C3%9Cberpr%C3%BCfungsfehler%20bei%20App-Manifest%3A%20Das%20App-Manifest%20muss%20gem%C3%A4%C3%9F%20dem%20Schema%20g%C3%BCltig%20sein%3A%20Zeile%2010%2C%3CBR%20%2F%3ESpalte%206.%20Hinweis%3A%20Das%20festgelegte%20Schema%20f%C3%BCr%20MaxVersionTested%20erkennt%20keine%20XML-Felder%20mit%20demhttp%3A%2F%2Fschemas.microsoft.com%2Fappx%2Fmanifest%2Ffoundation%2Fwindows10%2Frestrictedcapabilities%2F6-Namespace.%20Stellen%20Siesicher%2C%20dass%20MaxVersionTested%20richtig%20angegeben%20ist.%20Ursache%3A%20Der%20Inhalt%20des%20Elements%3CBR%20%2F%3E'%7B%3CA%20href%3D%22http%3A%2F%2Fschemas.microsoft.com%2Fappx%2Fmanifest%2Ffoundation%2Fwindows10%2Frestrictedcapabilities%2F6%7DModificationPackage%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttp%3A%2F%2Fschemas.microsoft.com%2Fappx%2Fmanifest%2Ffoundation%2Fwindows10%2Frestrictedcapabilities%2F6%7DModificationPackage%3C%2FA%3E'%20ist%3CBR%20%2F%3Egem%C3%A4%C3%9F%20dem%20Inhaltsmodell%20des%20%C3%BCbergeordneten%20Elements%3CBR%20%2F%3E'%7B%3CA%20href%3D%22http%3A%2F%2Fschemas.microsoft.com%2Fappx%2Fmanifest%2Ffoundation%2Fwindows10%7DProperties%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttp%3A%2F%2Fschemas.microsoft.com%2Fappx%2Fmanifest%2Ffoundation%2Fwindows10%7DProperties%3C%2FA%3E'%20nicht%20g%C3%BCltig.%3CBR%20%2F%3EHINWEIS%3A%20Wenn%20Sie%20weitere%20Informationen%20w%C3%BCnschen%2C%20suchen%20Sie%20im%20Ereignisprotokoll%20nach%20%5BActivityId%5D%3CBR%20%2F%3Ee26d322e-b1a9-0002-06ba-6fe2a9b1d401%2C%20oder%20verwenden%20Sie%20die%20Befehlszeile%20Get-AppxLog%20-ActivityID%3CBR%20%2F%3Ee26d322e-b1a9-0002-06ba-6fe2a9b1d401%3CBR%20%2F%3EIn%20Zeile%3A1%20Zeichen%3A1%3CBR%20%2F%3E%2B%20add-appxpackage%20.%5CNativeNotepadPolicySettings2.msix%3CBR%20%2F%3E%2B%20~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~%3CBR%20%2F%3E%2B%20CategoryInfo%20%3A%20NotSpecified%3A%20(D%3A%5CMSIX%5CSamples...ySettings2.msix%3AString)%20%5BAdd-AppxPackage%5D%2C%20Exception%3CBR%20%2F%3E%2B%20FullyQualifiedErrorId%20%3A%20DeploymentError%2CMicrosoft.Windows.Appx.PackageManager.Commands.AddAppxPackageCommand%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-323915%22%20slang%3D%22en-US%22%3ERe%3A%20Understand%20load%20behaviour%20of%20modification%20packages%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-323915%22%20slang%3D%22en-US%22%3E%3CP%3ECan%20you%20try%20installing%20the%20package%20using%20Powershell%20commands%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-321637%22%20slang%3D%22en-US%22%3ERe%3A%20Understand%20load%20behaviour%20of%20modification%20packages%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-321637%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Dian%2C%20after%20installing%20Windows%20SDK%26nbsp%3B10.0.18312.0%20on%201809%20t%20is%20possible%20to%20use%20the%20attribut%20and%20create%20a%20modification%20package%20with%20makeappx.exe.%20The%20package%20fails%20with%20the%20same%20exception.%3C%2FP%3E%3CP%3EI've%20seen%20the%20description%20to%20the%20new%20functionality%20at%20your%20web%20page%20and%20the%20hint%20to%20the%20january%20release%20of%20MSIX%20packaging%20tool.%20Where%20can%20i%20find%20this.%20Thx%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-320968%22%20slang%3D%22en-US%22%3ERe%3A%20Understand%20load%20behaviour%20of%20modification%20packages%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-320968%22%20slang%3D%22en-US%22%3E%3CP%3EAnd%20here's%20the%20manifest%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-320965%22%20slang%3D%22en-US%22%3ERe%3A%20Understand%20load%20behaviour%20of%20modification%20packages%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-320965%22%20slang%3D%22en-US%22%3E%3CP%3ESure.%20Attached%20is%20the%20manifest%20file.%20App%20install%20works%20perfectly%20with%2018312%20and%2018317.%20When%20installing%20at%201809%2C%20the%20install%20process%20terminate%20with%20%22Error%20in%20parsing%20the%20app%20package%22.%20See%20picture.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F69056i7683B26A52A33C18%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20alt%3D%22Exception.png%22%20title%3D%22Exception.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-320444%22%20slang%3D%22en-US%22%3ERe%3A%20Understand%20load%20behaviour%20of%20modification%20packages%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-320444%22%20slang%3D%22en-US%22%3E%3CP%3ECan%20you%20ensure%20that%20the%20min%20version%20of%20the%20manifest%20includes%201809%20build%3F%20It%20should%20be%20something%20like%20this%3A%3C%2FP%3E%0A%3CP%3E%3CSPAN%3E%26lt%3B%3C%2FSPAN%3E%3CSPAN%3ETargetDeviceFamily%3C%2FSPAN%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CSPAN%3EName%3C%2FSPAN%3E%3CSPAN%3E%3D%3C%2FSPAN%3E%3CSPAN%3E%22Windows.Universal%22%3C%2FSPAN%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CSTRONG%3EMinVersion%3D%2210.0.17763.0%22%26nbsp%3B%3C%2FSTRONG%3E%3CSPAN%3EMaxVersionTested%3C%2FSPAN%3E%3CSPAN%3E%3D%3C%2FSPAN%3E%3CSPAN%3E%2210.0.17763.0%22%3C%2FSPAN%3E%3CSPAN%3E%2F%3C%2FSPAN%3E%3CSPAN%3E%26gt%3B%3C%2FSPAN%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-320425%22%20slang%3D%22en-US%22%3ERe%3A%20Understand%20load%20behaviour%20of%20modification%20packages%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-320425%22%20slang%3D%22en-US%22%3EHi.%20I%20can%20create%20the%20msix%20at%20Insider%20Build%2018312%20and%20the%20Package%20works%20Fine.%20Installing%20the%20Package%20at%20actual%20Release%201809%20results%20in%20the%20parsing%20manifest%20error.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-320341%22%20slang%3D%22en-US%22%3ERe%3A%20Understand%20load%20behaviour%20of%20modification%20packages%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-320341%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%20does%20the%20modification%20package%20fail%20to%20install%20or%20the%20functionality%20is%20not%20working%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-320294%22%20slang%3D%22en-US%22%3ERe%3A%20Understand%20load%20behaviour%20of%20modification%20packages%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-320294%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Dian%2C%20it%20works%20perfectly%20with%20insider%20build%2018312%2C%20but%26nbsp%3Bit%26nbsp%3Bfails%20at%20build%201809.%20Is%20there%20a%20plan%20to%20update%201809%20to%20ignore%20the%20attribut%20if%20exists%20in%20a%20manifest.%3C%2FP%3E%3CP%3Ethx%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-319918%22%20slang%3D%22en-US%22%3ERe%3A%20Understand%20load%20behaviour%20of%20modification%20packages%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-319918%22%20slang%3D%22en-US%22%3E%3CP%3EWow%2C%20it's%20great.%20Thanks.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-314700%22%20slang%3D%22en-US%22%3ERe%3A%20Understand%20load%20behaviour%20of%20modification%20packages%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-314700%22%20slang%3D%22en-US%22%3E%3CP%3ETo%20support%20this%20scenario%20we%20added%20a%20attribute%20in%20the%20manifest%20under%20%3CPROPERTIES%3E.%20Make%20sure%20your%20modification%20package%20has%20the%20following%20attribute%3A%3C%2FPROPERTIES%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%20%3CPROPERTIES%3E%3C%2FPROPERTIES%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%20%26nbsp%3B%3CMODIFICATIONPACKAGE%3Etrue%3C%2FMODIFICATIONPACKAGE%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%20%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CP%3E%3C%2FP%3E%0A%3CP%3ETo%20update%20the%20manifest%20follow%20these%20steps%3A%26nbsp%3B%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3EGo%20to%20MSIX%20Packaging%20Tool%26nbsp%3B%3C%2FLI%3E%0A%3CLI%3EClick%20'Package%20editor'%26nbsp%3B%3C%2FLI%3E%0A%3CLI%3ESelect%20your%20package%3C%2FLI%3E%0A%3CLI%3E3.%20Click%20'Open%20package'%3C%2FLI%3E%0A%3CLI%3E%26nbsp%3BUnder%20Manifest%20file%2C%20Click%20'Open%20fil'%3C%2FLI%3E%0A%3CLI%3E%26nbsp%3BAdd%26nbsp%3B%3CSPAN%3E%20%3CMODIFICATIONPACKAGE%3Etrue%3C%2FMODIFICATIONPACKAGE%3E%20in%20%3CPROPERTIES%3E%3C%2FPROPERTIES%3E%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%26nbsp%3BClose%20the%20manifest%26nbsp%3B%3C%2FLI%3E%0A%3CLI%3EResign%20the%20package%26nbsp%3B%3C%2FLI%3E%0A%3CLI%3E%26nbsp%3BClick%20'Save'%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3CP%3EDocumentation%20highlighting%20these%20changes%20are%20coming%20shortly.%26nbsp%3B%3C%2FP%3E%3CLINGO-SUB%20id%3D%22lingo-sub-314049%22%20slang%3D%22en-US%22%3ERe%3A%20Understand%20load%20behaviour%20of%20modification%20packages%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-314049%22%20slang%3D%22en-US%22%3E%3CP%3EI've%20tested%20with%2018312%20but%20it%20doesn't%20works.%20Main%20package%20always%20win.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-313857%22%20slang%3D%22en-US%22%3ERe%3A%20Understand%20load%20behaviour%20of%20modification%20packages%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-313857%22%20slang%3D%22en-US%22%3E%3CP%3EMake%20sure%20you%20are%20on%2018312%20or%20later.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-313825%22%20slang%3D%22en-US%22%3ERe%3A%20Understand%20load%20behaviour%20of%20modification%20packages%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-313825%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20fix%20is%20out%20in%20our%20Insider%20Fast%20build.%20Please%20go%20ahead%20and%20test%20out%20the%20feature%20and%20let%20us%20know%20if%20you%20run%20into%20issues.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-308294%22%20slang%3D%22en-US%22%3ERe%3A%20Understand%20load%20behaviour%20of%20modification%20packages%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-308294%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Dian%2C%3C%2FP%3E%3CP%3Ethanks%20for%20your%20help%20-%20perfectly.%3C%2FP%3E%3CP%3EWhat%20is%20the%20timeframe%20for%20fixing%20scenario%20%233%3F%3C%2FP%3E%3CP%3EAndreas%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-308130%22%20slang%3D%22en-US%22%3ERe%3A%20Understand%20load%20behaviour%20of%20modification%20packages%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-308130%22%20slang%3D%22en-US%22%3E%3CP%20style%3D%22margin%3A%200in%3B%20font-family%3A%20Calibri%3B%20font-size%3A%2012.0pt%3B%20color%3A%20%23333333%3B%22%3EThanks%20for%20your%20question!%20Here%20is%20a%20description%20of%20what%20happens%20when%20you%20have%20a%20main%20package%20and%20a%20modification%20packages.%26nbsp%3B%3C%2FP%3E%0A%3CP%20style%3D%22margin%3A%200in%3B%20font-family%3A%20Calibri%3B%20font-size%3A%2012.0pt%3B%20color%3A%20%23333333%3B%22%3EScenario%201%3A%20Main%20package%20with%20help.txt%20in%20vfs%20with%20no%20modification%20packages%3C%2FP%3E%0A%3CP%20style%3D%22margin%3A%200in%3B%20font-family%3A%20Calibri%3B%20font-size%3A%2012.0pt%3B%20color%3A%20%23333333%3B%22%3EWhen%20the%20app%20runs%2C%20main%20app%20will%20load%20help.txt.%3C%2FP%3E%0A%3CP%20style%3D%22margin%3A%200in%3B%20font-family%3A%20Calibri%3B%20font-size%3A%2012.0pt%3B%20color%3A%20%23333333%3B%22%3EScenario%202%3A%20Main%20package%20with%20help.txt%20in%20vfs%20with%20modification%20packages%20that%20contains%20no%20help.txt%20in%20vfs%3C%2FP%3E%0A%3CP%20style%3D%22margin%3A%200in%3B%20font-family%3A%20Calibri%3B%20font-size%3A%2012.0pt%3B%20color%3A%20%23333333%3B%22%3EWhen%20the%20app%20runs%2C%20the%20main%20app%20will%20load%20help.txt%20from%20the%20main%20app%3C%2FP%3E%0A%3CP%20style%3D%22margin%3A%200in%3B%20font-family%3A%20Calibri%3B%20font-size%3A%2012.0pt%3B%20color%3A%20%23333333%3B%22%3EScenario%203%3A%20Main%20package%20with%20help.txt%20in%20vfs%20with%20modification%20package%20that%20contains%20help.txt%20in%20vfs%3C%2FP%3E%0A%3CP%20style%3D%22margin%3A%200in%3B%20font-family%3A%20Calibri%3B%20font-size%3A%2012.0pt%3B%20color%3A%20%23333333%3B%22%3EWhen%20the%20app%20runs%2C%20the%20main%20package%20will%20load%20help.txt%20from%20the%20main%20app.%20This%20is%20because%20we%20found%20that%20the%20main%20package%20will%20always%20win%20over%20the%20modification%20packages.%3C%2FP%3E%0A%3CP%20style%3D%22margin%3A%200in%3B%20font-family%3A%20Calibri%3B%20font-size%3A%2012.0pt%3B%20color%3A%20%23333333%3B%22%3EScenario%204%3A%20main%20package%20does%20not%20contain%20help.txt%20in%20vfs%20with%20modification%20package%20that%20contains%20help.txt%20in%20vfs.%20This%20is%20because%20when%20we%20do%20a%20look%20up%2C%20help.txt%20is%20first%20found%20in%20the%20modification%20package.%3C%2FP%3E%0A%3CP%20style%3D%22margin%3A%200in%3B%20font-family%3A%20Calibri%3B%20font-size%3A%2012.0pt%3B%20color%3A%20%23333333%3B%22%3EWhen%20the%20app%20runs%2C%20the%20main%20app%20will%20load%20help.txt%20from%20the%20modification%20package%3C%2FP%3E%0A%3CP%20style%3D%22margin%3A%200in%3B%20font-family%3A%20Calibri%3B%20font-size%3A%2012.0pt%3B%20color%3A%20%23333333%3B%22%3EScenario%205%3A%20main%20package%20does%20not%20contain%20help.txt%20in%20vfs%20with%20modification%20package%20%231%20(amodi.msix)%20and%20modification%20package%20%232%20(bmodi.msix)%2C%20both%20having%20help.txt%20in%20vfs.%3C%2FP%3E%0A%3CP%20style%3D%22margin%3A%200in%3B%20font-family%3A%20Calibri%3B%20font-size%3A%2012.0pt%3B%20color%3A%20%23333333%3B%22%3EWhen%20the%20app%20runs%2C%20the%20main%20app%20will%20load%20help.txt%20from%20modification%20package%20%231.%20This%20is%20because%20when%20we%20do%20a%20look%20up%2C%20we%20found%20help.txt%20first%20in%20amodi.msix.%3C%2FP%3E%0A%3CP%20style%3D%22margin%3A%200in%3B%20font-family%3A%20Calibri%3B%20font-size%3A%2012.0pt%3B%20color%3A%20%23333333%3B%22%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%20style%3D%22margin%3A%200in%3B%20font-family%3A%20Calibri%3B%20font-size%3A%2012.0pt%3B%20color%3A%20%23333333%3B%22%3EIn%20the%20next%20update%2C%20we%20will%20be%20fixing%20scenario%20%233%2C%20so%20that%20modification%20packages%20can%20overlay%20their%20files%20correctly%20when%20loading%20the%20main%20package.%20More%20details%20will%20be%20posted%20at%26nbsp%3B%3CU%3E%3CFONT%20color%3D%22%230b0117%22%3E%3CA%20href%3D%22http%3A%2F%2Faka.ms%2Fmsix%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttp%3A%2F%2Faka.ms%2Fmsix%3C%2FA%3E%3C%2FFONT%3E%3C%2FU%3E%20soon.%26nbsp%3B%3C%2FP%3E%0A%3CP%20style%3D%22margin%3A%200in%3B%20font-family%3A%20Calibri%3B%20font-size%3A%2012.0pt%3B%20color%3A%20%23333333%3B%22%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%20style%3D%22margin%3A%200in%3B%20font-family%3A%20Calibri%3B%22%3E%3CSPAN%20style%3D%22font-size%3A%2012.0pt%3B%20color%3A%20%23333333%3B%22%3EMore%20info%20on%20modification%20packages%20in%20the%20current%20release%20visit%20%3C%2FSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fmsix%2Fmodification-package-1809-update%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3E%3CSPAN%20style%3D%22font-size%3A%2011.0pt%3B%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fmsix%2Fmodification-package-1809-update%3C%2FSPAN%3E%3C%2FA%3E%3C%2FP%3E%0A%3CP%20style%3D%22margin%3A%200in%3B%20font-family%3A%20inherit%3B%20font-size%3A%2012.0pt%3B%20color%3A%20%23333333%3B%22%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Contributor

Hello,
I'm looking for a description of load behaviour in msix packages.

Sample: Simple app loads help.txt from %programfiles%\demo

  • Main msix contains help.txt in vfs, it loads every time.
  • Main msix doesn't contain help.txt in vfs. If help.txt exists on a local system (native), it loads from here.
  • Main msix doesn't contain help.txt in vfs, but help.txt is in modification package (modi1.msix), it loads from modi1 vfs.
  • Main msix doesn't contain help.txt in vfs, but help.txt is in a 2nd modification package (modi2.msix), it loads from modi1 vfs
  • Main msix doesn't contain help.txt in vfs, but help.txt is in a 3nd modification package (alpha.msix), it loads from alpha vfs, because names order is the relevant feature.

Is this correct?

thanks and kindly regards

Andreas

17 Replies
Best Response confirmed by John Vintzel (Microsoft)
Solution

Thanks for your question! Here is a description of what happens when you have a main package and a modification packages. 

Scenario 1: Main package with help.txt in vfs with no modification packages

When the app runs, main app will load help.txt.

Scenario 2: Main package with help.txt in vfs with modification packages that contains no help.txt in vfs

When the app runs, the main app will load help.txt from the main app

Scenario 3: Main package with help.txt in vfs with modification package that contains help.txt in vfs

When the app runs, the main package will load help.txt from the main app. This is because we found that the main package will always win over the modification packages.

Scenario 4: main package does not contain help.txt in vfs with modification package that contains help.txt in vfs. This is because when we do a look up, help.txt is first found in the modification package.

When the app runs, the main app will load help.txt from the modification package

Scenario 5: main package does not contain help.txt in vfs with modification package #1 (amodi.msix) and modification package #2 (bmodi.msix), both having help.txt in vfs.

When the app runs, the main app will load help.txt from modification package #1. This is because when we do a look up, we found help.txt first in amodi.msix.

 

In the next update, we will be fixing scenario #3, so that modification packages can overlay their files correctly when loading the main package. More details will be posted at http://aka.ms/msix soon. 

 

More info on modification packages in the current release visit https://docs.microsoft.com/en-us/windows/msix/modification-package-1809-update

 

Hi Dian,

thanks for your help - perfectly.

What is the timeframe for fixing scenario #3?

Andreas

The fix is out in our Insider Fast build. Please go ahead and test out the feature and let us know if you run into issues. 

Make sure you are on 18312 or later.

I've tested with 18312 but it doesn't works. Main package always win. 

To support this scenario we added a attribute in the manifest under <Properties>. Make sure your modification package has the following attribute:

  <Properties>

   <rescap6:ModificationPackage>true</rescap6:ModificationPackage>​

  </Properties>​

To update the manifest follow these steps: 

  1. Go to MSIX Packaging Tool 
  2. Click 'Package editor' 
  3. Select your package
  4. 3. Click 'Open package'
  5.  Under Manifest file, Click 'Open fil'
  6.  Add  <rescap6:ModificationPackage>true</rescap6:ModificationPackage>​ in <Properties>
  7.  Close the manifest 
  8. Resign the package 
  9.  Click 'Save'

Documentation highlighting these changes are coming shortly. 

Wow, it's great. Thanks.

Hi Dian, it works perfectly with insider build 18312, but it fails at build 1809. Is there a plan to update 1809 to ignore the attribut if exists in a manifest.

thx

Hi, does the modification package fail to install or the functionality is not working? 

Hi. I can create the msix at Insider Build 18312 and the Package works Fine. Installing the Package at actual Release 1809 results in the parsing manifest error.

Can you ensure that the min version of the manifest includes 1809 build? It should be something like this:

<TargetDeviceFamily Name="Windows.Universal" MinVersion="10.0.17763.0" MaxVersionTested="10.0.17763.0"/> 

Sure. Attached is the manifest file. App install works perfectly with 18312 and 18317. When installing at 1809, the install process terminate with "Error in parsing the app package". See picture.

 

Exception.png

And here's the manifest

Hi Dian, after installing Windows SDK 10.0.18312.0 on 1809 t is possible to use the attribut and create a modification package with makeappx.exe. The package fails with the same exception.

I've seen the description to the new functionality at your web page and the hint to the january release of MSIX packaging tool. Where can i find this. Thx

Can you try installing the package using Powershell commands? 

Sure, but installation fails:

-------------------------------

add-appxpackage : Fehler bei Bereitstellung. HRESULT: 0x80080204, Das Manifest des Appx-Pakets ist ungültig.
Fehler 0xC00CE014: Überprüfungsfehler bei App-Manifest: Das App-Manifest muss gemäß dem Schema gültig sein: Zeile 10,
Spalte 6. Hinweis: Das festgelegte Schema für MaxVersionTested erkennt keine XML-Felder mit dem
http://schemas.microsoft.com/appx/manifest/foundation/windows10/restrictedcapabilities/6-Namespace. Stellen Sie
sicher, dass MaxVersionTested richtig angegeben ist. Ursache: Der Inhalt des Elements
'{http://schemas.microsoft.com/appx/manifest/foundation/windows10/restrictedcapabilities/6}Modificat
Fehler 0xC00CE014: Überprüfungsfehler bei App-Manifest: Das App-Manifest muss gemäß dem Schema gültig sein: Zeile 10,
Spalte 6. Hinweis: Das festgelegte Schema für MaxVersionTested erkennt keine XML-Felder mit dem
http://schemas.microsoft.com/appx/manifest/foundation/windows10/restrictedcapabilities/6-Namespace. Stellen Sie
sicher, dass MaxVersionTested richtig angegeben ist. Ursache: Der Inhalt des Elements
'{http://schemas.microsoft.com/appx/manifest/foundation/windows10/restrictedcapabilities/6}Modificatio...' ist
gemäß dem Inhaltsmodell des übergeordneten Elements
'{http://schemas.microsoft.com/appx/manifest/foundation/windows10}Properties' nicht gültig.
HINWEIS: Wenn Sie weitere Informationen wünschen, suchen Sie im Ereignisprotokoll nach [ActivityId]
e26d322e-b1a9-0002-06ba-6fe2a9b1d401, oder verwenden Sie die Befehlszeile Get-AppxLog -ActivityID
e26d322e-b1a9-0002-06ba-6fe2a9b1d401
In Zeile:1 Zeichen:1
+ add-appxpackage .\NativeNotepadPolicySettings2.msix
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (D:\MSIX\Samples...ySettings2.msix:String) [Add-AppxPackage], Exception
+ FullyQualifiedErrorId : DeploymentError,Microsoft.Windows.Appx.PackageManager.Commands.AddAppxPackageCommand

Hi Dian, it works. I've forgotten "IgnorableNamespaces="rescap6">" in the manifest. thx.