Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

3.5 Win install fails with "TARGETDIR" #69331

Closed
felipeochoa mannequin opened this issue Sep 16, 2015 · 24 comments
Closed

3.5 Win install fails with "TARGETDIR" #69331

felipeochoa mannequin opened this issue Sep 16, 2015 · 24 comments
Assignees
@zooba
Labels
topic-installation

Comments

@felipeochoa
Copy link
Mannequin

felipeochoa mannequin commented Sep 16, 2015

BPO 25144
Nosy @pfmoore, @tjguk, @peterjc, @zware, @zooba
Files
  • Python 3.5.0 (32-bit)_20150916132422.log
  • python install failure.zip: The log of Python installer
  • Python 3.6.3 (32-bit)_20171120135800.log: TARGETDIR not set error
    		•

    Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

    Show more details

    GitHub fields:

    assignee = 'https://github.com/zooba'
closed_at = <Date 2016-09-09.23:40:57.652>
created_at = <Date 2015-09-16.17:35:32.120>
labels = ['expert-installation']
title = '3.5 Win install fails with "TARGETDIR"'
updated_at = <Date 2017-11-21.04:14:42.799>
user = 'https://github.com/felipeochoa'

    bugs.python.org fields:

    activity = <Date 2017-11-21.04:14:42.799>
actor = 'fov'
assignee = 'steve.dower'
closed = True
closed_date = <Date 2016-09-09.23:40:57.652>
closer = 'steve.dower'
components = ['Installation']
creation = <Date 2015-09-16.17:35:32.120>
creator = 'fov'
dependencies = []
files = ['40492', '47084', '47278']
hgrepos = []
issue_num = 25144
keywords = []
message_count = 19.0
messages = ['250857', '251375', '253734', '253738', '253747', '253751', '255817', '256226', '256227', '261144', '270418', '273115', '275496', '275497', '300290', '300299', '300328', '306538', '306626']
nosy_count = 15.0
nosy_names = ['paul.moore', 'tim.golden', 'maubp', 'python-dev', 'zach.ware', 'steve.dower', 'ivan.radic', 'lac', 'WadeH', 'cbj4074', 'Claude', 'OBSOLETE', 'basuj81', 'Yu Zhigang', 'Per Fryking']
pr_nums = []
priority = 'normal'
resolution = 'fixed'
stage = 'resolved'
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue25144'
versions = ['Python 3.5', 'Python 3.6']
    @felipeochoa
    Copy link
    Mannequin Author

    felipeochoa mannequin commented Sep 16, 2015

    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 features:

      • Check all boxes except "all users"

    3. Advanced options

      • Uncheck all
      • Pick a different path to install to (clean folder)

    4. A message box pops up saying "The TARGETDIR variable must be provided when invoking this installer" -- I hit OK.

    5. Final screen showing 0x8007063 - Fatal error during installation

    I've saved the log file and can upload if helpful, but will have to remove personal info first

    @felipeochoa felipeochoa mannequin added type-bug An unexpected behavior, bug, or error topic-installation labels Sep 16, 2015
    @zooba
    Copy link
    Member

    zooba commented Sep 23, 2015

    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.

    @zooba zooba self-assigned this Sep 23, 2015
    @peterjc
    Copy link
    Mannequin

    peterjc mannequin commented Oct 30, 2015

    We just hit this bug with "The TARGETDIR variable must be provided when invoking this installer" and an OK button (only) on a colleagues' machine.

    We first tried https://www.python.org/ftp/python/3.5.0/python-3.5.0-webinstall.exe (default options) and then https://www.python.org/ftp/python/3.5.0/python-3.5.0.exe (default options plus checked add to PATH) with the same problem.

    My colleague recalls having previously installed and then removed Python 3.5 on this machine (possibly a pre-release or beta version). Could anything in the registry or on left disk trigger this?

    @zooba
    Copy link
    Member

    zooba commented Oct 30, 2015

    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 contain anything other than letters or digits (spaces and punctuation may be very important here).

    @lac
    Copy link
    Mannequin

    lac mannequin commented Oct 30, 2015

    webmaster just got mail from another person hit with this on Windows 10.

    @WadeH
    Copy link
    Mannequin

    WadeH mannequin commented Oct 30, 2015

    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.

    @WadeH WadeH mannequin removed the type-bug An unexpected behavior, bug, or error label Oct 30, 2015
    @cbj4074
    Copy link
    Mannequin

    cbj4074 mannequin commented Dec 3, 2015

    Still a problem with python-2.7.10.amd64.msi. A bit surprising that this has not been addressed since 2015.05.23...

    @ivanradic
    Copy link
    Mannequin

    ivanradic mannequin commented Dec 11, 2015

    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.

    @zooba
    Copy link
    Member

    zooba commented Dec 11, 2015

    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.

    @Claude
    Copy link
    Mannequin

    Claude mannequin commented Mar 3, 2016

    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\xxxx\Downloads>python-3.5.1-amd64.exe TargetDir=c:\Python35

    I also us the custom installation option (using the Install Now might not work). You should see that the target dir is properly setup to what you have specified.

    Now it installed without a problem.

    @OBSOLETE
    Copy link
    Mannequin

    OBSOLETE mannequin commented Jul 14, 2016

    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

    @basuj81
    Copy link
    Mannequin

    basuj81 mannequin commented Aug 19, 2016

    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.

    @python-dev
    Copy link
    Mannequin

    python-dev mannequin commented Sep 9, 2016

    New changeset 16d652760a06 by Steve Dower in branch '3.5':
    Issue bpo-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 bpo-25144: Ensures TargetDir is set before continuing with custom install.
    https://hg.python.org/cpython/rev/024f3312ccee

    @zooba
    Copy link
    Member

    zooba commented Sep 9, 2016

    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.

    @zooba zooba closed this as completed Sep 9, 2016
    @YuZhigang
    Copy link
    Mannequin

    YuZhigang mannequin commented Aug 15, 2017

    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.

    @zooba
    Copy link
    Member

    zooba commented Aug 15, 2017

    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 admin processes. There is very little we can do about that, and the fix applied for this issue is not intended to solve it.

    @YuZhigang
    Copy link
    Mannequin

    YuZhigang mannequin commented Aug 16, 2017

    Hi, if everything goes well you shall see the log in the attachment or somewhere. I'm uploading it.

    @PerFryking
    Copy link
    Mannequin

    PerFryking mannequin commented Nov 20, 2017

    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

    @zooba
    Copy link
    Member

    zooba commented Nov 21, 2017

    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 prefix?

    @ezio-melotti ezio-melotti transferred this issue from another repository Apr 10, 2022
    @nemozny
    Copy link

    nemozny commented Jul 18, 2023 •
    edited

    Still doesn't work as of 2023/7/18. Incredible.
    I did run it as admin and also provided the TargetDir argument.
    image

    @zware
    Copy link
    Member

    zware commented Jul 18, 2023

    Please provide logs and details about how you provoked the error, and whether you can do so reliably. Or better, submit pull requests for any bugs you find in Tools/msi while debugging the issue.

    Complaints without data or offered help merely contribute to burnout in the people providing you software for free.

    @VitaliyAT
    Copy link

    3.10.9 the same problem. Showing path that was set. Showing installation. No effects - it installs to the same folder as it was before... I already have it installed in system, but I need to install it in project folder. No luck.

    @zware
    Copy link
    Member

    zware commented Jan 29, 2024

    1. Installers are no longer produced for 3.10; any issue will need to be reproducible with the latest 3.12 installer to have any hope of being changed.
    2. That problem description does not sound to me like the original issue report, or like later off-topic add-ons.
    3. This issue has been closed for over 7 years now; it is not the right place to report current issues. If there is a problem with the latest Python 3.12 installer, please open a new issue with a precise description of the steps you took and what went wrong. Please include as many relevant details as you can, including your Windows version, other Python installations, and ideally the log from the failed installation (check to make sure the log does not include anything you don't want to share publicly).

    @python python locked as resolved and limited conversation to collaborators Jan 29, 2024
    @zooba
    Copy link
    Member

    zooba commented Jan 29, 2024

    I already have it installed in system, but I need to install it in project folder. No luck.

    The installer doesn't support this. You may want to look at our Nuget packages for getting a per-project copy

    Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
    Assignees

    @zooba zooba

    Labels
    topic-installation
    Projects
    None yet
    Milestone
    No milestone
    Development

    No branches or pull requests
    4 participants
    @VitaliyAT @nemozny @zooba @zware