From an old post on python-dev:
2010/08/04 Paul Kippes:
> For the most part, the information at
> http://www.python.org/download/releases/2.4/msi/ assisted me with
> automating a 2.7 installation on Windows XP.  The following initial
> attempt, however, failed to provide a working python installation.
> (Messages are either "The system cannot execute the specified
> program." or "This application has failed to start because the
> application configuration is incorrect.  Reinstalling the application
> may fix this problem.")
>
> msiexec /qb /i python-2.7.msi ALLUSERS=1 ADDLOCAL=Extensions
>
> After looking through Tools/msi/msi.py, I was able to automate a
> minimal and working Python installation with this adjustment:
>
> ADDLOCAL=Extensions,SharedCRT
>
> Since the only reference I could find to the above web page was when
> the MSI installer was first announced
> (http://www.python.org/download/releases/2.4.2), the installer options
> may have changed since then.
>
> Would you check if my change is what you intended and perhaps migrate
> the web page of the 2.4 release note to 2.7?
>
> Thanks!

Can we close this as "out of date" as we're already working on msi for 3.5?

If we wanted to migrate the instructions to 2.7/3.5 as suggested then there's some updating to do, but if there's no plan to update them then I agree, there's nothing to do here.

FWIW, the 3.5 installer will accept the same command line options as previous versions, even as the internals change.

Nothing from the OP so to close or not to close, that is the question?