Skip to main content

How to Add Python to the Windows Path Variable: A Simple Solution

If you've ever installed Python on a Windows machine but encountered issues running Python commands in the terminal, you might be facing a missing Path variable entry. Recently, I solved this issue by manually adding Python to the Windows environment variables. Here’s how you can do it too.

The Problem

After installing Python, you might open the Command Prompt and type:

python --version

and receive an error stating that Python is not recognized as an internal or external command. This happens when Python’s installation path isn’t added to the system’s environment variables.

The Solution

To fix this, follow these steps:

Step 1: Locate the Python Installation Directory

  1. Open the Windows search bar and type Python.

  2. Click on Open file location to navigate to the installed Python folder.

  3. Inside this directory, locate the Scripts folder. The path should look something like this:

    C:\Users\YourUsername\AppData\Local\Programs\Python\PythonXX\Scripts

    (where PythonXX represents your installed version of Python, such as Python39 for Python 3.9).

Step 2: Add Python to the Environment Variables

  1. Open the Windows Search and type Environment Variables, then select Edit the system environment variables.

  2. In the System Properties window, click on the Environment Variables button.

  3. Under System Variables, find and select Path, then click Edit.

  4. Click New and add the full path of the Scripts folder you found earlier.

  5. Also, add the main Python directory path (e.g., C:\Users\YourUsername\AppData\Local\Programs\Python\PythonXX).

  6. Click OK to save your changes.

Step 3: Verify the Installation

To confirm that Python is correctly added to the Path:

  1. Open Command Prompt and type:

    python --version

    or

    python

    If Python starts without an error, the setup is complete!

Conclusion

Adding Python to the Windows Path variable manually ensures that you can run Python commands seamlessly from any terminal window. If you ever run into the same issue, simply locate the Python directory and update the environment variables as outlined above. Happy coding!

Comments

Popular posts from this blog

PromptCraft Blog Series #7: Visual Prompt Design for No-Coders – Learn how to build effective AI prompt flows using visual tools in no-code platforms like Lovable, Bubble, and more

PromptCraft Series #7 – Visual Prompt Design for No-Coders ✨ PromptCraft Series #7 "Visual Prompt Design for No-Coders" 🗕️ New post every Monday 🎨 Why Visual Prompt Design Matters Prompt engineering doesn’t have to be text-only or code-heavy. Today, powerful no-code tools allow you to design, trigger, and connect prompts visually using simple blocks, fields, and flows. Drag-and-drop interfaces reduce human error Inputs can be dynamically passed to prompt templates Output logic can be reused across different use cases Non-developers can build intelligent apps visually This blog explores how to do it right — with examples, templates, and real platform walkthroughs. 🔧 Anatomy of a Visual Prompt Block Component Purpose 🔢 Input Field Captures dynamic user input (text, image, number) 🧠 Prompt Template Combines static in...

The behind-the-scenes story of how we chose our tech stack, what went wrong, and why we changed course

The Tech Stack We Chose (And Why We Switched Midway) The Tech Stack We Chose (And Why We Switched Midway) By Rexman Published: 13/06/2025 – Behind the Scenes Series #2 🧠 The Master Plan Choosing a tech stack was easy. Or so we thought. We had a Notion page comparing Postgres vs Mongo, Firebase vs Supabase, React vs Vue vs SvelteKit. We were acting like we were choosing our life partner — when really, we just needed a stack that wouldn’t break in 3 weeks. We picked: Frontend: React Native with Expo Backend: Supabase (Postgres + Auth) Storage: Supabase Storage AI integration: Claude (Anthropic) Deployment: Vercel 💥 Reality Bites Week 1 was smooth. By Week 2, cracks appeared. Supabase’s Postgres was fine… until our expensive queries choked it. React Native was okay, but we hit prop-passing hell fast. Claude integration was awesome… until we realized we needed more dynamic prompt chaining a...

PromptCraft Blog Series #6: Prompt Debugging and Optimization – Learn how to fix and improve AI prompt outputs for more accurate, helpful results.

PromptCraft Series #6 – Prompt Debugging and Optimization "As of May 2025, summarize one real, recent science discovery based on known sources. Add links if available and avoid speculation." ✨ PromptCraft Series #6 "Prompt Debugging and Optimization: Getting the Output You Want" 🗕️ New post every Monday 🔍 Why Prompts Sometimes Fail Even the best models can give you: ❌ Irrelevant answers ❌ Generic or vague responses ❌ Hallucinated facts or made-up data ❌ Wrong tone or misunderstanding of intent Often, it’s not the AI’s fault — it’s the prompt . 🔧 How to Debug a Prompt Start with these questions: Is the role or task clearly defined? Did you give examples or context? Are your constraints too loose or too strict? Did you format the output instructions properly? Then iterate your prompt, one element at...