6/16/2023 0 Comments Power uninstallerOn the same machine above, I've also tried this: PS C:\WINDOWS\system32> choco uninstall python At least some of the machines may have had python installed using chocolaty from the public repository. I think Chocolatey v0.10.1 may have contributed to the current situation. At this point Uninstall-Package on the "Python Launcher" succeeded with a warning that a reboot was required. Once the other parts of Python 3 were repaired, there was one MSI package called "Python Launcher", and the Python 2.7 MSI package remaining reported by Get-Package, but nothing in the GUI. I'm surprised there is no Repair-Package command to go with Get-Package. I've had some success in cleaning up the majority of this by using the control panel GUI to first repair and then uninstall the Python 3 installations. ![]() ![]() Why are these packages still present after Uninstall-Package? Is there a best-practice way to do this? Is there a best-practice way to script Python's re-installation so this won't happen again? PS C:\WINDOWS\system32> Get-Package "*python*" Which, when run from an admin console, seems to work nicely, but on further investigation leaves some packages remaining. ![]() I'm currently trying to do this using the Package Management cmdlets in PowerShell 3.187.įor the cleanup script, I started with PowerShell's package commands: Get-Package "*python*" | Uninstall-Package I want to write a script which cleans up all existing versions of Python on a machine, and a separate script to re-install both versions 2.7 and 3.5 in standardized locations.
0 Comments
Leave a Reply. |