How to Manage App Execution Aliases in Windows 11: Complete Guide

Quick answer: To manage app execution aliases in Windows 11, press Windows + I, open Apps, select Advanced app settings, and choose App execution aliases. Turn an alias off when it conflicts with another program or sends a command to the wrong app; leave it on when you want that command to launch the listed app.

App execution aliases are command-line shortcuts registered by packaged Windows apps. They let you type a short command such as wt instead of locating and entering an application’s full path. They are convenient until two programs compete for the same command or a placeholder alias opens the Microsoft Store instead of the program you installed.

This guide explains what the aliases do, how to enable or disable them, how to resolve common Python and Windows Terminal problems, and what to check when a command still is not recognized.

How to Open App Execution Aliases in Windows 11

  1. Open Settings. Press Windows + I.
  2. Select Apps. It appears in the left sidebar.
  3. Choose Advanced app settings.
  4. Select App execution aliases.
  5. Find the app or command you want to manage. Use the switch beside it to turn the alias on or off.

You can also open Start, search for Manage app execution aliases, and select the matching Settings result. That shortcut is often faster when you are troubleshooting a command.

What Is an App Execution Alias?

An app execution alias is a short executable name that a packaged app registers with Windows. When the alias is enabled and you enter that name in Command Prompt, PowerShell, the Run dialog, or another process, Windows can route the request to the associated app.

For example, Windows Terminal uses the wt.exe alias. With the alias enabled and the WindowsApps location available through your PATH, entering wt can launch Terminal without a full file path.

The Settings list is therefore not a list of suspicious hidden programs. It is a control panel for legitimate command names exposed by installed app packages. An alias can appear automatically when Windows or a Microsoft Store app registers it.

When Should You Turn an Alias Off?

Most aliases can remain enabled. Consider disabling one in these situations:

  • A command opens the Microsoft Store even though you installed the program another way.
  • Two installed apps register the same command and Windows launches the wrong one.
  • You want a traditional desktop program earlier in PATH to handle the command.
  • A developer tool’s installer specifically tells you to disable a conflicting Windows alias.
  • You are troubleshooting whether WindowsApps routing is causing a command problem.

Turning an alias off does not normally uninstall the app. It removes that particular command-line route. You can still open the app from Start or another shortcut, and you can return to the same Settings page to enable the alias again.

How to Fix Python Opening the Microsoft Store

Windows includes App Installer aliases named python.exe and python3.exe. They help people who do not have Python find an installation in the Microsoft Store. If you installed Python from another source, one of those shortcuts can sometimes take precedence and open the Store unexpectedly.

  1. Open Settings > Apps > Advanced app settings > App execution aliases.
  2. Find the App Installer entries for python.exe and python3.exe.
  3. Turn both entries Off.
  4. Close every open Command Prompt, PowerShell, and Terminal window.
  5. Open a new terminal window and run python --version.

If Windows now says the command is not recognized, the Store shortcut is no longer intercepting it, but your actual Python installation is not available through PATH. Follow our guide to adding Python to PATH in Windows 11, then open a new terminal and test again.

You can also use the checks in our article on confirming whether Python is installed in Windows 11. Do not disable the aliases simply because they exist; do so when their behavior conflicts with the Python installation you intend to use.

How to Fix the wt Command Not Opening Windows Terminal

Windows Terminal normally registers wt.exe. If entering wt produces a “not recognized” error, check the alias first:

  1. Open the App execution aliases page.
  2. Find the Windows Terminal entry for wt.exe.
  3. Turn it On.
  4. Close and reopen the terminal window from which you are testing.
  5. Enter wt again.

If the command still fails, confirm that %LOCALAPPDATA%\Microsoft\WindowsApps is present in your user PATH. Microsoft specifically recommends checking that location and warns against trying to modify the protected C:\Program Files\WindowsApps folder.

If you need a standard shell while troubleshooting, our guide explains several ways to open Command Prompt in Windows 11.

How to See Which Program a Command Uses

The App execution aliases page tells you which packaged app owns a listed alias, but it does not show every executable that could answer the same command. Use the command line to see what Windows can find.

In Command Prompt

Run:

where commandname

Replace commandname with the command you are checking, such as python or wt. Add .exe if needed.

In PowerShell

Run:

Get-Command commandname -All

These checks can reveal multiple matches and help you distinguish a WindowsApps alias from a traditional program installation. The first result Windows resolves is usually the one that runs.

Why an Alias Change May Not Appear to Work

Your terminal still has the old environment

Close all Command Prompt, PowerShell, and Terminal windows after changing an alias or PATH value. A window that was already open may keep the environment it received when it started.

The real application is not installed

Disabling a placeholder alias prevents it from handling the command, but it does not install a replacement program. If python changes from opening the Store to “not recognized,” install Python or correct its PATH entry.

The WindowsApps folder is missing from PATH

Enabled aliases are commonly exposed through %LOCALAPPDATA%\Microsoft\WindowsApps. If that location is missing from the current user’s PATH, commands such as wt may fail even though their switches are on.

Another installation wins the PATH search

Windows may find a different executable with the same name first. Use where or Get-Command -All to inspect the matches instead of repeatedly toggling switches.

The app registration is damaged

If an alias is enabled, PATH is correct, and the app is installed but the command still fails, repair or reset the app from Settings > Apps > Installed apps. Reinstalling the app can also recreate its package registration.

Are App Execution Aliases Safe?

The feature itself is a normal part of Windows. An alias listed in Settings is not evidence of malware or an unauthorized remote user. It is a registered command name associated with an app package.

That does not mean every app that can register an alias is automatically trustworthy. Apply the same judgment you use for any software: install apps from sources you trust, keep Windows Security active, and remove software you no longer need. Avoid taking ownership of or deleting files inside the protected WindowsApps folder as a troubleshooting shortcut.

App Execution Aliases vs. PATH

PATH is an ordered list of folders Windows searches when you enter a command without a full location. App execution aliases are small registered entry points made available through Windows’ app infrastructure, commonly through the WindowsApps location in your user profile.

The two systems work together. Enabling an alias makes it available, while PATH helps the shell find it. A conflict can arise when the same command name exists in WindowsApps and in another folder. That is why both the Settings switch and the command search order matter during troubleshooting.

Tips for Managing App Execution Aliases

  • Change only the alias connected to the problem you are solving.
  • Record the original switch state so you can reverse a test.
  • Open a new terminal window after every alias or PATH change.
  • Use where or Get-Command -All before assuming the alias is at fault.
  • Do not delete files from WindowsApps to remove an alias.
  • If an app repeatedly restores a conflicting alias, check the app’s own settings or installation method.

Frequently Asked Questions

What happens if I turn off an app execution alias?

Windows stops using that alias to launch the associated packaged app. The app usually remains installed and can still be opened normally. A different executable with the same name may then be found through PATH.

Should I turn off every alias I do not recognize?

No. Unknown does not mean unsafe, and disabling aliases without a reason can break commands used by apps, scripts, or tools. Change a switch when you are resolving a specific conflict or following trusted documentation.

Why does typing python open the Microsoft Store?

The App Installer Python alias is designed to help users obtain Python from the Store. If you installed Python elsewhere, disable the App Installer entries for python.exe and python3.exe, then verify that the intended installation is in PATH.

Can two apps use the same alias?

Conflicts are possible when apps register the same executable name. Windows may invoke the most recently registered eligible app or find another matching executable earlier in PATH. The Settings switches let you disable an unwanted packaged-app route.

Do app execution aliases work inside WSL?

Do not assume they behave like native Linux commands inside a WSL distribution. Microsoft notes, for example, that the Windows Terminal alias does not run directly there; you can call it through Windows Command Prompt when needed.

Summary

  1. Press Windows + I.
  2. Open Apps > Advanced app settings.
  3. Select App execution aliases.
  4. Turn a conflicting alias off or a needed alias on.
  5. Open a new terminal and test the command.
  6. Use where or Get-Command -All if the result is still unexpected.

Conclusion

App execution aliases make command-line access to packaged apps convenient, but they can also explain why a short command opens the wrong program or the Microsoft Store. The safest fix is targeted: identify the command, inspect its matches, change only the relevant alias, and retest in a new terminal window.

For more technical detail, Microsoft documents how packaged apps register app execution aliases and separately explains the built-in Python Store shortcuts in Windows.

Join Our Free Newsletter

Featured guides and deals

You may opt out at any time.
Read our Privacy Policy