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: Unable to install Python 3.4.2 amd64 on Windows 8.1
Type: behavior Stage:
Components: Installation, Windows Versions: Python 3.4
Status: closed Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: brp-log, eryksun, georg.brandl, loewis, steve.dower, tim.golden, zach.ware
Priority: normal Keywords:

Created on 2014-10-15 19:45 by brp-log, last changed 2022-04-11 14:58 by admin. This issue is now closed.

File name Uploaded Description Edit
log.txt brp-log, 2014-10-18 19:52
Messages (13)
msg229494 - (view) Author: Pierre Boulanger (brp-log) Date: 2014-10-15 19:45
I try to install python 3.4.2-amd 64 but i have an error: a program used for the installation could not be run.

befor i have python 3.4.1 and it work perfectly.
msg229495 - (view) Author: Georg Brandl (georg.brandl) * (Python committer) Date: 2014-10-15 19:50
Can you describe a bit more in detail at which step of the installer the error occurs?
msg229496 - (view) Author: Steve Dower (steve.dower) * (Python committer) Date: 2014-10-15 20:15
If you deselect pip from the feature list, do you have any more success?
msg229498 - (view) Author: Pierre Boulanger (brp-log) Date: 2014-10-15 20:42
the error occurs when the installer create shortcuts after removed files of old python version.
msg229500 - (view) Author: Steve Dower (steve.dower) * (Python committer) Date: 2014-10-15 20:49
Unless Martin knows what could be going wrong, I don't think that's too helpful.

Can you run the following command from an elevated command prompt and post the log it creates:

msiexec /l*vx log.txt /i (path to Python.msi)
msg229633 - (view) Author: Pierre Boulanger (brp-log) Date: 2014-10-18 06:46
the result of log is:
=== Verbose logging started: 18-10-14  08:42:21  Build type: SHIP UNICODE 5.00.9600.00  Calling process: C:\WINDOWS\system32\msiexec.exe ===
MSI (c) (C4:34) [08:42:21:518]: Font created.  Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg

MSI (c) (C4:34) [08:42:21:518]: Font created.  Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg

MSI (c) (C4:24) [08:42:21:550]: Resetting cached policy values
MSI (c) (C4:24) [08:42:21:565]: Machine policy value 'Debug' is 0
MSI (c) (C4:24) [08:42:21:565]: ******* RunEngine:
           ******* Product: C:\Users\pierre\Doocuments\python-3.4.2.amd64.msi
           ******* Action: 
           ******* CommandLine: **********
MSI (c) (C4:24) [08:42:21:565]: Note: 1: 2203 2: C:\Users\pierre\Doocuments\python-3.4.2.amd64.msi 3: -2147287037 
MSI (c) (C4:24) [08:42:21:565]: MainEngineThread is returning 3
=== Verbose logging stopped: 18-10-14  08:42:21 ===
msg229642 - (view) Author: Steve Dower (steve.dower) * (Python committer) Date: 2014-10-18 13:55
Hmm, I'm used to seeing far more detail in verbose logs than that (normally they'd be a few hundred KB).

I'm sorry, I don't know how to diagnose this issue. Have you tried clearing your internet cache and downloading it again? Maybe try the 32-bit version (just to rule out some system configuration issues).
msg229643 - (view) Author: Martin v. Löwis (loewis) * (Python committer) Date: 2014-10-18 14:09
2203 is "Cannot open database file. System error [3].", with -2147287037 being 0x80030003, which in turn is  STG_E_PATHNOTFOUND. Could it be that C:\Users\pierre\Doocuments\python-3.4.2.amd64.msi is on a SUBSTed drive? Installer does not support installing from that location.
msg229646 - (view) Author: Eryk Sun (eryksun) * (Python triager) Date: 2014-10-18 17:24
> MSI (c) (C4:24) [08:42:21:565]: Note: 1: 2203 2: 
> C:\Users\pierre\Doocuments\python-3.4.2.amd64.msi 3: 
> -2147287037 

"Doocuments" is probably a typo. Try again using "Documents".
msg229657 - (view) Author: Georg Brandl (georg.brandl) * (Python committer) Date: 2014-10-18 19:45
Removed the message containing the log. It is making it very clumsy to view this issue. Please resubmit as a file attachment.
msg229658 - (view) Author: Pierre Boulanger (brp-log) Date: 2014-10-18 19:52
Here is the right log...
msg229692 - (view) Author: Martin v. Löwis (loewis) * (Python committer) Date: 2014-10-19 19:22
The problem is this:

Error 1721. 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. Action: RemovePip, location: C:\Python34\python.exe, command: -B -m ensurepip._uninstall

It tries to uninstall 3.4.1 for the upgrade, including an uninstallation of pip. Uninstallation fails, so it cannot upgrade.

Can you report whether any terminal windows show up, and what they say? Also, can you try to run "python3 -B -m ensurepip._uninstall' manually in a terminal window and report whether it works?

As a work-around, you can uninstall Python 3.4.1 first, then install 3.4.2.
msg229747 - (view) Author: Pierre Boulanger (brp-log) Date: 2014-10-21 04:34
your soluce works.
great tanks !
Date User Action Args
2022-04-11 14:58:09adminsetgithub: 66838
2014-10-21 04:34:46brp-logsetstatus: open -> closed

messages: + msg229747
2014-10-19 19:22:51loewissetmessages: + msg229692
2014-10-18 19:52:04brp-logsetfiles: + log.txt

messages: + msg229658
2014-10-18 19:46:28georg.brandlsetmessages: - msg229655
2014-10-18 19:45:37georg.brandlsetmessages: - msg229654
2014-10-18 19:45:33georg.brandlsetmessages: + msg229657
2014-10-18 19:38:22brp-logsetmessages: + msg229655
2014-10-18 19:32:30brp-logsetmessages: + msg229654
2014-10-18 17:24:01eryksunsetnosy: + eryksun
messages: + msg229646
2014-10-18 14:09:06loewissetmessages: + msg229643
2014-10-18 13:55:03steve.dowersetmessages: + msg229642
2014-10-18 06:46:52brp-logsetmessages: + msg229633
2014-10-15 20:49:08steve.dowersetmessages: + msg229500
2014-10-15 20:42:02brp-logsetmessages: + msg229498
2014-10-15 20:15:09steve.dowersetmessages: + msg229496
2014-10-15 19:50:01georg.brandlsetnosy: + georg.brandl
messages: + msg229495
2014-10-15 19:46:03ned.deilysetnosy: + loewis, tim.golden, steve.dower, zach.ware
components: + Windows
2014-10-15 19:45:08brp-logcreate