The plain command may be reaching an install-manager or Store route rather than the runtime you expected.
If typing python opens the Store or an install prompt, Windows may be routing the command through an App Execution Alias.
That result is evidence, not a reason to switch every alias off. Current Python-on-Windows setups use aliases as part of command routing. The useful question is which alias is active, whether py or pymanager can reach a runtime, and whether the plain python command is pointing where you expect.

An alias gives a command name a managed route to an application.
Windows exposes App Execution Aliases through Settings. Python’s current Windows documentation specifically uses these aliases for commands such as python, py and the Python Install Manager. The alias can therefore be part of a healthy installation, or it can be the reason a command opens installation behavior instead of the runtime you expected.
pythonpy still worksThat is strong evidence that a Python runtime is reachable even though the plain python route is different.
The problem may be broader than one alias. The guided fix then checks installation and command-access evidence before changing settings.
Current Python guidance may require the alias to be enabled.
With the current Python Install Manager, Python documentation recommends checking that the relevant “Python (default)” aliases are enabled when python or py is not working. If an enabled alias is stale, toggling it off and back on can refresh the registration. This is very different from the older one-size-fits-all advice to disable Python aliases whenever the Store opens.
One read-only check can tell us whether the runtime is reachable another way.
py --versionread-onlyIf a version appears, The guided fix knows a runtime is reachable and can focus on the plain command route.
py -c "import sys; print(sys.executable)"read-onlyShows the executable selected by the py route without editing aliases.
where.exe pythonread-onlyShows what executable locations the current environment can discover for python.
The same symptom can come from different Windows/Python setups.
A Store or install prompt does not tell us by itself whether Python is absent, whether the current Python Install Manager is handling the name, or whether an older launcher or PATH entry is taking priority. That is why the guided fix combines several clues instead of treating the alias screen as the whole diagnosis.
Python’s current Windows documentation expects commands such as python, py and pymanager to be exposed by the Python Install Manager, with aliases and the WindowsApps route participating in command access.
An older Python Launcher can still exist on upgraded machines. If it takes priority, py can behave differently from the current manager model. The guided fix treats that as a distinct installation style instead of mixing the instructions.
The current Python troubleshooting guidance also checks that %UserProfile%\AppData\Local\Microsoft\WindowsApps remains available in PATH. Removing that route can make managed shortcuts disappear even when their aliases are enabled.
This guide explains why the behavior happens; the guided fix still decides what to check next.
This page does not tell every visitor to change an alias. If the symptom is a Store/install prompt, the guided fix uses that observation plus the py result and installation clues to choose a reviewed path. Tools explains the commands used for that evidence.