Conda Is Not Recognized As An Internal Or External Command | Fix Steps

Guide / By

The “conda is not recognized as an internal or external command” message shows your shell can’t find conda on PATH, so it won’t run.

You type conda, hit Enter, and Windows throws a blunt error. It’s common after installing Anaconda or Miniconda, switching terminals, or moving folders around. The good news is that you can fix it with a few clean checks.

This article gives you a step-by-step path that works in Command Prompt, PowerShell, and Windows Terminal. You’ll learn what the message means, how to confirm where conda.exe lives, and how to make your shell see it every time you open a new window.

What This Error Usually Means

Windows runs commands by searching folders listed in PATH. When you type conda, the shell looks through those PATH folders for conda.exe (or a matching command file). If it can’t find it, you get the “not recognized” message.

That points to a short list of causes. Conda might be installed, yet its folder isn’t on PATH. Conda might be installed, yet your shell wasn’t initialized. Or you might be using a terminal profile that’s tied to a different Python install.

There’s one more thing worth saying early. Many Anaconda installs work perfectly inside Anaconda Prompt even when Command Prompt fails. That’s not magic. Anaconda Prompt loads startup scripts that add the right folders for you.

Fast Checks Before You Touch Settings

Start with these checks. They save time and prevent you from changing PATH when the real issue is simpler.

What You See Likely Cause Fast Check
Anaconda Prompt works, cmd fails PATH missing conda folders Run where conda in cmd
PowerShell fails after install Shell not initialized Run conda init powershell
Windows Terminal profile fails Profile uses different shell Open the profile you initialized
Nothing works anywhere Install missing or corrupted Search for conda.exe on disk
  1. Try Anaconda Prompt — Open it from the Start menu and run conda --version. If it works there, your install is fine and the issue is terminal setup.
  2. Check Where Conda Lives — In File Explorer, search inside your user folder for conda.exe. Note the folder path that contains it.
  3. Run A Quick “Where” Test — In the terminal that fails, run where conda. If it prints nothing, PATH can’t see conda.

If Anaconda Prompt can run conda, stick with that prompt for the next steps. It’s a steady place to run setup commands even while other shells are still broken.

Conda Is Not Recognized As An Internal Or External Command

If you’re seeing conda is not recognized as an internal or external command in Command Prompt, the fix is usually PATH. If you’re seeing it in PowerShell, PATH can be part of it, and shell init often finishes the job.

There are two safe paths you can take. One is to rely on Anaconda Prompt and initialize the shells you use. The other is to add the right conda folders to PATH so any shell can find it.

Both routes can work. The “init the shell” route often stays cleaner, since you keep PATH shorter. The “add to PATH” route is handy if you want conda available in plain cmd without special profiles.

Decide Which Setup Fits Your Use

  • Use Anaconda Prompt As Home Base — Pick this if you mainly use conda for package work and you want fewer PATH edits.
  • Add Conda Folders To PATH — Pick this if you want conda to run from cmd, PowerShell, and scripts without switching prompts.

Conda Not Recognized Command Error In PowerShell

PowerShell can look “fine” yet still fail on conda because it needs a shell hook that sets up activation scripts. If you installed Miniconda or Anaconda and jumped straight into PowerShell, it may not have been initialized for conda yet.

Start by checking whether PowerShell can see the file at all. Run where conda. If you get a path, PATH is OK and shell init is the missing piece. If you get nothing, fix PATH first, then return here.

  1. Open Anaconda Prompt — Use it even if PowerShell is the one failing.
  2. Init PowerShell — Run conda init powershell and wait for it to finish.
  3. Close All PowerShell Windows — End the session fully, then open a fresh one.
  4. Test The Command — Run conda --version in PowerShell.

If that still doesn’t work, your PowerShell profile may block script execution. You can fix that without opening system-wide permissions.

Fix Script Policy If PowerShell Blocks Conda

  1. Check The Current Policy — Run Get-ExecutionPolicy -List and look at CurrentUser.
  2. Set Current User Policy — Run Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser.
  3. Re-Run Init — Run conda init powershell again from Anaconda Prompt, then reopen PowerShell.

This change affects only your user account. It allows local scripts to run while still warning on unsigned scripts downloaded from the web.

Git Bash And Other Terminals

Git Bash, Cmder, and Windows Terminal can each behave a little differently. You still have a simple path forward: init the shell you use, then reopen it.

  • Init For Bash — Run conda init bash, then restart Git Bash.
  • Init For Cmd — Run conda init cmd.exe if Command Prompt activation feels broken.
  • Check Windows Terminal Profiles — Pick a profile that matches the shell you initialized.

Add Conda To PATH Without Breaking Other Tools

If you want conda to run from plain cmd, adding the correct folders to PATH is the direct fix. Do it carefully so you don’t shuffle other tools in a way that creates new conflicts.

Conda installs in one main folder, and it usually has a few subfolders that matter for commands. The exact paths depend on your install location. Common locations look like C:\Users\\miniconda3 or C:\Users\\anaconda3.

Typical PATH Entries That Make Conda Work

  • Add The Base Folder — Add the folder like C:\Users\\miniconda3.
  • Add Scripts Folder — Add C:\Users\\miniconda3\Scripts so helper commands run.
  • Add Condabin Folder — Add C:\Users\\miniconda3\condabin for the shim that helps activation.

If you aren’t sure which install you have, use File Explorer to locate conda.exe and work backward from that folder.

Edit PATH In Windows

  1. Open System Variables — Press the Windows logo button, type “system variables,” then open “Edit the system variables.”
  2. Open The PATH List — Click “System Variables,” select “Path” under your user account, then click “Edit.”
  3. Add The Conda Paths — Click “New” and paste the three folders listed above for your install.
  4. Save And Restart Terminals — Click OK on all dialogs, then close and reopen cmd or PowerShell.

After you restart the terminal, run where conda, then run conda --version. If you see a path and a version number, PATH is fixed.

Fix Shell Setup After PATH Is Correct

Once PATH can locate conda, shell setup is the next layer. This is where activation and shell functions get wired up, which matters when you run conda activate or use conda inside startup scripts.

If you only need conda install and conda list, PATH might be enough. If you want smooth activation in your daily terminal, init is worth doing.

Init The Shell You Actually Use

  • Init For PowerShell — Run conda init powershell, then reopen PowerShell.
  • Init For Cmd — Run conda init cmd.exe, then reopen Command Prompt.
  • Init For Bash — Run conda init bash, then restart Git Bash.

If you use Windows Terminal, double-check which profile you open. “PowerShell” and “Command Prompt” profiles load different startup files, so init has to match the profile you run.

When The Error Still Won’t Quit

At this point you’ve handled PATH and shell setup. If you still get the same message, one of three things is going on: files are missing, your install is corrupted, or a different tool is hijacking the command name.

Confirm You’re Calling The Right Conda

Quick check: run where conda and open the first path it shows in File Explorer. You should see conda.exe in that folder. If the folder exists yet conda.exe is missing, the install is damaged.

Repair The Install Without A Full Wipe

  1. Update Conda In The Working Prompt — In Anaconda Prompt, run conda update conda.
  2. Update Base Packages — Run conda update --all and let it finish.
  3. Reset Shell Hooks — Run conda init --reverse, then run conda init for your shells again.

If you can’t run conda in any prompt, you won’t be able to repair it from inside conda. In that case, reinstall is faster than wrestling with half-missing files.

Reinstall Cleanly And Avoid The Same Trap

  1. Uninstall The Old Copy — Use Windows “Apps & features” to remove Anaconda or Miniconda.
  2. Delete Leftover Folders — Remove the old install folder if it still exists, plus leftover .conda folders in your user directory.
  3. Install To A Simple Path — Pick a path with no spaces, like C:\Users\\miniconda3.
  4. Choose PATH Option Carefully — If the installer asks about adding to PATH, leave it off and use conda init after install.

Once it’s installed, run a quick smoke test in a fresh terminal. Log out and back in so fresh sessions pick up the new PATH on Windows. Try conda --version, then make a small test env and remove it. You’ll know right away that PATH and your shell hooks are behaving.

Sanity Checks That Catch Sneaky Cases

  • Restart The Whole Machine — A reboot clears stale terminal sessions and reloads user PATH everywhere.
  • Check For Alias Functions — In PowerShell, run Get-Command conda to see if an alias is masking the real command.
  • Keep One Install — Two conda installs on PATH is asking for confusion. Remove the one you don’t use.
  • Watch For Antivirus Quarantine — Some security tools can block scripts in Scripts. Check quarantine logs if files vanish.

If you’ve made it here, you now have a repeatable method: find where conda lives, make sure PATH points there, then initialize the shell you actually run. When you do those three in that order, this error stops being a mystery and turns into a quick tidy-up.

One last check: open a fresh terminal, type conda --version, then create a tiny test env with conda create -n test python. If that runs, you’re back in business and you won’t see that message again unless PATH changes.

Two Extra Checks That Save Time

Store Python can add aliases that steal python calls. Turn them off, then confirm which python runs in that terminal profile too.

  • Review App Execution Aliases — Open Settings, search for “App execution aliases,” then turn off alias toggles for python and python3 if they point to the Store.
  • Confirm The Active Python — Run where python and make sure the first path matches the install you expect, not a Store stub.