[issue35203] Windows Installer Ignores Launcher Installer Options Where The Python Launcher Is Already Present

Steve Dower added the comment: Timothy - are you able to share your install logs? Look for all log files starting with "Python" in your %TEMP% directory. We definitely do not (and without an installer rewrite, cannot) support simultaneous per-user and per-machine installs of the same

[issue35203] Windows Installer Ignores Launcher Installer Options Where The Python Launcher Is Already Present

Timothy Fleenor added the comment: I am also having this same problem with python 3.9.5.. I am currently in windows 11 preview but it has also occurred for me in the windows 20h2 with no updates and caused a lot of issues running python for me including saying the pip command was not

[issue35203] Windows Installer Ignores Launcher Installer Options Where The Python Launcher Is Already Present

Dexter added the comment: Sadly due to the secure environment I'm unable to attach the log. The exact error is: "You must be an Administrator to remove this application. To remove this application you can log on as an Administrator, or contact your technical support group for assistance."

[issue35203] Windows Installer Ignores Launcher Installer Options Where The Python Launcher Is Already Present

Steve Dower added the comment: Does it actually try to upgrade the launcher? This is a case that was deliberately designed and tested before release, though it's possible that there's some mix of versions that is new. The box is checked to indicate that the launcher will be installed at the

[issue35203] Windows Installer Ignores Launcher Installer Options Where The Python Launcher Is Already Present

Change by Max Bowsher : -- nosy: +Max Bowsher ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue35203] Windows Installer Ignores Launcher Installer Options Where The Python Launcher Is Already Present

New submission from Dexter : When installing Python 3.7 from the Windows Installer in a restricted environment the installer appears to ignore the InstallLauncherAllUsers=0 and Include_launcher=0 flags if the launcher is already present from a previous install. I am on a machine where the