Python Install Manager installed runtimes appear in winget list and winget will attempt to manage them

[dtreth]

Install source and version

• Installed from the Windows Store
• Installed with the MSIX from python.org
• Installed with the MSI from python.org
• Installed with winget install 9NQ7512CXL7T

Version: 26.0.240.0

Describe the bug
when Python Install Manager installs a new runtime, that runtime is listed in the winget list command. This is new-ish, and it introduces a weird bug where winget upgrade --all will detect it as needing an upgrade, and install the "old" style python installer, which may clobber the py command with the old launcher.

To Reproduce
Steps to reproduce the behavior:

1. Open terminal.
2. Install pymanager winget install 9NQ7512CXL7T
3. run the launcher py and let it automatically install the latest version of Python (3.14.3 as of this writing)
4. run winget list

Expected behavior
Either the runtime doesn't exist at all in the list, being managed by Python Install Manager, OR the runtime exists with proper version listed and allows winget to upgrade the appropriate package rather than installing the standalone.

Observed behavior
The runtime appears as:
Python 3.14.3 Python.Python.3.14 < 3.14.0 3.14.3 winget

The < 3.14.0 is the real killer here, but I suspect even with the correctly reported version it would still clobber if the runtime version was bumped before the Python Install Manager got its chance to grab the new one.

[zooba]

We don't have any control or influence over what WinGet does here, it'll need to be reported on their repository. Most likely it's detecting the uninstall information we register to allow Add/Remove Programs to remove individual runtimes, but they ought to be able to figure out that it's not theirs. They probably just haven't caught up with the fact that we're not relying on our old installer anymore, and still have assumptions that we are.