Скачать или смотреть How to Fix Pip Launcher Issues After Uninstalling Python on Windows

Struggling with Pip errors after uninstalling Python on Windows? Discover how to resolve launcher issues and clean up your installation for smooth module management!
---
This video is based on the question https://stackoverflow.com/q/62503975/ asked by the user 'O 0 O' ( https://stackoverflow.com/u/13787691/ ) and on the answer https://stackoverflow.com/a/62508078/ provided by the user 'ivan_pozdeev' ( https://stackoverflow.com/u/648265/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: Python launcher tries to run Pip from a Python installation that I've already uninstalled

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Troubleshooting Pip Launcher Errors After Uninstalling Python on Windows

Many Windows users have encountered issues with Pip, especially after uninstalling a version of Python. If you recently uninstalled Python 3.5 and are now facing problems when trying to install modules (like TensorFlow), you're not alone. In this post, we’ll dive into the error messages you're receiving and show you how to resolve them step by step.

The Problem at Hand

Here's what you might see when you attempt to check your Pip version or run a command:

[[See Video to Reveal this Text or Code Snippet]]

Additionally, other commands may produce a warning similar to this:

[[See Video to Reveal this Text or Code Snippet]]

What Does This Mean?

These errors suggest that there's still a reference to the Python 3.5 installation in your system, even though you've uninstalled it. This could be due to leftover files or configuration settings that persist after removing the Python installation. Let's explore how to fully resolve these issues.

Solution Steps

Follow the steps below to ensure that all remnants of Python 3.5 are cleared from your system, which should help get Pip working again.

Step 1: Restart Command Prompt

After uninstalling Python, it's crucial to restart your command prompt. This sets the environment to recognize any changes made, including the uninstallation of Python. If you want to be thorough, go ahead and restart your system to ensure that no processes are hindering the uninstallation.

Step 2: Check Control Panel for Python 3.5

Open Control Panel: Type appwiz.cpl into the Run dialog (Win + R) and hit Enter.

Uninstall Python: Look for Python 3.5 in the list. If you find it listed, uninstall it again.

Step 3: Remove Leftover Files

You need to manually delete the remaining files associated with Python 3.5:

Navigate to c:\users\yoonh\appdata\local\programs\python\python35.

Delete the entire python35 folder and its contents.

Step 4: Clean Up Environment Variables

Type SystemPropertiesAdvanced into the Run dialog (again, Win + R) and hit Enter.

In the dialog that opens, click on Environment Variables.

Check the PATH: Look for any entries that point to the uninstalled Python 3.5 directory. If found, remove them.

Step 5: Edit the Windows Registry (Use with Caution)

Editing the registry can be risky; ensure you proceed carefully and back up any important data beforehand. Follow these steps:

Open the Registry Editor by typing regedit into the Run dialog.

Navigate to these locations:

HKCU\Software\Python\PythonCore

HKCU\Software\Wow6432Node\Python\PythonCore

HKLM\Software\Python\PythonCore

Check for Remnants: Look for any keys related to Python 3.5 and delete them if they exist.

Conclusion

By following the steps outlined above, you should be able to resolve the issue and have Pip functioning appropriately again. Always remember to restart your command prompt after making changes and to double-check for leftover files or registry entries. This will prevent similar issues in the future as you install and manage Python packages.

Troubleshooting can be a hassle, but with this guide, we hope you’ve found an effective solution to your Pip errors! If you need further assistance or have any questions, feel free to ask in the comments below.