Apparently casual Python installer since 3.5 has the MSIs I require embeded and they won't come out. There's however the web-installer for each Python and with that one you can do the same thing and get a working Python installation:

python-3.5.0-webinstall.exe /layout <folder>

This downloads the Release MSIs files (not Debug or PDB only). Then you'll need to filter the files that have _d.msi and _pdb.msi suffix, which is trivial with Batch now and you end up with this structure:

core.msi
dev.msi
doc.msi
exe.msi
launcher.msi
lib.msi
path.msi
pip.msi
python-3.6.0-webinstall.exe
tcltk.msi
test.msi
tools.msi

and quite a lot of VS redistributables. Depending on your needs you may want to delete .exe, .msu(redists), _d.msi, _pdb.msi files in your working directory. The rest are Release files and files that extend the interpreter functionality such as launcher(py.exe), path(probably just permanently puts python to PATH), etc.

If you run each of them with this:

msiexec.exe /a <file> targetdir=<folder>

you get a working portable Python installation. Note that such thing is not officially supported.

It is possible to create your own MSI installer from the source distributions at https://www.python.org/downloads/source/. This is what I did to install Python 3.6.12 on my Windows machine.

In each source distribution, the files at PCBuild/readme.txt and Tools/msi/README.txt provide guidance for how to build your own Python installer. If you have not built Python from source before on Windows, this may be a challenge to set up.

If you do not want to build the installer yourself, you can download unofficial installers from https://github.com/adang1345/PythonWindows. These are the installers that I built recently as part of a personal project.

You should download the Windows X86-64 MSI Installer (2.7.7) because your system is 64-bit. x64 uses a link register rather than pushing return addresses on the stack, so its a tad bit safer than its x86 counterparts. In addition, the x64 code will likely run a little faster.

For completeness, you could run both x86 and x64 on a 64-bit Windows machine. But the reverse does not hold true.

You might be able to install Python 3.4, too. But you have to be careful because Python broke some prominent features between 2.x and 3.x. If you get mysterious errors when using Python 3.x, you should try using Python 2.x (or run Python's 2to3 conversion program on the 2.x *.py source files). Google is very specific about the Python versions, and 3.x is not allowed. Its likely due to the Python 3 redesign and improvements that were not backwards-compatible.

Pyinstaller does not intergrate such a tool.

You could get a third party installer (some suggested here How to create a robust, minimal installer for Windows?) and add your output exe to it and install that way, if you choose the right tool you will be able to add to desktop (plus a lot of other actions such as adding to path ect).

Or you could use cx_Freeze which has it built in. When running the setup script just add the bdist_msi flag.

It can add to shortcut desktop but is fairly limited in other ways (or you may need to perform some hack).

To add to desktop with cx_Freeze see Use cx-freeze to create an msi that adds a shortcut to the desktop.

simple use. No transforms provided, and code is non-blocking:

import os
os.system('msiexec /i %s /qn' % msi_location)

With transforms, and code is non-blocking:

import os
os.system('msiexec /i %s TRANSFORMS=%s /qn' % (msi_location, transforms_location)

With transforms, and code is blocking - so you know when it has completed:

import subprocess
subprocess.call('msiexec /i %s TRANSFORMS=%s /qn' % (msi_location, transforms_location), shell=True)

For more info on TRANSFORMS: https://msdn.microsoft.com/en-us/library/aa367447%28v=vs.85%29.aspx