GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — More troubleshooting tips for 'py' command not found · Issue #223 · python/pymanager

More troubleshooting tips for 'py' command not found #223

New issue
Copy link
New issue
Copy link
Closed
Closed
More troubleshooting tips for 'py' command not found#223
Copy link
Labels
questionFurther information is requestedFurther information is requested

Description

@RussellHuizinga
RussellHuizinga
opened on Nov 19, 2025
Issue body actions

Background

This issue I encountered is largely self inflicted. But I feel what I learned could be added to the troubleshooting documentation or this post itself can hopefully help anyone who puts themselves in a similar predicament.

I was encountering the issue where 'py' gives me a “command not found” error when I type it in my terminal. I followed the troubleshooting documentation, but was still unable to call the command.

Two things combined contributed to my issue, I recently upgraded my windows install to windows 11, and I decided to reinstall Python using the Python Install Manager downloaded from the Microsoft Store. Before my Windows upgrade, I backed up my path and system variables, and at some point in my life with windows 10, I likely removed or never had "%USERPROFILE%\AppData\Local\Microsoft\WindowsApps". This appears to be where windows places the app execution aliases, I can even see the contents of the folder update when I switch the App Execution Aliases on and off. Adding this folder to path resolved my problems.

Details

Not sure if its worth adding to the troubleshooting doc, this is possibly an edge case. But I thought I would write something here to suggest that things to try could be expanded to check that the path contains the expected folder.

Reacted by Steve Dower

Activity

  1. RussellHuizinga
    added
    questionFurther information is requestedFurther information is requested
    on Nov 19, 2025
  2. zooba commented on Nov 20, 2025

    @zooba
    zooba
    on Nov 20, 2025
    Member
    More actions

    That's a good tip. You aren't the first person to remove that directory entirely, and plenty of people have been trapped by dodgy installers that duplicate and move the directory. Having a troubleshooting step that gives the right setting is probably helpful (I wish Windows would just fix it automatically, but alas...)

  3. zooba commented on Jan 15, 2026

    @zooba
    zooba
    on Jan 15, 2026
    Member
    More actions

    The troubleshooting docs now include this tip.

    Reacted by Russell Huizinga
  4. zooba
    closed this as completedon Jan 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    questionFurther information is requestedFurther information is requested

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402520 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.