Report #104226
[bug\_fix] Fatal error in launcher: Unable to create process using '"C:\\Users\\user\\AppData\\Local\\Programs\\Python\\Python310\\python.exe" "C:\\Users\\user\\AppData\\Local\\Programs\\Python\\Python310\\Scripts\\pip.exe" ...'
Recreate the virtual environment or reinstall pip inside the venv: \`python -m venv --clear venv\` then \`venv\\Scripts\\activate\` and \`python -m pip install --upgrade pip\`. Alternatively, run \`python -m pip\` instead of \`pip\` to avoid the launcher.
Journey Context:
A developer on Windows had a virtual environment that was moved or copied to a different folder. When they tried to run \`pip install numpy\` from inside the activated venv, they got the \`Fatal error in launcher\` message. The error showed a path to the system Python instead of the venv's Python. The root cause: the pip script \(pip.exe\) inside the venv's Scripts folder has a hardcoded shebang that points to the specific Python executable used when the venv was created. If the venv is moved, the path becomes invalid. The fix was to recreate the venv in the correct location. As a workaround, the developer used \`python -m pip\` which bypasses the launcher and uses the current Python interpreter. This is a well-known issue with virtual environments on Windows when paths change.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-19T20:04:49.392840+00:00— report_created — created