How to activate different anaconda environment from powershell

Question

I have two environments in anaconda, namely: root, 2env. When I open anaconda prompt, I can switch from root to 2env by typing: activate 2env. I also have conda in my powershell, but when I open powershell and try to run conda activate 2env it gives the following error:

CommandNotFoundError: 'activate'

Any suggestions on how to fix this?

Activate is not a valid command for `conda`. Conda is mostly used for package management. Try `conda -h` to see valid commands. You need `activate` in your powershell. — it's-yer-boy-chet, Dec 13 '17 at 19:36
I also typed `activate env2` but it doesn't activate the env2 environment. — Hector Barbossa, Dec 13 '17 at 19:55
So the way anaconda works is by default (an option in the install) it doesn't add itself to your `PATH` environmental variable, so the commands will not be available in your shell. Starting the anaconda shell adds the reference to PATH. — it's-yer-boy-chet, Dec 13 '17 at 21:03

Seanny123 · Answer 1 · 2020-08-21T12:36:54.190

65

Although Conda previously did not support PowerShell, this is now resolved in Conda 4.6.

After adding Anaconda3/Scripts/ to your PATH variable, you should be able to initialize Conda for use with powershell with:

conda init powershell

Afterwards, you can use conda normally:

conda activate base

edited Aug 21 '20 at 12:36

answered Feb 21 '19 at 15:53

Seanny123

8,776
13
68
124

1

It cannot activate the virtualenv. – GoingMyWay May 07 '19 at 13:34
@GoingMyWay Conda 4.6.14 is functional – jCisco Jun 05 '19 at 12:21
If for some reason you are using a custom prompt (for something else), it gets messed up by the activate. But you can fix it, if you're good at PS profile hacking and adding: `if ("$env:CONDA_PROMPT_MODIFIER" -match "(base)") { ... }`. – not2qubit Apr 23 '20 at 17:06
@not2qubit I think that would be a valid question-answer pair which you could link to – Seanny123 Apr 23 '20 at 18:10
Does `conda init powershell` need to be run from powershell, or can it be run from a command prompt? – wordsforthewise Apr 08 '21 at 00:11

score 8 · Answer 2 · answered Sep 08 '18 at 16:19

8

I found this command while using vs code & cmd /k "activate <env> & powershell" . It is working

answered Sep 08 '18 at 16:19

it opens in powershell but you can change envs making it useless for my usecase. – Umar.H Jan 17 '21 at 20:38

score 6 · Answer 3 · edited Feb 21 '19 at 15:56

6

I found this solution:

I've been building on BCSharp's excellent work at my own repo (currently on PR).

Just do: conda install -n root -c pscondaenvs pscondaenvs

You need Conda 4.1 or above (check with conda info conda) - otherwise please install the latest version.

Behavior is exactly like CMD - use activate or deactivate appropriately. It's completely backwards compatible and will also launch both .ps1 and .bat activate.d/deactivate.d scripts.

from https://github.com/conda/conda/issues/626#issuecomment-346224990 has worked really well for me.

edited Feb 21 '19 at 15:56

Seanny123

8,776
13
68
124

answered Sep 28 '18 at 09:34

John Forbes

1,248
14
19

1

This no longer works with Conda 4.6, which resolves issue #626. – Seanny123 Feb 21 '19 at 15:53

score 1 · Answer 4 · answered Jul 19 '18 at 09:15

1

I have been battling this issue for a while. I found a solution by using a batch script and calling call activate %env%. I hope this can help somebody.

answered Jul 19 '18 at 09:15

didac

83
1
8

score 0 · Answer 5 · answered Apr 28 '21 at 10:04

0

Open PowerShell.
Run conda init (not conda init powershell as the accepted answer suggests).
Close and re-open PowerShell.
Use conda normally.

answered Apr 28 '21 at 10:04

Sabito stands with Ukraine

4,271
8
34
56

Gives `conda : The term 'conda' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.` – codeananda Mar 06 '23 at 15:41

score 0 · Answer 6 · answered Jun 16 '22 at 10:16

Someone may encounter some errors, like \WindowsPowerShell\profile.ps1 cannot be loaded because its operation is blocked by software restriction policies Just execution Set-ExecutionPolicy -ExecutionPolicy RemoteSigned as administrator in powershell, after that then reopen powershell the problem should be resolve.

score -5 · Answer 7 · answered Jan 23 '18 at 23:55

-5

Here is a work around - start cmd shell . Run - activate . Check - conda env list . Start powershell - powershell .

answered Jan 23 '18 at 23:55

whatdhack

1

How to activate different anaconda environment from powershell

7 Answers7

Linked