Issues launching or initializing#

If you are having problems launching Anaconda Navigator, follow these steps.

If you cannot launch the Anaconda Navigator desktop app, you can still launch it from the terminal or an Anaconda Prompt with anaconda-navigator.

Permissions issues#

If you have permissions issues, there may be a problem with the licenses directory, .continuum. Open a terminal or Anaconda Prompt and delete the .continuum directory. Run rm -rf ~/.continuum on macOS and Linux and rd /s .continuum on Windows.

Then relaunch Navigator from the desktop app, terminal, or Anaconda Prompt.

Other options#

If removing the licenses directory does not resolve the issue, manually update Navigator from a terminal or an Anaconda Prompt:

conda update anaconda-navigator

If you have updated Navigator and still have problems, remove Anaconda Navigator, then reinstall from the terminal or Anaconda Prompt:

conda remove anaconda-navigator
conda install anaconda-navigator

If none of the above work, please reset the Anaconda Navigator configuration back to default values:

anaconda-navigator --reset

PermissionError on macOS Catalina#

MacOS Catalina users may experience permission errors where the system does not prompt you for permission to folders requiring access.

First, update Navigator.

conda update anaconda-navigator

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

import os
# Replace <DIRECTORY> with the folder you need access to.

Access denied error#

This is caused by a lock file that sometimes gets stuck and isn’t removed when it should be.

In Anaconda Prompt or a terminal, run:

conda update conda
conda update anaconda-navigator
conda update navigator-updater
anaconda-navigator --reset

The last command is the key to fixing the issue, as it removes the lock file causing the problem.

Trouble logging in to the Anaconda Server connection in Navigator#

If you are having issues logging in or know you’re logged in but cannot interact with Anaconda Server, try the following steps:

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


    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 Version 2.4.0. If you downgrade your Navigator application to a version older than 2.3.0, you will need to manually change these variable names back to their older versions within your anaconda-navigator.ini file.

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

  3. Try signing in again.

VS Code is not appearing on my Anaconda Navigator home tab#

Anaconda Navigator displays and launches VS Code, and many other applications, through that application’s executable file. VS Code’s installation should have placed the executable in a specific directory where Anaconda Navigator is programmed to look. For example:

  • Windows User-Only Installation: C:\\Users\\User\\AppData\\Local\\Programs\\Microsoft VS Code

  • Windows System-Wide Installation: C:\\Program Files\\Microsoft VS Code

  • Linux-64: /usr/share/code

  • macOS: /Applications

Reinstall VS Code to ensure that executable is installed in the default location.

  1. Close Anaconda Navigator.

  2. Uninstall (if necessary) and reinstall VS Code.


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

  3. Re-open Anaconda Navigator.

Another option, if you have installed VS Code to a different location than the default, is to edit VS Code’s path in your Anaconda 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 the examples above, especially if you have a user-specific installation you would rather use over your system-wide installation.


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

  4. Close and reopen Anaconda Navigator.

Anaconda Navigator fails to start and gives Permission denied error#

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. This will lead to incorrect user permissions for the anaconda-client config file.


You can do a few things to solve this. They are listed from most straightforward to most complex.

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.

Uninstall and reinstall without admin privileges

Uninstall Anaconda and then reinstall Anaconda without admin privileges.

Manually change the .continuum folder’s user permissions

You will need administrator privileges to do this.

To change user permissions on Windows:

  1. Search for “powershell”.

  2. Right-click the Windows PowerShell app and select Run as administrator.

  3. Run the following command:

    #Replace <USERNAME> with your username
    icacls C:\Users\<USERNAME>\.continuum /grant:r <USERNAME>:(i,f) /t

To change user permissions on macOS or Linux

  1. Open your terminal application.

  2. Run the following command:

    sudo chmod 766 /.continuum

CentOS 7: Orange3 fails to launch after installation#


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


  1. Open a terminal application.

  2. Install the missing system libraries and run updates by running the following commands:

    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.