MSIX not visible in Apps & Features ?

%3CLINGO-SUB%20id%3D%22lingo-sub-1728714%22%20slang%3D%22en-US%22%3EMSIX%20not%20visible%20in%20Apps%20%26amp%3B%20Features%20%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1728714%22%20slang%3D%22en-US%22%3E%3CP%3EHi%3C%2FP%3E%3CP%3EI'm%20a%20beginner%20in%20MSIX%20(but%20enough%20skilled%20in%20MSI%20design)%3C%2FP%3E%3CP%3ESo%20I%20started%20to%20create%20a%20very%20simple%20MSI%20just%20installing%20one%20EULA%20file%20under%20its%20%5BINSTALLDIR%5D%3C%2FP%3E%3CP%3EThe%20I%20used%20MSIX%20packaging%20tool%20(provided%20by%20Microsoft%20version%20%3CSTRONG%3E1.2020.709.0)%3C%2FSTRONG%3E%20and%20translated%20the%20%22simple%22%20MSI%20into%20MSIX%20package%2C%20and%20signed%20also%20with%20my%20own%20Enterprise%20certificate%20(the%20same%20I'm%20using%20for%20signing%20my%20MSIs).%20No%20problem%20at%20this%20stage.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EInstallation%20of%20such%20MSIX%20is%20going%20well%20apparently%20but%20NO%20entry%20is%20visible%20under%20%22Apps%20%26amp%3B%20Features%22...%3C%2FP%3E%3CP%3EI%20can%20just%20see%20it%20with%20Get-AppxPackage%20cmd%20thru%20a%20Powser%20Shell%20with%20Admin%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20guess%20it%20is%20a%20problem%20from%20MSIX%20packaging%20tool%20usage%20as%20installing%20the%20%22normal%22%20MSI%20is%20OK.%3C%2FP%3E%3CP%3EWhere%20am%20I%20wrong%20please%20%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERgds%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1733474%22%20slang%3D%22en-US%22%3ERe%3A%20MSIX%20not%20visible%20in%20Apps%20%26amp%3B%20Features%20%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1733474%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F814739%22%20target%3D%22_blank%22%3E%40JF_BAUDE%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20never%20had%20this%20problem%20before%2C%20but%20if%20I%20were%20to%20guess%20I%20would%20suspect%20that%20having%20a%20simple%20EULA%20file%20as%20target%20instead%20of%20an%20actual%20executable%20might%20confuse%20the%20OS.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECan%20you%20try%20placing%20a%20dummy%20EXE%20in%20the%20package%20instead%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20EULA%20might%20trick%20the%20MSIX%20Packaging%20Tool%20to%20not%20detect%20correctly%20an%20entry%20point%20for%20your%20package%20and%20this%20might%20(I%20am%20just%20guessing%20here)%20not%20be%20supported%20correctly%20by%20the%20OS%20when%20you%20install%20the%20package.%3CBR%20%2F%3E%3CBR%20%2F%3EBogdan%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1733597%22%20slang%3D%22en-US%22%3ERe%3A%20MSIX%20not%20visible%20in%20Apps%20%26amp%3B%20Features%20%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1733597%22%20slang%3D%22en-US%22%3E%3CP%3EHi%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F147865%22%20target%3D%22_blank%22%3E%40Bogdan%20Mitrache%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20for%20your%20reply.%3C%2FP%3E%3CP%3EI'll%20do%20as%20you%20are%20suggesting%20below.%3C%2FP%3E%3CP%3ENotice%20nevetheless%20that%20I%20used%20this%20morning%20(I'm%20located%20in%20France)%20AdvancedInstaller%20free%20tool%2C%20instead%20of%20MSIX%20Packaging%20tool%20from%20Microsoft%2C%20and%20it%20worked%20properly%20meaning%20I%20could%20see%20the%20new%20entry%20under%20%22Apps%20%26amp%3B%20Feature%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERgds%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1734128%22%20slang%3D%22en-US%22%3ERe%3A%20MSIX%20not%20visible%20in%20Apps%20%26amp%3B%20Features%20%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1734128%22%20slang%3D%22en-US%22%3EHi%20Bogdan%3CBR%20%2F%3E%3CBR%20%2F%3EI%20redo%20with%20my%20%22simple%22%20MSI%20with%20one%20EULA%20%2B%20added%20EXE%20file%20to%20be%20installed%20under%20%5BINSTALLDIR%5D%20but%20still%20the%20same%20visibility%20issue%20under%20%22Apps%20%26amp%3B%20Features%22%3CBR%20%2F%3E%3CBR%20%2F%3EI%20still%20suspect%20that%20I'm%20wrong%20using%20MSIX%20Package%20tool%20but%20at%20which%20step%20%3F%3CBR%20%2F%3E%3CBR%20%2F%3ERgds%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1734502%22%20slang%3D%22en-US%22%3ERe%3A%20MSIX%20not%20visible%20in%20Apps%20%26amp%3B%20Features%20%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1734502%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%2F814739%22%20target%3D%22_blank%22%3E%40JF_BAUDE%3C%2FA%3E%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20glad%20to%20hear%20you%20got%20it%20working%20with%20Advanced%20Installer.%20Our%20team%20is%20doing%20some%20automatic%20fixes%20for%20certain%20packages%20(at%20conversion%20time)%20but%20I%20couldn't%20find%20anything%20documented%20that%20might%20be%20related%20to%20your%20package.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECan%20you%20share%20download%20links%20for%20both%20the%20package%20build%20with%20Advanced%20Installer%20and%20the%20one%20built%20with%20the%20MPT%3F%20Maybe%20we%20can%20notice%20what%20the%20MPT%20is%20doing%20wrong.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1735201%22%20slang%3D%22en-US%22%3ERe%3A%20MSIX%20not%20visible%20in%20Apps%20%26amp%3B%20Features%20%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1735201%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Bogdan%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAs%20requested%2C%20please%20find%20attached%20ZIPs%2C%20one%20containing%20the%20MSIX%20not%20visible%20under%20Apps%20%26amp%3B%20Features%20after%20its%20installation%2C%20done%20thru%20MPT%2C%20and%20the%20other%20MSIX%2C%20which%20is%20visible%2C%20done%20thru%20AdvancedInstaller%20tool%20v.17.5%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERgds%3C%2FP%3E%3CP%3EJF%20BAUDE%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1738296%22%20slang%3D%22en-US%22%3ERe%3A%20MSIX%20not%20visible%20in%20Apps%20%26amp%3B%20Features%20%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1738296%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%2F814739%22%20target%3D%22_blank%22%3E%40JF_BAUDE%3C%2FA%3E%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%2C%20after%20using%20the%20%3CSTRONG%3EMSIX%20Diff%3C%2FSTRONG%3E%20support%20from%20Advanced%20Installer%2C%20as%20you%20can%20see%20in%20the%20image%20below%2C%20it%20seems%20the%20package%20you%20built%20with%20the%20MSIX%20Packaging%20Tool%20does%20not%20detect%20an%20entry%20point%20for%20your%20application.%20(This%20is%20missing%20from%20the%20AppxManifest).%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%20image-alt%3D%22msixDiff.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F223642i1B00675A39C93554%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%22msixDiff.png%22%20alt%3D%22msixDiff.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20entry%20point%20is%20usually%20detected%20in%20this%20page%20from%20the%20MPT%3A%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%20image-alt%3D%22PN01-16-Run-the-application.png%22%20style%3D%22width%3A%20786px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F223641i1C289DD1F6523A1D%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%22PN01-16-Run-the-application.png%22%20alt%3D%22PN01-16-Run-the-application.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESince%20the%20package%20generated%20by%20MPT%20has%20no%20entry%20point%20I%20suspect%20the%20OS%20hides%20it%20from%20the%20list%20of%20applications%2C%20but%20I%20don't%20have%20any%20official%20docs%20from%20MS%20to%20support%20my%20supposition.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMay%20I%20ask%2C%20since%20you%20got%20the%20package%20working%20with%20Advanced%20Installer%20Express%2C%20why%20do%20you%20insist%20on%20rebuilding%20it%20with%20the%20MPT%3F%20Is%20there%20some%20restriction%20that%20prevents%20you%20from%20using%20the%20free%20Express%20edition%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegards%2C%3C%2FP%3E%3CP%3EBogdan%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1738332%22%20slang%3D%22en-US%22%3ERe%3A%20MSIX%20not%20visible%20in%20Apps%20%26amp%3B%20Features%20%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1738332%22%20slang%3D%22en-US%22%3E%3CP%3EHi%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F147865%22%20target%3D%22_blank%22%3E%40Bogdan%20Mitrache%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhy%20not%20using%20your%20%3CSTRONG%3EExpress%3C%2FSTRONG%3E%20edition%20if%20it%20is%20free%20of%20charge.%20Is%20it%20the%20case%20%3F%3C%2FP%3E%3CP%3ENo%20limitation%20for%20translating%20any%20MSI%20to%20MSIX%20%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERgds%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1738439%22%20slang%3D%22en-US%22%3ERe%3A%20MSIX%20not%20visible%20in%20Apps%20%26amp%3B%20Features%20%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1738439%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%2F814739%22%20target%3D%22_blank%22%3E%40JF_BAUDE%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20package%20that%20you%20create%20with%20the%20free%20Express%20edition%2C%20downloaded%20from%20the%20MS%20Store%20can%20be%20deployed%20in%20your%20enterprise%20without%20any%20limitations.%20Is%20there%20any%20text%20on%20our%20website%20or%20store%20page%20that%20made%20you%20believe%20these%20packages%20cannot%20be%20used%20in%20production%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOnly%20if%20you%20create%20a%20package%20using%20one%20of%20our%20paid%20editions%20(Professional%2C%20Enterprise%20or%20Architect)%20you%20need%20to%20purchase%20a%20license.%20Currently%2C%20most%20of%20the%20MSIX%20features%20include%20din%20the%20Architect%20edition%20are%20also%20available%20in%20the%20Express%20edition.%20What%20the%20Architect%20edition%20brings%20additionally%20is%20extended%20support%20for%20repackaging%26nbsp%3B%20EXE%20to%20MSIs%2C%20editing%20MSIs%2C%20virtual%20machines%20management%20(AI%20can%20connect%20to%20a%20machine%20and%20execute%20automated%20repackaging%20operations%2C%20restore%20de%20VM%2C%20etc...)%20and%20automation%20features.%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CP%3ERegards%2C%3C%2FP%3E%3CP%3EBogdan%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1738878%22%20slang%3D%22en-US%22%3ERe%3A%20MSIX%20not%20visible%20in%20Apps%20%26amp%3B%20Features%20%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1738878%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20again%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESorry%20but%20I%20got%20an%20issue%20when%20trying%20to%20install%20'Express%20edition'%20from%20uSoft%20Store%2C%20as%20you%20suggested%20in%20previous%20mail.%3C%2FP%3E%3CP%3ESee%20attached%20PNG%20for%20the%20details%20(sorry%20it%20is%20in%20french...)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFYI%2C%20I%20un-installed%20before%20Advanced%20Installer%20v17.5%20(30%20days%20evaluation)%20from%20my%20laptop%20Windows%2010%20Enterprise%20v.%201809%3C%2FP%3E%3CP%3EAny%20idea%20%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERgds%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1739054%22%20slang%3D%22en-US%22%3ERe%3A%20MSIX%20not%20visible%20in%20Apps%20%26amp%3B%20Features%20%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1739054%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%2F814739%22%20target%3D%22_blank%22%3E%40JF_BAUDE%3C%2FA%3E%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20can%20read%20French%2C%20that%20is%20not%20a%20problem.%20However%2C%20the%20error%20message%20is%20a%20generic%20one%2C%20it%20does%20not%20provide%20any%20clues%20for%20further%20investigation.%3CBR%20%2F%3E%3CBR%20%2F%3EIs%20your%20internet%20connection%20good%3F%20Can%20you%20try%20on%20another%20machine%20or%20virtual%20machine%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20assume%20you%20installed%20the%20MPT%20from%20the%20store%20too%2C%20so%20other%20apps%20can%20be%20installed%20from%20the%20store%20on%20that%20machine%2C%20right%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegards%2C%3C%2FP%3E%3CP%3EBogdan%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1739212%22%20slang%3D%22en-US%22%3ERe%3A%20MSIX%20not%20visible%20in%20Apps%20%26amp%3B%20Features%20%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1739212%22%20slang%3D%22en-US%22%3E%3CP%3EIndeed%20I%20installed%20th%20MPT%20tool%20from%20the%20store%20a%20few%20days%20ago%20!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20retried%20with%20my%20VPN%20disconnected%20but%20same%20issue.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20tried%20to%20run%20troubleshooter%20from%20Windows%20Store%20Apps%20but%20no%20success%20either.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERgds%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1740582%22%20slang%3D%22en-US%22%3ERe%3A%20MSIX%20not%20visible%20in%20Apps%20%26amp%3B%20Features%20%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1740582%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F814739%22%20target%3D%22_blank%22%3E%40JF_BAUDE%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAs%20Bogdan%20said%2C%20if%20your%20package%20does%20not%20have%20an%20entry%20point%2C%20it%20will%20not%20show%20up%20in%20the%20Apps%20%26amp%3B%20Features%20page.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFor%20the%20MSIX%20Packaging%20Tool%20to%20create%20an%20entry%20point%20for%20your%20application%2C%20you%20need%20to%20include%20an%20executable%20and%20a%20shortcut%20to%20it%2C%20or%20mark%20the%20installed%20executable%20as%20an%20entry%20point%20from%20the%20%22First%20launch%20tasks%22%20page%20using%20the%20Browse%20button.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ESince%20you%20are%20creating%20the%20MSIs%20yourself%2C%20maybe%20you%20could%20create%20the%20MSIX%20package%20directly%20instead%20of%20creating%20the%20MSI%20and%20then%20converting%20it%20to%20MSIX.%20You%20can%20do%20this%20using%20a%20Windows%20Application%20Packaging%20Project%20in%20Visual%20Studio.%20The%20MSIX%20Packaging%20Tool%20is%20meant%20for%20cases%20when%20you%20do%20not%20have%20access%20to%20the%20source%20of%20the%20application%20and%20thus%20cannot%20build%20the%20package%20directly.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

Hi

I'm a beginner in MSIX (but enough skilled in MSI design)

So I started to create a very simple MSI just installing one EULA file under its [INSTALLDIR]

The I used MSIX packaging tool (provided by Microsoft version 1.2020.709.0) and translated the "simple" MSI into MSIX package, and signed also with my own Enterprise certificate (the same I'm using for signing my MSIs). No problem at this stage.

 

Installation of such MSIX is going well apparently but NO entry is visible under "Apps & Features"...

I can just see it with Get-AppxPackage cmd thru a Powser Shell with Admin

 

I guess it is a problem from MSIX packaging tool usage as installing the "normal" MSI is OK.

Where am I wrong please ?

 

Rgds

 

13 Replies

Hi @JF_BAUDE 

 

I never had this problem before, but if I were to guess I would suspect that having a simple EULA file as target instead of an actual executable might confuse the OS.

 

Can you try placing a dummy EXE in the package instead?

 

The EULA might trick the MSIX Packaging Tool to not detect correctly an entry point for your package and this might (I am just guessing here) not be supported correctly by the OS when you install the package.

Bogdan


Hi@Bogdan Mitrache 

 

Thanks for your reply.

I'll do as you are suggesting below.

Notice nevetheless that I used this morning (I'm located in France) AdvancedInstaller free tool, instead of MSIX Packaging tool from Microsoft, and it worked properly meaning I could see the new entry under "Apps & Feature"

 

Rgds

Hi Bogdan

I redo with my "simple" MSI with one EULA + added EXE file to be installed under [INSTALLDIR] but still the same visibility issue under "Apps & Features"

I still suspect that I'm wrong using MSIX Package tool but at which step ?

Rgds

Hi @JF_BAUDE,

 

I am glad to hear you got it working with Advanced Installer. Our team is doing some automatic fixes for certain packages (at conversion time) but I couldn't find anything documented that might be related to your package.

 

Can you share download links for both the package build with Advanced Installer and the one built with the MPT? Maybe we can notice what the MPT is doing wrong.

Hi Bogdan

 

As requested, please find attached ZIPs, one containing the MSIX not visible under Apps & Features after its installation, done thru MPT, and the other MSIX, which is visible, done thru AdvancedInstaller tool v.17.5

 

Rgds

JF BAUDE

Hi @JF_BAUDE,

 

So, after using the MSIX Diff support from Advanced Installer, as you can see in the image below, it seems the package you built with the MSIX Packaging Tool does not detect an entry point for your application. (The "Application" node is missing entirely from the AppxManifest.xml found in the package built with MPT).

 

msixDiff.png

 

This entry point is usually detected in this page from the MPT:

 

PN01-16-Run-the-application.png

 

Since the package generated by MPT has no entry point I suspect the OS hides it from the list of applications, but I don't have any official docs from MS to support my supposition.

 

May I ask, since you got the package working with Advanced Installer Express, why do you insist on rebuilding it with the MPT? Is there some restriction that prevents you from using the free Express edition?

 

Regards,

Bogdan

Hi@Bogdan Mitrache 

 

Why not using your Express edition if it is free of charge. Is it the case ?

No limitation for translating any MSI to MSIX ?

 

Rgds

Hi @JF_BAUDE 

 

Any package that you create with the free Express edition, downloaded from the MS Store can be deployed in your enterprise without any limitations. Is there any text on our website or store page that made you believe these packages cannot be used in production?

 

Only if you create a package using one of our paid editions (Professional, Enterprise or Architect) you need to purchase a license. Currently, most of the MSIX features include din the Architect edition are also available in the Express edition. What the Architect edition brings additionally is extended support for repackaging  EXE to MSIs, editing MSIs, virtual machines management (AI can connect to a machine and execute automated repackaging operations, restore de VM, etc...) and automation features.

Regards,

Bogdan

Hi again

 

Sorry but I got an issue when trying to install 'Express edition' from uSoft Store, as you suggested in previous mail.

See attached PNG for the details (sorry it is in french...)

 

FYI, I un-installed before Advanced Installer v17.5 (30 days evaluation) from my laptop Windows 10 Enterprise v. 1809

Any idea ?

 

Rgds

Hi @JF_BAUDE,

 

I can read French, that is not a problem. However, the error message is a generic one, it does not provide any clues for further investigation.

Is your internet connection good? Can you try on another machine or virtual machine?

 

I assume you installed the MPT from the store too, so other apps can be installed from the store on that machine, right?

 

Regards,

Bogdan

Indeed I installed th MPT tool from the store a few days ago !

 

I retried with my VPN disconnected but same issue.

 

I tried to run troubleshooter from Windows Store Apps but no success either.

 

Rgds

@JF_BAUDE 

Hi Bogdan

 

After so many trials the following process worked for me (and according to post https://answers.microsoft.com/en-us/windows/forum/all/pur-inventoryneveraugmented/c9661417-b144-4fd0... )

- Reset the Microsoft store
Go to Settings > Apps > Apps & Features > select Microsoft Store > Advance options > Reset

- Sign in to Microsoft Store, but first go through your own LDAP credentials. Really strange... (I'm not sure to redo it properly)

- Then downloading the package from uSoft store was good at last !

 

Notice I didn't use any VPN

Hi @JF_BAUDE 

 

As Bogdan said, if your package does not have an entry point, it will not show up in the Apps & Features page.

 

For the MSIX Packaging Tool to create an entry point for your application, you need to include an executable and a shortcut to it, or mark the installed executable as an entry point from the "First launch tasks" page using the Browse button.

 

Since you are creating the MSIs yourself, maybe you could create the MSIX package directly instead of creating the MSI and then converting it to MSIX. You can do this using a Windows Application Packaging Project in Visual Studio. The MSIX Packaging Tool is meant for cases when you do not have access to the source of the application and thus cannot build the package directly.