[issue25166] Windows AllUsers installation places uninstaller in user profile

Change by Eryk Sun : -- versions: +Python 3.10, Python 3.9 -Python 3.6, Python 3.7 ___ Python tracker ___ ___ Python-bugs-list

[issue25166] Windows AllUsers installation places uninstaller in user profile

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

[issue25166] Windows AllUsers installation places uninstaller in user profile

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,

[issue25166] Windows AllUsers installation places uninstaller in user profile

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

[issue25166] Windows AllUsers installation places uninstaller in user profile

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

[issue25166] Windows AllUsers installation places uninstaller in user profile

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

[issue25166] Windows AllUsers installation places uninstaller in user profile

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.

[issue25166] Windows AllUsers installation places uninstaller in user profile

Steve Dower added the comment: WiX issue is http://wixtoolset.org/issues/4914/ -- ___ Python tracker ___ ___

[issue25166] Windows AllUsers installation places uninstaller in user profile

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

[issue25166] Windows AllUsers installation places uninstaller in user profile

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;> <>

[issue25166] Windows AllUsers installation places uninstaller in user profile

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

[issue25166] Windows AllUsers installation places uninstaller in user profile

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.