Get the Application User Model ID (AUMID)
Windows

Get the Application User Model ID (AUMID)

jannikreinhard

The Application User Model ID (AUMID) is the identifier Windows uses to recognise a UWP app — and you’ll need it any time you want to launch one programmatically, pin it to the Start menu via Intune, target it in AppLocker, or surface a toast notification from the right “owner” application. The challenge is that the AUMID is rarely visible in the UI, varies between OEM-installed apps and re-published store apps, and can change after an upgrade. This post documents the three reliable ways I retrieve AUMIDs in production, plus how to use them in Intune assignments.

The AUMID is an ID which is assigned to each application installed on a device. It is used e.g. in the Kiosk multi app mode to select apps. Which possibilities exist to get this AUMID I want to explain you in this blog.

Possibility 1

Press WIN + R to open a Run dialog. Type in the following command and click OK:

shell:Appsfolder

A folder opens in which all applications are located

Get the Application User Model ID (AUMID)

Press F10 and click View -> Choose details

Get the Application User Model ID (AUMID)
  • Select AppUserModelId and click OK
Get the Application User Model ID (AUMID)
  • Change the view to Details
Get the Application User Model ID (AUMID)

Here we are. Here you can see the AUMID

Get the Application User Model ID (AUMID)

Possibility 2

Open a Powershell and enter the following command:

get-StartApps
Get the Application User Model ID (AUMID)

Possibility 3

Open the Registry Editor. Press WIN + R and type in regedit and click OK

Get the Application User Model ID (AUMID)

Navigate to HKEY_CURRENT_USER\Software\Classes\ActivatableClasses\Package

Get the Application User Model ID (AUMID)

Also here we can see all the AUMID.

Where AUMIDs actually matter in production

Knowing how to grab an AUMID is one thing; knowing where it shows up in real Intune work is what makes it worth memorizing.

  • Toast notifications and ownership branding: custom toasts must reference an existing AUMID so Action Center attributes the message correctly.
  • AppLocker and WDAC targeting: packaged-app rules match against the publisher and package family inside the AUMID, not the executable path.
  • Pinned Start menu layouts via Intune: Start layout XML and the JSON pinning policy expect exact AUMIDs; one typo and the tile silently disappears.
  • Per-user install tracking: AUMIDs correlate launches and crash telemetry back to the provisioned user, which matters on Cloud PC and shared devices.
  • Upgrades and recovery: AUMIDs can change after feature updates or store re-provisioning, so always re-export them from a freshly imaged reference device before pushing policy.

Stay healthy, Cheers
Jannik