Is Python really broken?
A damaged installation is more likely when the executable exists but crashes, standard-library imports fail, pip points into missing locations, or a maintenance/update operation left the runtime inconsistent. A missing python command alone can be only a PATH or alias problem.
Run a four-command health check
Write down exactly which command fails. That isolates interpreter damage from pip, PATH and environment issues.
Refresh Python Install Manager configuration
Current Python documentation recommends checking the manager and Windows aliases when commands become inconsistent. If the manager is available, refresh generated shortcuts and run its configuration checker.
If the manager itself is damaged, reinstalling the Python Install Manager can restore management access to runtimes without automatically deleting those runtimes.
Use Modify or Repair when available
If your Python version came from the classic Windows executable installer, open Installed apps, select that Python version, and use its maintenance options such as Modify or Repair when offered. This is safer than manually copying DLLs or standard-library folders.
If your workflow needs IDLE, Tcl/Tk, pip, shortcuts or the standard library, verify those installer features are enabled.
Use a clean reinstall only when repair cannot restore core Python
If the interpreter crashes, core imports fail, or maintenance repair repeatedly fails, preserve projects and dependencies, uninstall only the affected runtime, restart Windows, and reinstall the required version from an official source.
Confirm Python and pip belong to the same repaired setup
The interpreter shown by Python and the interpreter associated with pip should match the installation you intended to repair.
Know which layer you are repairing
Python on Windows has several layers that can fail independently: the runtime files, Python Install Manager, app execution aliases, PATH entries, pip, virtual environments, and IDE interpreter settings. A working python -c test means the core interpreter is alive even if another layer is broken.
Repair the smallest failed layer first. For example, a missing package command may be solved by python -m pip or py install --refresh; it does not justify deleting the runtime.
Frequently asked questions
Should I delete Python folders manually?
Not as a first step. Manual deletion can leave shortcuts, aliases, launchers and virtual environments pointing at files that no longer exist.
Why does pip fail when Python works?
pip may belong to another interpreter or its files may be damaged. Test it through the intended interpreter using python -m pip.
Can reinstalling the manager delete my runtimes?
The Python Install Manager and the runtimes it manages are separate; current documentation notes that uninstalling the manager does not uninstall runtimes.
Related Python fixes
Continue with the page that matches the symptom you see after this step.
References
Installation behavior and commands were checked against current Python documentation on 8 August 2026.