Troubleshooting

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.

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.

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 terminal or Anaconda Prompt:

conda remove anaconda-navigator
conda install anaconda-navigator

If none of the above work, please reset 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, you can have Navigator generate the permissions prompt for the first time by launching Spyder and running something like this in the console (you can replace Desktop with Downloads/Documents folder depending on which you need access to):

import os
os.listdir('Desktop')

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.

RStudio fails to install in Navigator 1.6.2 if special characters are in install path

This is a known issue in Navigator 1.6.2 on Windows 7 64-bit.