python.exe and other aliases not working before reinstalling the manager

[R4ygen]

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.2.240.0

Describe the bug
I was trying to start python via the "python" command, instead of the "py" command. But it was not working.
Powershell kept giving me this error:

Program 'python.exe' failed to run: The system cannot find the path specifiedAt line:1 char:1
+ python
+ ~~~~~~.
At line:1 char:1
+ python
+ ~~~~~~
    + CategoryInfo          : ResourceUnavailable: (:) [], ApplicationFailedException
    + FullyQualifiedErrorId : NativeCommandFailed

The "py" command on the other hand was working like a charm.

I've tried to:

1. Refresh the python install with py install --refresh
2. Unchecked and re-checked all python aliases in Windows' "Manage app execution aliases" settings.
3. Re-configure the python installation with py install --configure
4. Force re-installing python with py install -f default

Nothing was working. And %UserProfile%\AppData\Local\Microsoft\WindowsApps was correctly in the PATH.
So I've tried to launch the python.exe directly present in the WindowsApps folder: Nope, same issue.

At that point, since it was an issue with the Windows app, I thought I'd try to reinstall the Python Install Manager itself from the Store. And that fixed it!

No idea what was wrong with the .exe link inside the WindowsApps folder. But this error, and this fix (reinstalling the manger itself) are not present in the troubleshooting steps in the online docs. So I'm reporting this in case another user finds itself in this same pickle, and, to perhaps include "reinstall the manger" as an additional troubleshooting step in the online docs?

To Reproduce
No idea.
I'm glad to provide log files. But dunno where to find log files related to the WindowsApps .exe files.

Expected behavior
Implement the fix found, in the troubleshooting steps.

[zooba]

Hmm, all I can imagine here is that Windows somehow created corrupt shortcuts on the initial install. It's unlikely that anything would show up in the OS logs, as it would clearly be an unintended bug. Unfortunately, there are a few of those floating around in alias management, but they're never reproducible enough to get them fixed.

If you (or anyone else) would like to make a PR adding the suggestion as a final fallback (it's really not going to do anything more for the most common problems, only the really obscure ones like yours), the file is Doc/using/windows.rst over in https://github.com/python/cpython.