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

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>;
};

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>;

This page includes common troubleshooting topics for Anaconda Navigator.

If you are experiencing issues with conda, see the [Troubleshooting](/reference/troubleshooting) page for workarounds to common issues.

<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>
    ### Custom Navigator app isn't appearing on the Home page
  </TroubleshootTitle>

  <TroubleshootCause>
    Apps may not appear on the Home page if the conda package hasn't been uploaded to your Anaconda.org channel, your channel isn't in the Channels list, or Navigator's configuration information is corrupted.
  </TroubleshootCause>

  <TroubleshootSolution>
    1. Check that the conda package has been uploaded to your Anaconda.org channel.
    2. Check that your channel has been added to the Channels list.
    3. Remove the `.anaconda/navigator` folder from your home directory to reset Navigator's configuration information, then restart Navigator.
  </TroubleshootSolution>
</Troubleshoot>

<Troubleshoot>
  <TroubleshootTitle>
    ### Custom Navigator app won't launch
  </TroubleshootTitle>

  <TroubleshootCause>
    The app can fail to launch due to Navigator configuration issues, even if the application itself is functioning correctly.
  </TroubleshootCause>

  <TroubleshootSolution>
    1. If the application does not launch after installation, confirm that it works via the command line by running the following command:

       ```sh theme={null}
       conda run jupyter lab
       ```

           <Note>
             If you are not using the example feedstock, the command after `run` will be the `entry:` command you have designated.
           </Note>

    2. If JupyterLab starts correctly with conda, remove the `.anaconda/navigator` folder from your home directory to reset the Navigator configuration information and enable the app to launch correctly from the Navigator application. Then, restart Navigator.
  </TroubleshootSolution>
</Troubleshoot>

<Troubleshoot>
  <TroubleshootTitle>
    ### Navigator fails to update to version 2.6.4
  </TroubleshootTitle>

  <TroubleshootCause>
    If you are using Navigator version 2.6.3 and are unable to update to version 2.6.4, it might be because of a dependency conflict between the `anaconda-navigator` package and the `anaconda-toolbox` package. (Each package lists incompatible versions of `anaconda-cloud-auth` as a dependency.)
  </TroubleshootCause>

  <TroubleshootSolution>
    To check if you have the `anaconda-toolbox` package, open Anaconda Prompt (Terminal on macOS/Linux) and run the following command:

    ```sh theme={null}
    conda list anaconda-toolbox
    ```

    To solve the dependency conflict between `anaconda-navigator` and `anaconda-toolbox`:

    1. Close Navigator, if open.

    2. Open Anaconda Prompt (Terminal on macOS/Linux).

    3. Run the following command:

       ```sh theme={null}
       conda install --name base anaconda-navigator=2.6.4 anaconda-toolbox=4.1.0
       ```

    4. Enter `y` to approve the package changes.

           <Tip>
             Once your base environment is updated, it is safe to close Anaconda Prompt/Terminal.
           </Tip>

    5. Reopen Navigator.

    Once this dependency conflict is resolved, any future updates to Navigator can be accomplished as usual.
  </TroubleshootSolution>
</Troubleshoot>

<Troubleshoot>
  <TroubleshootTitle>
    ### Navigator error on start up
  </TroubleshootTitle>

  <TroubleshootCause>
    This is often the result of a corrupted `.condarc` file.
  </TroubleshootCause>

  <TroubleshootSolution>
    To resolve, delete the `.condarc` file and restart Navigator.

    1. Find the `.condarc` file.

       Open Anaconda Prompt (Terminal on macOS/Linux) and enter the command `conda info`. The output will tell you the location of your `.condarc` file(s). You can also search for ".condarc" on your computer.<br /><br />

       The `.condarc` file is frequently found in:

           <CodeGroup>
             ```sh Windows theme={null}
             C:\Users\<USERNAME>
             ```

             ```sh macOS theme={null}
             /Users/<USERNAME>
             ```

             ```sh Linux theme={null}
             ~/.condarc
             ```
           </CodeGroup>

    2. Optional: Save custom configurations.<br /><br />

       If you had custom configuration in your `.condarc` file before it was corrupted, save the information to add that configuration back to the new file.<br /><br />

    3. Delete the `.condarc` file.<br /><br />

    4. Restart Navigator.
  </TroubleshootSolution>
</Troubleshoot>

<Troubleshoot>
  <TroubleshootTitle>
    ### Issues launching or initializing
  </TroubleshootTitle>

  <TroubleshootCause>
    Issues launching or initializing Anaconda Navigator may be caused by permission or licensing problems.
  </TroubleshootCause>

  <TroubleshootSolution>
    * If you cannot launch the Anaconda Navigator desktop app via its desktop or application shortcut, you might still be able to launch it via Anaconda Prompt (Terminal on macOS/Linux). Enter the following command:

      ```sh theme={null}
          anaconda-navigator
      ```

    * If you have permissions issues, there may be a problem with the hidden licenses directory, `.continuum`. To delete the `.continuum` directory, open Anaconda Prompt (Terminal on macOS/Linux) and run the following command, depending on your operating system:

          <CodeGroup>
            ```sh Windows theme={null}
            rd /s .continuum
            ```

            ```sh macOS/Linux   theme={null}
            rm -rf ~/.continuum
            ```
          </CodeGroup>

      Then, relaunch Navigator from the desktop app or Anaconda Prompt (Terminal on macOS/Linux).

    * If removing the licenses directory does not resolve the issue, manually update Navigator by opening Anaconda Prompt (Terminal on macOS/Linux) and running the following command:

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

    * If you have updated Navigator and still have problems, remove and reinstall Anaconda Navigator by opening Anaconda Prompt (Terminal on macOS/Linux) and running the following command:

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

    * If none of the above work, reset the Anaconda Navigator configuration back to default values by opening Anaconda Prompt (Terminal on macOS/Linux) and running the following command:

      ```sh theme={null}
      anaconda-navigator --reset
      ```
  </TroubleshootSolution>
</Troubleshoot>

<Troubleshoot>
  <TroubleshootTitle>
    ### PermissionError on macOS Catalina
  </TroubleshootTitle>

  <TroubleshootCause>
    macOS Catalina users may experience permission errors where the system does not prompt you for permission to folders requiring access.
  </TroubleshootCause>

  <TroubleshootSolution>
    1. Update Navigator by opening Anaconda Prompt (Terminal on macOS/Linux) and running the following command:

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

    2. Once updated, have Navigator generate the permissions prompt by launching Spyder and running the following in the console:

       ```sh theme={null}
       import os
       os.listdir('<DIRECTORY>')
       ```

           <Comments>
             Replace \<DIRECTORY> with the folder you need access to.
           </Comments>
  </TroubleshootSolution>
</Troubleshoot>

<Troubleshoot>
  <TroubleshootTitle>
    ### Access denied error
  </TroubleshootTitle>

  <TroubleshootCause>
    A lock file wasn't removed when it should have been.
  </TroubleshootCause>

  <TroubleshootSolution>
    Open Anaconda Prompt (Terminal on macOS/Linux) and remove the lock file by running the following commands:

    ```sh theme={null}
    conda update --name base conda anaconda-navigator navigator-updater
    anaconda-navigator --reset
    ```
  </TroubleshootSolution>
</Troubleshoot>

<Troubleshoot>
  <TroubleshootTitle>
    ### Navigator buttons are missing
  </TroubleshootTitle>

  <TroubleshootCause>
    The disappearance of Navigator buttons may be caused by an out of sync repodata, a corrupt `.condarc` file, or an unknown issue.
  </TroubleshootCause>

  <TroubleshootSolution>
    1. Run **Update Index** from the **Environments** page of Navigator.
    2. Quit and restart Navigator.

    If that solution doesn't work, try one of the following:

    * Confirm that your `.condarc` file is not corrupt (see the "Navigator error on start up" troubleshooting topic). Specifically confirm that your channel settings contain `defaults`.
    * Open Anaconda Prompt (Terminal on macOS/Linux) and run the following command:

      ```sh theme={null}
      conda search python
      ```

      This downloads a fresh copy of the repodata, which should resolve the problem.
    * If none of the above options work, [open an issue](https://github.com/ContinuumIO/anaconda-issues/issues) detailing the error.
  </TroubleshootSolution>
</Troubleshoot>

<Troubleshoot>
  <TroubleshootTitle>
    ### Trouble logging in to Package Security Manager (On-prem) in Navigator
  </TroubleshootTitle>

  <TroubleshootCause>
    Login issues or inability to interact with Package Security Manager (On-prem) can be caused by stale authentication tokens or conflicting channel configurations in Navigator's config files.
  </TroubleshootCause>

  <TroubleshootSolution>
    If you are having issues logging in or know you're logged in but cannot interact with Package Security Manager (On-prem), try the following solution:

    1. Set `logged_api_url`, `anaconda_server_token`, and `anaconda_server_token_id` in the Navigator config file (`anaconda-navigator.ini`) to **None**.

           <Note>
             The `token` and `token_id` config variable names have been updated from `team_edition_token` to `anaconda_server_token` and `team_edition_token_id` to `anaconda_server_token_id` as of Navigator Version 2.4.0. If you downgrade your Navigator application to a version older than 2.4.0, you must manually change these variable names back to their previous versions within your `anaconda-navigator.ini` file.
           </Note>

    2. Remove the `channel_alias:` entry from the conda configuration file (`.condarc`).

    3. Try signing in again.
  </TroubleshootSolution>
</Troubleshoot>

<Troubleshoot>
  <TroubleshootTitle>
    ### VS Code is not appearing on the Navigator Home tab
  </TroubleshootTitle>

  <TroubleshootCause>
    Anaconda Navigator launches applications using their executable files. Verify that VS Code's executable file is located in the correct directory (based on your OS and installation):

    <CodeGroup>
      ```sh Windows User-Only Installation theme={null}
      C:\Users\User\AppData\Local\Programs\Microsoft VS Code
      ```

      ```sh Windows System-Wide Installation theme={null}
      C:\Program Files\Microsoft VS Code
      ```

      ```sh macOS theme={null}
      /Applications
      ```

      ```sh Linux-64 theme={null}
      /usr/share/code
      ```
    </CodeGroup>
  </TroubleshootCause>

  <TroubleshootSolution>
    There are two options for solving this issue:<br /><br />

    <AccordionGroup>
      <Accordion title="Ensure that executable is installed in the default location">
        Reinstall VS Code to ensure that executable is installed in the default location.

        1. Close Navigator.

        2. Uninstall (if necessary) and reinstall [VS Code](https://code.visualstudio.com/).

                   <Note>
                     On macOS, make sure the VS Code application is moved from your Downloads folder to your Applications folder.
                   </Note>

        3. Re-open Navigator.
      </Accordion>

      <Accordion title="Edit VS Code's path in your Navigator user preferences">
        If you have installed VS Code to a different location than the default, edit VS Code's path in your Navigator user preferences.

        1. Open the Anaconda Navigator Preferences dialog from the top menu bar (such as **File** > **Preferences** or **Anaconda Navigator** > **Preferences**).

        2. Scroll down to the VS Code path setting.

        3. Enter the path to the installation of VS Code you would like Anaconda Navigator to use. This may be similar to examples above, especially if you have a user-specific installation you would rather use over your system-wide installation.

                   <Note>
                     You do not need to enter the name of the executable file itself. Just the path to the folder that contains that file.
                   </Note>

        4. Close and reopen Navigator.
      </Accordion>
    </AccordionGroup>
  </TroubleshootSolution>
</Troubleshoot>

<Troubleshoot>
  <TroubleshootTitle>
    ### Anaconda Navigator fails to start and gives Permission denied error
  </TroubleshootTitle>

  <TroubleshootCause>
    After installation, Anaconda Navigator may fail to start and give you a "Permission denied" error on the anaconda-client configuration file (`/.continuum/anaconda-client/config.yaml`). This error is likely due to `anaconda-client` being installed with admin rights, which leads to incorrect user permissions for the `anaconda-client` config file.
  </TroubleshootCause>

  <TroubleshootSolution>
    You can do a few things to solve this. They are listed from most straightforward to most complex.<br /><br />

    <AccordionGroup>
      <Accordion title="Delete your .continuum folder">
        1. Back up your `.config.yaml` file to a different location.
        2. Delete your `.continuum` folder.
        3. Start Navigator again.
        4. Copy your saved `.config.yaml` file back into `/.continuum/anaconda-client`.
      </Accordion>

      <Accordion title="Uninstall and reinstall without admin privileges">
        [Uninstall Anaconda](/getting-started/anaconda/uninstall) and then [reinstall Anaconda](/getting-started/anaconda/install/overview) without admin privileges.
      </Accordion>

      <Accordion title="Manually change the .continuum folder's user permissions">
        <Note>
          You will need administrator privileges to do this.
        </Note>

        <Tabs>
          <Tab title="Windows">
            1. Search for "powershell".
            2. Right-click the Windows PowerShell app and click **Run as administrator**.
            3. Run the following command:

               ```
               icacls C:\Users\<USERNAME>\.continuum /grant:r <USERNAME>:(i,f) /t
               ```

                           <Comments>
                             Replace \<USERNAME> with your username.
                           </Comments>
          </Tab>

          <Tab title="macOS/Linux ">
            1. Open your terminal application.
            2. Run the following command:

               ```sh theme={null}
               sudo chmod 766 /.continuum
               ```
          </Tab>
        </Tabs>
      </Accordion>
    </AccordionGroup>
  </TroubleshootSolution>
</Troubleshoot>

<Troubleshoot>
  <TroubleshootTitle>
    ### Navigator gives 'Email verification failed' error 403
  </TroubleshootTitle>

  <TroubleshootCause>
    Users with unverified Anaconda.org email addresses can no longer access the API that Navigator and Anaconda Client use to communicate with Anaconda.org. Navigator 2.5.0+ now catches this error and logs you out of your Anaconda.org connection.
  </TroubleshootCause>

  <TroubleshootSolution>
    To connect to Anaconda.org again through Navigator, [update your Navigator version](/tools/anaconda-navigator/update-navigator) or verify your Anaconda.org account.<br /><br />

    **Verify your anaconda.org account**<br /><br />

    To fully resolve the issue, we recommend verifying your account on Anaconda.org:

    1. Log in to your Anaconda.org account.
    2. If your email is unverified, you will be prompted to verify it.
    3. Click **Resend Confirmation Email**.
    4. Follow the instructions in the email you receive to complete the verification process.
  </TroubleshootSolution>
</Troubleshoot>

<Troubleshoot>
  <TroubleshootTitle>
    ### Navigator fails to start due to "Could not load the Qt platform plugin "xcb" in "" even though it was found" error
  </TroubleshootTitle>

  <TroubleshootCause>
    In the CentOS 7 Linux operating system, Orange3 is missing some graphics libraries required by Qt, a framework that Orange Canvas requires to work. These missing dependencies cause an error when starting Navigator: "Could not load the Qt platform plugin "xcb" in "" even though it was found. This application failed to start because no Qt platform plugin could be initialized."
  </TroubleshootCause>

  <TroubleshootSolution>
    1. Open a terminal application.
    2. Install the missing system libraries and run updates:

       ```sh theme={null}
       sudo yum install xcb-util-wm xcb-util-image xcb-util-keysyms xcb-util-renderutil
       sudo yum update
       ```

    Once these libraries are installed and updated, Orange3 should launch correctly on CentOS 7 and the above error should no longer appear when opening Navigator with Orange3 installed.
  </TroubleshootSolution>
</Troubleshoot>

<Troubleshoot>
  <TroubleshootTitle>
    ### Disable Anaconda.com login reminder
  </TroubleshootTitle>

  <TroubleshootCause>
    In Navigator versions 2.5.0 and later, a dialog appears every hour (or every 24 hours as of version 2.6.2) to remind users to log in to Anaconda.com, if they are not already logged in. This can be disruptive to users who do not want to log in to Anaconda.com.
  </TroubleshootCause>

  <TroubleshootSolution>
    There are a few ways to disable the Anaconda.com login reminder, depending on your version of Navigator:

    <Tabs>
      <Tab title="2.6.1 and later">
        Work in [offline mode](/tools/anaconda-navigator/tutorials/offline-mode) or [log in to another repository](/tools/anaconda-navigator/tutorials/connecting-to-other-repos).
      </Tab>

      <Tab title="2.5.2 to 2.6.0">
        1. [Open the Navigator configuration file](/tools/anaconda-navigator/tutorials/editing-config-files).
        2. Edit the `cloud_login_popup_state` to be `0` in the `[internal]` section of the configuration file.

           ```sh theme={null}
           [internal]
           anaconda_toolbox_installed = True
           cloud_login_popup_state = 0
           ```
      </Tab>

      <Tab title="2.5.0">
        1. [Open the Navigator configuration file](/tools/anaconda-navigator/tutorials/editing-config-files).
        2. Edit the `welcome_state` to be `0` in the `[internal]` section of the configuration file.

           ```sh theme={null}
           [internal]
           welcome_state = 0
           ```
      </Tab>
    </Tabs>
  </TroubleshootSolution>
</Troubleshoot>

<Troubleshoot>
  <TroubleshootTitle>
    ### Update popup not automatically appearing
  </TroubleshootTitle>

  <TroubleshootCause>
    If you are not automatically prompted to update Navigator upon sign in, there can be several reasons why:

    * The dialog has been hidden
    * Your package index is out of sync
    * `defaults` is missing from your channels list
  </TroubleshootCause>

  <TroubleshootSolution>
    <AccordionGroup>
      <Accordion title="The dialog has been hidden">
        You might have selected *Do not show again* in the **Update** popup. If this is the only reason your update popup is failing to appear, you should still see the **Update now** option beside Connect. To update, click **Update now.**

        To have the **Update** popup appear automatically again:

        1. Open **Preferences** from the **File** or **Anaconda Navigator** menu.
        2. Deselect **Hide update dialog on startup**.
      </Accordion>

      <Accordion title="Your package index is out of sync">
        Navigator fails to recognize an update is available if your package table is not properly updated. To update your package table, click **Environments**, then **Update index…**.
      </Accordion>

      <Accordion title="defaults is missing from your channels list">
        <Note>
          This issue specifically impacts users without a subscription to our premium repository.
        </Note>

        Not having `defaults` added to your channels list can also cause Navigator's Update popup to fail to appear.

        To add `defaults` to your channels list:

        1. Click **Channels** on the **Home** or **Environments** page.
        2. Click **Add**.
        3. Enter `defaults`, then press Enter (Windows)/Return (Mac) on your keyboard.
        4. Click **Update channels**.
        5. Close and reopen Navigator.
      </Accordion>
    </AccordionGroup>
  </TroubleshootSolution>
</Troubleshoot>

<Troubleshoot>
  <TroubleshootTitle>
    ### Environment backup not working in Navigator with Unable to create requested file error
  </TroubleshootTitle>

  <TroubleshootCause>
    An update to the environment export option in conda v25.7.0 is incompatible with the existing Navigator implementation for backing up environments.
  </TroubleshootCause>

  <TroubleshootSolution>
    Upgrade conda to the latest version by running the following command:

    ```sh theme={null}
    conda update --name base conda
    ```

    Confirm your installed version of conda by running the following command:

    ```sh theme={null}
    conda --version
    ```
  </TroubleshootSolution>
</Troubleshoot>