The problem: not everything speaks AUMID
An AUMID identifies a packaged app, but plenty of tools can only run an executable by name. Kapustein's post also notes that Windows has no convenient built-in way to launch an app by AUMID interactively. Scripts, scheduled tasks, installers and shells expect something they can type or spawn.
The post's answer is the AppExecutionAlias. The post describes it as behaving like a traditional command-line executable, except that launching it activates the packaged application.
Declaring an alias in the manifest
The developer declares the alias in the package's AppxManifest.xml, inside the application's Extensions element. The post's example uses a fictional Contoso point-of-sale package (Contoso.PointOfSale, application ID CardReader, executable PointOfSale.exe):
<uap5:Extension Category="windows.appExecutionAlias">
<uap5:AppExecutionAlias>
<uap5:ExecutionAlias Alias="cardreader.exe" />
</uap5:AppExecutionAlias>
</uap5:Extension>
Windows creates the alias for a user when the package is registered for that user. Running it activates the app the same way AUMID activation does, and arguments are forwarded:
cardreader.exe --merchant Contoso --device USB0
Some version and format notes:
- The
uap5schema is supported from Windows 10 version 1709 onward, according to a third-party how-to that summarizes Microsoft's documentation (rottenwifi.com). That includes Windows 11. - Microsoft Learn says an app can specify only a single execution alias per application in the package.
- The alias name must end in
.exe. This comes from the research brief's reading of Learn's documentation, which I couldn't re-check in this session. - If the package declares no alias, none exists. Per the post, AUMID activation is then the only route.
Where the alias lives, and why it shows 0 bytes
The post says the alias appears in the user's profile, for example C:\Users\bob\AppData\Local\Microsoft\WindowsApps\cardreader.exe. That folder is on the user's PATH, so the alias works interactively and programmatically.
If you list the folder, the .exe files show a size of zero bytes. This is normal. The post says they are special file system entries that the activation stack uses to find the real executable. The binary isn't copied out of the package, so its integrity protection stays intact.
Microsoft's Sysinternals Suite documentation backs this up with a real MSIX package. It describes app execution aliases as a special type of reparse point managed by Windows, stored under %LOCALAPPDATA%\Microsoft\WindowsApps. It also says they are deleted when the package is uninstalled. The post says the same: Windows removes the alias when the package is deregistered for the user. A script that expects a command to exist after the app is removed will break.
Duplicate aliases: the post and the docs disagree
Many packages can declare the same alias name. The post's example is several graphics apps all declaring paint.exe. Only one entry can sit in the user's alias directory.
Here the sources conflict:
- Inside MSIX post: MSIX deployment applies a "First Writer Wins" rule when registering a package for a user. The alias is written only if no alias of that name already exists.
- Microsoft Learn (desktop packaging extensions page): If multiple apps register for the same alias, the system will invoke the last one that was registered, so choose a unique alias.
- Older community notes: A 2018 Windows Community Standup write-up by developer Michal Zikmund says the rule is the first registered app wins, and users can switch aliases on and off in Settings. That matches the post, not the Learn page.
The sources may describe different schemas, scenarios or eras. The available evidence doesn't say which. Don't build deployment logic on either ordering rule. Choose distinctive alias names if you are the developer. If you are the admin, verify which app actually answers a given name on your machines.
What users can control
The post describes a Settings page at Apps > Advanced app settings > App execution aliases. It lists the aliases across packages registered for the user and shows which are enabled. When several apps define the same alias, the user chooses which one is active. The post compares this to a default app for a file type: there is one default, or none.
Users can also disable an alias. The post says that if no alias of that name remains enabled, Windows deletes the file system entry. Launching the name then fails as if the package never existed. Microsoft's Learn documentation confirms users can disable an app's alias on this page. The Sysinternals page says you can find it by searching "Manage app execution aliases" in Windows Search or Settings.
The stable path for automation
The user can toggle the plain alias, so a script that depends on it depends on a Settings choice. The post offers a more predictable target. Package registration also creates the alias in a subdirectory named for the package family name. The post says this is unconditional and unaffected by the Settings page. Its example is:
%LOCALAPPDATA%\Microsoft\WindowsApps\Contoso.PointOfSale_eh4htm4n7tdre\cardreader.exe
Sysinternals Suite shows the same per-package pattern in practice. Its aliases sit under %LOCALAPPDATA%\Microsoft\WindowsApps\Microsoft.SysinternalsSuite_8wekyb3d8bbwe. Microsoft notes that browsing this folder lists all the package's aliases.
The "immune to the toggle" claim comes from the Inside MSIX post alone. The Sysinternals page confirms the folder pattern but doesn't state that claim. Treat it as vendor-asserted rather than independently verified. It also doesn't guarantee behavior in every execution context.
AUMID or alias?
| Situation | Better choice |
|---|---|
| Interactive use, scripts, scheduled tasks, installers | Execution alias |
| Package declares no alias | AUMID activation |
| Automation that must not depend on Settings | Package-family-name alias path |
Troubleshooting checklist
- Confirm the package is registered for the current user. Aliases are per user, and uninstalling removes them.
- Open Apps > Advanced app settings > App execution aliases and check that the alias is on for the app you expect.
- Confirm
%LOCALAPPDATA%\Microsoft\WindowsAppsis onPATH. Microsoft's Windows Terminal documentation recommends this check when aliases can't be reached. The same page says to leaveC:\Program Files\WindowsAppsalone. - List the package-family subfolder to see which aliases the package actually registered.
- Switch to the package-family-name path if a Settings toggle or a duplicate name is causing trouble.
- In WSL, remember Microsoft warns that execution aliases don't work in WSL distributions. Spawn through
cmd.exe /cinstead. This is documented for Windows Terminal'swt.exe, but it is a general limitation worth knowing.
Bottom line
Execution aliases are the simplest way to give a packaged app an ordinary command name. Their per-user, user-toggleable nature makes the bare name a poor target for unattended automation. The package-family subfolder path is the more robust option according to Microsoft's own engineer. The conflicting first-registered and last-registered guidance means collisions need testing, not assumptions.
References
- Activation via Command Line Inside MSIX · 2026-11-17T17:00:57+00:00
- Windows Terminal command line arguments | Microsoft Learn learn.microsoft.com
- Notes from Windows Community Standup (February 2018) mzikmund.dev