> ## Documentation Index
> Fetch the complete documentation index at: https://anaconda.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Uninstalling Navigator

> [!NOTE]
>
> Uninstalling Anaconda Navigator removes the `anaconda-navigator` package from your base environment. After uninstalling, you will no longer be able to launch Navigator, but you can still manage packages and environments using [conda commands](https://anaconda.com/docs/getting-started/working-with-conda/main.md).
>
> Your base conda installation, environments, packages, and other settings will remain intact. To remove Anaconda Distribution or Miniconda entirely, see [Uninstalling Anaconda Distribution](https://anaconda.com/docs/getting-started/anaconda/uninstall.md) or [Uninstalling Miniconda](https://anaconda.com/docs/getting-started/miniconda/uninstall.md).

To uninstall Anaconda Navigator, open Anaconda Prompt (A command-line application included with Windows installations of Anaconda Distribution and Miniconda. Find it by searching 'Anaconda Prompt' in the Windows Start menu.) (Terminal on macOS or Linux), and enter the following command:

```sh theme={null}
conda remove --name base anaconda-navigator
```

Troubleshoot

### command not found: conda

***

<details>
  <summary>Cause</summary>

  The `command not found: conda` error occurs when your command line interface (CLI) can't find the conda command in order to use it. This might be because:

  * You don't have conda properly initialized.
  * You have set `auto_activate_base` to `false`.
  * You're using a shell that conda doesn't support.
  * Conda is not installed or the install was incomplete or corrupted.

  > [!NOTE]
  >
  > These issues primarily occur on macOS/Linux computers. Anaconda Distribution and Miniconda installations on Windows include Anaconda Prompt (A command-line application included with Windows installations of Anaconda Distribution and Miniconda. Find it by searching 'Anaconda Prompt' in the Windows Start menu.), which opens with conda initialized by default.
</details>

***

<details>
  <summary>Solution</summary>

  > [accordion] Initialize conda in your shell
  >
  > If you recently installed Anaconda Distribution or Miniconda, make sure you closed and reopened your CLI to make conda's initialization take effect.
  >
  > > [!TIP]
  > >
  > > If you don't want to close your CLI, you can also use one of the following `source` commands to refresh your shell:
  > >
  > > ```sh bash theme={null}
  > > source ~/.bashrc
  > > ```
  > >
  > > ```sh zsh theme={null}
  > > source ~/.zshrc
  > > ```
  > >
  > > ```sh fish theme={null}
  > > source ~/.config/fish/config.fish
  > > ```
  > >
  > > ```sh cshrc theme={null}
  > > source ~/.cshrc
  > > ```
  > >
  > > ```sh xonshrc theme={null}
  > > source ~/.xonshrc
  > > ```
  > >
  > > Use the command that matches your shell.
  >
  > You can also initialize conda directly from its `bin` directory:
  >
  > ```sh Initialization command theme={null}
  > <PATH_TO_CONDA>/bin/conda init
  > ```
  >
  > ```sh Examples theme={null}
  > miniconda3/bin/conda init
  > /opt/miniconda3/bin/conda init
  > anaconda3/bin/conda init
  > /opt/anaconda3/bin/conda init
  > ```
  >
  > Replace \<PATH\_TO\_CONDA> with a path to your conda installation.

  > [accordion] Set auto\_activate\_base to true
  >
  > To see the value for `auto_activate_base`, run the following command:
  >
  > ```sh theme={null}
  > conda config --describe auto_activate_base
  > ```
  >
  > If your terminal returns `false`, this means that conda is not automatically activating your base environment when you start a new shell. This behavior emulates your system Python, and some users prefer to have their conda environment be inactive until they need it. However, this is not conda's default behavior after installation.
  >
  > To change the value of `auto_activate_base` to `true`, run the following command:
  >
  > ```sh theme={null}
  > conda config --set auto_activate_base true
  > ```
  >
  > If you have `auto_activate_base` set as `false`, the conda command will still be available as a shell function, but your base environment will not be active when a new shell is started. To activate your base environment, run `conda activate`.

  > [accordion] Use a shell that conda supports
  >
  > For information on which shells conda supports, see [Conda activate](https://docs.conda.io/projects/conda/en/stable/dev-guide/deep-dives/activation.html#conda-activate) in the official conda documentation.

  > [accordion] Verify your installation of conda
  >
  > If you have tried to initialize conda in your shell but it didn't work, try uninstalling and reinstalling [Anaconda Distribution](https://anaconda.com/docs/getting-started/installation.md) or [Miniconda](https://anaconda.com/docs/getting-started/installation.md).
  >
  > > [!TIP]
  > >
  > > Make sure that you say yes to the initialization option, and, if installing from the CLI, reinitialize your shell by restarting it or using its `source` command. For more information, see [Initialize conda in your shell](#initialize-conda-in-your-shell).
</details>