pip Is Not Recognized in Windows Command Prompt? Fix It Fast

You install Python on Windows, open Command Prompt, type pip install requests, and Windows answers that pip is not recognized as an internal or external command. Nothing is wrong with pip itself. Windows simply cannot find it, because the folder containing pip was never added to the PATH environment variable. This guide shows you how to confirm the cause, fix it with a reinstall or a manual PATH edit, and use the py launcher method that avoids the problem entirely.

Quick Answer

The “pip is not recognized” error means Windows cannot locate the pip program, usually because Python was installed without ticking Add python.exe to PATH. The quickest workaround is to run py -m pip install package-name, which works on most Windows installs immediately. The permanent fix is to reinstall Python with the PATH option ticked, or to add Python’s folder and its Scripts folder to the PATH variable manually.

Why Windows Cannot Find pip

When you type a command, Windows searches the folders listed in the PATH environment variable, in order, looking for a matching program. The Python installer places python.exe in one folder and pip.exe in a subfolder called Scripts. If neither folder is in PATH, both python and pip produce the “not recognized” message even though they exist on your disk.

There is also a Windows quirk to know about. Typing python on a fresh machine may open the Microsoft Store instead of running Python. That is Windows’ app execution alias doing it, and it fools many beginners into thinking Python is installed when it is only a placeholder shortcut.

Quick Test Before You Fix Anything

1. Open a fresh Command Prompt window.
2. Type py --version and press Enter. If a Python version prints, the Python Launcher is installed and working.
3. Type py -m pip --version. If this prints a pip version, pip is perfectly fine and only the PATH shortcut is missing. You can install packages right now with py -m pip install requests and fix PATH afterwards for convenience.
4. If both commands fail, Python itself is probably not installed properly, so go straight to the reinstall fix below.

Fix 1: Reinstall Python With the PATH Option

This is the most reliable fix for beginners because the installer sets everything up correctly.

1. Download the latest Python 3 installer from python.org and run it.
2. On the very first screen, tick the box labelled Add python.exe to PATH at the bottom before clicking anything else. This box is easy to miss and is the whole reason for the error.
3. Choose Install Now and let the setup finish.
4. Close all Command Prompt windows, open a new one, and test python --version and pip --version. Both should now answer correctly.

The official Python on Windows documentation describes each installer option, including the PATH checkbox and the py launcher, if you want the background details.

Fix 2: Add Python to PATH Manually

If you would rather not reinstall, add the folders yourself:

1. Find your Python installation folder. A typical location is C:\Users\YourName\AppData\Local\Programs\Python\Python312. The version number at the end may differ.
2. Press the Windows key, type environment variables, and open Edit the system environment variables, then click Environment Variables.
3. Under User variables, select Path and click Edit.
4. Click New and add the Python folder path, then click New again and add the same path with \Scripts on the end. The Scripts entry is the one that makes pip work.
5. Click OK on every dialog, then open a brand-new Command Prompt and test pip --version. Existing terminal windows never see PATH changes, so reopening is essential.

Fix 3: Turn Off the Microsoft Store Alias

If typing python opens the Microsoft Store even after a correct install, open Settings → Apps → Advanced app settings → App execution aliases and switch off the entries for python.exe and python3.exe. Windows will then use your real installation. Our step-by-step walkthrough on running a Python file from the Windows terminal also covers this alias problem with screenshots described in text.

Common Mistakes to Avoid

• Testing in the same terminal window. PATH changes only apply to newly opened windows, so an old window will keep reporting the error and mislead you.
• Adding only the Python folder and not Scripts. python will work but pip will still be missing, because pip lives in the Scripts subfolder.
• Typing pip commands into the Python interpreter. If your prompt shows >>>, you are inside Python. pip commands belong in Command Prompt or PowerShell, not in the interpreter.
• Editing the system PATH instead of the user PATH by accident. Either works on your own machine, but the user Path is safer and needs no admin rights.

After the Fix: A Two-Minute Sanity Tour

With PATH repaired, take a moment to confirm the whole toolchain behaves, so you are not surprised later. Run python --version and pip --version side by side. The pip output ends with the Python version it belongs to, in brackets, such as (python 3.12). Those versions should agree; if pip claims a different Python than the one python launches, you have multiple installations and should prefer the py -m pip form so the pairing is explicit.

Next, install something harmless to prove the pipeline end to end: pip install requests is the traditional first package. Then list what you have with pip list, and inspect one entry with pip show requests. Finally, keep pip itself healthy with python -m pip install --upgrade pip every few months; pip prints a notice when a newer release exists, and upgrading avoids subtle warnings when installing modern packages. None of this is strictly required, but five minutes of verification now means that when a tutorial says “just pip install it,” your machine quietly does — which is exactly the state a Python learner on Windows wants to reach and stay in.

Conclusion

“Pip is not recognized” is a PATH problem, never a pip problem. Use py -m pip to keep working immediately, then fix PATH properly by reinstalling with the PATH box ticked or by adding the Python and Scripts folders manually. Restart your terminal after any change, and both python and pip will respond as expected.

Frequently Asked Questions

Why does py work when python does not?

The py launcher is installed into the Windows folder, which is always on the PATH. It then finds your Python installations by looking in the standard install locations and the registry. That is why py -m pip succeeds even when the plain pip command is not found.

Where is pip.exe located on Windows?

Inside the Scripts folder of your Python installation, for example C:\Users\YourName\AppData\Local\Programs\Python\Python312\Scripts\pip.exe. You can run it with its full path as a one-off test, but adding the folder to PATH is the real fix.

Do I need administrator rights to fix PATH?

No. Editing your user PATH needs no admin rights and covers Command Prompt, PowerShell, and VS Code terminals opened under your account. Only the system-wide PATH requires administrator permission.

pip works in Command Prompt but not in PowerShell. Why?

Both shells read the same PATH, so first open fresh windows of each and test again. If PowerShell still fails, you may have typed the command inside a Python session or a virtual environment state differs between them. A fresh window test rules most of this out.

What if I have two versions of Python installed?

That is normal on many machines and not a problem in itself. Each installation has its own pip and its own packages. Problems start only when you forget which one a command belongs to. The py launcher keeps them straight: run py --list to see every version it can find, and call a specific one with a flag such as py -3.11 -m pip install requests when a project needs that exact interpreter’s pip.

Should I just always use py -m pip instead?

Honestly, yes — many experienced Windows users do exactly that. It guarantees pip matches the Python version you intend, and it keeps working even on machines where PATH is messy. Fixing PATH is still worthwhile so that plain python and pip behave in tutorials.