The decision cannot reasonably be reversed now - this sort of passionate feedback was really needed during the alphas to have any impact. I'm sorry you didn't feel the need to participate in Python's development, as this extra feedback would have been useful.

For most users who are installing Python for themselves, the bundle launcher provides a much better experience. As well as CRT detection, it also allows true per-user installation as well as decoupling tasks such as precompiling .pyc files from installing components and enabling the web installers. There is also a more reliable upgrade mechanism that retains previous settings and the launcher is now correctly reference counted (though there will be conflicts with the 2.7 and 3.4 installer...).

After discussions at PyCon US in April, I chose to make the per-user installation the default as it best fits the user segment we (as a development team) are most concerned about. Administrators who are deploying across a network do now need to work harder than before, which we considered a fair tradeoff for non-admin users to be able to install and use Python.

If you much prefer MSIs, you can pass the /layout option to the wrapper and obtain the raw MSIs and install them individually (passing "TARGETPATH=location" as a property). However, I think the documentation for the launcher options (https://docs.python.org/3.5/using/windows.html) is much better than anything we had in the past (I had nothing to do with the old installer, but had to regularly decompile it to diagnose installation issues).

So thankyou for the feedback, but on balance between administrators and individual users we've decided to help save individual users from having to read documentation, at the expense of needing administrators to refer to the instructions to do automated installation.