You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I searched open reports and couldn't find a duplicate
What happened?
The installer/uninstaller for Miniconda3-py39_4.12.0-Windows-x86_64 seems to be broken. When uninstalling Miniconda which has been installed using this package (through Windows 10/11's "Programs and Features") it fails to completely remove the command line integration.
It throws an installation error (see screenshot below) and then leaves an orphaned reference in the Autorun registry key which breaks the command line on the system.
The Registry key that is left broken is: 'Computer\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Command Processor\AutoRun' with the value 'if exist & if exist'. One has to manually delete this key to restore command line interface functionality or everytime the command shell runs there is the error '& was unexpected at this time'.
Conda Info
active environment : base
active env location : C:\Users\angus\miniconda3
shell level : 1
user config file : C:\Users\angus\.condarc
populated config files :
conda version : 4.12.0
conda-build version : not installed
python version : 3.9.12.final.0
virtual packages : __win=0=0
__archspec=1=x86_64
base environment : C:\Users\angus\miniconda3 (writable)
conda av data dir : C:\Users\angus\miniconda3\etc\conda
conda av metadata url : None
channel URLs : https://repo.anaconda.com/pkgs/main/win-64
https://repo.anaconda.com/pkgs/main/noarch
https://repo.anaconda.com/pkgs/r/win-64
https://repo.anaconda.com/pkgs/r/noarch
https://repo.anaconda.com/pkgs/msys2/win-64
https://repo.anaconda.com/pkgs/msys2/noarch
package cache : C:\Users\angus\miniconda3\pkgs
C:\Users\angus\.conda\pkgs
C:\Users\angus\AppData\Local\conda\conda\pkgs
envs directories : C:\Users\angus\miniconda3\envs
C:\Users\angus\.conda\envs
C:\Users\angus\AppData\Local\conda\conda\envs
platform : win-64
user-agent : conda/4.12.0 requests/2.27.1 CPython/3.9.12 Windows/10 Windows/10.0.19044
administrator : False
netrc file : None
offline mode : False
The error only appears to be happening with Conda when installed using Miniconda3-py39_4.12.0-Windows-x86_64 (Python 3.9 version). I've tested it with Miniconda3-py38_4.12.0-Windows-x86_64 (Python 3.8) and there is no installation error.
Furthermore, whilst reproducing the error to get the screenshot for this issue, I still received the installation error shown in the screenshot however the AutoRun registry key was instead left as "if exist" which doesn't appear to break the command line anymore. I'm not sure under what conditions the registry keys are left in these different states, maybe it has something to do with me installing and uninstalling Python 3.8 and 3.9 versions of Miniconda multiple times to gather information for this issue?
In any case, this can cause serious system instability if left unchecked due to it breaking the command line interface on the whole system and corrupting the registry. I frequently install miniconda on clients' computers as a convenient way of running python scripts and without knowing the details of this error and that I have to do some extra registry cleanup after uninstalling, it could be disastrous and leave their systems inoperable.
There is a similar issue reported in Issue conda/conda#10110 but it is for the chocolately installation of a different version.
This is my first issue report on GitHub (of anything, not just Conda) so please let me know if you need more info.
The text was updated successfully, but these errors were encountered:
Thanks a lot for your detailed bug report. This is in fact a known issue that we currently have a fix for. Check out this pull request in the conda/constructor for more information:
Just FYI, conda constructor is the project that is actually responsible for creating these installers.
This will take a little bit of time before the new versions of these installers are uploaded to https://docs.conda.io/en/latest/miniconda.html, but thanks to your issue (and others' as well) we now have a greater appreciation for the urgency of this problem and will be working as quickly as possible to remediate it.
In the meantime, I will be closing this issue as this is not directly related to this specific part of the conda project. If you experience further issues with installer/uninstaller, please create a new issue in conda/constructor.
Checklist
What happened?
The installer/uninstaller for Miniconda3-py39_4.12.0-Windows-x86_64 seems to be broken. When uninstalling Miniconda which has been installed using this package (through Windows 10/11's "Programs and Features") it fails to completely remove the command line integration.
It throws an installation error (see screenshot below) and then leaves an orphaned reference in the Autorun registry key which breaks the command line on the system.
The Registry key that is left broken is: 'Computer\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Command Processor\AutoRun' with the value 'if exist & if exist'. One has to manually delete this key to restore command line interface functionality or everytime the command shell runs there is the error '& was unexpected at this time'.
Conda Info
Conda Config
No response
Conda list
Additional Context
The error only appears to be happening with Conda when installed using Miniconda3-py39_4.12.0-Windows-x86_64 (Python 3.9 version). I've tested it with Miniconda3-py38_4.12.0-Windows-x86_64 (Python 3.8) and there is no installation error.
Furthermore, whilst reproducing the error to get the screenshot for this issue, I still received the installation error shown in the screenshot however the AutoRun registry key was instead left as "if exist" which doesn't appear to break the command line anymore. I'm not sure under what conditions the registry keys are left in these different states, maybe it has something to do with me installing and uninstalling Python 3.8 and 3.9 versions of Miniconda multiple times to gather information for this issue?
In any case, this can cause serious system instability if left unchecked due to it breaking the command line interface on the whole system and corrupting the registry. I frequently install miniconda on clients' computers as a convenient way of running python scripts and without knowing the details of this error and that I have to do some extra registry cleanup after uninstalling, it could be disastrous and leave their systems inoperable.
There is a similar issue reported in Issue conda/conda#10110 but it is for the chocolately installation of a different version.
This is my first issue report on GitHub (of anything, not just Conda) so please let me know if you need more info.
The text was updated successfully, but these errors were encountered: