Open Microsoft Store Apps From Command Prompt

This guide shows you how to launch any Microsoft Store (UWP) app directly from Command Prompt or PowerShell, without clicking through the Start menu. You’ll learn the exact command syntax, how to find the correct app ID, and what to do when an app refuses to open. All steps work on Windows 10 and Windows 11.

What You’ll Need

• A Windows 10 or Windows 11 PC
• Command Prompt or PowerShell (both work the same way)
• The app you want to open must already be installed from the Microsoft Store

Step-by-Step

1. Open Command Prompt – Press Win + R, type cmd, and press Enter. Or search for “Command Prompt” in the Start menu and click it. For PowerShell, search “PowerShell” instead.
2. Find the app’s Package Family Name – This is the unique identifier Windows uses for each Store app. Run this command:
   Get-AppxPackage | Select Name, PackageFamilyName
   This lists every installed Store app with its name and PackageFamilyName. Scroll through the output to find your app (e.g., “Microsoft.WindowsCalculator”). Copy the PackageFamilyName value — it looks like Microsoft.WindowsCalculator_8wekyb3d8bbwe.
3. Get the Application ID – The PackageFamilyName alone isn’t enough; you also need the app’s internal Application ID. Run:
   Get-AppxPackage -Name *appname* | Get-AppxPackageManifest
   Replace *appname* with a partial name, e.g., *Calculator*. Look in the output for a line like <Application Id="App" ...>. The ID is usually “App” for most apps, but some use different values like “Microsoft.MicrosoftEdge” or “AppX…”.
4. Build the launch command – The full command uses this format:
   explorer.exe shell:AppsFolder\PackageFamilyName!ApplicationId
   For example, to open Calculator:
   explorer.exe shell:AppsFolder\Microsoft.WindowsCalculator_8wekyb3d8bbwe!App
5. Run the command – Paste the full command into Command Prompt and press Enter. The app should open immediately. If nothing appears, check the Troubleshooting section below.
6. Create a shortcut (optional) – To avoid typing this every time, create a desktop shortcut: right-click the desktop, choose New > Shortcut, paste the command as the location, and name it. Double-clicking the shortcut opens the app.

Common Mistakes

• Using the wrong slash direction – The command uses a backslash (\) between the PackageFamilyName and the Application ID, not a forward slash. Copy-paste carefully.
• Missing the exclamation mark – The ! between the package name and app ID is required. Without it, Windows won’t recognize the command.
• Typing the PackageFamilyName wrong – It’s case-sensitive and includes a long suffix (like _8wekyb3d8bbwe). Don’t try to type it manually — copy it from the command output.
• Using the app’s display name – “Calculator” won’t work. You must use the internal PackageFamilyName and Application ID.
• Running in the wrong shell – The command starts with explorer.exe. If you omit that and just type shell:AppsFolder\..., it won’t run.

Tips

• Use wildcards to find apps faster – Instead of scrolling the full list, filter: Get-AppxPackage *mail* | Select PackageFamilyName finds anything with “mail” in the name.
• Batch open multiple apps – Put several explorer.exe shell:AppsFolder\... lines in a .bat file to open your daily apps at once.
• Combine with Task Scheduler – You can schedule the command to run at startup, so your favorite Store apps open automatically when you log in.
• Use PowerShell aliases – In PowerShell, gps is short for Get-AppxPackage, saving typing.
• Pin to taskbar via command – While this command opens the app, pinning still requires right-clicking the app in Start and choosing “Pin to taskbar”.

Troubleshooting

Nothing happens when I run the command – First, check that you copied the PackageFamilyName exactly. Re-run the Get-AppxPackage command and compare. If it’s correct, try running the command in PowerShell instead of Command Prompt. Some systems need the shell command to be run with admin rights — right-click Command Prompt and select “Run as administrator”.

Error: “The system cannot find the file specified” – This usually means the PackageFamilyName or Application ID is wrong. Double-check both. For the Application ID, run the manifest command and look for the Id= attribute inside the <Application> tag. It’s often “App” but not always.

The app opens but immediately closes – This is an app-specific issue, not a command problem. Try launching the app normally from Start. If it also crashes there, the app itself is broken — try updating it from the Store or reinstalling it.

Get-AppxPackage returns nothing – If the command outputs nothing, either the app isn’t installed or you’re in a restricted environment (like a locked-down corporate PC). Verify the app appears in Start menu. If it does, try Get-AppxPackage -AllUsers (requires admin).

Command works but only opens a folder window – This happens when the Application ID is wrong. Windows interprets the command as a path and opens Explorer. Re-check the manifest for the correct ID.

App opens but not the right one – If you have multiple versions (e.g., from different accounts), the command may target the wrong one. Use Get-AppxPackage -User <username> to filter by user.

Frequently Asked Questions

Can I open a specific page inside a Store app? – Not with this method. The shell:AppsFolder command only launches the app’s default view. Some apps support URL protocols (like ms-settings:) but that’s separate.

Does this work for all Microsoft Store apps? – Yes, every Store app (UWP and MSIX) has a PackageFamilyName and Application ID, so this method works universally. It also works for some pre-installed apps like Settings and Photos.

Why use this instead of just clicking the app? – It’s useful for scripting, automation, creating custom shortcuts, or when the Start menu is broken. You can also use it in batch files to launch multiple apps with one command.

Is there a shorter command? – You can create a PowerShell function or a batch file to reduce typing. For example, save a .bat file with the full command and just double-click it each time.

Can I use this to open apps as administrator? – No, this method doesn’t elevate privileges. Store apps generally don’t run as admin anyway. If you need admin rights, use a desktop app instead.

What if the app is not installed for my user account? – The command only works for apps installed for the current user. If the app is installed for another user, log in as that user or reinstall the app under your account.

Related

• JRPG Platform Guide: Console, PC, or Handheld
• Least Privilege Access for AI Agents: Setup Guide
• Chrome Send Tab to Self: How to Use It