VS Code Says ‘Python Was Not Found’? Causes and Fixes That Work

You press Run in VS Code and instead of your program, the terminal shows Python was not found; run without arguments to install from the Microsoft Store. Your code is fine. VS Code, or Windows itself, simply cannot locate a real Python interpreter. This message confuses everyone because Python might genuinely be installed already. This guide explains the three situations behind the message and the exact fix for each one.

Quick Answer

The “Python was not found” message appears when the command VS Code runs does not reach a real Python installation. Either Python is not installed at all, Windows’ Microsoft Store alias is intercepting the python command, or VS Code is set to a missing interpreter. Install Python from python.org with the PATH option ticked, turn off the Store’s app execution aliases, install the Microsoft Python extension, and select a valid interpreter with Python: Select Interpreter.

The Three Situations Behind the Message

Situation 1: Python really is not installed

On a fresh Windows 11 machine, typing python does not run Python at all. Windows provides a placeholder that sends you to the Microsoft Store. If you have never deliberately installed Python, that placeholder is all you have, and VS Code’s message is literally correct.

Situation 2: Python is installed but the Store alias wins

Windows keeps app execution aliases for python.exe and python3.exe that point to the Store stub. These aliases can take priority over your real installation, so the terminal opens the Store or prints the “was not found” text even though Python exists in another folder.

Situation 3: VS Code is pointing at a ghost interpreter

If you uninstalled Python, deleted a virtual environment, or moved a project from another computer, VS Code settings may still reference an interpreter path that no longer exists. The editor then reports it cannot find Python when, really, it cannot find that Python.

The Fix, Step by Step

1. Install Python properly. Download the installer from python.org and run it. On the first screen, tick Add python.exe to PATH, then choose Install Now. Avoid the Microsoft Store version for development work, because the full installer gives you the py launcher and predictable paths.
2. Turn off the Store aliases. Open Settings → Apps → Advanced app settings → App execution aliases and switch off the entries for python.exe and python3.exe that mention the Store.
3. Test in a fresh terminal. Close and reopen VS Code (or just open a new terminal panel) and run py --version and python --version. Both should print a version now. If python still fails while py works, your PATH needs attention; the steps in our guide to pip not recognized in Command Prompt fix that too.
4. Install the Python extension. In VS Code, open the Extensions view, search for Python by Microsoft, and install it. Without this extension, VS Code has no Python-aware Run button, interpreter picker, or linting, and terminal behaviour is unpredictable.
5. Select a real interpreter. Press Ctrl+Shift+P, run Python: Select Interpreter, and choose an entry whose path actually exists, such as the python.org install or your project’s .venv. The status bar at the bottom will show the chosen version.
6. Run your file again. Use the Run button or Ctrl+F5. The message should be gone and your program’s output will appear in the terminal.

Checking a Project That Came From Another Computer

Projects carry per-folder settings in a .vscode folder. If settings.json there contains a python.defaultInterpreterPath pointing to a folder from the original machine, delete that line and select the interpreter again. This single step fixes most “it worked on my laptop” mysteries. The VS Code Python environments documentation explains how the editor discovers and stores interpreter choices.

Common Mistakes to Avoid

• Installing from the Microsoft Store and stopping there. The Store build works for casual use but its sandboxed paths confuse many tools. The python.org installer is the safer default for learning and development.
• Testing in an old terminal window. Terminals created before the install cannot see the new PATH. Always open a new terminal, or restart VS Code completely.
• Skipping the Python extension. VS Code alone does not know how to run Python files. The Run triangle without the extension launches a plain shell command that inherits every PATH problem.
• Choosing an interpreter from a deleted virtual environment. If the status bar shows a path inside a .venv you removed, reselect a valid interpreter rather than recreating folders at random.

After the Fix: Confirm Everything Agrees

Before returning to your project, run one verification that ties the whole setup together. Create a two-line test file:

import sys
print(sys.executable)

Run it with the VS Code Run button. The printed path is the interpreter VS Code is truly using — not the one you hope it is using. It should point either at your python.org installation or at your project’s .venv folder, whichever you selected. Then, in the same integrated terminal, run python -m pip --version and confirm pip reports that same Python family. When interpreter, pip, and editor all agree, package installs, imports, and debugging behave predictably, and the whole class of “not found” messages stops recurring.

It is also worth knowing that VS Code settings exist at three levels — user, workspace, and folder — and a stale interpreter path saved at any level can resurface later. If this error ever returns without you uninstalling anything, search all three settings levels for defaultInterpreterPath entries pointing at folders that no longer exist, remove the stale one, and reselect. Five minutes of housekeeping here prevents the ghost-interpreter version of the problem from following a project around for months.

Conclusion

“Python was not found” is a locator problem with three possible causes: no real install, the Store alias intercepting the command, or VS Code pointing at a vanished interpreter. Install Python from python.org with PATH enabled, disable the aliases, add the Microsoft Python extension, and select an existing interpreter. After those steps, the Run button does what you expected all along.

Frequently Asked Questions

Why does VS Code say Python was not found when I installed it yesterday?

Most likely the Store alias is intercepting the python command, or the terminal inside VS Code was opened before you installed and still holds the old PATH. Disable the aliases in Windows Settings and restart VS Code fully, then test python --version in a new terminal.

Should I install Python from the Microsoft Store instead?

For development with VS Code, the python.org installer is the better choice. It includes the py launcher, standard folder paths, and the PATH option, all of which reduce exactly the class of errors described in this guide. The Store version is fine for quick experiments only.

What does “run without arguments to install from the Microsoft Store” mean?

That text comes from the Windows placeholder program, not from VS Code or Python. Windows intercepts the python command when no real installation is found and offers the Store as a shortcut. Treat the message as a sign that your command never reached a genuine interpreter.

How can I check which interpreter VS Code is using?

Look at the status bar at the bottom of the VS Code window; it shows the selected Python version. Click it to change the selection. You can also run import sys; print(sys.executable) in your script to print the exact interpreter path at runtime.

Does reinstalling VS Code itself ever help?

Almost never for this message. The editor is only reporting what the operating system tells it: the command it ran did not reach a Python interpreter. Reinstalling Python correctly, clearing the Store aliases, or repairing the saved interpreter path addresses the cause. Reinstall VS Code only if the editor itself is damaged, which presents with far broader symptoms than one Python error.

The error appears only for one project. What is different?

That project almost certainly has a .vscode\settings.json file pinning an interpreter path that does not exist on this machine, or its virtual environment was deleted. Remove the stale path or reselect the interpreter while that folder is open, and the project will behave like the others.