This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Title: Automated MSI installation does not work
Type: Stage: resolved
Components: Installation Versions:
Status: closed Resolution: out of date
Dependencies: Superseder:
Assigned To: Nosy List: amaury.forgeotdarc, loewis, steve.dower, zach.ware
Priority: normal Keywords:

Created on 2010-10-01 20:11 by amaury.forgeotdarc, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Messages (4)
msg117831 - (view) Author: Amaury Forgeot d'Arc (amaury.forgeotdarc) * (Python committer) Date: 2010-10-01 20:11
From an old post on python-dev:
2010/08/04 Paul Kippes:
> For the most part, the information at
> 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/, 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
> (, 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!
msg220855 - (view) Author: Mark Lawrence (BreamoreBoy) * Date: 2014-06-17 18:40
Can we close this as "out of date" as we're already working on msi for 3.5?
msg220871 - (view) Author: Steve Dower (steve.dower) * (Python committer) Date: 2014-06-17 20:07
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.
msg241613 - (view) Author: Mark Lawrence (BreamoreBoy) * Date: 2015-04-20 06:28
Nothing from the OP so to close or not to close, that is the question?
Date User Action Args
2022-04-11 14:57:07adminsetgithub: 54218
2019-03-07 16:35:49steve.dowersetstatus: open -> closed
resolution: out of date
stage: resolved
2019-02-24 22:54:55BreamoreBoysetnosy: - BreamoreBoy
2015-04-20 06:28:35BreamoreBoysetmessages: + msg241613
2014-06-17 20:07:52steve.dowersetmessages: + msg220871
2014-06-17 19:42:13ned.deilysetnosy: + zach.ware, steve.dower
2014-06-17 18:40:34BreamoreBoysetnosy: + BreamoreBoy
messages: + msg220855
2010-10-01 20:11:48amaury.forgeotdarccreate