Python Manager Installation Path & `py` Launcher Inconsistency

[m-asadullah]

Python Manager installed from Microsoft Store

C:\Users\<UserName>\Downloads>where py
INFO: Could not find files for the given pattern(s).

C:\Users\<UserName>\Downloads>py list
'py' is not recognized as an internal or external command,
operable program or batch file.

C:\Users\<UserName>\Downloads>where python
C:\Users\<UserName>\AppData\Local\Python\bin\python.exe

C:\Users\<UserName>\Downloads>python --version
Python 3.14.0

Warning

After installation python found but not py

C:\Users\<UserName>\AppData\Local\Packages\PythonSoftwareFoundation.PythonManager_*>tree /f
C:.
├───AC
│   └───Temp
├───AppData
├───LocalCache
├───LocalState
├───RoamingState
├───Settings
│       roaming.lock
│       settings.dat
│
├───SystemAppData
│   └───Helium
└───TempState

C:\Users\<UserName>\AppData\Local\Packages\PythonSoftwareFoundation.PythonManager_*>

The Python Manager open from here in new location,

Caution

This version-oriented location will change in every update so need to add new versioned path to Environment Variables manually.

C:\Program Files\WindowsApps\PythonSoftwareFoundation.PythonManager_25.0.240.0_x64__*>tree /f
C:.
│   AppxBlockMap.xml
│   AppxManifest.xml
│   AppxSignature.p7x
│   py-manager.exe
│   py.exe
│   pymanager.exe
│   pymanager.json
│   pyshellext.exe
│   python.exe
│   python3.exe
│   pythonw.exe
│   pythonw3.exe
│   pyw-manager.exe
│   pyw.exe
│   pywmanager.exe
│   vcruntime140.dll
│   vcruntime140_1.dll
│   version.txt
│   _resources.map.txt
│   _resources.pri
│
├───AppxMetadata
│       CodeIntegrity.cat
│
├───bundled
│       fallback-index.json
│       pythoncore-3.14-64-3.14.0.zip
│
├───MSIX.AppInstaller.Data
│       MSIXAppInstallerData.xml
│
├───runtime
│       manage.cp314-win_amd64.pyd
│       python314.dll
│       python314.zip
│       python314._pth
│       _native.cp314-win_amd64.pyd
│
├───templates
│       launcher-32.exe
│       launcher-64.exe
│       launcher-arm64.exe
│       launcherw-32.exe
│       launcherw-64.exe
│       launcherw-arm64.exe
│       template.py
│
└───_resources
        py.ico
        pyc.ico
        pyd.ico
        python.ico
        pythonw.ico
        pythonwx150.png
        pythonwx44.png
        pythonx150.png
        pythonx44.png
        pythonx50.png
        pyx256.png
        setupx150.png
        setupx44.png

Default behavior of Python Manager, currently is

Location	User PATH	System PATH	Run Python	Run PythonManager
C:\Program Files\WindowsApps\PythonSoftwareFoundation.PythonManager_25.0.240.0_x64...	❌	❌	❌	❌
C:\Users\<UserName>\AppData\Local\Python\bin\	✅	❌	✅	❌

Note

Default installation location C:\Program Files\WindowsApps\PythonSoftwareFoundation.PythonManager_25.0.240.0_x64__*> of Python Manager is not in PATH, if this in PATH then there is no need to report issue. Only installed (bundled) Python 3.14.0 is ~\AppData\Local\Python\bin\ and in PATH, so python (only) run from here.

Expected Behavior

• Default installation location of Python Manager should be in PATH by default.
• py.exe should be exposed via PATH (like python.exe) so commands like py list work.
• PATH entries should remain stable across Store updates without requiring manual symlink creation.

Impact

• Users cannot use the py launcher, breaking workflows that rely on py (e.g., py -3.14, py list).
• PATH breaks after Store updates because executables live in versioned directories.
• Manual fixes (symlinks or copying executables) are required, which is error-prone.

Suggested Fixes

1. Expose py.exe via App Execution Alias (same as python.exe but point is python.exe currently run from separate installation).
2. Stabilize PATH:
   • Provide a non-versioned folder (e.g., C:\Users\<UserName>\AppData\Local\PythonManager) with symlinks to the latest executables.
   • Or update PATH automatically after Store updates.
   • For System wide use this by default System PATH: C:\Program Files\WindowsApps\PythonSoftwareFoundation.PythonManager_25.0.240.0_x64__*.
3. Clarify Documentation:
   • Document where Python Manager installs files.
   • Explain how users can access py.exe and py-manager.exe.
4. Clean up AppData Packages folder:
   • Remove it if unused, or populate it with metadata/symlinks.

Environment

• OS: Windows 11
• Installation source: Microsoft Store → Python Manager
• Python Manager version: 25.0.240.0_x64
• Observed Python version: 3.14.0
• User PATH: C:\Users\<UserName>\AppData\Local\Python\bin\python.exe

Notes

This issue affects reproducibility, automation, and developer workflows. The lack of a stable py launcher in PATH is particularly problematic for scripts, CI/CD pipelines, and educational materials that rely on py.

---

The answer in that issue #223 is not helpful.

[zooba]

py.exe is already exposed as an execution alias, and since that is your first proposed solution, I assume your issue is with the OS (or potentially OS configuration) that didn't create that alias.

Are you able to launch pymanager.exe from anywhere? If so, pymanager install --configure should give you the first-run steps again, and if py.exe is not available it should warn you about missing shortcuts. Opening the "Manage app execution aliases" settings pane and reactivating the alias there ought to fix it. Could you try this and confirm?

Also, it looks like you've used AI to expand your bug. Please don't do that, it's just a waste of our time reading it. We'd rather have short and direct bug reports that don't waste our time.

[m-asadullah]

...assume your issue is with the OS (or potentially OS configuration) that didn't create that alias.

Almost, but Python Manager is not putting its location to PATH, but it asks for CPython and on y= yes, it install the bundled python and put it into user PATH, so it only runs.

Tip

For putting the path into System Path might be elevated step, require administrator permission.

Question: Are you able to launch pymanager.exe from anywhere?
Answer: Not from terminal

Also, if bother the command line traces then might understand, issue is updated for convenience and there is now table to view actual behavior of Python Manager

[zooba]

It sounds like you may have inadvertently (or deliberately) removed the %UserProfile%\AppData\Local\Microsoft\WindowsApps entry from your PATH, which is how aliases are made available. If you've done this, then you should add that path back, which will restore your operating system to it's original state.

I can't decipher anything here that is our responsibility. If you think we've done something wrong, please just write a short summary in a new post - editing old posts, especially excessively long ones, is not at all helpful.

[m-asadullah]

...removed the %UserProfile%\AppData\Local\Microsoft\WindowsApps entry from your PATH, which is how aliases are made available. If you've done this, then you should add that path back, which will restore your operating system to it's original state.

It’s possible that the %UserProfile%\AppData\Local\Microsoft\WindowsApps entry was accidentally removed from the PATH. This had not been a problem before.

Manually, adding this entry into PATH, and the py and python both found.

C:\Users\UserName>where py
C:\Users\UserName\AppData\Local\Microsoft\WindowsApps\py.exe 

C:\Users\UserName>where python
C:\Users\UserName\AppData\Local\Microsoft\WindowsApps\python.exe 
C:\Users\UserName\AppData\Local\Python\bin\python.exe 

C:\Users\UserName>where pymanager
C:\Users\UserName\AppData\Local\Microsoft\WindowsApps\pymanager.exe

Thanks, a lot for figuring this out.

Note: PythonManager (msi) variant works perfect.

---

Scenario: Faced before

After installing Python manager from Microsoft Store, its first run:

After first run complete, then open CMD:

The Python Manager is not able to add this entry %USERPROFILE%\AppData\Local\Microsoft\WindowsApps.

These screenshots are taken after reinstallation of Python Manager from Microsoft Store

[brunoamancio]

I have not removed %UserProfile%\AppData\Local\Microsoft\WindowsApps from path and still got the same issue on Win11. Adding it to PATH fixed the issue.