Home

MSIX Packaging Tool and shortcut icons

%3CLINGO-SUB%20id%3D%22lingo-sub-359418%22%20slang%3D%22en-US%22%3EMSIX%20Packaging%20Tool%20and%20shortcut%20icons%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-359418%22%20slang%3D%22en-US%22%3E%3CP%3EIf%20you%20have%20a%20package%20that%20uses%20the%20PSFLauncher%2C%20you%20want%20to%20create%20a%20shortcut%20to%20the%20Launcher%2C%20but%20have%20that%20shortcut%20use%20an%20icon%20from%20the%20target%20package.%20If%20you%20do%20this%20you%20end%20up%20with%20a%20blank%20icon%20for%20both%20the%20MSIX%20package%20and%20the%20MSIX%20generated%20shortcut.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWhile%20in%20monitoring%2C%20you%20install%20an%20app%20that%20has%20a%20shortcut%20(any%20app).%20You%20then%20copy%20an%20appropriate%20PsfLauncherXX.exe%20file%20to%20the%20installation%20folder%2C%20and%20modify%20the%20properties%20of%20the%20shortcut.%26nbsp%3B%20The%20modification%20would%20change%20the%20target%20to%20the%20PsfLauncher%2C%20and%20you%20make%20sure%20that%20the%20icon%20field%20points%20to%20the%20original%20exe%20and%20not%20PsfLauncher%20(which%20has%20no%20icon%20resources).%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20package%20generated%20has%20AppXManifest%20visual%20assets%20listed%20in%20the%20XML%20that%20is%20not%20in%20the%20package.%26nbsp%3B%20Looking%20at%20the%20log%20file%20it%20seems%20that%20the%20packaging%20tool%20ignores%20the%20shortcut%20icon%20property%20and%20just%20tries%20to%20pull%20an%20icon%20from%20the%20target%20exe.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-360127%22%20slang%3D%22en-US%22%3ERe%3A%20MSIX%20Packaging%20Tool%20and%20shortcut%20icons%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-360127%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20for%20reporting%20this%2C%20Tim!%3C%2FP%3E%0A%3CP%3EI've%20let%20the%20Packaging%20tool%20team%20know%20and%20they%20are%20looking%20into%20it.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Tim Mangan
MVP

If you have a package that uses the PSFLauncher, you want to create a shortcut to the Launcher, but have that shortcut use an icon from the target package. If you do this you end up with a blank icon for both the MSIX package and the MSIX generated shortcut.

 

While in monitoring, you install an app that has a shortcut (any app). You then copy an appropriate PsfLauncherXX.exe file to the installation folder, and modify the properties of the shortcut.  The modification would change the target to the PsfLauncher, and you make sure that the icon field points to the original exe and not PsfLauncher (which has no icon resources).

 

The package generated has AppXManifest visual assets listed in the XML that is not in the package.  Looking at the log file it seems that the packaging tool ignores the shortcut icon property and just tries to pull an icon from the target exe.

1 Reply
Highlighted

Thanks for reporting this, Tim!

I've let the Packaging tool team know and they are looking into it.

Related Conversations
Stable version of Edge insider browser
HotCakeX in Discussions on
35 Replies
flashing a white screen while open new tab
cntvertex in Discussions on
13 Replies
Tabs and Dark Mode
cjc2112 in Discussions on
22 Replies
How to Prevent Teams from Auto-Launch
chenrylee in Microsoft Teams on
28 Replies
description for autoplay blocking in settings page
HotCakeX in Discussions on
8 Replies