[issue25166] Windows AllUsers installation places uninstaller in user profile

[Eryk Sun]

Change by Eryk Sun :


--
versions: +Python 3.10, Python 3.9 -Python 3.6, Python 3.7

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue25166] Windows AllUsers installation places uninstaller in user profile

[James Russell]

James Russell  added the comment:

I have been reviewing the Install process as we need to start installing / 
patching Python and I have seen the same issue as mentioned below however the 
difference for me is I am running the install on a Silent command line.  

I cannot seem to override "AllUsers" Property using the command line as WiX 
logs the following: "Ignoring attempt to set non-overridable variable: 
'AllUsers'."  If this parameter was made overridable I believe this would then 
allow the Bootstrapper to be listed under all users Uninstall area rather than 
the current user (or in my case it gets written to HKEY_USERS\.Default\... 
(which is really unhelpful) as the installer is being run under the system 
context).

--
nosy: +beefy80
versions: +Python 3.8

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue25166] Windows AllUsers installation places uninstaller in user profile

[Steve Dower]

Steve Dower added the comment:

There are no more binary installers for 3.5, so updating the target versions.

I have some ideas about how to do this and will hopefully get time at the dev 
sprints to try them out.

--
stage:  -> needs patch
type:  -> behavior
versions: +Python 3.6, Python 3.7 -Python 3.5

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue25166] Windows AllUsers installation places uninstaller in user profile

[Steve Dower]

Steve Dower added the comment:

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

As my (volunteer) time allows, I've been working on resolving the issue in WiX 
and we are totally capable of moving to a private build of WiX that includes a 
fix. There is no need to wait for 4.0.

If you would like a single MSI installer, I'd suggest offering some time (or 
paying someone to spend their time) to develop one and distribute it 
independently. The old installer might be a good starting point, but it had a 
range of issues that have been resolved by the new installer. There are also a 
number of features available in the new installer that are not available under 
a single MSI (such as per-user installs, installing/skipping the CRT, and 
disabling MAX_PATH limitations). However, if your installer becomes more 
popular than the official one, it will be strong evidence that people would 
rather have one monolithic installer with less reliable options, and we can 
consider switching back to that format.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue25166] Windows AllUsers installation places uninstaller in user profile

[Zachary Ware]

Zachary Ware added the comment:

Christian, your desire for a single MSI is well known, and repeatedly stating 
that desire is far more likely to raise ire rather than spur change.  No, you 
did not need to include "ceterum censeo".

The installer system that Steve created for us has many features that I and 
many others would be very sad to see disappear again, and which cannot be 
supported by a single MSI distribution.  In particular, selecting which 
components to install and only downloading those components is a wonderful 
feature for anyone with a low-bandwidth or metered internet connection.

If the current installer is unusable to you, feel free to forward-port the old 
3.4 installer system and create your own installers.  Alternately, feel free to 
provide patches to resolve this or any other issues you have with the current 
installer.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue25166] Windows AllUsers installation places uninstaller in user profile

[Christian Ullrich]

Christian Ullrich added the comment:

This bug has been open for over a year and two subsequent releases, and its 
planned resolution depends on a change to WiX. The related WiX bug (see comment 
above) is scheduled to be implemented in WiX 4.0, which has no prospective 
release date. According to , 
only 27 percent of the issues currently planned for this release are resolved.

In my opinion, this is an important bug that cannot wait indefinitely.

Ceterum censeo (yes, there had to be one): This is particularly true when 
considering that a (relatively) simple fix exists that can be done by the 
Python project alone, with no external dependencies. I am referring, of course, 
to dropping the burn bundle entirely and shipping a single MSI package again, 
rather than 43 (!) of them (across x86 and amd64) with an average of ~190 and a 
median of 8 (eight) installed files per package in 3.5.2, counting pip.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue25166] Windows AllUsers installation places uninstaller in user profile

[Steve Dower]

Steve Dower added the comment:

After discussing it on the WiX mailing list, this definitely requires a change 
to WiX.

Currently, as soon as you include any per-user packages in your bundle the 
entire registration is forced to per-user regardless of whether or not they are 
ever installed.

I'm going to propose a change where the bootstrap application can assert that 
the bundle should be registered for the whole machine, so that when we start 
installing we can correct it. Can't be sure it'll be available for 3.5.1, but 
some time in 3.5's lifetime we should get this fixed.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue25166] Windows AllUsers installation places uninstaller in user profile

[Steve Dower]

Steve Dower added the comment:

WiX issue is http://wixtoolset.org/issues/4914/

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue25166] Windows AllUsers installation places uninstaller in user profile

[Steve Dower]

Steve Dower added the comment:

Burn is always started in the per-user scope so that we can do per-user 
installs without elevating, but it looks like we need to manually change this 
once we know it's an all-users install.

--
assignee:  -> steve.dower

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue25166] Windows AllUsers installation places uninstaller in user profile

[eryksun]

eryksun added the comment:

Where is the API documented to change the install scope dynamically? I see 
where it's apparently defined in the burn manifest (extracted from the 
executable) as PerMachine="no":

http://schemas.microsoft.com/wix/2008/Burn;>
  <>
  
http://www.python.org/; 
 DisableModify="button"/>
  

--
nosy: +eryksun

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue25166] Windows AllUsers installation places uninstaller in user profile

[Steve Dower]

Steve Dower added the comment:

Not sure yet :)

There are a lot of undocumented (or not-yet-documented) APIs accessible from 
the bootstrap app and I haven't gone through them yet - see 
https://github.com/wixtoolset/wix3/tree/develop/src/libs, probably dutil.

It may also be something that we have to request or contribute to WiX.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue25166] Windows AllUsers installation places uninstaller in user profile

[Christian Ullrich]

New submission from Christian Ullrich:

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.

Ceterum censeo: This bug would have been avoided by using MSI as the 
distribution package format.

--
components: Installation, Windows
messages: 250962
nosy: Christian.Ullrich, paul.moore, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
status: open
title: Windows AllUsers installation places uninstaller in user profile
versions: Python 3.5

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com