Resolving the ‘Python Was Not Found’ Error: Fixing PATH Variables and Windows App Execution Aliases
Quick Summary / Direct Answer: The ‘Python Was Not Found’ error on Windows happens when the command shell cannot locate the executable in your system’s PATH, or when Windows App Execution Aliases intercept the command. Fix it by checking ‘Add Python to PATH’ during installation, manually updating environment variables, or disabling Microsoft Store aliases in Settings.
Key Takeaways:
- Windows App Execution Aliases frequently hijack terminal commands if Python wasn’t installed from the official Microsoft Store.
- Your system PATH environment variable must contain explicit directories pointing to both the Python installation folder and the Scripts subdirectory.
- Running a manual repair via the original Python installer provides a reliable, automated fix for broken symlinks and registry keys.
Diagnosing the Windows PATH Breakdown
It happens constantly. You open your terminal, type python, and the system throws a frustrating error. It failed. Here is why.
Windows relies on the PATH environment variable to know where executable binaries live on your disk. When you type a command, the OS scans a prioritized list of directories. If the folder containing python.exe isn’t in that list, Windows shrugs and throws an exit code.
Most tutorials gloss over this edge case, but we see it daily in enterprise environments. When deploying automation scripts or onboarding junior engineers, missing PATH entries account for nearly half of all initial setup tickets. Let’s fix that right now.
The Conflict with Windows App Execution Aliases
Even if your PATH looks pristine, you might still hit a wall. Windows 10 and 11 feature App Execution Aliases. These act as blank pointers designed to push users toward the Microsoft Store. If the alias is enabled but the actual runtime is missing or misconfigured, typing python opens the Windows Store instead of executing your script.
How to Disable Store Aliases
- Open the Windows Start Menu and search for Manage app execution aliases.
- Scroll down until you locate entries named App Installer for Python (typically
python.exeandpython3.exe). - Toggle these switches to Off.
This simple action frees your command-line interface from Microsoft Store interception, allowing your shell to read your actual local environment variables.
Manual PATH Configuration Workflow
If disabling aliases doesn’t cut it, you must manually register the binary locations. Let’s look at where Python typically resides under standard modern installations for a user named Developer:
| Environment Path Type | Target Directory | Purpose |
|---|---|---|
| User Binary Directory | C:\Users\Developer\AppData\Local\Programs\Python\Python311\ |
Contains the core python.exe and pythonw.exe executables. |
| User Scripts Directory | C:\Users\Developer\AppData\Local\Programs\Python\Python311\Scripts\ |
Houses third-party CLI tools installed via pip (e.g., pytest, black). |
| Global Alternative | C:\Program Files\Python311\ |
System-wide installation path used when installing for all users. |
To add these manually, open your System Properties, navigate to Advanced system settings, click Environment Variables, and edit the Path variable under User or System variables. Append both directories using absolute paths.
Validating Your Fix via PowerShell
Once you update your environment variables, close all open terminal windows. Windows does not dynamically reload PATH variables for active shell sessions. Open a fresh PowerShell instance and run the validation sequence below:
# Check the resolved path of python
Get-Command python
# Verify the active interpreter version
python --version
# Ensure pip is correctly bound
pip --versionIf these commands return valid version numbers without throwing errors, your configuration is solid. If PowerShell still complains, double-check for trailing backslashes in your PATH string, which occasionally break Windows path resolution.
Frequently Asked Questions
Why does typing python open the Microsoft Store?
This behavior is controlled by Windows App Execution Aliases. Windows inserts dummy stubs into the PATH to encourage users to download packages directly from the Microsoft Store. Disabling these aliases via system settings resolves the issue immediately.
Should I add Python to the User PATH or System PATH?
For most individual developer workstations, adding Python to the User PATH is safer and does not require administrator privileges. Use System PATH only if multiple users on the same machine require shared access to the identical interpreter installation.
How do I fix pip commands failing after fixing Python?
If Python works but pip throws an error, your ...\Scripts\ directory is missing from the PATH variable. Add that specific subdirectory alongside your main Python directory to restore package management functionality.
The Bottom Line: Actionable Next Steps
Stop wrestling with broken terminals. First, disable those pesky Microsoft Store execution aliases. Next, verify your user PATH contains both the base installation folder and the Scripts directory. Finally, restart your shell to apply changes. Implement these steps now and get back to writing production-grade code without environment friction.
