> recommend we change "install launcher" to "install py launcher" to be explicit.

To be clear, you mean we change "Install launcher for all users" to "Install py launcher for all users"? You get the launcher by default regardless, the only choice here is whether _everyone_ on your machine gets it (and you need to be an admin).

> Long term - it would be cleaner if the user had only 'default' and customize installation on this screen, with all configurations either bundled under Default, or moved to other screens for 'Customized' installs.  We could add notes under default that we're installing python for all users, py launcher, adding Python to PATH, etc.

This is where we started, and the notes are already there. What changed is:
* we don't add Python to PATH by default (because it's bad), and people couldn't find the option
* we had to replace the 3.4 py.exe launcher, which was always for all users, while making it easy for non-admins to install Python

> If a user does not have admin privileges, it may not be helpful to them to present choices they can't install.  For a default install - we could test if user has admin privileges and install for all users, or fall back to 'user' only install.

This is not possible. Most users do not start with admin privileges, but when prompted can provide them (via UAC). What we have here is the best we can offer without requiring complicated leaps of understanding for every type of user.

> recommend we move "for all users" to screen 3, since this screen is about features to add, while the following screen is about how they are configured on the system.

To clarify, we add an "Install py launcher for all users" checkbox on screen 3 and remove it from screen 2? What gets removed from screen 3 to make space for it?

> 1. changing current "py launcher" checkbox to "upgrade py launcher"

But this is incorrect. If you don't select the checkbox, you don't get the launcher. It's a choice to have or not-have, not a choice to upgrade or not-upgrade.

> 2. moving "for all users" to next line down - looks like we have space
> 3. changing "for all users" to "py launcher for all users"

This is feasible, but not high priority. PRs welcome.

> 1. change "install for all users" to "install python for all users"

Trivial - the string is in one of the .wxl files in Tools/msi/bundle (I forget which one right now).

> 2. insert checkbox for "install py launcher for all users" as 2nd item in list.  This would then be directly above the existing "Associate files with Python" checkbox

Instead of the "for all users" on the previous page? This should be straightforward as well, as the enable/disable logic should be the same as for the current one. A change to one of the .thm files, IIRC.


But all this is going to take someone motivated enough to contribute and test it. Right now, I have higher priority issues to spend my limited volunteer time on than the traditional installer. I can review PRs though (ideally including real screenshots so I don't also have to do the manual testing myself).