[issue30725] Windows installer for 2.7.13 doesn't install pip when installing to C:\Program Files

Change by Zachary Ware : -- resolution: -> out of date stage: -> resolved status: open -> closed ___ Python tracker ___ ___

[issue30725] Windows installer for 2.7.13 doesn't install pip when installing to C:\Program Files

Kevin Keating added the comment: Running the msi from an elevated command prompt worked. Thanks! -- ___ Python tracker ___

[issue30725] Windows installer for 2.7.13 doesn't install pip when installing to C:\Program Files

Eryk Sun added the comment: You can still create and use virtual environments (virtualenv) without requiring administrator access. -- ___ Python tracker

[issue30725] Windows installer for 2.7.13 doesn't install pip when installing to C:\Program Files

Paul Moore added the comment: Note that even if you do get this working, you'll still need to run pip from an elevated prompt every time you want to use it to install new packages (or use --user). -- ___ Python tracker

[issue30725] Windows installer for 2.7.13 doesn't install pip when installing to C:\Program Files

Eryk Sun added the comment: Issue 27888 switched to using WiX CAQuietExec task to hide the console, but it also changed the action flags to no longer include msidbCustomActionTypeNoImpersonate (2048). Without this flag, the installer impersonates the user for these custom actions: UpdatePip,

[issue30725] Windows installer for 2.7.13 doesn't install pip when installing to C:\Program Files

Steve Dower added the comment: The relevant lines are just above the ones you posted, but I can't view the attachment from my phone so I'll have to look later. Seems like the custom action is running as the original user and not admin. This should just be a flag on the command, though since

[issue30725] Windows installer for 2.7.13 doesn't install pip when installing to C:\Program Files

Kevin Keating added the comment: Yeah, I only run into this problem if I install Python 2.7.13 into C:\Program Files\Python27. If I install Python 2.7.12 or 3.6.1 to the same location, then everything works fine. I can successfully install Python 2.7.13 to C:\Python27, C:\Programs\Python27,

[issue30725] Windows installer for 2.7.13 doesn't install pip when installing to C:\Program Files

Paul Moore added the comment: Presumably you overrode the default location of C:\Python27 in favour of C:\Program Files? I'm not sure we've ever supported installing Python 2.7 in "Program Files", precisely because of the security constraints on that directory (plus the fact that a long time

[issue30725] Windows installer for 2.7.13 doesn't install pip when installing to C:\Program Files

Kevin Keating added the comment: Here's the log file. I'm assuming that the relevant bit starts at around line 18663: CAQuietExec: Collecting setuptools CAQuietExec: Collecting pip CAQuietExec: Installing collected packages: setuptools, pip CAQuietExec: Exception: CAQuietExec: Traceback

[issue30725] Windows installer for 2.7.13 doesn't install pip when installing to C:\Program Files

Steve Dower added the comment: I wonder if the custom action to run _ensurepip isn't running as admin... that would be the only thing I can think of. Can you try running the installer with: msiexec /l*vx log.txt /i path_to.msi Then attach the generated log.txt file? We might be able to see

[issue30725] Windows installer for 2.7.13 doesn't install pip when installing to C:\Program Files

New submission from Kevin Keating: If I use the Python 64-bit 2.7.13 Windows installer and install to C:\Program Files\Python27, then the Scripts folder doesn't get created and pip doesn't get installed. If I uninstall Python and reinstall it to C:\Python27, C:\Programs\Python27, or "C:\Path