How to Reset App Execution Alias Overrides in Windows 11 Advanced App Settings

Checking App Execution Aliases in Settings

Checking app execution aliases in Settings lets you see which programs use shortcuts to run from the command prompt. Open Settings ⚙️, go to Apps, click Advanced app settings, and choose App execution aliases to view the full list of apps installed on your computer.

1. Open Settings ⚙️.

   

2. Select Apps from the left-hand navigation menu.

   

3. Click on Advanced app settings.

   

4. Click on App execution aliases to view a complete list of all command shortcuts registered on your computer.

The resulting list displays every available command alias alongside a toggle switch indicating whether it is enabled or disabled. Applications that register duplicate aliases appear here with individual toggles, letting you turn off specific store packages without affecting your primary desktop tools.

How to Reset App Execution Aliases via Settings

To reset app execution aliases via Settings, you need to turn the switch for a specific program off and back on again. This forces Windows to fix broken shortcut links that stop commands from working properly in your terminal window.

1. Open Settings ⚙️.
2. Go to Apps and select Advanced app settings.

   

3. Click App execution aliases.

   

4. Locate the specific application alias you want to fix in the list.
5. Toggle the switch next to the application from On to Off.
6. Wait a few moments, then toggle the switch back to On to reset the internal routing table for that command.

If a toggle switch appears greyed out, the application package is protected by the operating system or currently running in the background. Close any active instances of that application and try toggling the switch again.

Cleaning Up Orphaned Alias Files in WindowsApps

You can delete these lingering files using File Explorer to stop ghost commands from showing up when you type in PowerShell.

Open File Explorer from your taskbar or by pressing the Windows Key + E.

1. Open File Explorer and click the View menu at the top.
2. Hover over Show and click to check Hidden items so you can see protected system directories.
3. Navigate to your local application folder by pasting %LocalAppData%\Microsoft\WindowsApps into the File Explorer address bar and pressing Enter.
4. Locate the shortcut files associated with the problematic application, such as python*.exe or similar stubs.
5. Right-click the target file and select Delete. (Note: Deleting files directly from the WindowsApps folder may require administrator permissions and ownership changes if the files belong to protected Microsoft Store packages).

Resetting Aliases Using PowerShell Automation

Resetting aliases using PowerShell automation lets you fix many broken command shortcuts at once without clicking through menus. You run an administrator-level console and use script commands to clear out multiple overrides quickly across your computer user accounts.

1. Open an administrator-level console by right-clicking the Start button and selecting Terminal (Admin) or PowerShell (Admin).
2. Open the Start menu, type powershell, right-click Windows PowerShell, and select Run as administrator.
3. Approve the User Account Control prompt that appears on your screen.
4. Query the current state of your installed package execution aliases by typing the appropriate management cmdlet or script loop designed to check app capability registrations.
5. Execute your cleanup or reset script to clear invalid alias mappings from the current user registry hive.

Troubleshooting Persistent Alias Conflicts

Troubleshooting persistent alias conflicts fixes programs that keep turning their command shortcuts back on after you restart your computer. You fix this stubborn behavior by stopping background Microsoft Store updates or changing settings in the Registry Editor.

Check for lingering user-level environment variables that might point to outdated installation directories. Open the Start menu, type Edit the system environment variables, and click the button to inspect your user and system paths. Removing dead paths ensures your terminal sessions look at the correct executable locations rather than falling back to broken Microsoft Store stubs.

What to do next

You should now see your command-line environment correctly routing commands to your preferred applications without interference from unwanted store stubs. If command-line redirection still fails, verify your system and user PATH environment variables to ensure your preferred executable directories take precedence over the default WindowsApps path.