What pip Is Rejecting
Windows cannot find the pip command because Python or its Scripts directory is missing from PATH, or pip was not installed correctly.
Fix the command
Use the Windows Python launcher:py -m pip ... (recommended).
If you need pip directly, add the correct ...\PythonXX\Scripts\ directory to PATH (or use the venv's Scripts\).
If pip is missing, reinstall Python and ensure the "pip" component is enabled, or use py -m ensurepip --upgrade where available.
Prefer per-project virtual environments to avoid global PATH confusion.
Manual Windows launcher checks
Confirm which Python the launcher selects with py -0p, check pip through the launcher with py -m pip --version, and if using a virtual environment, ensure it's activated and then run with python -m pip --version.
Typical Output
'pip' is not recognized as an internal or external command, operable program or batch file Why the Command Was Rejected
Usually this comes down to python was installed without pip (or pip was removed), you're using a Python install that isn't the one you think (multiple Python installs), or the Scripts\ directory for that Python/venv isn't on PATH.
Re-run the Minimal Correct Command
Run py -m pip --version and confirm it succeeds, and re-run your original install command using py -m pip install ....
How pip is launched on Windows
On Windows, pip is typically installed as a console script (for example pip.exe) inside a Python install or virtual environment's Scripts\ directory. If that Scripts\ directory is not on PATH (or you intended to use a different Python), pip will not be found.
Avoid Command and Config Drift
To prevent this, use py -m pip on Windows instead of calling pip.exe directly, create and activate a venv per project (py -m venv .venv) and install inside it, and avoid manually editing PATH for multiple Python installs unless you standardize on one.