Is there some reason that recent Windows 3.6 releases don't included executable nor msi installers?

[Adam Preble]

On Friday, May 29, 2020 at 7:30:32 AM UTC-5, Eryk Sun wrote:
> On 5/28/20, Adam Preble <adam.preble at gmail.com> wrote:
> Sometimes a user will open a script via "open with" and browse to
> python.exe or py.exe. This associates .py files with a new progid that
> doesn't pass the %* command-line arguments.
> 
> The installed Python.File progid should be listed in the open-with
> list, and, if the launcher is installed, the icon should have the
> Python logo with a rocket on it. Select that, lock it in by selecting
> to always use it, and open the script. This will only be wrong if a
> user or misbehaving program modified the Python.File progid and broke
> its "open" action.

Thank you for responding! The computers showing the problem are remote to me and I won't be able to access one for a few days, but I will be making it a point in particular to check their associations before continuing without anything else with it.