SOLVED

MSIX: Unable to update TargetDevice in Manifest XML file

%3CLINGO-SUB%20id%3D%22lingo-sub-2397112%22%20slang%3D%22en-US%22%3EMSIX%3A%20Unable%20to%20update%20TargetDevice%20in%20Manifest%26nbsp%3BXML%20file%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2397112%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20Team%2C%3C%2FP%3E%3CP%3E%3CSTRONG%3EIssue%3C%2FSTRONG%3E%3A%20MSIX%3A%20Unable%20to%20update%20TargetDevice%20in%20Manifest%20file%3C%2FP%3E%3CP%3E%3CSTRONG%3EScenario%3C%2FSTRONG%3E%3A%3CBR%20%2F%3EPackaging%20Build%20machine%20version%3A1909%3CBR%20%2F%3ETest%20machine%20version%3A%201809%20and%201803%3C%2FP%3E%3CP%3E%3CSTRONG%3EError%3C%2FSTRONG%3E%3A%20Unsupported%20version%20while%20deploying%20the%20package%3C%2FP%3E%3CP%3EMSIX%20package%20is%20captured%20on%201909%20build.%20but%20while%20installing%20the%20package%20on%20the%20windows10-1809%20version%20machine%20getting%20OS%20unsupported%20version%20error.%3C%2FP%3E%3CP%3EAs%20per%20my%20understanding%2C%20the%20MinimumVersion%20of%20TargetDevice%20in%20Manifest.xml%20file%20is%20set%20to%201909%20hence%20package%20is%20failing%20to%20install%20on%20the%201809%20build%20machine%3C%2FP%3E%3CP%3ESo%20fix%20this%20issue%20we%20are%20trying%20to%20update%20the%20Minimum%20version%20in%20the%20Manifest%20file%20but%20after%20updating%20TargetDevice%20in%20the%20package%20it%20is%20still%20pointing%20to%20the%201909%20version%20after%20saving%20the%20package.%20we%20are%20using%20MSIX%20packaging%20tool%20to%20update%20the%20manifest.xml.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20there%20any%20restriction%20of%20using%20the%20same%20build%20for%20packaging%20and%20for%20testing%3F%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3ECould%20you%20please%20help%20us%20in%20fixing%20this%20issue%3F%20Let%20us%20know%20if%20you%20need%20more%20information%20on%20this.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2405621%22%20slang%3D%22en-US%22%3ERe%3A%20MSIX%3A%20Unable%20to%20update%20TargetDevice%20in%20Manifest%26nbsp%3BXML%20file%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2405621%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%2F787767%22%20target%3D%22_blank%22%3E%40shreedhar_ghare%3C%2FA%3E%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThank%20you%20for%20reaching%20out%2C%20I'd%26nbsp%3Bbe%20happy%20to%20help%20out.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EPlease%20provide%20some%20additional%20information%3A%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3ECan%20you%20confirm%20that%20the%20device%20you%20are%20failing%20to%20install%20on%20is%20Windows%2010%201909.%3C%2FLI%3E%0A%3CLI%3EPlease%20provide%20the%20steps%20you%20performed%20when%20updating%20the%20Min%20and%20tested%20versions%20of%20the%20Windows%20App%20in%20the%20AppXManifest.%26nbsp%3B%3C%2FLI%3E%0A%3CLI%3EWhat%20value%20were%20you%20attempting%20to%20set%20for%20the%20%3CEM%3E%3CU%3EMinVersion%3C%2FU%3E%3C%2FEM%3E%2C%20and%20%3CEM%3E%3CU%3ETestVersion%3C%2FU%3E%3C%2FEM%3E%3F%3C%2FLI%3E%0A%3CLI%3EIf%20you%20are%20using%20the%20Microsoft%20Packaging%20Tool%20to%20edit%20the%20AppXManifest%2C%20which%20version%20of%20the%20tool%20are%20you%20using%3F%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EQuestion%3A%3C%2FSTRONG%3E%20Is%20there%20any%20restriction%20of%20using%20the%20same%20build%20for%20packaging%20and%20for%20testing%3F%26nbsp%3B%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E%3CSTRONG%3EAnswer%3A%3C%2FSTRONG%3E%20The%20Windows%2010%20Build%20that%20you%20test%20on%2C%20should%20be%20reflective%20of%20the%20devices%20existing%20in%20your%20environment.%20Meaning%20if%20all%20of%20your%20Windows%2010%20devices%20are%20on%20Ver.%201909%2C%20you%20should%20be%20testing%20your%20Windows%20Apps%20on%20Ver.%201909.%26nbsp%3B%3C%2FLI%3E%0A%3C%2FUL%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2409731%22%20slang%3D%22en-US%22%3ERe%3A%20MSIX%3A%20Unable%20to%20update%20TargetDevice%20in%20Manifest%26nbsp%3BXML%20file%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2409731%22%20slang%3D%22en-US%22%3E%3CP%3E%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%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%20very%20much%20for%20your%20response!!!%3C%2FP%3E%3CP%3E%26nbsp%3BPlease%20find%20my%20comments%20below%2C%3C%2FP%3E%3CP%3ECan%20you%20confirm%20that%20the%20device%20you%20are%20failing%20to%20install%20on%20is%20Windows%2010%201909.%3C%2FP%3E%3CP%3E%3CSTRONG%3EYes%20that%20is%20correct%201909(OS%20Build%2018363.1556)%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3EPlease%20provide%20the%20steps%20you%20performed%20when%20updating%20the%20Min%20and%20tested%20versions%20of%20the%20Windows%20App%20in%20the%20AppXManifest.%3C%2FP%3E%3CP%3E%3CSTRONG%3ESteps%3C%2FSTRONG%3E%3C%2FP%3E%3COL%3E%3CLI%3E%3CSTRONG%3ESelect%20.MSIX%20file%20and%20right%20click%20to%20edit%20in%20MSIX%20packaging%20Tool%3C%2FSTRONG%3E%3C%2FLI%3E%3CLI%3E%3CSTRONG%3EFrom%20Package%20Editor%20select%20%22Open%20File%22%20under%20Manifest%20file%20section%3C%2FSTRONG%3E%3C%2FLI%3E%3CLI%3E%3CSTRONG%3EManifest%20file%20will%20be%20open%20in%20notepad.exe%20the%20replace%20belo%20line%3C%2FSTRONG%3E%3C%2FLI%3E%3C%2FOL%3E%3CP%3E%3CSTRONG%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%20old%3A%3CTARGETDEVICEFAMILY%20name%3D%22%26quot%3BWindows.Desktop%26quot%3B%22%20minversion%3D%22%26quot%3B10.0.19025.0%26quot%3B%22%20maxversiontested%3D%22%26quot%3B10.0.19041.1%26quot%3B%22%3E%3C%2FTARGETDEVICEFAMILY%3E%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%3CSTRONG%3Enew%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20%3CTARGETDEVICEFAMILY%20name%3D%22%26quot%3BWindows.Desktop%26quot%3B%22%20minversion%3D%22%26quot%3B10.0.18363.1556%26quot%3B%22%20maxversiontested%3D%22%26quot%3B10.0.19041.1%26quot%3B%22%3E%3C%2FTARGETDEVICEFAMILY%3E%3C%2FSTRONG%3E%3C%2FP%3E%3COL%3E%3CLI%3E%3CSTRONG%3EClick%20Save%20button%20then%20it%20will%20ask%20to%20increase%20Pakcage%20version%20select%20%22Yes%20Increment%22%3C%2FSTRONG%3E%3C%2FLI%3E%3CLI%3E%3CSTRONG%3ENew%20MSIX%20file%20will%20be%20generated%20with%20new%20version%20AdobeAcrobatReaderDC21.001.20155_1.0.1.0_x64__8h66172c634n0_2.msix%3C%2FSTRONG%3E%3C%2FLI%3E%3C%2FOL%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3EBut%20when%20we%20check%20the%20Manifest%20file%20by%20extracting%20loose%20file%20it%20is%20still%20using%20old%20min%20version%2010.0.19025.0%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EQ%3A%20What%20value%20were%20you%20attempting%20to%20set%20for%20the%20MinVersion%2C%20and%20TestVersion%3F%3C%2FP%3E%3CP%3E%3CSTRONG%3EPackaging%20machine%20version%202004%20(OS%20Build%2019041.985)%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3EDefault%20value%3A%3C%2FP%3E%3CP%3E%3CSTRONG%3E%3CTARGETDEVICEFAMILY%20name%3D%22%26quot%3BWindows.Desktop%26quot%3B%22%20minversion%3D%22%26quot%3B10.0.19025.0%26quot%3B%22%20maxversiontested%3D%22%26quot%3B10.0.19041.1%26quot%3B%22%3E%3C%2FTARGETDEVICEFAMILY%3E%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3ETest%20machine%20version%201909(OS%20Build%2018363.1556)%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3EExpected%20value%3C%2FP%3E%3CP%3E%3CSTRONG%3E%3CTARGETDEVICEFAMILY%20name%3D%22%26quot%3BWindows.Desktop%26quot%3B%22%20minversion%3D%22%26quot%3B10.0.18363.1556%26quot%3B%22%20maxversiontested%3D%22%26quot%3B10.0.19041.1%26quot%3B%22%3E%3C%2FTARGETDEVICEFAMILY%3E%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EQ%3A%20If%20you%20are%20using%20the%20Microsoft%20Packaging%20Tool%20to%20edit%20the%20AppXManifest%2C%20which%20version%20of%20the%20tool%20are%20you%20using%3F%3C%2FP%3E%3CP%3E%3CSTRONG%3EMSIX%20Packaging%20Tool%201.2021.422.0%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EJust%20to%20update%20you%20we%20are%20providing%20an%20MSIX%20solution%20to%20our%20existing%20customer.%20they%20have%20an%20older%20build%20at%20their%20end.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2414485%22%20slang%3D%22en-US%22%3ERe%3A%20MSIX%3A%20Unable%20to%20update%20TargetDevice%20in%20Manifest%26nbsp%3BXML%20file%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2414485%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%2F787767%22%20target%3D%22_blank%22%3E%40shreedhar_ghare%3C%2FA%3E%2C%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThank%20you%20for%20the%20quick%20response!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFollowing%20the%20steps%20you%20provided%20(using%20a%20newer%20Operating%20System%2C%20but%20same%20version%20of%20MSIX%20Packaging%20Tool)%20in%20the%20reproduction%20of%20the%20issue%2C%20I%20was%20able%20to%20successfully%20update%20the%20version%20information%20to%20the%20values%20you've%20specified%2C%20as%20well%20as%20setting%26nbsp%3B%3CEM%3E10.0.0.0%3C%2FEM%3E%20for%20both%20the%20%3CEM%3EMaxVersionTested%3C%2FEM%3E%60%20and%20the%20%3CEM%3EMinVersion%20%3C%2FEM%3Evalues.%20I%20wanted%20to%20confirm%20with%20you%20that%20after%20you%20updated%20the%20Manifest%20file%2C%20did%20you%20select%26nbsp%3B%3CSTRONG%3EFile%20%26gt%3B%20Save%3C%2FSTRONG%3E%20from%20within%20Notepad%3F%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAfter%20you've%20updated%20and%20closed%20the%20Windows%20App%20AppxManifest%2C%20re-open%20the%20file%20and%20verify%20that%20the%20setting%20changes%20you%20made%20were%20retained%20before%20saving%20and%20packaging%20your%20Windows%20App.%20Please%20let%20me%20know%20if%20the%20settings%20are%20updated%20to%20the%20values%20you've%20specified.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2416452%22%20slang%3D%22en-US%22%3ERe%3A%20MSIX%3A%20Unable%20to%20update%20TargetDevice%20in%20Manifest%26nbsp%3BXML%20file%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2416452%22%20slang%3D%22en-US%22%3EHello%20Roy_MacLachlan%3CBR%20%2F%3E%3CBR%20%2F%3EThank%20you%20for%20your%20quick%20response!%3CBR%20%2F%3E%3CBR%20%2F%3EAs%20suggested%20by%20you%20we%20have%20tried%20the%20steps%20below%2C%3CBR%20%2F%3E1.%20Open%20MSIX%20file%20in%20Edit%20MSIX%20packaging%20Tool%3CBR%20%2F%3E2.%20Select%20%22Open%20file%22%20under%20Manifest%20section--%26gt%3B%20FIle%20opened%20in%20notepad.txt%3CBR%20%2F%3E3.%20Updated%20the%20MinVersion%3D%2210.0.18363.1556%22%20Saved%20the%20notepad%20and%20closed%3CBR%20%2F%3E4%20Again%20click%20the%20%22Open%20file%22%20option%20and%20observed%20that%20MinVersion%20still%20pointing%20to%20MinVersion%3D%2210.0.19025.0%22%20old%20value.%3CBR%20%2F%3E%3CBR%20%2F%3EThat%20means%20settings%20are%20not%20getting%20updated%20with%20the%20%22Open%20file%22%20option.%20Please%20find%20the%20attached%20screenshot%20for%20more%20details.%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2416453%22%20slang%3D%22en-US%22%3ERe%3A%20MSIX%3A%20Unable%20to%20update%20TargetDevice%20in%20Manifest%26nbsp%3BXML%20file%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2416453%22%20slang%3D%22en-US%22%3EUnable%20to%20attach%20the%20screenshot.%20Let%20me%20know%20if%20you%20needs%20any%20logs%20from%20my%20machine%2C%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2417541%22%20slang%3D%22en-US%22%3ERe%3A%20MSIX%3A%20Unable%20to%20update%20TargetDevice%20in%20Manifest%26nbsp%3BXML%20file%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2417541%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%2F787767%22%20target%3D%22_blank%22%3E%40shreedhar_ghare%3C%2FA%3E%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWhile%20editing%20the%20Windows%20App%20using%20the%20MSIX%20Packaging%20Tool%2C%20can%20you%20please%20review%20the%20%3CSTRONG%3EServices%20report%3C%2FSTRONG%3E%20section%2C%20and%20confirm%20if%20there%20are%20any%20Services%20included%20in%20your%20package.%20(See%20the%20following%20image%20for%20reference)%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22Roy_MacLachlan_1-1622833986528.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F286435i8D43F594CDFB9701%2Fimage-size%2Fmedium%3Fv%3Dv2%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22Roy_MacLachlan_1-1622833986528.png%22%20alt%3D%22Roy_MacLachlan_1-1622833986528.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CBR%20%2F%3EPlease%20follow%20the%20instructions%20found%20in%20the%26nbsp%3B%3CA%20href%3D%22http%3A%2F%2FHi%26nbsp%3B%40shreedhar_ghare%2C%2520%20%5BMicrosoft%20Docs%20%7C%20MSIX%20Packaging%20Tool%20Logs%5D(https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fmsix%2Fpackaging-tool%2Ftool-known-issues%23troubleshooting)%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3EMicrosoft%20Docs%20%7C%20MSIX%20Packaging%20Tool%20Logs%3C%2FA%3E%26nbsp%3BArticle%20to%20retrieve%20the%20MSIX%20Packaging%20Tool%20logs.%20You%20can%20share%20these%20as%20a%20Private%20message%20to%20myself%2C%20or%20as%20an%20attachment%20to%20this%20post.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThank%20you%2C%3C%2FP%3E%0A%3CP%3ERoy%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2417580%22%20slang%3D%22en-US%22%3ERe%3A%20MSIX%3A%20Unable%20to%20update%20TargetDevice%20in%20Manifest%26nbsp%3BXML%20file%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2417580%22%20slang%3D%22en-US%22%3EHello%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%3CBR%20%2F%3E%3CBR%20%2F%3EYes%2C%20the%20application%20Adobe%20AcrobatReaderDC%2021.001.20155%20has%20Adobe%20ARM%20service%20(AdobeARMservice).%3CBR%20%2F%3EIs%20this%20service%20creating%20an%20issue%3F%3CBR%20%2F%3EThe%20provided%20link%20is%20not%20opening%20at%20my%20end%20getting%20the%20error%20%22about%3Ablank%23blocked%22%3CBR%20%2F%3EI%20will%20try%20to%20get%20logs%20and%20share%20them%20with%20you.%3CBR%20%2F%3E%3CBR%20%2F%3EThank%20you%2C%3CBR%20%2F%3EShreedhar%20Ghare%3C%2FLINGO-BODY%3E
Occasional Contributor

Hello Team,

Issue: MSIX: Unable to update TargetDevice in Manifest file

Scenario:
Packaging Build machine version:1909
Test machine version: 1809 and 1803

Error: Unsupported version while deploying the package

MSIX package is captured on 1909 build. but while installing the package on the windows10-1809 version machine getting OS unsupported version error.

As per my understanding, the MinimumVersion of TargetDevice in Manifest.xml file is set to 1909 hence package is failing to install on the 1809 build machine

So fix this issue we are trying to update the Minimum version in the Manifest file but after updating TargetDevice in the package it is still pointing to the 1909 version after saving the package. we are using MSIX packaging tool to update the manifest.xml.

 

Is there any restriction of using the same build for packaging and for testing?  

Could you please help us in fixing this issue? Let us know if you need more information on this.

11 Replies

Hi @shreedhar_ghare,

 

Thank you for reaching out, I'd be happy to help out.

 

Please provide some additional information:

  • Can you confirm that the device you are failing to install on is Windows 10 1909.
  • Please provide the steps you performed when updating the Min and tested versions of the Windows App in the AppXManifest. 
  • What value were you attempting to set for the MinVersion, and TestVersion?
  • If you are using the Microsoft Packaging Tool to edit the AppXManifest, which version of the tool are you using?

 

Question: Is there any restriction of using the same build for packaging and for testing?  

  • Answer: The Windows 10 Build that you test on, should be reflective of the devices existing in your environment. Meaning if all of your Windows 10 devices are on Ver. 1909, you should be testing your Windows Apps on Ver. 1909. 

@Roy_MacLachlan 

Thank you very much for your response!!!

 Please find my comments below,

Can you confirm that the device you are failing to install on is Windows 10 1909.

Yes that is correct 1909(OS Build 18363.1556)

Please provide the steps you performed when updating the Min and tested versions of the Windows App in the AppXManifest.

Steps

  1. Select .MSIX file and right click to edit in MSIX packaging Tool
  2. From Package Editor select "Open File" under Manifest file section
  3. Manifest file will be open in notepad.exe the replace belo line

    old:<TargetDeviceFamily Name="Windows.Desktop" MinVersion="10.0.19025.0" MaxVersionTested="10.0.19041.1" />

new     <TargetDeviceFamily Name="Windows.Desktop" MinVersion="10.0.18363.1556" MaxVersionTested="10.0.19041.1" />

  1. Click Save button then it will ask to increase Pakcage version select "Yes Increment"
  2. New MSIX file will be generated with new version AdobeAcrobatReaderDC21.001.20155_1.0.1.0_x64__8h66172c634n0_2.msix

 

But when we check the Manifest file by extracting loose file it is still using old min version 10.0.19025.0

 

Q: What value were you attempting to set for the MinVersion, and TestVersion?

Packaging machine version 2004 (OS Build 19041.985)

Default value:

<TargetDeviceFamily Name="Windows.Desktop" MinVersion="10.0.19025.0" MaxVersionTested="10.0.19041.1" />

 

Test machine version 1909(OS Build 18363.1556)

Expected value

<TargetDeviceFamily Name="Windows.Desktop" MinVersion="10.0.18363.1556" MaxVersionTested="10.0.19041.1" />

 

Q: If you are using the Microsoft Packaging Tool to edit the AppXManifest, which version of the tool are you using?

MSIX Packaging Tool 1.2021.422.0

 

Just to update you we are providing an MSIX solution to our existing customer. they have an older build at their end. 

 

Hi @shreedhar_ghare

Thank you for the quick response!

 

Following the steps you provided (using a newer Operating System, but same version of MSIX Packaging Tool) in the reproduction of the issue, I was able to successfully update the version information to the values you've specified, as well as setting 10.0.0.0 for both the MaxVersionTested` and the MinVersion values. I wanted to confirm with you that after you updated the Manifest file, did you select File > Save from within Notepad? 

 

After you've updated and closed the Windows App AppxManifest, re-open the file and verify that the setting changes you made were retained before saving and packaging your Windows App. Please let me know if the settings are updated to the values you've specified.

Hello Roy_MacLachlan

Thank you for your quick response!

As suggested by you we have tried the steps below,
1. Open MSIX file in Edit MSIX packaging Tool
2. Select "Open file" under Manifest section--> FIle opened in notepad.txt
3. Updated the MinVersion="10.0.18363.1556" Saved the notepad and closed
4 Again click the "Open file" option and observed that MinVersion still pointing to MinVersion="10.0.19025.0" old value.

That means settings are not getting updated with the "Open file" option. Please find the attached screenshot for more details.



Unable to attach the screenshot. Let me know if you needs any logs from my machine,

Hi @shreedhar_ghare,

 

While editing the Windows App using the MSIX Packaging Tool, can you please review the Services report section, and confirm if there are any Services included in your package. (See the following image for reference)

 

Roy_MacLachlan_1-1622833986528.png


Please follow the instructions found in the Microsoft Docs | MSIX Packaging Tool Logs Article to retrieve the MSIX Packaging Tool logs. You can share these as a Private message to myself, or as an attachment to this post.

 

Thank you,

Roy

Hello @Roy_MacLachlan,

Yes, the application Adobe AcrobatReaderDC 21.001.20155 has Adobe ARM service (AdobeARMservice).
Is this service creating an issue?
The provided link is not opening at my end getting the error "about:blank#blocked"
I will try to get logs and share them with you.

Thank you,
Shreedhar Ghare
##############Log file ############################
[6/4/2021 7:51:40 PM] [Info] Microsoft (R) MsixPackagingTool Tool
[6/4/2021 7:51:40 PM] [Info] Copyright (C) 2020 Microsoft. All rights reserved.
[6/4/2021 7:51:40 PM] [Info] ************************************************************
[6/4/2021 7:51:40 PM] [Info] MSIX Packaging Tool Launch
[6/4/2021 7:51:40 PM] [Info] ************************************************************
[6/4/2021 7:51:40 PM] [Info] Log file is located under: %UserProfile%\AppData\Local\Packages\Microsoft.MsixPackagingTool_8wekyb3d8bbwe\LocalState\DiagOutputDir\Logs_22\Log.txt
[6/4/2021 7:51:40 PM] [Info] Tool Version: 1.2021.422.0
[6/4/2021 7:51:40 PM] [Info] Feedback logs are located under: %UserProfile%\AppData\Local\Packages\Microsoft.MsixPackagingTool_8wekyb3d8bbwe\LocalState\DiagOutputDir\FeedbackLogs\Logs_22
[6/4/2021 7:51:40 PM] [Debug] Attempting to read settings file: %UserProfile%\AppData\Local\Packages\Microsoft.MsixPackagingTool_8wekyb3d8bbwe\LocalState\settings.xml
[6/4/2021 7:51:40 PM] [Debug] Updating the settings file from version 1.2021.422.0 to a newer version.
[6/4/2021 7:51:40 PM] [Debug] Enabling Telemetry
[6/4/2021 7:51:40 PM] [Debug] Tool install location: C:\Program Files\WindowsApps\Microsoft.MsixPackagingTool_1.2021.422.0_x64__8wekyb3d8bbwe
[6/4/2021 7:51:40 PM] [Debug] Launching directly into Package editor with package %UserProfile%\Desktop\AdobeAcrobatReaderDC21.001.20155_1.0.0.0_x64__8h66172c634n0.msix
[6/4/2021 7:51:40 PM] [Debug] ************************************************************
[6/4/2021 7:51:40 PM] [Debug] OpenPackageScreen Workflow
[6/4/2021 7:51:40 PM] [Debug] ************************************************************
[6/4/2021 7:51:40 PM] [Debug] ************************************************************
[6/4/2021 7:51:40 PM] [Debug] PackageEditor
[6/4/2021 7:51:40 PM] [Debug] ************************************************************
[6/4/2021 7:51:40 PM] [Debug] Attempting to open the msix package.
[6/4/2021 7:51:40 PM] [Debug] Editing package:
[6/4/2021 7:51:40 PM] [Debug] packagePath: %UserProfile%\Desktop\AdobeAcrobatReaderDC21.001.20155_1.0.0.0_x64__8h66172c634n0.msix
[6/4/2021 7:51:40 PM] [Debug] manifestFile: ttvhjrsu.li3.Manifest
[6/4/2021 7:51:40 PM] [Debug] registryHiveFile: remlxson.tda.RegistryHive
[6/4/2021 7:51:41 PM] [Debug] IgnorableNamespaces attribute value is : uap uap2 uap3 uap10 desktop6 rescap com
[6/4/2021 7:51:41 PM] [Debug] Reading services under application element
[6/4/2021 7:51:41 PM] [Debug] AppID = ADOBEARMSERVICE
[6/4/2021 7:51:41 PM] [Debug] Executable = VFS\ProgramFilesCommonX86\Adobe\ARM\1.0\armsvc.exe
[6/4/2021 7:51:41 PM] [Debug] DisplayName = Adobe Acrobat Update Service
[6/4/2021 7:51:41 PM] [Debug] Description = Adobe Acrobat Updater keeps your Adobe software up to date.
[6/4/2021 7:51:41 PM] [Debug] Service name: AdobeARMservice
[6/4/2021 7:51:41 PM] [Debug] StartAccount = LocalSystem
[6/4/2021 7:51:41 PM] [Debug] StartType = Auto
[6/4/2021 7:51:41 PM] [Debug] ImagePath = VFS\ProgramFilesCommonX86\Adobe\ARM\1.0\armsvc.exe
[6/4/2021 7:51:41 PM] [Debug] Arguments =
[6/4/2021 7:51:41 PM] [Debug] Opened msix package successfully.
[6/4/2021 7:51:41 PM] [Debug] Populating the default signing information from settings
[6/4/2021 7:51:41 PM] [Debug] No accounts to sign out from.
[6/4/2021 7:51:41 PM] [Debug] No access token file exists.
[6/4/2021 7:51:47 PM] [Debug] Spawning background worker thread.
[6/4/2021 7:51:47 PM] [Debug] IgnorableNamespaces attribute value is : uap uap2 uap3 uap10 desktop6 rescap com
[6/4/2021 7:51:47 PM] [Debug] Adding Capability: localSystemServices
[6/4/2021 7:51:47 PM] [Debug] Adding Capability: packagedServices
[6/4/2021 7:51:47 PM] [Debug] Adding Capability: runFullTrust
[6/4/2021 7:51:47 PM] [Debug] Translating Packaged Services to Manifest
[6/4/2021 7:51:47 PM] [Debug] Adding new service application entry Adobe Acrobat Update Service to manifest
[6/4/2021 7:51:47 PM] [Debug] Mandatory Service Parameters:
ServiceName: AdobeARMservice
Executable: VFS\ProgramFilesCommonX86\Adobe\ARM\1.0\armsvc.exe
StartupType: auto
StartAccount: localSystem
[6/4/2021 7:51:47 PM] [Debug] IgnorableNamespaces attribute value is : uap uap2 uap3 uap10 desktop6 rescap com
[6/4/2021 7:51:47 PM] [Debug] File type associated with Manifest: C:\Windows\system32\NOTEPAD.EXE
[6/4/2021 7:52:27 PM] [Debug] Manifest Process Exited.
[6/4/2021 7:52:27 PM] [Debug] Attempting to read and validate the saved manifest file: %UserProfile%\AppData\Local\Packages\Microsoft.MsixPackagingTool_8wekyb3d8bbwe\LocalState\DiagOutputDir\Logs_22\rhjoxkx2.l4y.Manifest
[6/4/2021 7:52:27 PM] [Debug] IgnorableNamespaces attribute value is : uap uap2 uap3 uap10 desktop6 rescap com
[6/4/2021 7:52:27 PM] [Debug] Reading services under application element
[6/4/2021 7:52:27 PM] [Debug] AppID = ADOBEARMSERVICE
[6/4/2021 7:52:27 PM] [Debug] Executable = VFS\ProgramFilesCommonX86\Adobe\ARM\1.0\armsvc.exe
[6/4/2021 7:52:27 PM] [Debug] DisplayName = Adobe Acrobat Update Service
[6/4/2021 7:52:27 PM] [Debug] Description = Adobe Acrobat Updater keeps your Adobe software up to date.
[6/4/2021 7:52:27 PM] [Debug] Service name: AdobeARMservice
[6/4/2021 7:52:27 PM] [Debug] StartAccount = LocalSystem
[6/4/2021 7:52:27 PM] [Debug] StartType = Auto
[6/4/2021 7:52:27 PM] [Debug] ImagePath = VFS\ProgramFilesCommonX86\Adobe\ARM\1.0\armsvc.exe
[6/4/2021 7:52:27 PM] [Debug] Arguments =
[6/4/2021 7:52:27 PM] [Debug] Opened and validated manifest successfully.
[6/4/2021 7:52:27 PM] [Debug] Manifest parsing succeeded.
[6/4/2021 7:52:27 PM] [Debug] Updating view models with the input from manifest.
[6/4/2021 7:52:27 PM] [Debug] Returning back to Package Editor view.
[6/4/2021 7:52:30 PM] [Debug] Spawning background worker thread.
[6/4/2021 7:52:30 PM] [Debug] IgnorableNamespaces attribute value is : uap uap2 uap3 uap10 desktop6 rescap com
[6/4/2021 7:52:30 PM] [Debug] Adding Capability: localSystemServices
[6/4/2021 7:52:30 PM] [Debug] Adding Capability: packagedServices
[6/4/2021 7:52:30 PM] [Debug] Adding Capability: runFullTrust
[6/4/2021 7:52:30 PM] [Debug] Translating Packaged Services to Manifest
[6/4/2021 7:52:30 PM] [Debug] Adding new service application entry Adobe Acrobat Update Service to manifest
[6/4/2021 7:52:30 PM] [Debug] Mandatory Service Parameters:
ServiceName: AdobeARMservice
Executable: VFS\ProgramFilesCommonX86\Adobe\ARM\1.0\armsvc.exe
StartupType: auto
StartAccount: localSystem
[6/4/2021 7:52:30 PM] [Debug] TargetDevice Minimum Version updated to 10.0.19025.0 due to including a service.
[6/4/2021 7:52:30 PM] [Debug] IgnorableNamespaces attribute value is : uap uap2 uap3 uap10 desktop6 rescap com
[6/4/2021 7:52:30 PM] [Debug] File type associated with Manifest: C:\Windows\system32\NOTEPAD.EXE
[6/4/2021 7:52:33 PM] [Debug] Manifest Process Exited.
[6/4/2021 7:52:33 PM] [Debug] Attempting to read and validate the saved manifest file: %UserProfile%\AppData\Local\Packages\Microsoft.MsixPackagingTool_8wekyb3d8bbwe\LocalState\DiagOutputDir\Logs_22\rhjoxkx2.l4y.Manifest
[6/4/2021 7:52:33 PM] [Debug] IgnorableNamespaces attribute value is : uap uap2 uap3 uap10 desktop6 rescap com
[6/4/2021 7:52:33 PM] [Debug] Reading services under application element
[6/4/2021 7:52:33 PM] [Debug] AppID = ADOBEARMSERVICE
[6/4/2021 7:52:33 PM] [Debug] Executable = VFS\ProgramFilesCommonX86\Adobe\ARM\1.0\armsvc.exe
[6/4/2021 7:52:33 PM] [Debug] DisplayName = Adobe Acrobat Update Service
[6/4/2021 7:52:33 PM] [Debug] Description = Adobe Acrobat Updater keeps your Adobe software up to date.
[6/4/2021 7:52:33 PM] [Debug] Service name: AdobeARMservice
[6/4/2021 7:52:33 PM] [Debug] StartAccount = LocalSystem
[6/4/2021 7:52:33 PM] [Debug] StartType = Auto
[6/4/2021 7:52:33 PM] [Debug] ImagePath = VFS\ProgramFilesCommonX86\Adobe\ARM\1.0\armsvc.exe
[6/4/2021 7:52:33 PM] [Debug] Arguments =
[6/4/2021 7:52:33 PM] [Debug] Opened and validated manifest successfully.
[6/4/2021 7:52:33 PM] [Debug] Manifest parsing succeeded.
[6/4/2021 7:52:33 PM] [Debug] Updating view models with the input from manifest.
[6/4/2021 7:52:33 PM] [Debug] Returning back to Package Editor view.
[6/4/2021 7:52:56 PM] [Debug] Spawning background worker thread.
[6/4/2021 7:52:56 PM] [Debug] IgnorableNamespaces attribute value is : uap uap2 uap3 uap10 desktop6 rescap com
[6/4/2021 7:52:56 PM] [Debug] Adding Capability: localSystemServices
[6/4/2021 7:52:56 PM] [Debug] Adding Capability: packagedServices
[6/4/2021 7:52:56 PM] [Debug] Adding Capability: runFullTrust
[6/4/2021 7:52:56 PM] [Debug] Translating Packaged Services to Manifest
[6/4/2021 7:52:56 PM] [Debug] Adding new service application entry Adobe Acrobat Update Service to manifest
[6/4/2021 7:52:56 PM] [Debug] Mandatory Service Parameters:
ServiceName: AdobeARMservice
Executable: VFS\ProgramFilesCommonX86\Adobe\ARM\1.0\armsvc.exe
StartupType: auto
StartAccount: localSystem
[6/4/2021 7:52:56 PM] [Debug] TargetDevice Minimum Version updated to 10.0.19025.0 due to including a service.
[6/4/2021 7:52:56 PM] [Debug] IgnorableNamespaces attribute value is : uap uap2 uap3 uap10 desktop6 rescap com
[6/4/2021 7:52:56 PM] [Debug] File type associated with Manifest: C:\Windows\system32\NOTEPAD.EXE
[6/4/2021 7:52:59 PM] [Debug] Manifest Process Exited.
[6/4/2021 7:52:59 PM] [Debug] Attempting to read and validate the saved manifest file: %UserProfile%\AppData\Local\Packages\Microsoft.MsixPackagingTool_8wekyb3d8bbwe\LocalState\DiagOutputDir\Logs_22\rhjoxkx2.l4y.Manifest
[6/4/2021 7:52:59 PM] [Debug] IgnorableNamespaces attribute value is : uap uap2 uap3 uap10 desktop6 rescap com
[6/4/2021 7:52:59 PM] [Debug] Reading services under application element
[6/4/2021 7:52:59 PM] [Debug] AppID = ADOBEARMSERVICE
[6/4/2021 7:52:59 PM] [Debug] Executable = VFS\ProgramFilesCommonX86\Adobe\ARM\1.0\armsvc.exe
[6/4/2021 7:52:59 PM] [Debug] DisplayName = Adobe Acrobat Update Service
[6/4/2021 7:52:59 PM] [Debug] Description = Adobe Acrobat Updater keeps your Adobe software up to date.
[6/4/2021 7:52:59 PM] [Debug] Service name: AdobeARMservice
[6/4/2021 7:52:59 PM] [Debug] StartAccount = LocalSystem
[6/4/2021 7:52:59 PM] [Debug] StartType = Auto
[6/4/2021 7:52:59 PM] [Debug] ImagePath = VFS\ProgramFilesCommonX86\Adobe\ARM\1.0\armsvc.exe
[6/4/2021 7:52:59 PM] [Debug] Arguments =
[6/4/2021 7:52:59 PM] [Debug] Opened and validated manifest successfully.
[6/4/2021 7:52:59 PM] [Debug] Manifest parsing succeeded.
[6/4/2021 7:52:59 PM] [Debug] Updating view models with the input from manifest.
[6/4/2021 7:52:59 PM] [Debug] Returning back to Package Editor view.
best response confirmed by shreedhar_ghare (Occasional Contributor)
Solution

Hi @shreedhar_ghare,

 

According to the Supported platforms - MSIX | Microsoft Docs article, the Windows Apps with Services is unsupported on your targeted client devices. As this functionality is only supported on Windows 10 2004 (and newer).

 

The MSIX Packaging Tool will automatically override the version settings to Windows 10 Insider Build (November 2019) version: 10.0.19025.0 if an App service is detected. Which explains why when you set your version to below this value, the tool will override it.

 

Apologies, I must have copied the link incorrectly. Thank you for sharing the log information in this post.

 

[Note]

If this comment has answered your question, please mark it as Best Answer and close out the post. If you have any other questions please feel free to reach out to us by creating a new post in our Tech Community :-).

 

Thanks,

Roy

Hello Roy_MacLachlan,
Thank you for helping me in resolving this issue. We excluded the services and the application started working as expected!!!
Thank you very much once again for your help and support
It was no problem at all. I'm happy that we were able to resolve the challenges you were experiencing.