Jump to content

Recommended Posts

Posted

I am trying to install Python 3.7 to Windows 10 via startup script.

 

I am running this:

 

python-3.7.0-amd64.exe /quiet InstallAllUsers=1 AssociateFiles=1 PrependPath=1 Include_launcher=1 InstallLauncherAllUsers=1

 

it installs and seems to work but no entries for python or python launcher are in programs and features....

there also seems to be no corresponding values in reg uninstall keys

 

If I run the file manually when logged in it all appears OK

Other installs fine, always have been.

 

 

Has anyone successfully deployed Python using startup? there is no MSI after about v3.

 

Thanks

Posted (edited)
it installs and seems to work but no entries for python or python launcher are in programs and features....

there also seems to be no corresponding values in reg uninstall keys

That sound a bit like this bug...

 

https://bugs.python.org/issue32791

 

I'm using the installation property InstallAllUsers=1 but find that Python is still placing it's Add/Remove programs entry in user context.

 

Applications usually write system level installs to HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall or HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall

 

What I'm encountering with Python is that it's writing them to HKCU:\Software\Microsoft\Windows\CurrentVersion\Uninstall

 

This is causing some difficulty as it prevents software such as SCCM, KACE, Altiris from being able to detect the main program install or a user with elevated privileges from being able to remove it.

 

Deploying the software will end up with the entry located the System Account's registry within HKU\S-5-1-18\Software\Microsoft\WIndows\CurrentVersion\Uninstall\{Prodct GUID}

 

Have you tried running the installer with the /log parameter to find out what's happening?

 

Edit. Did you also pre-download all of the installer files with the /layout switch to avoid it trying to access the Internet during installation?

Edited by Arthur
Posted

Several other annoying installer bugs I have experienced include...

 

https://bugs.python.org/issue25166

 

A system-wide installation on Windows (using InstallAllUsers=1) still places the uninstall executable into the profile (%LOCALAPPDATA%) of the installing user. If that user profile is deleted, the (system-wide) installation cannot be removed anymore.

 

https://bugs.python.org/issue29033

 

When I try to use the Python 3.5 and later installer for windows to make an automated unattended install via SCCM, it seems to work, but some time later it rolls back leaving only a few files installed (seems to be pip.exe and friends).

 

https://bugs.python.org/issue34562

 

I tried to unsuccessfully install 3.7.0 and 3.6.5. The error I received was 0x80072f7d unspecified error.

 

I wish they would switch back to the old installer, but that's never going to happen. :(

 

https://bugs.python.org/issue25166#msg279454

 

I won't be changing the official releases to be a single MSI again - the experience is too hostile towards regular users.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...