[issue25144] 3.5 Win install fails with "TARGETDIR"

Change by Felipe : -- nosy: -fov ___ Python tracker ___ ___ Python-bugs-list

[issue25144] 3.5 Win install fails with "TARGETDIR"

Steve Dower added the comment: > Got the same issue with the 3.6 installer You've got a different issue, but I can't tell what it is without all of the logs. Can you look in your %TEMP% directory for the file you attached, and then also include those with the same

[issue25144] 3.5 Win install fails with "TARGETDIR"

Per Fryking added the comment: Got the same issue with the 3.6 installer from python.org The thing is that I can't elevate the priviliges to be administrator. So I'm stuck. Uploading the log. Running windows 7 -- nosy: +Per Fryking Added file:

[issue25144] 3.5 Win install fails with "TARGETDIR"

Yu Zhigang added the comment: Hi, if everything goes well you shall see the log in the attachment or somewhere. I'm uploading it. -- Added file: http://bugs.python.org/file47084/python install failure.zip ___ Python tracker

[issue25144] 3.5 Win install fails with "TARGETDIR"

Steve Dower added the comment: Yu Zhigang - can you post your install logs from the failed install? You'll notice in my last message I said that I added some extra logging. However, it sounds like you have a certain system option set that essentially breaks paths passed between non-admin and

[issue25144] 3.5 Win install fails with "TARGETDIR"

Yu Zhigang added the comment: It's quite an issue... This is 2017 and it's still there. Anyway, I encountered the same problem by running the installer in Win7, and it was fixed by running it again in administrative mode. -- nosy: +Yu Zhigang ___

[issue25144] 3.5 Win install fails with "TARGETDIR"

Steve Dower added the comment: I believe this change will fix it, or at least provide some more diagnostic info if it fails again. There doesn't seem to be any other way to trigger the install process without setting a target directory. -- resolution: -> fixed stage: -> resolved

[issue25144] 3.5 Win install fails with "TARGETDIR"

Roundup Robot added the comment: New changeset 16d652760a06 by Steve Dower in branch '3.5': Issue #25144: Ensures TargetDir is set before continuing with custom install. https://hg.python.org/cpython/rev/16d652760a06 New changeset 024f3312ccee by Steve Dower in branch 'default': Issue #25144:

[issue25144] 3.5 Win install fails with "TARGETDIR"

Jagannath Basu added the comment: I ran the python-3.5.2.exe file as administrator (right click > Run as Admin) and then followed the custom installation to set up target directory. It got installed without further complaints. -- nosy: +basuj81 ___

[issue25144] 3.5 Win install fails with "TARGETDIR"

Futur Fusionneur added the comment: For me the custom installer worked by combining the two solutions above: 1. open an elevated command prompt 2. run the installer by specifying the TargetDir -- nosy: +Futur Fusionneur ___ Python tracker

[issue25144] 3.5 Win install fails with "TARGETDIR"

Claude Chouinard added the comment: To solve the problem with the variable TARGETDIR not being initialized, I called the installation program from the command shell and added the target dir option. c:\Users\\Downloads>python-3.5.1-amd64.exe TargetDir=c:\Python35 I also us the custom

[issue25144] 3.5 Win install fails with "TARGETDIR"

Ivan Radic added the comment: I got this with 3.5.1 installer on Windows 7. I solved it by running installer with elevated privileges. Installer for 2.7.11 was not affected. -- nosy: +ivan.radic ___ Python tracker

[issue25144] 3.5 Win install fails with "TARGETDIR"

Steve Dower added the comment: Good to hear there's a workaround. I seem to recall an issue in the past with some security policies that disallow passing parameters to installers. This may be the cause here. When I get a chance to sit at a computer I'll see if I can track that down.

[issue25144] 3.5 Win install fails with "TARGETDIR"

Ben added the comment: Still a problem with python-2.7.10.amd64.msi. A bit surprising that this has not been addressed since 2015.05.23... -- nosy: +cbj4074 ___ Python tracker

[issue25144] 3.5 Win install fails with "TARGETDIR"

Steve Dower added the comment: That's a good idea. Can you grab the log files from %UserProfile%\AppData\Local\Temp (sort by date - they'll all be grouped together) and upload to this issue? Like Felipe, you may want to censor some usernames/paths. If you do, please let me know if they

[issue25144] 3.5 Win install fails with "TARGETDIR"

Laura Creighton added the comment: webmaster just got mail from another person hit with this on Windows 10. -- nosy: +lac ___ Python tracker ___

[issue25144] 3.5 Win install fails with "TARGETDIR"

Wade Hedrick added the comment: I had the same problem when trying to install 3.5 with Windows 10. I got the same results as Felipe has listed in the post from 9/16. -- nosy: +WadeH type: behavior -> ___ Python tracker

[issue25144] 3.5 Win install fails with "TARGETDIR"

Steve Dower added the comment: Well, I made this happen once, but not a second time. That's better than most setup issues I get to deal with :) Still working on it - will post when I figure it out. -- assignee: -> steve.dower ___ Python tracker

[issue25144] 3.5 Win install fails with "TARGETDIR"

Changes by Felipe : Added file: http://bugs.python.org/file40492/Python 3.5.0 (32-bit)_20150916132422.log ___ Python tracker ___

[issue25144] 3.5 Win install fails with "TARGETDIR"

Changes by Terry J. Reedy : -- nosy: +paul.moore, steve.dower, tim.golden, zach.ware ___ Python tracker ___

[issue25144] 3.5 Win install fails with "TARGETDIR"

New submission from Felipe: The 3.5 Windows installer fails with "The TARGETDIR variable must be provided when invoking this installer" Here are the steps I followed: 1. Initial screen: - uncheck the add path and all users options - select "Customize installation" 2. Optional