I've been running Anaconda successfully for a few months on my PC (Win 10) using Git Bash and Anaconda3. However, today I tried to update to the latest version of Anaconda (I don't remember which version but it was xxxx.6 or 8 to xxxx.11). The installation failed (stupid me didn't save the error messages) and after that, I keep started getting this error when I type 'conda xxxxx
'.
CommandNotFoundError: No command 'conda conda'.
However, I am still able to use most conda commands if I called the conda.exe file by giving the full path, with one very unfortunate exception, activating environments.
I've also noticed some other weird behavior. If I reboot my PC, conda works fine, even without calling the full path. I can create a new environment, but as soon as I call source activate or activate or conda activate, it breaks and from then on, any reference to 'conda' gives me CommandNotFoundError: No command 'conda conda'.
There is also some weird behavior in anaconda prompt. Everything seems to work fine. I can create and activate environments with no problem but when I first start the prompt, it says The system cannot find the path specified.
I tried
– making sure my PATH was correct
– uninstalling and reinstalling for all users, then for just my user
– using the 'conda init bash' –> I think this just broke it further.
– deleting the registry keys associated with Python – they look good now
I'm at a loss for what to do. I really want to be able to use conda within my git bash again. Any advice is appreciated.
Best Answer
This issue has been addressed in
conda 4.6.14
as per discussions in the linked Anaconda Github issue #8506Short version
Longer shell outputs
In git bash (2.21.0) Win10: