Adding MSIX package to Windows Server 2019 - Icon not visible

%3CLINGO-SUB%20id%3D%22lingo-sub-1580429%22%20slang%3D%22en-US%22%3EAdding%20MSIX%20package%20to%20Windows%20Server%202019%20-%20Icon%20not%20visible%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1580429%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20tried%20to%20create%20a%20few%20MSIX%20packages%20as%20test.%20I'm%20using%20a%20Windows%2010%20Enterprise%20x64%20machine%20since%20the%20packaging%20tool%20is%20only%20available%20from%20Windows%20Store%20(And%20Server%202019%20has%20no%20Windows%20Store).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENow%2C%20when%20I%20package%20an%20app%20and%20add%20it%20to%20Server%202019%20using%20Add-AppPackage%2C%20there%20are%20no%20errors%20everything%20seems%20fine%20and%20the%20package%20is%20visible%20in%20the%20WindowsApps%20folder%20however%2C%20the%20application%20icon%20is%20not%20visible%20and%20thus%20the%20application%20cannot%20be%20launched.%20When%20you%20go%20into%20the%20control%20panel%20the%20app%20is%20actually%20visible%20and%20can%20be%20uninstalled.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20aware%20you%20can%20specify%20a%20remote%20machine%20with%20the%20packaging%20tool%2C%20but%20I%20would%20assume%20I%20can%20just%20package%20for%20Windows%2010%20Enterprise%20and%20it%20would%20work%20on%20Server%202019%2C%20and%20I%20don't%20need%20different%20packages%20for%20each%20OS%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1585092%22%20slang%3D%22en-US%22%3ERe%3A%20Adding%20MSIX%20package%20to%20Windows%20Server%202019%20-%20Icon%20not%20visible%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1585092%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F289411%22%20target%3D%22_blank%22%3E%40martijnk79%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EDoes%20the%20application%20icon%20show%20up%20when%20installing%20on%20a%20machine%20with%20Windows%2010%20Enterprise%3F%20If%20it%20does%20not%2C%20then%20the%20problem%20is%20likely%20the%20package%20and%20not%20the%20Windows%20edition%20you%20use.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWhen%20creating%20the%20package%20with%20the%20the%20packaging%20tool%2C%20is%20your%20application%20listed%20in%20the%20First%20launch%20tasks%20page%3F%20The%20applications%20listed%20there%20are%20the%20ones%20that%20will%20be%20used%20as%20entry%20points%20for%20the%20package%2C%20i.e.%20the%20ones%20you%20will%20see%20as%20icons.%20If%20the%20application%20does%20not%20show%20up%20in%20the%20First%20launch%20tasks%20initially%2C%20you%20may%20need%20to%20add%20it%20using%20the%20Browse%20button.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAnother%20way%20to%20verify%20this%20without%20packaging%20your%20application%20again%20is%20to%20check%20the%20package%20manifest.%20The%20application%20icons%20you%20see%20correspond%20to%20%3CAPPLICATION%3E%20elements%20in%20the%20manifest.%20Is%20the%20application%20you%20expect%20listed%20there%3F%20If%20it%20is%2C%20does%20it%20have%20the%20attribute%20AppListEntry%3D%22none%22%20that%20would%20hide%20it%3F%3C%2FAPPLICATION%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1585336%22%20slang%3D%22en-US%22%3ERe%3A%20Adding%20MSIX%20package%20to%20Windows%20Server%202019%20-%20Icon%20not%20visible%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1585336%22%20slang%3D%22en-US%22%3EHi%20Luis%2C%3CBR%20%2F%3E%3CBR%20%2F%3EYes%20I%20forgot%20the%20mention%20it%20does%20show%20up%20on%20Windows%2010%20Enterprise%20and%20works%20just%20fine.%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1589907%22%20slang%3D%22en-US%22%3ERe%3A%20Adding%20MSIX%20package%20to%20Windows%20Server%202019%20-%20Icon%20not%20visible%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1589907%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F289411%22%20target%3D%22_blank%22%3E%40martijnk79%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI'm%20not%20sure%20what%20could%20be%20causing%20the%20problem%20you%20are%20seeing.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EDoes%20your%20server%20have%20Desktop%20Experience%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ECan%20you%20launch%20the%20app%20through%20other%20mechanisms%3F%20For%20example%2C%20can%20you%20launch%20it%20from%20the%20command%20prompt%20if%20you%20add%20an%20%3CA%20href%3D%22https%3A%2F%2Fblogs.windows.com%2Fwindowsdeveloper%2F2017%2F07%2F05%2Fcommand-line-activation-universal-windows-apps%2F%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Eapp%20execution%20alias%3C%2FA%3E%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIs%20there%20any%20other%20details%20you%20could%20share%20about%20your%20app%20for%20us%20to%20investigate%20what%20is%20happening%2C%20either%20here%20or%20through%20Feedback%20Hub%3F%20For%20example%20what%20app%20are%20you%20packaging%2C%20the%20packaging%20tool's%20conversion%20logs%20or%20the%20package%20manifest.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

Hi,

 

I've tried to create a few MSIX packages as test. I'm using a Windows 10 Enterprise x64 machine since the packaging tool is only available from Windows Store (And Server 2019 has no Windows Store).

 

Now, when I package an app and add it to Server 2019 using Add-AppPackage, there are no errors everything seems fine and the package is visible in the WindowsApps folder however, the application icon is not visible and thus the application cannot be launched. When you go into the control panel the app is actually visible and can be uninstalled.

 

I am aware you can specify a remote machine with the packaging tool, but I would assume I can just package for Windows 10 Enterprise and it would work on Server 2019, and I don't need different packages for each OS?

3 Replies
Highlighted

Hi @martijnk79 

 

Does the application icon show up when installing on a machine with Windows 10 Enterprise? If it does not, then the problem is likely the package and not the Windows edition you use.

 

When creating the package with the the packaging tool, is your application listed in the First launch tasks page? The applications listed there are the ones that will be used as entry points for the package, i.e. the ones you will see as icons. If the application does not show up in the First launch tasks initially, you may need to add it using the Browse button.

 

Another way to verify this without packaging your application again is to check the package manifest. The application icons you see correspond to <Application> elements in the manifest. Is the application you expect listed there? If it is, does it have the attribute AppListEntry="none" that would hide it?

Highlighted
Hi Luis,

Yes I forgot the mention it does show up on Windows 10 Enterprise and works just fine.

Highlighted

Hi @martijnk79 

 

I'm not sure what could be causing the problem you are seeing.

 

Does your server have Desktop Experience?

 

Can you launch the app through other mechanisms? For example, can you launch it from the command prompt if you add an app execution alias?

 

Is there any other details you could share about your app for us to investigate what is happening, either here or through Feedback Hub? For example what app are you packaging, the packaging tool's conversion logs or the package manifest.