Diagnose first. Fix second.
Choose the symptom closest to what you see. Each guided fix shows one useful step at a time. When a command needs explanation, you can open it in Tools before running it, then verify the original problem before calling it solved.
Start from the symptom
No account required. Progress is saved on this device as you work through a fix.
Diagnose command discovery before editing PATH.
PythonScript opens then closesKeep the window open long enough to tell normal completion from a real Python error.
Pythonpip command not recognizedVerify pip through the interpreter and repair only the missing layer.
PythonModuleNotFoundError after pip installFind interpreter/package mismatch instead of reinstalling blindly.
PythonPython opens Microsoft StoreSeparate aliases, runtime availability and command routing.
VS CodeWrong Python interpreterMatch VS Code to the intended project interpreter.
VS Code · RestoredPackages not detectedMatch VS Code, Python and pip to the same environment before reinstalling anything.
VS Code · RestoredVirtual environment not workingVerify activation and interpreter selection instead of rebuilding the environment blindly.
VS Code · RestoredPython debugger not startingSeparate interpreter, launch configuration and debugger issues with a guided check.
Python · RestoredInstall multiple Python versionsKeep multiple Python versions side by side and select the intended runtime deliberately.
Python · RestoredInstall a specific Python versionChoose and verify an exact Python version without breaking the working setup.
Python · JupyterJupyter kernel not showing / wrong interpreterMatch the notebook kernel to the Python environment you actually intend to run.
WindowsWindows 11 fixesNetwork, storage, crashes, devices, heat and recovery fixes.
Windows100% disk usageFind the workload or storage cause before disabling services.
Windows UpdateError 0x80070643Identify the failed KB first, including the documented KB5034441 WinRE case.
Evidence → smallest safe action → verify. You can open a command in Tools and return to the same troubleshooting step.