Troubleshooting - Anaconda

If you encounter an issue that is not listed here, you can obtain support for Anaconda through the Anaconda community forums. For Anaconda installation or technical support options, visit our support offerings page.

The Navigator and Anaconda.org troubleshooting pages have been consolidated into this page. Click to view their sections:

Navigator
Anaconda.org

Most common issues

Conda: Channel is unavailable/missing or package itself is missing

Cause

Solution

Receiving a 403 error from an Anaconda channel

Cause

A 403 errors is a generic Forbidden error issued by a web server in the event the client is forbidden from accessing a resource.The 403 error you are receiving may look like the following:

Collecting package metadata (current_repodata.json): failed

UnavailableInvalidChannel: The channel is not accessible or is invalid.
  channel name: pkgs/main
  channel url: https://repo.anaconda.com/pkgs/main
  error code: 403

You will need to adjust your conda configuration to proceed.
Use `conda config --show channels` to view your configuration's current state,
and use `conda config --show-sources` to view config file locations.
There are several reasons a 403 error could be received:

There are a few possible reasons for receiving this error:

The user has misconfigured their channels in their configuration. For example, the secure location where the token is stored was accidentally deleted (most common).
A firewall or other security device or system is preventing user access (second most common)
We are blocking their access because of a potential terms of service violation (third most common)

Solution

First, run the following to undo your configuration:
```
conda config --remove-key default_channels
```
When conda is first installed, the default channels it uses to install packages are https://repo.anaconda.com/main and https://repo.anaconda.com/r (as well as https://repo.anaconda.com/msys2 for Windows operating systems).
If your other channels require a token, install or upgrade the conda-token tool by running the following command:
```
conda install --freeze-installed conda-token
```
Lastly, re-apply the token and configuration settings:
```
# Replace <TOKEN> with your token
conda token set <TOKEN>
```

If this doesn’t resolve the issue, Anaconda recommends consulting our Terms of Service error page.

HTTP 000 CONNECTION FAILED

Cause

Solution

If you receive this error message, first run the following command:

conda config --set ssl_verify false

(Package Security Manager users) If necessary, install conda-token by running the following command:

conda install conda-token --name base

(Package Security Manager users) Ensure the token verification step ignores SSL errors by running the following command:

# Replace <TOKEN> with your token
conda token set --no-ssl-verify <TOKEN>

You may see the following warning, though you can safely ignore it:

/Users/<USERNAME>/Applications/miniconda3/lib/python3.7/site-packages/urllib3/connectionpool.py:1020: InsecureRequestWarning: Unverified HTTPS request is being made to host 'repo.anaconda.cloud'. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage#ssl-warnings
InsecureRequestWarning,

Conda: command not found on macOS/Linux

Cause

Solutions

If your install is new, close and reopen your terminal application. If you want your terminal to remain open, you can source your ~/.zshrc file (in macOS) or ~/.bashrc file (in Linux). When you “source” a script, your terminal re-reads it and applies the changes, which usually only happens when the terminal is first opened.

source ~/.zshrc

To initialize conda in your current terminal, run the following command, depending on your operating system:

# Replace <PATH-TO-CONDA> with the file path to your conda installation
<PATH-TO-CONDA>/bin/conda init zsh

For example, if you installed Anaconda Distribution to the default location with the .sh installer (~/anaconda3/), your command would look like the following:

~/anaconda3/bin/conda init zsh

To see the value for auto_activate_base, run the following command:

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, run the following command:

# Replace <TRUE_OR_FALSE> with true or false
conda config --set auto_activate_base <TRUE_OR_FALSE>

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.

`conda update anaconda` command does not install the latest version of the `anaconda` metapackage

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.

Cause

Solution

Obtain a list of the conflicting packages by running conda update anaconda or conda install anaconda=2023.07.
Replace 2023.07 with the latest version number.
Enter n to cancel the installation or update.
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:

Remove the anaconda metapackage itself by running the following command:
```
conda remove anaconda
```
Update all currently installed packages by running the following command:
```
conda update --all
```

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

Remove the conflicting packages by running the following command for each one:
```
conda remove <PACKAGE>
```
Update to the latest version of the anaconda metapackage:
```
conda update anaconda
```

Recovering your Anaconda installation

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.

Solution

Download a new installer, then follow the instructions for your operating system.

Use the actual path, filename, and directory name for your installation.

Open a terminal application, such as Command Prompt.
Change your original installer’s name so you do not overwrite it:
```
move anaconda3 anaconda_old
```
Run the Anaconda.exe installer as usual and use robocopy to sync the directories:
```
robocopy anaconda_old anaconda3 /S
```
Delete your old Anaconda installation directory:
```
rd /s anaconda_old
```

Run conda list to view the packages from the previous installation.
Run conda info -e to list the environments created in the previous installation, which are now available in the new installation.

Channels list adding extra channels

Cause

Solution

Checking your current configurationTo 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.

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:

C:\Users\<USERNAME>\anaconda3
C:\Users\<USERNAME>\miniconda3
/Users/<USERNAME>/anaconda3
/Users/<USERNAME>/miniconda3
/opt/anaconda3
/opt/miniconda

Solving your issueThere are a few ways you can solve this issue, depending on how you use your .condarc file:

If you have write access to the installation directory .condarc file

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.

Locate the installer root .condarc file using conda config --show-sources.
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:
Use the --file flag to specify the path to the root .condarc file.
```
conda config --file <PATH/TO/YOUR/ROOT>/.condarc --add channels defaults
conda config --file <PATH/TO/YOUR/ROOT>/.condarc --remove channels <CHANNEL1> <CHANNEL2>
```
Example commands
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
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 in the official conda documentation.You can edit your .condarc manually using your preferred text editor, or by using the following conda CLI command:
# This command can add one channel at a time # Replace <CHANNEL> with the URL to your channel conda config --add default_channels <CHANNEL>
To remove a channel instead, replace --add with --remove.

Delete the installation directory .condarc file

If you 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.

If you continue to experience issues, please open a support ticket.

Anaconda Distribution issues

Using Anaconda behind a firewall or proxy

Corporate security policies may prevent a new Anaconda installation from downloading packages and other functionality that requires connecting to an external server. To make external connections, you may need to connect to a firewall/proxy. Additionally, your IT team may need to allow connections to https://anaconda.org and https://repo.anaconda.com, as these are the main package repositories.

Solution

To add the proxy information, you will need to add two entries to your .condarc file, located in the user’s home directory. This information should be made available by your IT team and may contain a username and password that is included in the URL. For more information, see configure conda for use behind a proxy server.Example .condarc file configuration:

channels:
  - defaults

proxy_servers:
  http: http://username:[[email protected]](/cdn-cgi/l/email-protection):8080
  https: https://username:[[email protected]](/cdn-cgi/l/email-protection):8443

In some situations, it may be necessary to export the HTTP_PROXY and HTTPS_PROXY environment variables.

set HTTP_PROXY=http://username:[[email protected]](/cdn-cgi/l/email-protection):8080
set HTTPS_PROXY=https://username:[[email protected]](/cdn-cgi/l/email-protection):8443

If these steps have not allowed connections, you should speak to your IT team to verify that security policies are not blocking connections to https://anaconda.com or https://repo.continuum.io.

InsecurePlatformWarning error

Cause

Solution

To resolve this, install the updated package ndg-httpsclient:

conda install ndg-httpsclient

When initially installing this package, you receive the SSL warning again. Once it is installed, the package will prevent the warnings.

Anaconda search error: not recognized as an internal or external command/unrecognized arguments

Cause

If anaconda-client is not installed and you search for a package on anaconda.org using the Anaconda search command…

# Replace <PACKAGE> with the name of a package you want to search for
anaconda search --package-type conda <PACKAGE>

…You will receive the following error message:

'anaconda' is not recognized as an internal or external command,
operable program or batch file.

Solution

To resolve the error:

Install anaconda-client by running the following command:
```
conda install anaconda-client
```

Search for a package:

# Replace <PACKAGE> with the name of the package you are looking for
anaconda search --package-type conda <PACKAGE>

Collecting package metadata (repodata.json): - Killed

Cause

When installing or searching for a package, you may see the process end abruptly with a “Killed” message:

$ conda install numpy
Collecting package metadata (current_repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with flexible solve.
Collecting package metadata (repodata.json): - Killed

This may be because your system lacks the sufficient disk space or memory to complete the process.

Solution

Linking problems when Python extensions are compiled with gcc

Cause

Solution

Error message: Unable to remove files

When trying to update or install packages with conda, you may see an error message such as:

Error: Unable to remove files for package: <PACKAGE>
Please close all processes running code from conda and try again.

Cause

Solution

Before updating or installing any packages with conda, be sure to terminate any running Anaconda processes, such as Navigator, Spyder, or IPython.You can also force the installation of the package:

# Replace <PACKAGE> with the name of the package you want to install
conda install --force-reinstall <PACKAGE>

Using 32- and 64-bit libraries and CONDA_FORCE_32BIT

To work with both 32- and 64-bit libraries, Anaconda recommends that you have two separate installs: Anaconda32 and Anaconda64 or Miniconda32 and Miniconda64.

Solution

When working with both versions, add the path to your installer files to the PATH.To get the information about conda, including your PATH, run the following command:

conda info -a

Always specify which version you want to work with because mixing 32- and 64-bit packages can cause problems in your environment.
Using force_32bit is not recommended because it forces 32-bit packages to be installed in the environment, but does not force 32-bit libraries to load at runtime.
force_32bit should be used only when running conda-build to build 32-bit packages on a 64-bit system.

Anaconda Distribution installation issues

Cannot get conda to run after installing

In macOS or Linux, you may get “conda not found” or “conda is not recognized as an internal or external command” or a similar message, and you cannot execute conda in a terminal window regardless of what path you are on. This will not happen in Windows if you use the Anaconda Prompt terminal dialog.

Cause

Solution

”This package is incompatible with this version of macOS” error when running a .pkg installer on OSX

When running the .pkg installer, you may encounter this error during the “Installation” step:

Cause

Solution

Anaconda installer download problems

Cause

Solution

Download and install the smaller Miniconda (between 70 and 100 MB).
Download and install the remaining packages in Anaconda by using the following command:
```
conda install anaconda
```

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.

Error message on Miniconda install: Already installed

Cause

Solution

For macOS and Linux, download and install the appropriate Miniconda for your operating system from the Miniconda download page using the --force or -f option by running the following command:

# Replace the name of the installer if you need a different version or operating system
bash ~/Downloads/Miniconda3-latest-MacOSX-x86_64.sh -f

Make sure to install to the same location as your existing install so it overwrites the core conda files and does not install duplicates in a new folder.

”The installation failed” message when running a .pkg installer on OSX

Cause

When running the .pkg installer, you may see this message at the end of the installation:

If so, check for the following:

Open your /var/log/install.log file and check whether the most recent lines show errors following a call to conda init --all.
```
open /var/log/install.log
```
In your $HOME directory, check whether the owner of your shell config files is root:
```
ls -la ~/.bash_profile ~/.config/fish/config.fish ~/.tcshrc ~/.xonshrc ~/.zshrc
```

Solution

If both of the above are true, do the following:

Change the owner of your shell config files to your current user:

sudo chown -R $USER ~/.bash_profile ~/.config/fish/config.fish ~/.tcshrc ~/.xonshrc ~/.zshrc

Uninstall the previous installation. Then re-run the installer, making sure to select the Install for me only option.

Windows-specific Anaconda Distribution issues

After installing on Windows, the Anaconda Prompt and Anaconda Navigator shortcuts do not appear in the Windows Start menu.

Cause

Solution

Windows error: Failed to create Anaconda menus or Failed to add Anaconda to the system PATH

During installation on a Windows system, a dialog box 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.

Solution

Anaconda interfering with other software on Windows

Cause

Solution

Files left behind after uninstalling Anaconda on Windows

Cause

Solution

Spyder errors or failure to launch on Windows

Cause

Solution

Close and relaunch Spyder and see if the problem remains.
Open the Start Menu and then click Reset Spyder Settings and see if the problem remains.
Close Spyder and relaunch it from Anaconda Prompt with the following command:
```
spyder
```
Delete the directory .spyder2 and then repeat the first item in this list. Depending on your version of Windows, .spyder2 may be in C:\Documents and Settings\<USERNAME> or in C:\Users\<USERNAME>.

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

Uninstaller requests admin privileges on Windows

After installing Anaconda or Miniconda as a non-administrative user on Windows, uninstalling may prompt for administrative privileges.

Cause

Solution

Windows permission errors when installing from Favorites folder

Cause

Solution

Trouble with activation on PowerShell on Windows

Some users might run into the following backtrace on Windows:

File "C:\Users\damia\Miniconda3\lib\site-packages\conda\activate.py", line 550, in _replace_prefix_in_path
assert last_idx is not None
AssertionError

Solution

Open a Command Prompt window.
Navigate to where you installed conda. The following command shows the default:
```
cd C:\Users\<USERNAME>
```
Run the following command:
```
python -m conda init
```
Close the Command Prompt window.

If the above method didn’t work, try running:

conda update conda

macOS-specific Anaconda Distribution issues

”Conda: command not found” in zsh shell

Cause

Solution

To initialize conda for zsh:

Open a terminal application and run the following command:
```
# Replace <PATH-TO-CONDA> with the file path to your conda installation
<PATH-TO-CONDA>/bin/conda init zsh
```
For example, if you installed Miniconda to the default location with the .sh installer (~/miniconda3/), the command would be:
```
~/miniconda3/bin/conda init zsh
```
Close and reopen your terminal application.

Segmentation fault on package import with macOS Python 3.7 interpreter

In CPython < 3.8, using python3-config to determine a linking command line to compile an extension module will cause that extension module to segfault upon import. python3-config does provide command-line flags, but for the different purpose of embedding a Python interpreter.

Cause

Solution

You should only use python*-config --ldflags when linking to an interpreter library (either static or shared).

Action	Python < 3.8	Python >= 3.8
Get command line to link to extension module	`python -c "import sysconfig; print(sysconfig.get_config_var('LDSHARED'))"`	`python3-config --ldflags`
Get command line to embed Python interpreter	`python3-config --ldflags`	`python3-config --ldflags --embed`

python3-config doesn’t include the command/compiler name, whereas the sysconfig way does. This works provided none of your arguments have spaces:

python -c "import sysconfig; print(' '.join(sysconfig.get_config_var('LDSHARED').split(' ')[1:]))"

Linux-specific Anaconda Distribution issues

Missing libgomp on Power8

If the Python command import numpy fails, the system is likely missing the libgomp system library.

Cause

Solution

Check whether the system is missing libgomp by running the following command:

conda inspect linkages --name root numpy

If libgomp.so.1 is listed in the not found: section, it must be installed.Install libgomp on Ubuntu by running the following command:

apt install libgomp1

Install libgomp on Red Hat Enterprise Linux (RHEL) or CentOS by running the following command:

yum install libgomp

Anaconda on Power8 reports “can not execute binary file”

Cause

Solution

Anaconda Distribution installation failed with “‘ascii’ codec can’t encode character ‘xe4’ in position 96” error

Cause

Solution

Add the following to your current shell config file (for example, .bashrc or .zshrc):

export LANGUAGE="en_US.utf8"
export LC_ALL="en_US.utf8"
export LC_CTYPE="en_US.utf8"
export LANG="en_US.utf8"

If your installer partially ran before failing, your installation directory may not be empty. If so, delete your installation directory.
Rerun your installer.

Navigator issues

Navigator fails to update to version 2.6.4

Cause

Solution

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

conda list anaconda-toolbox

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

Close Navigator, if open.
Open Anaconda Prompt (Terminal on macOS/Linux).

Run the following command:

conda install --name base anaconda-navigator=2.6.4 anaconda-toolbox=4.1.0

Enter y to approve the package changes.
Once your base environment is updated, it is safe to close Anaconda Prompt/Terminal.
Reopen Navigator.

Once this dependency conflict is resolved, any future updates to Navigator can be accomplished as usual. See Updating Navigator.

Navigator error on start up

Cause

Solution

Issues launching or initializing

Cause

Solution

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:
```
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:
rd /s .continuum
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:
```
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:
```
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:
```
anaconda-navigator --reset
```

PermissionError on macOS Catalina

Cause

Solution

Update Navigator by opening Anaconda Prompt (Terminal on macOS/Linux) and running the following command:
```
conda update --name base anaconda-navigator
```
Once updated, have Navigator generate the permissions prompt by launching Spyder and running the following in the console:
```
# Replace <DIRECTORY> with the folder you need access to
import os
os.listdir('<DIRECTORY>')
```

Access denied error

Cause

Solution

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

conda update --name base conda anaconda-navigator navigator-updater
anaconda-navigator --reset

Navigator buttons are missing

Cause

Solution

Run Update Index from the Environments page of Navigator.
Quit and restart Navigator.

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

Confirm that your .condarc file is not corrupt. Specifically confirm that your channel settings contain defaults.
Open Anaconda Prompt (Terminal on macOS/Linux) and run the following command:
```
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 detailing the error.

Trouble logging in to the Package Security Manager On-prem connection in Navigator

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:

Solution

VS Code is not appearing on the Navigator Home tab

Cause

Solution

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

Cause

Solution

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

Back up your .config.yaml file to a different location.
Delete your .continuum folder.
Start Navigator again.
Copy your saved .config.yaml file back into /.continuum/anaconda-client.

Uninstall and reinstall without admin privilegesUninstall Anaconda and then reinstall Anaconda without admin privileges.Manually change the .continuum folder’s user permissionsYou will need administrator privileges to do this.

Search for “powershell”.
Right-click the Windows PowerShell app and select Run as administrator.

Run the following command:

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

Navigator gives ‘Email verification failed’ error 403

Cause

Solution

Navigator fails to start due to “Could not load the Qt platform plugin “xcb” in "" even though it was found” error

Cause

Solution

Open a terminal application.
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.

Cause

Solution

Cause

Solution

Anaconda.org issues

Captcha not appearing when trying to create an Anaconda.org account on Firefox

The captcha at the bottom of the Sign In panel on Anaconda.org sometimes fails to appear on Firefox browsers.

Cause

Solution

”URI no longer exists and has been permanently removed” 410 error when attempting to upload notebooks or environments to Anaconda.org

Cause

Solution

Reference

​Most common issues

​Conda: Channel is unavailable/missing or package itself is missing

​Receiving a 403 error from an Anaconda channel

​HTTP 000 CONNECTION FAILED

​Conda: command not found on macOS/Linux

​conda update anaconda command does not install the latest version of the anaconda metapackage

​Recovering your Anaconda installation

​Channels list adding extra channels

​Anaconda Distribution issues

​Using Anaconda behind a firewall or proxy

​InsecurePlatformWarning error

​Anaconda search error: not recognized as an internal or external command/unrecognized arguments

​Collecting package metadata (repodata.json): - Killed

​Linking problems when Python extensions are compiled with gcc

​Error message: Unable to remove files

​Using 32- and 64-bit libraries and CONDA_FORCE_32BIT

​Anaconda Distribution installation issues

​Cannot get conda to run after installing

​”This package is incompatible with this version of macOS” error when running a .pkg installer on OSX

​Anaconda installer download problems

​Error message on Miniconda install: Already installed

​”The installation failed” message when running a .pkg installer on OSX

​Windows-specific Anaconda Distribution issues

​Cannot see Anaconda menu shortcuts after installation on Windows

​Windows error: Failed to create Anaconda menus or Failed to add Anaconda to the system PATH

​Anaconda interfering with other software on Windows

​Files left behind after uninstalling Anaconda on Windows

​Spyder errors or failure to launch on Windows

​Uninstaller requests admin privileges on Windows

​Windows permission errors when installing from Favorites folder

​Trouble with activation on PowerShell on Windows

​macOS-specific Anaconda Distribution issues

​”Conda: command not found” in zsh shell

​Segmentation fault on package import with macOS Python 3.7 interpreter

​Linux-specific Anaconda Distribution issues

​Missing libgomp on Power8

​Anaconda on Power8 reports “can not execute binary file”

​Anaconda Distribution installation failed with “‘ascii’ codec can’t encode character ‘xe4’ in position 96” error

​Navigator issues

​Navigator fails to update to version 2.6.4

​Navigator error on start up

​Issues launching or initializing

​PermissionError on macOS Catalina

​Access denied error

​Navigator buttons are missing

​Trouble logging in to the Package Security Manager On-prem connection in Navigator

​VS Code is not appearing on the Navigator Home tab

​Anaconda Navigator fails to start and gives Permission denied error

​Navigator gives ‘Email verification failed’ error 403

​Navigator fails to start due to “Could not load the Qt platform plugin “xcb” in "" even though it was found” error

​Disable Anaconda.com login reminder

​Update popup not automatically appearing

​Anaconda.org issues

​Captcha not appearing when trying to create an Anaconda.org account on Firefox

​”URI no longer exists and has been permanently removed” 410 error when attempting to upload notebooks or environments to Anaconda.org

Most common issues

Conda: Channel is unavailable/missing or package itself is missing

Receiving a 403 error from an Anaconda channel

HTTP 000 CONNECTION FAILED

Conda: command not found on macOS/Linux

`conda update anaconda` command does not install the latest version of the `anaconda` metapackage

Recovering your Anaconda installation

Channels list adding extra channels

Anaconda Distribution issues

Using Anaconda behind a firewall or proxy

InsecurePlatformWarning error

Anaconda search error: not recognized as an internal or external command/unrecognized arguments

Collecting package metadata (repodata.json): - Killed

Linking problems when Python extensions are compiled with gcc

Error message: Unable to remove files

Using 32- and 64-bit libraries and CONDA_FORCE_32BIT

Anaconda Distribution installation issues

Cannot get conda to run after installing

”This package is incompatible with this version of macOS” error when running a .pkg installer on OSX

Anaconda installer download problems

Error message on Miniconda install: Already installed

”The installation failed” message when running a .pkg installer on OSX

Windows-specific Anaconda Distribution issues

Cannot see Anaconda menu shortcuts after installation on Windows

Windows error: Failed to create Anaconda menus or Failed to add Anaconda to the system PATH

Anaconda interfering with other software on Windows

Files left behind after uninstalling Anaconda on Windows

Spyder errors or failure to launch on Windows

Uninstaller requests admin privileges on Windows

Windows permission errors when installing from Favorites folder

Trouble with activation on PowerShell on Windows

macOS-specific Anaconda Distribution issues

”Conda: command not found” in zsh shell

Segmentation fault on package import with macOS Python 3.7 interpreter

Linux-specific Anaconda Distribution issues

Missing libgomp on Power8

Anaconda on Power8 reports “can not execute binary file”

Anaconda Distribution installation failed with “‘ascii’ codec can’t encode character ‘xe4’ in position 96” error

Navigator issues

Navigator fails to update to version 2.6.4

Navigator error on start up

Issues launching or initializing

PermissionError on macOS Catalina

Access denied error

Navigator buttons are missing

Trouble logging in to the Package Security Manager On-prem connection in Navigator

VS Code is not appearing on the Navigator Home tab

Anaconda Navigator fails to start and gives Permission denied error

Navigator gives ‘Email verification failed’ error 403

Navigator fails to start due to “Could not load the Qt platform plugin “xcb” in "" even though it was found” error

Disable Anaconda.com login reminder

Update popup not automatically appearing

Anaconda.org issues

Captcha not appearing when trying to create an Anaconda.org account on Firefox

”URI no longer exists and has been permanently removed” 410 error when attempting to upload notebooks or environments to Anaconda.org