Skip to content

Dear Internet Explorer user: Your browser is no longer supported

Please switch to a modern browser such as Microsoft Edge, Mozilla Firefox or Google Chrome to view this website's content.

Create a permanent link or shortcut to an application installed via an MSIX

A methodology for creating persistent shortcuts to Windows applications installed via MSIX technology.

To create a reliable, permanent link or shortcut to an application installed via an MSIX package, you cannot use traditional .exe file paths. Because MSIX applications are containerised and updated atomically by Windows, their installation paths (found under C:\ProgramFiles\WindowsApps) include dynamic version numbers and security hashes that change with every update, breaking standard links.

The solution to this is to create a permanent shortcut file using the application’s unique Package Family Name (PFN) and Application ID. These identifiers remain completely static across all software updates.

Step 1: Identify your app’s PFN and Application ID

In PowerShell, enter the following command:

Get-StartApps

This will reveal a list of installed software with application identifiers:

PowerShell in Windows Terminal displaying a list of installed applications and associated IDs

In this example, I am interested in Canva Affinity, which has the code Canva.Affinity_8a0j1tnjnt4a4!Canva.Affinity.

The part before the ! is the Package Family Name (Canva.Affinity_8a0j1tnjnt4a4) and the part after the ! is the Application ID (Canva.Affinity).

Step 2: Create a shortcut link

The format to create a shortcut link is as follows:

explorer.exe shell:AppsFolder\<PackageFamilyName>!<ApplicationID>

So, to make a shortcut for Canva Affinity, the path would be:

explorer.exe shell:AppsFolder\Canva.Affinity_8a0j1tnjnt4a4!Canva.Affinity

If a full path is required, explorer.exe is found at c:\Windows\.

   

Comments

No comments have yet been submitted. Be the first!

Have Your Say

The following HTML is permitted:
<a href="" title=""> <b> <blockquote cite=""> <code> <em> <i> <q cite=""> <strike> <strong>

Comments will be published subject to the Editorial Policy.