> ## 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.

# Troubleshooting Anaconda Distribution

export const TroubleshootSolution = ({children}) => <>
    <hr className="my-3 w-full" />
    <details className="mt-3">
      <summary className="cursor-pointer font-semibold text-base mb-1">
        Solution
      </summary>
      <div className="mt-2 ml-4" data-component-part="step-content">
        {children}
      </div>
    </details>
  </>;

export const TroubleshootCause = ({children}) => <details className="mt-3 mb-2">
    <summary className="cursor-pointer font-semibold text-base mb-1">
      Cause
    </summary>
    <div className="mt-2 ml-4" data-component-part="step-content">
      {children}
    </div>
  </details>;

export const TroubleshootTitle = ({children}) => <>
    <p className="m-0 font-semibold text-xl leading-tight mb-2" role="heading" aria-level={3}>
      {children}
    </p>
    <hr className="my-3 w-full" />
  </>;

export const Troubleshoot = ({children}) => <div className="callout my-4 px-5 py-4 overflow-hidden rounded-2xl flex gap-3 border troubleshoot-admonition dark:troubleshoot-admonition" data-callout-type="troubleshoot">
    <div className="mt-0.5 w-4">
      <svg width="14" height="14" viewBox="0 0 640 640" fill="currentColor" className="w-4 h-4" aria-label="Troubleshoot">
        <path d="M541.4 162.6C549 155 561.7 156.9 565.5 166.9C572.3 184.6 576 203.9 576 224C576 312.4 504.4 384 416 384C398.5 384 381.6 381.2 365.8 376L178.9 562.9C150.8 591 105.2 591 77.1 562.9C49 534.8 49 489.2 77.1 461.1L264 274.2C258.8 258.4 256 241.6 256 224C256 135.6 327.6 64 416 64C436.1 64 455.4 67.7 473.1 74.5C483.1 78.3 484.9 91 477.4 98.6L388.7 187.3C385.7 190.3 384 194.4 384 198.6L384 240C384 248.8 391.2 256 400 256L441.4 256C445.6 256 449.7 254.3 452.7 251.3L541.4 162.6z" />
      </svg>
    </div>
    <div className="prose min-w-0 w-full">{children}</div>
  </div>;

export const Comments = ({children}) => {
  return <div class="my-4 px-5 py-4 overflow-hidden rounded-2xl flex gap-3 border border-zinc-500/20 bg-zinc-50/50 dark:border-zinc-500/30 dark:bg-zinc-500/10" data-callout-type="comments">
      <div class="w-4">
        <svg width="14" height="14" viewBox="0 0 640 640" fill="currentColor" xmlns="http://www.w3.org/2000/svg" class="w-5 h-5" aria-label="Comments">
            <path d="M320 112C434.9 112 528 205.1 528 320C528 434.9 434.9 528 320 528C205.1 528 112 434.9 112 320C112 205.1 205.1 112 320 112zM320 576C461.4 576 576 461.4 576 320C576 178.6 461.4 64 320 64C178.6 64 64 178.6 64 320C64 461.4 178.6 576 320 576zM280 400C266.7 400 256 410.7 256 424C256 437.3 266.7 448 280 448L360 448C373.3 448 384 437.3 384 424C384 410.7 373.3 400 360 400L352 400L352 312C352 298.7 341.3 288 328 288L280 288C266.7 288 256 298.7 256 312C256 325.3 266.7 336 280 336L304 336L304 400L280 400zM320 256C337.7 256 352 241.7 352 224C352 206.3 337.7 192 320 192C302.3 192 288 206.3 288 224C288 241.7 302.3 256 320 256z" />
        </svg>
      </div>
      <div class="text-sm prose min-w-0 w-full">
        {children}
      </div>
    </div>;
};

This page includes common troubleshooting topics for Anaconda Distribution.

<Troubleshoot>
  <TroubleshootTitle>
    ### command not found: conda
  </TroubleshootTitle>

  <TroubleshootCause>
    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](/reference/glossary#anaconda-prompt), which opens with conda initialized by default.
    </Note>
  </TroubleshootCause>

  <TroubleshootSolution>
    <AccordionGroup>
      <Accordion title="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:

          <CodeGroup>
            ```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
            ```
          </CodeGroup>

          <Comments>
            Use the command that matches your shell.
          </Comments>
        </Tip>

        You can also initialize conda directly from its `bin` directory:

        <CodeGroup>
          ```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
          ```
        </CodeGroup>

        <Comments>
          Replace \<PATH\_TO\_CONDA> with a path to your conda installation.
        </Comments>
      </Accordion>

      <Accordion title="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>

      <Accordion title="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>

      <Accordion title="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](/getting-started/anaconda/main) or [Miniconda](/getting-started/miniconda/main).

        <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).
        </Tip>
      </Accordion>
    </AccordionGroup>
  </TroubleshootSolution>
</Troubleshoot>

<Troubleshoot>
  <TroubleshootTitle>
    ### PackagesNotFoundError: The following packages are not available from current channels
  </TroubleshootTitle>

  <TroubleshootCause>
    The `PackagesNotFoundError` occurs when conda cannot find the requested packages in any of your currently configured channels in order to install or update it. This might be because:

    * The package name is misspelled.
    * The package doesn't exist in the channels included in your conda configuration file (`.condarc`).
    * The package is not available for your operating system or architecture.
  </TroubleshootCause>

  <TroubleshootSolution>
    <AccordionGroup>
      <Accordion title="Verify your command syntax">
        Verify that your package name is spelled correctly and that your command contains no syntax errors. For more information about command syntax, see [Using conda install](/getting-started/working-with-conda/packages/install-packages#using-conda-install).
      </Accordion>

      <Accordion title="Install from the package's details page">
        If you're unsure what the correct command to install the package is, you can find it on the package's details page.

        Search [Anaconda.org](https://anaconda.org) or your [Anaconda Platform channels](/anaconda-platform/self-hosted/latest/user/package#searching-for-packages) for your preferred package, and view its details. Each package's details page provides a copyable command to install the package from that channel. Run that command to install the package in your currently active environment.

        <Warning>
          Remember to pay close attention to the command's syntax! The command you copy might not be the exact command you want to run, depending on your use case. Anaconda.org uses the double-colon syntax for channel specification, while Anaconda Platform uses the channel flag syntax by default. For more information, see [Installing packages from a specific channel](/getting-started/working-with-conda/channels#installing-packages-from-a-specific-channel).
        </Warning>
      </Accordion>

      <Accordion title="Add the missing channel to your .condarc file">
        [Add the missing channel to your .condarc file](/getting-started/working-with-conda/channels#managing-channels). However, keep in mind that any channels listed in the `channels:` section of your `.condarc` file will be searched by conda every time you install a new package.
      </Accordion>

      <Accordion title="Verify the package is compatible with your system architecture">
        Check your system architecture to determine if the package is compatible. This information is found under `platform:` in your `conda info` output.

        ```sh theme={null}
        conda info
        ```

        Conda restricts searches to packages that are compatible with your system architecture. If the package you're looking for is not available for your system architecture, it is not listed in conda's package search results.
      </Accordion>
    </AccordionGroup>
  </TroubleshootSolution>
</Troubleshoot>

<Troubleshoot>
  <TroubleshootTitle>
    ### DirectoryNotACondaEnvironmentError: The target directory exists, but it is not a conda environment
  </TroubleshootTitle>

  <TroubleshootCause>
    This error means that you don't have a conda environment currently active. You might have used `conda deactivate` while in your `base` environment and deactivated conda.
  </TroubleshootCause>

  <TroubleshootSolution>
    Activate your `base` environment or another environment:

    ```sh theme={null}
    # Activate your base environment
    conda activate

    # Activate an environment by name
    conda activate <ENV_NAME>
    ```

    <Comments>
      Replace \<ENV\_NAME> with the name of the environment.
    </Comments>
  </TroubleshootSolution>
</Troubleshoot>

<Troubleshoot>
  <TroubleshootTitle>
    ### EnvironmentNotWriteableError
  </TroubleshootTitle>

  <TroubleshootCause>
    You might see this error when trying to install or update a package, when attempting to create an environment in a restricted file location, or when attempting to modify an environment that was created by a user with admin permissions. This error is usually caused when you don't have the permissions to edit files in the directory where the environment exists. These are known as *write permissions*.
  </TroubleshootCause>

  <TroubleshootSolution>
    Create your own environment instead, in a directory you don't need admin permissions to work in, such as your home directory:

    ```sh theme={null}
    conda create --name <ENV_NAME> --prefix <PATH_TO_USER_DIRECTORY>
    ```

    <Comments>
      Replace \<ENV\_NAME> with the name of your environment.<br />
      Replace \<PATH\_TO\_USER\_DIRECTORY> with the file path to a directory you have control over.
    </Comments>

    <Tip>
      Talk with your system administrator or the user that created the environment in a location that was not editable by you. They can use `conda export` to [share an environment](/getting-started/working-with-conda/environments#sharing-an-environment) with you and you can then use that exported `environment.yml` file to create a new environment.

      Run the following command in the same directory as the `environment.yml` file or include the file path to the `environment.yml` file:

      ```sh theme={null}
      conda create --file environment.yml --prefix <PATH_TO_USER_DIRECTORY>
      ```

      <Comments>
        Replace \<PATH\_TO\_USER\_DIRECTORY> with the file path to a directory you have control over.
      </Comments>
    </Tip>
  </TroubleshootSolution>
</Troubleshoot>

<Troubleshoot>
  <TroubleshootTitle>
    ### ModuleNotFoundError: No module named X
  </TroubleshootTitle>

  <TroubleshootCause>
    A `ModuleNotFoundError` occurs when your project tries to use a package that isn't available in your currently active environment. You could be in the wrong environment for the project you're working on, or the package could simply not have been included in your project's environment.
  </TroubleshootCause>

  <TroubleshootSolution>
    Verify you are using the correct environment. Conda displays your currently active environment in parenthesis beside your command line interface (CLI) prompt. Another way to see your currently active environment is with the following command:

    ```sh theme={null}
    conda info --envs
    ```

    An asterisk is displayed next to your currently active environment:

    ```sh Environment list example theme={null}
    (my-active-environment) ~ conda info --envs

    # conda environments:
    #
    base                      /Users/user1/miniconda3
    my-active-environment   * /Users/user1/miniconda3/envs/my-active-environment
    python312                 /Users/user1/miniconda3/envs/python312
    ```

    If you are not in the correct environment, switch to your project's intended environment. For more information, see [Switching between environments](/getting-started/working-with-conda/environments#switching-between-environments).

    If your environment is missing the needed package, install it in your environment. For more information, see [Installing conda packages](/getting-started/working-with-conda/packages/install-packages).
  </TroubleshootSolution>
</Troubleshoot>

<Troubleshoot>
  <TroubleshootTitle>
    <h3 id="this-package-is-incompatible-with-this-version-of-macos-error-when-running-a-pkg-installer-on-osx">
      This package is incompatible with this version of macOS error when running a .pkg installer on OSX
    </h3>
  </TroubleshootTitle>

  <TroubleshootCause>
    When running the `.pkg` installer, you may encounter this error during the "Installation" step:<br />

    <Frame>
      <img src="https://mintcdn.com/anaconda-29683c67/YGtija9HXl-k020Y/images/anaconda_pkg_incompatible_error_1.png?fit=max&auto=format&n=YGtija9HXl-k020Y&q=85&s=9110e32ce6c4ac8373415db81a08af20" alt="" width="1242" height="892" data-path="images/anaconda_pkg_incompatible_error_1.png" />
    </Frame>

    <br />

    This error occurs when the installation attempts to write to a directory for which it does not have write permissions.
  </TroubleshootCause>

  <TroubleshootSolution>
    Manually select an appropriate install location. The following example shows how to select your user's home directory.

    1. Re-run the installer and click through until you reach either the Installation Type or Destination Select page.

    2. If you reach the Installation Type page first, click **Change Install Location…**. This will take you to the Destination Select page.

           <Frame>
             <img src="https://mintcdn.com/anaconda-29683c67/YGtija9HXl-k020Y/images/anaconda_pkg_incompatible_error_2.png?fit=max&auto=format&n=YGtija9HXl-k020Y&q=85&s=16da66d0ba347ad75f65b43fe3fedd70" alt="" width="1250" height="892" data-path="images/anaconda_pkg_incompatible_error_2.png" />
           </Frame>

    3. Click **Install on a specific disk…**.

    4. Click the appropriate destination drive. Then click **Choose Folder…**.

           <Frame>
             <img src="https://mintcdn.com/anaconda-29683c67/YGtija9HXl-k020Y/images/anaconda_pkg_incompatible_error_3.png?fit=max&auto=format&n=YGtija9HXl-k020Y&q=85&s=9b258d8d3d6218b792ed0e337619ddfd" alt="" width="1250" height="892" data-path="images/anaconda_pkg_incompatible_error_3.png" />
           </Frame>

    5. Click your user's home directory (for example, /Users/john.doe/). Then, click **Choose**.

    6. In the message box, confirm the name of the install folder you chose in the previous step. Then click **Continue**.

           <Frame>
             <img src="https://mintcdn.com/anaconda-29683c67/YGtija9HXl-k020Y/images/anaconda_pkg_incompatible_error_4.png?fit=max&auto=format&n=YGtija9HXl-k020Y&q=85&s=355ba3f7018ce7b72397a455a4e3d0b6" alt="" width="1250" height="892" data-path="images/anaconda_pkg_incompatible_error_4.png" />
           </Frame>

    7. Click **Install**, and then proceed with the rest of the installation.

    If you continue to receive the same error message, please open an issue [here](https://github.com/ContinuumIO/anaconda-issues/issues/new/choose/), and be sure to include the installation log output from your `install.log` file, which can be found at `/var/log/install.log`.
  </TroubleshootSolution>
</Troubleshoot>

<Troubleshoot>
  <TroubleshootTitle>
    <h3 id="macos-installation-failure-x86_64-intel-chip">
      macOS installation failure - x86\_64 (Intel chip)
    </h3>
  </TroubleshootTitle>

  <TroubleshootCause>
    Anaconda no longer supports Anaconda Distribution and Miniconda installers for Intel chip macOS computers (osx-64) and has removed these installers from the Anaconda.com website. If you downloaded a macOS installer from the website and your installation is failing, it is possible that you have an Intel chip macOS computer and the installer on the website is not compatible with your computer.
  </TroubleshootCause>

  <TroubleshootSolution>
    To check what architecture your macOS computer has:

    1. Click the <Icon icon="apple" /> **Apple** icon on your title bar.
    2. Click **About This Mac**.
    3. A macOS computer with an Intel chip will have "Intel" in the **Processor** item, while a macOS computer with an Apple silicon chip will have a **Chip** item labeled "Apple M1" or similar.

    macOS computers with Intel chip architecture use installers labeled `MacOSX-x86_64`, while macOS computers with Apple silicon chips use installers labeled `MacOSX-arm64`. While Anaconda no longer provides `MacOSX-x86_64` installers on its website, you can still find them in our installer archives.

    * [Anaconda Distribution installer archive](https://repo.anaconda.com/archive)
    * [Miniconda installer archive](https://repo.anaconda.com/miniconda)
  </TroubleshootSolution>
</Troubleshoot>

<Troubleshoot>
  <TroubleshootTitle>
    ### Receiving a 403 Forbidden error from an Anaconda channel
  </TroubleshootTitle>

  <TroubleshootCause>
    A **403 Forbidden** error occurs when you attempt to access a resource you don't have permissions for—such as a channel, package, or API endpoint.<br /><br />

    The 403 error you are receiving may look like the following:

    ```sh wrap theme={null}
    AnacondaAuthError: Received authentication error (403) when accessing <CHANNEL_URL>. If your token is invalid or expired, please re-install with anaconda token install.
    ```

    This error is likely because your token is invalid or expired, but can also be because Anaconda is blocking your access because of a potential terms of service violation.
  </TroubleshootCause>

  <TroubleshootSolution>
    Run `anaconda token install` to issue and set a new token for yourself, then try again.<br /><br />

    If the **403 Forbidden** error persists, ensure you are not blocked by a Terms of Service violation by consulting our [Terms of Service error](https://www.anaconda.com/legal/terms/terms-of-service) page.<br /><br />

    If you believe you have been blocked in error, please [open a support ticket](https://support.anaconda.com/hc/en-us/requests/new?ticket_form_id=360000993773).
  </TroubleshootSolution>
</Troubleshoot>

<Troubleshoot>
  <TroubleshootTitle>
    ### HTTP 000 CONNECTION FAILED
  </TroubleshootTitle>

  <TroubleshootCause>
    This is generally caused by a proxy misconfiguration.
  </TroubleshootCause>

  <TroubleshootSolution>
    Follow instructions on [Using Anaconda behind a company proxy](/getting-started/working-with-conda/reference/proxy) to configure your proxy correctly.
  </TroubleshootSolution>
</Troubleshoot>

<Troubleshoot>
  <TroubleshootTitle>
    ### `conda update anaconda` command does not install the latest version of the `anaconda` metapackage
  </TroubleshootTitle>

  <TroubleshootCause>
    <Note>
      The `anaconda` metapackage was removed from Anaconda Distribution installers in February of 2023 and no longer appears in your `base` environment by default. This troubleshooting topic assumes you are working with package incompatibilities in an environment containing the `anaconda` metapackage.
    </Note>

    If you have installed packages that are incompatible with the latest version of the Anaconda metapackage, running `conda update anaconda` updates the Anaconda metapackage to the latest compatible version. Keep in mind this might not be the latest version.
  </TroubleshootCause>

  <TroubleshootSolution>
    1. Obtain a list of the conflicting packages by running `conda update anaconda` or `conda install anaconda=2023.07`.

           <Note>
             Replace `2023.07` with the latest version number.
           </Note>

    2. Enter `n` to cancel the installation or update.

    3. Once you know which packages are conflicting, you can:
       * update all current packages without upgrading to the latest version of the `anaconda` metapackage, or
       * remove the conflicting packages and then upgrade to the latest version of the `anaconda` metapackage.

    To update all current packages without upgrading to the latest version of the `anaconda` metapackage:

    1. Remove the `anaconda` metapackage itself by running the following command:

       ```sh theme={null}
       conda remove anaconda
       ```
    2. Update all currently installed packages by running the following command:

       ```sh theme={null}
       conda update --all
       ```

    To remove the conflicting packages and upgrade to the latest version of the `anaconda` metapackage:

    1. Remove the conflicting packages by running the following command for each one:

       ```sh theme={null}
       conda remove <PACKAGE>
       ```
    2. Update to the latest version of the `anaconda` metapackage:

       ```sh theme={null}
       conda update anaconda
       ```
  </TroubleshootSolution>
</Troubleshoot>

<Troubleshoot>
  <TroubleshootTitle>
    ### Recovering your Anaconda installation
  </TroubleshootTitle>

  <TroubleshootCause>
    If your Anaconda installation has become corrupted and is in a state where normal conda commands are not functioning, use the following steps to repair Anaconda and preserve your installed packages and environments.
  </TroubleshootCause>

  <TroubleshootSolution>
    1. Download a [new installer](https://repo.anaconda.com/archive/), then follow the instructions for your operating system.

           <Note>
             Use the actual path, filename, and directory name for your installation.
           </Note>

           <Tabs>
             <Tab title="Windows">
               1. Open a terminal application, such as Command Prompt.
               2. Change your original installer's name so you do not overwrite it:

                  ```sh theme={null}
                  move anaconda3 anaconda_old
                  ```
               3. Run the Anaconda.exe installer as usual and use robocopy to sync the directories:

                  ```sh theme={null}
                  robocopy anaconda_old anaconda3 /S
                  ```
               4. Delete your old Anaconda installation directory:

                  ```sh theme={null}
                  rd /s anaconda_old
                  ```
             </Tab>

             <Tab title="macOS">
               1. Open a terminal application.
               2. Change your original installer's name so you do not overwrite it:

                  ```sh theme={null}
                  mv anaconda3 anaconda_old
                  ```
               3. Install to same directory as your original installer:

                  ```sh theme={null}
                  # Replace <INSTALLER> the name of your installer file
                  bash ~/Downloads/<INSTALLER>
                  rsync -a anaconda_old/ anaconda3/
                  ```
               4. Delete your old Anaconda installation directory:

                  ```sh theme={null}
                  rm -rf anaconda_old
                  ```
             </Tab>

             <Tab title="Linux">
               1. Open a terminal application.
               2. Change your original installer's name so you do not overwrite it:

                  ```sh theme={null}
                  mv anaconda3 anaconda_old
                  ```
               3. Install to same directory as your original installer:

                  ```sh theme={null}
                  # Replace <INSTALLER> the name of your installer file
                  bash ~/Downloads/<INSTALLER>
                  rsync -a anaconda_old/ anaconda3/
                  ```
               4. Delete your old Anaconda installation directory:

                  ```sh theme={null}
                  rm -rf anaconda_old
                  ```
             </Tab>
           </Tabs>

    2. Run `conda list` to view the packages from the previous installation.

    3. Run `conda info --envs` to list the environments created in the previous installation, which are now available in the new installation.
  </TroubleshootSolution>
</Troubleshoot>

<Troubleshoot>
  <TroubleshootTitle>
    ### Channels list adding extra channels
  </TroubleshootTitle>

  <TroubleshootCause>
    A `.condarc` file has been added to the root folder of your Anaconda Distribution and Miniconda installations. This file has a `channels:` list that contains either:

    * a list of hard-coded URLs
    * the `defaults` channel

    When using channels, conda merges all of your computer's `.condarc` files together in specific ways. For more information on how conda uses your `.condarc` files, see the [Searching for .condarc](https://docs.conda.io/projects/conda/en/stable/user-guide/configuration/use-condarc.html#searching-for-condarc) section of the official conda documentation.<br /><br />

    All `channels:` lists in your `.condarc` files are merged together when conda searches for packages. This causes the Anaconda default URLs to be appended to (added to the end of) your `channels:` list.<br /><br />

    To see all the `.condarc` files influencing your currently active conda environment, run the following command:

    ```
    conda config --show-sources
    ```

    This returns a list of `.condarc` file locations and their contents.

    <Tip>
      Your installation directory `.condarc` file should be in the folder where you installed Anaconda Distribution or Miniconda, most likely similar to one of the following:

      ```text theme={null}
      C:\Users\<USERNAME>\anaconda3
      C:\Users\<USERNAME>\miniconda3
      /Users/<USERNAME>/anaconda3
      /Users/<USERNAME>/miniconda3
      /opt/anaconda3
      /opt/miniconda
      ```
    </Tip>
  </TroubleshootCause>

  <TroubleshootSolution>
    There are a few ways you can solve this issue, depending on how you use your `.condarc` file:<br /><br />

    <AccordionGroup>
      <Accordion title="If you have write access to the installation directory .condarc file">
        <AccordionGroup>
          <Accordion title="Add defaults to the installation directory .condarc file (Recommended)">
            If you use `defaults` to configure your channels, you should edit the installer root `.condarc` file to use `defaults` as well.

            1. Locate the installer root `.condarc` file using `conda config --show-sources`.
            2. Add defaults to the installation directory `.condarc` file's `channels:` list, then remove the hardcoded URLs.

               You can edit the files manually using your preferred text editor, or by using the following conda CLI command:

                           <Tip>
                             Use the `--file` flag to specify the path to the root `.condarc` file.
                           </Tip>

               ```
               conda config --file <PATH/TO/YOUR/ROOT>/.condarc --add channels defaults
               conda config --file <PATH/TO/YOUR/ROOT>/.condarc --remove channels <CHANNEL1> <CHANNEL2>
               ```

                           <Accordion title="Example commands">
                             <Tabs>
                               <Tab title="Windows">
                                 ```
                                 conda config --file C:\Miniconda3\.condarc --add channels defaults
                                 conda config --file C:\Miniconda3\.condarc --remove channels https://repo.anaconda.com/pkgs/main https://repo.anaconda.com/pkgs/r https://repo.anaconda.com/pkgs/msys2
                                 ```
                               </Tab>

                               <Tab title="Linux/macOS">
                                 ```
                                 conda config --file /opt/miniconda3/.condarc --add channels defaults
                                 conda config --file /opt/miniconda3/.condarc --remove channels https://repo.anaconda.com/pkgs/main https://repo.anaconda.com/pkgs/r
                                 ```
                               </Tab>
                             </Tabs>
                           </Accordion>

                           <Tip>
                             If you are using `defaults` and want to change the URLs it points to, use `default_channels` in your `.condarc` file. For more information on this setting, see [default\_channels: Default channels](https://docs.conda.io/projects/conda/en/stable/user-guide/configuration/settings.html#default-channels-default-channels) in the official conda documentation.

                             You can edit your `.condarc` manually using your preferred text editor, or by using the following conda CLI command:

                             ```sh theme={null}
                             conda config --add default_channels <CHANNEL>
                             ```

                             <Comments>
                               This command adds one channel at a time.
                               Replace \<CHANNEL> with the URL to your channel.
                             </Comments>

                             To remove a channel instead, replace `--add` with `--remove`.
                           </Tip>
          </Accordion>

          <Accordion title="Delete the installation directory .condarc file">
            If you have your channels configured in a different `.condarc` file (whether you use `defaults` or not), you can also delete the installation directory `.condarc` file.

            <Warning>
              Make sure that you always have at least one `.condarc` file with a `channels:` list defined. Conda requires this to function.
            </Warning>

            1. Locate the installation directory `.condarc` file using `conda config --show-sources`.
            2. Delete the installation directory `.condarc` file. This is a hidden file on macOS and Linux and is not visible in file browsers under normal circumstances.

                           <HiddenFiles />
          </Accordion>
        </AccordionGroup>
      </Accordion>

      <Accordion title="If you do not have write access to the installation directory .condarc file">
        If you do not want to use the `defaults` channels and cannot edit or remove the installation directory `.condarc` file (for example, you installed on macOS using the graphical installer without `sudo` access):

        * You must use the `--override-channels` flag with every conda command that installs or updates packages.
        * You must also specify at least one channel using the `--channel` (or `-c`) flag.

        Example:

        ```
        conda install --override-channels --channel conda-forge numpy
        ```

        This tells conda to ignore all channels in your `.condarc` files and only use the channels you explicitly specify to install or update packages and their dependencies.
      </Accordion>
    </AccordionGroup>

    If you continue to experience issues, please [open a support ticket](https://support.anaconda.com/hc/en-us/requests/new?ticket_form_id=360000993773).
  </TroubleshootSolution>
</Troubleshoot>

<Troubleshoot>
  <TroubleshootTitle>
    ### Anaconda installer download problems
  </TroubleshootTitle>

  <TroubleshootCause>
    The Anaconda installer files are large (over 600 MB), and some users have problems with errors and interrupted downloads when downloading large files.
  </TroubleshootCause>

  <TroubleshootSolution>
    <Tabs>
      <Tab title="Download Miniconda">
        1. Download and install the smaller [Miniconda](/getting-started/miniconda/main) (between 70 and 100 MB).
        2. Download and install the remaining packages in Anaconda by using the following command:

           ```sh theme={null}
           conda install anaconda
           ```

        <Note>
          If the package downloads are interrupted, just run `conda install anaconda` again. Conda only downloads the packages that were not finished in any previous attempts.
        </Note>
      </Tab>

      <Tab title="Restart the download">
        Download the large Anaconda installer file, and restart it if the download is interrupted or you need to pause it.

        <Tabs>
          <Tab title="Windows">
            <Tabs>
              <Tab title="Chrome">
                1. Find the latest installer at [anaconda.com](https://www.anaconda.com), or an older installer at [repo.anaconda.com/archive](https://repo.anaconda.com/archive).
                2. In Chrome, use Ctrl+J to open the Chrome download manager.
                3. Click **Resume** to continue the interrupted download.

                The Chrome download manager also enables you to pause and resume or cancel and retry downloads in progress.
              </Tab>

              <Tab title="Edge">
                1. Find the latest installer at [anaconda.com](https://www.anaconda.com), or an older installer at [repo.anaconda.com/archive](https://repo.anaconda.com/archive).
                2. In Edge, click **Settings and more**.
                3. Click **Downloads** to open the Downloads dialog.
                4. From here, you can use the play, pause, and cancel buttons to control downloads in progress.

                <Tip>
                  Go to `edge://downloads/all` to open the full page of recent downloads. From here, you can retry cancelled downloads.
                </Tip>
              </Tab>
            </Tabs>
          </Tab>

          <Tab title="macOS/Linux">
            1. Open a terminal window.

            2. To download the file, use the following command:

               ```sh theme={null}
               # Replace <INSTALLER> with the the installer file you want to install
               # See all available installers on https:://repo.anaconda.com/archive/
               curl -O https://repo.anaconda.com/archive/<INSTALLER>
               ```

            3. To pause the download, use Ctrl+C.

                           <Note>
                             While a download is paused, you can shut down or restart your computer.
                           </Note>

            4. When you are ready to resume your download, use the following command:

               ```sh theme={null}
               curl -O -C https://repo.anaconda.com/archive/<INSTALLER>
               ```

                           <Comments>
                             Replace \<INSTALLER> with the same file you used above
                           </Comments>

            <Note>
              The `-C` flag is the option for "continue". You can pause and restart a download as many times as you wish.
            </Note>
          </Tab>
        </Tabs>
      </Tab>
    </Tabs>
  </TroubleshootSolution>
</Troubleshoot>

<Troubleshoot>
  <TroubleshootTitle>
    ### Cannot see Anaconda menu shortcuts after installation on Windows
  </TroubleshootTitle>

  <TroubleshootCause>
    After installing on Windows, the Anaconda Prompt and Anaconda Navigator shortcuts do not appear in the Windows Start menu.<br /><br />

    This may be caused by the way Windows updates the Start menu, or by having multiple versions of Python installed that are interfering with one another. Existing Python installations, installations of Python modules in global locations, or libraries that have the same names as Anaconda libraries can all prevent Anaconda from working properly.
  </TroubleshootCause>

  <TroubleshootSolution>
    If Start menu shortcuts are missing, Microsoft recommends rebooting your computer or [restarting Windows Explorer](https://answers.microsoft.com/en-us/windows/forum/windows8_1-performance/force-refresh-of-start-menu-start-screen-in/ee4e36d2-91d0-4f34-9eb8-b17ab096e83c?auth=1).<br /><br />

    If that doesn't work, clear your `$PYTHONPATH` environment variable, if applicable, and re-install Anaconda.<br /><br />

    Other potential solutions are covered in the "Conflicts with system state" section of the following [blog post](https://www.anaconda.com/blog/who-you-gonna-call-halloween-tips-treats-to-protect-you-from-ghosts-gremlins-and-software-vulnerabilities).
  </TroubleshootSolution>
</Troubleshoot>

<Troubleshoot>
  <TroubleshootTitle>
    ### Windows error: Failed to create Anaconda menus or Failed to add Anaconda to the system PATH
  </TroubleshootTitle>

  <TroubleshootCause>
    During installation on a Windows system, a dialog appears that says "Failed to create Anaconda menus, Abort Retry Ignore" or "Failed to add Anaconda to the system PATH." There are many possible Windows causes for this.
  </TroubleshootCause>

  <TroubleshootSolution>
    Try these solutions, in order:

    * Do not install on a PATH longer than 1024 characters.
    * Turn off anti-virus programs before installing, then turn the anti-virus programs back on.
    * Uninstall all previous Python installations.
    * Clear all PATHs related to Python in sysdm.cpl file.
    * Delete any previously set up Java PATHs.
    * If JDK is installed, uninstall it.

    <Note>
      To find your path variable:

      1. Search for "environment variables" in the search in your taskbar.
      2. Click **Edit the System Environment Variables** in the sidebar.
      3. Click **Environment Variables** in the System Properties dialog.
      4. Highlight the **path** variable for your user.
      5. Click **Edit**.
    </Note>
  </TroubleshootSolution>
</Troubleshoot>

<Troubleshoot>
  <TroubleshootTitle>
    ### Files left behind after uninstalling Anaconda on Windows
  </TroubleshootTitle>

  <TroubleshootCause>
    Some users may need to keep settings files and other users may need to delete them, so Anaconda leaves some settings files in place when it is uninstalled. Specifically, the directories `.spyder2`, `.ipython`, `.matplotlib`, and `.astropy` remain. Depending on your version of Windows, these may be in `C:\Documents and Settings\<USERNAME>` or in `C:\Users\<USERNAME>`.

    <Note>
      Replace `<USERNAME>` with your Windows username as it appears in the `Documents and Settings` or `Users` folder.
    </Note>
  </TroubleshootCause>

  <TroubleshootSolution>
    Manually delete any unneeded settings files.
  </TroubleshootSolution>
</Troubleshoot>

<Troubleshoot>
  <TroubleshootTitle>
    ### Proxy request sent, not found
  </TroubleshootTitle>

  <TroubleshootCause>
    Your company likely has security policies or a firewall in place that prevent communications with external servers or certain URLs.
  </TroubleshootCause>

  <TroubleshootSolution>
    1. First, work with your IT team to allowlist connections to the following URLs:

       ```txt theme={null}
       https://anaconda.org
       https://repo.anaconda.com
       https://repo.anaconda.cloud
       ```

           <Note>
             Allowlisting `https://repo.anaconda.cloud` is only necessary if your company has an Anaconda Platform (Cloud) organization and you require access to channels in that organization.
           </Note>

    2. [Install](/getting-started/main) Anaconda Distribution or Miniconda again.

    Once your installation is complete, you might also need to connect your company's firewall/proxy server to your conda configuration file (`.condarc`). For more information on this, see [Using Anaconda behind a firewall or proxy](/anaconda-platform/cloud/getting-started-with-anaconda-platform#using-anaconda-behind-a-firewall-or-proxy-optional).
  </TroubleshootSolution>
</Troubleshoot>

<Note>
  If you encounter an issue or bug that isn't covered on this page, you can ask for help in the [Anaconda community forums](https://forum.anaconda.com) or [open a support ticket](https://support.anaconda.com/hc/en-us/requests/new).
</Note>

<Troubleshoot>
  <TroubleshootTitle>
    ### Uninstall.sh not found
  </TroubleshootTitle>

  <TroubleshootCause>
    It is likely that you are receiving the `uninstall.sh not found` error for one of two reasons:

    * You are not using the correct file path to run the `uninstall.sh` file.
    * The `uninstall.sh` script was introduced in Anaconda Distribution 2025.06 (released June 23, 2025) and Miniconda 24.11.1 (released December 16, 2024). If you installed either product before those releases, the `uninstall.sh` file is not included.
  </TroubleshootCause>

  <TroubleshootSolution>
    Use the following instructions to find your `uninstall.sh` file and use it:

    1. Open a new Terminal window.

    2. Run the following command to find your installation folder:

       ```sh theme={null}
       conda info --base
       ```

    3. Check the contents of your installation folder for the `uninstall.sh` script:

       ```sh theme={null}
       ls <PATH/TO/INSTALLER>
       ```

           <Comments>
             Replace \<PATH/TO/INSTALLER> with the returned path from the previous command.
           </Comments>

    4. If your install is in your home directory (`\Users\<USERNAME>\` or `\home\<USERNAME>`), use the macOS/Linux **Basic uninstall** instructions.<br /><br />

       If your install is in your `\opt\` folder, use the macOS/Linux **System uninstall** instructions.<br /><br />

       If your install folder does not contain the `uninstall.sh` file, use the macOS/Linux **Manual uninstall** instructions.

       * [Anaconda Distribution uninstall instructions](/getting-started/anaconda/uninstall#uninstall-procedure)
       * [Miniconda uninstall instructions](/getting-started/miniconda/uninstall#uninstall-procedure)
  </TroubleshootSolution>
</Troubleshoot>