> the inevitable confusion when multiple PATH updates do not play well together (which they don't).

Oh I see. Did not think about that. I can see a scenario where you install 3.9, PATH is set, you install 3.10, the PATH update fails for some reason and then you get stuck because PATH was not updated correctly... and then you're back to manually setting PATH which was the thing we were trying to prevent ...

> you can modify [Python installations coming from the Windows store] through the built-in "Manage App Execution Aliases" control panel if you have multiple)

Good to know, thanks. That was one of my concerns actually.

> I'm sick to death of being abused over this issue

I'm sorry to hear that and I apologize - I was simply trying to get answers.

Well, now that I know why the box is not ticked, I can say I'm happy with the state of the installer, and I guess I'll continue to teach my students about PATH - after all, it's a useful skill to have ;)