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: 2.7.12 Windows Installer package broken.
Type: behavior Stage: resolved
Components: Installation, Windows Versions: Python 2.7
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: steve.dower Nosy List: busfault, paul.moore, steve.dower, tim.golden, zach.ware
Priority: normal Keywords:

Created on 2016-07-18 15:29 by busfault, last changed 2022-04-11 14:58 by admin. This issue is now closed.

Messages (7)
msg270762 - (view) Author: Tom Middleton (busfault) Date: 2016-07-18 15:29
I was running:
Python 2.7.11 (v2.7.11:6d1b6a68f775, Dec  5 2015, 20:32:19) [MSC v.1500 32 bit (Intel)] on win32
Type "help", "copyright", "credits" or "license" for more information.

I downloaded the msi for Python 2.7.12 and attempted to run it. During the installation it gave me the following error:

"There is a problem with this Windows Installer package. A program required for this install to complete could not be run. Contact your support personnel or package vendor."

Then it "rolls back" the action, which killed my current 2.7.11 installation.  Despite that it states: 

"Python 2.7.12 setup ended prematurely because of an error. Your system has not been modified. To install this program at a later time, please run the installation again."

(pardon any typos in the error messages since I wasn't able to copy the text directly.)

I attempted this twice with the same result.

msg270770 - (view) Author: Zachary Ware (zach.ware) * (Python committer) Date: 2016-07-18 16:03
What happens if you first uninstall 2.7.11 and then install 2.7.12?
msg270773 - (view) Author: Steve Dower (steve.dower) * (Python committer) Date: 2016-07-18 16:37
Or if you first repair 2.7.11 and then install 2.7.12.

This error often happens because your pip installation is corrupt, and then pip fails to uninstall itself which aborts the whole installation. Generally repairing the install before uninstalling resolves it.
msg270775 - (view) Author: Tom Middleton (busfault) Date: 2016-07-18 16:50
I think my pip install was fine? I was using pip pretty regularly with 2.7.11.

I had to do a restore to get 2.7.11 working again, and after an install of 2.7.12 failed again with the same issue.
msg270777 - (view) Author: Tom Middleton (busfault) Date: 2016-07-18 16:59
I tried to uninstall (the C:\python27\ directory seemed to persist after) the install of 2.7.12 failed again same message.
msg270780 - (view) Author: Tom Middleton (busfault) Date: 2016-07-18 17:18
Ok, so really bizarre. I uninstalled 2.7.11, then I was getting the same error with the 2.7.11 msi. So I was thinking that I should go back to the original version I had installed (2.7.10) the installer showed a "repair" option so I did that, then the 2.7.11 install worked.
And then the 2.7.12 installer worked.

I would have to agree with Steve Dower. I think that it had something to do with pip because there were a couple cmd windows that popped up during the install process that showed something to do with pip which didn't the first time I ran the installer.
msg275536 - (view) Author: Steve Dower (steve.dower) * (Python committer) Date: 2016-09-10 01:44
The fix for issue27888 will prevent this from happening again.
Date User Action Args
2022-04-11 14:58:33adminsetgithub: 71751
2016-09-10 01:44:03steve.dowersetstatus: open -> closed
messages: + msg275536

assignee: steve.dower
resolution: fixed
stage: resolved
2016-07-18 17:18:29busfaultsetmessages: + msg270780
2016-07-18 16:59:27busfaultsetmessages: + msg270777
2016-07-18 16:50:46busfaultsetmessages: + msg270775
2016-07-18 16:37:26steve.dowersetmessages: + msg270773
2016-07-18 16:03:53zach.waresetnosy: + paul.moore, tim.golden, zach.ware, steve.dower
messages: + msg270770
components: + Windows
2016-07-18 15:29:05busfaultcreate