Conda command is not recognized on Windows 10

Conda command is not recognized on Windows 10 (Overflow, 2017)

rw-book-cover

Metadata

Author: Stack Overflow
Full Title: Conda command is not recognized on Windows 10
Category: #articles
Document Tags: conda python
Summary: To use the conda command in cmd.exe or Powershell on Windows 10, you need to add the appropriate path to your system's environment variables. If Anaconda is installed for your user only, add %USERPROFILE%\Anaconda3\condabin to your PATH, or C:\ProgramData\Anaconda3\condabin if it's for all users. After updating the PATH, run conda init in Powershell to ensure the command works in both shells.
URL: https://stackoverflow.com/questions/44597662/conda-command-is-not-recognized-on-windows-10/58211115#58211115

Highlights

Conda command is not recognized on Windows 10 (View Highlight)
Things have been changed after conda 4.6. Programs "Anaconda Prompt" and "Anaconda Powershell" expose the command conda for you automatically. Find them in your startup menu. If you don't wanna use the prompts above and try to make conda available in a standard cmd.exe or a standard Powershell. Read the following content.
Expose conda in Every Shell The purpose of the following content is to make command conda available both in cmd.exe and Powershell on Windows. If you have already checked "Add Anaconda to my PATH environment variable" during Anaconda installation, skip step 1.
1. If Anaconda is installed for the current use only, add %USERPROFILE%\Anaconda3\condabin (I mean condabin, not Scripts) into the environment variable PATH (the user one). If Anaconda is installed for all users on your machine, add C:\ProgramData\Anaconda3\condabin into PATH. How do I set system environment variables on Windows?
2. Open a new Powershell, run the following command once to initialize conda. conda init These steps make sure the conda command is exposed into your cmd.exe and Powershell.
Extended Reading: conda init from Conda 4.6 Caveat: Add the new \path\to\anaconda3\condabin but not \path\to\anaconda3\Scripts into your PATH. This is a big change introduced in conda 4.6. Activation script initialization fron conda 4.6 release log

Conda 4.6 adds extensive initialization support so that more shells than ever before can use the new conda activate command. For more information, read the output from conda init –help We’re especially excited about this new way of working, because removing the need to modify PATH makes Conda much less disruptive to other software on your system. In the old days, \path\to\anaconda3\Scripts is the one to be put into your PATH. It exposes command conda and the default Python from "base" environment at the same time. After conda 4.6, conda related commands are separated into condabin. This makes it possible to expose ONLY command conda without activating the Python from "base" environment. References • Conda 4.6 Release • How do I prevent Conda from activating the base environment? (View Highlight)