ℹ️ Skipped - page is already crawled
| Filter | Status | Condition | Details |
|---|---|---|---|
| HTTP status | PASS | download_http_code = 200 | HTTP 200 |
| Age cutoff | PASS | download_stamp > now() - 6 MONTH | 0 months ago |
| History drop | PASS | isNull(history_drop_reason) | No drop reason |
| Spam/ban | PASS | fh_dont_index != 1 AND ml_spam_score = 0 | ml_spam_score=0 |
| Canonical | PASS | meta_canonical IS NULL OR = '' OR = src_unparsed | Not set |
| Property | Value |
|---|---|
| URL | https://www.anaconda.com/docs/reference/troubleshooting |
| Last Crawled | 2026-04-12 20:01:15 (12 hours ago) |
| First Indexed | 2025-02-28 21:25:10 (1 year ago) |
| HTTP Status Code | 200 |
| Meta Title | Troubleshooting - Anaconda |
| Meta Description | null |
| Meta Canonical | null |
| Boilerpipe Text | This page includes common troubleshooting topics for Anaconda products. Issues are grouped by product and category.
If you encounter an issue or bug that isn’t covered on this page, you can ask for help in the
Anaconda community forums
or
open a support ticket
.
Most common issues
command not found: conda
Cause
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.
These issues primarily occur on macOS/Linux computers. Anaconda Distribution and Miniconda installations on Windows include
Anaconda Prompt
, which opens with conda initialized by default.
Solution
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.
If you don’t want to close your CLI, you can also use one of the following
source
commands to refresh your shell:
source
~/.bashrc
You can also initialize conda directly from its
bin
directory:
<
PATH_TO_CONDA
>
/bin/conda init
Set auto_activate_base to true
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
to
true
, run the following command:
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
.
Use a shell that conda supports
For information on which shells conda supports, see
Conda activate
in the official conda documentation.
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
or
Miniconda
.
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
.
CondaHTTPError: HTTP 400 Bad Request for URL
Cause
A
400 Bad Request
error typically means there’s a typo in your channel URL. When you pass a full URL with the
-c
flag, conda doesn’t validate whether the channel exists—it just makes the request. If the path is wrong, the server returns a 400 error.
Solution
Double-check your channel URL for typos and try again.
UnavailableInvalidChannel: HTTP 404 Not Found for channel
Cause
A
404 Not Found
error means the channel you specified doesn’t exist. This is usually caused by a typo in the channel name, either in your
.condarc
file or when using the
-c
flag.
Solution
Check your command for typos and try again.
To see which channels are currently configured, run:
conda
config
--show
channels
If you see a misspelled channel in your configuration, remove it with:
conda
config
--remove
channels
<
MISSPELLED_CHANNE
L
>
For help adding adding and removing channels to your
.condarc
file, see
Managing channels
.
PackagesNotFoundError: The following packages are not available from current channels
Cause
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.
Solution
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
.
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
or your
Anaconda Platform channels
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.
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
.
Add the missing channel to your .condarc file
Add the missing channel to your .condarc file
. 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.
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.
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.
DirectoryNotACondaEnvironmentError: The target directory exists, but it is not a conda environment
Cause
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.
Solution
Activate your
base
environment or another environment:
# Activate your base environment
conda
activate
# Activate an environment by name
conda
activate
<
ENV_NAM
E
>
EnvironmentNotWriteableError
Cause
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
.
Solution
Create your own environment instead, in a directory you don’t need admin permissions to work in, such as your home directory:
conda
create
--name
<
ENV_NAM
E
>
--prefix
<
PATH_TO_USER_DIRECTOR
Y
>
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
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:
conda
create
--file
environment.yml
--prefix
<
PATH_TO_USER_DIRECTOR
Y
>
ModuleNotFoundError: No module named X
Cause
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.
Solution
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:
conda
info
--envs
An asterisk is displayed next to your currently active environment:
Environment list example
(
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
.
If your environment is missing the needed package, install it in your environment. For more information, see
Installing conda packages
.
Receiving a 403 Forbidden error from an Anaconda channel
Cause
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.
The 403 error you are receiving may look like the following:
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.
Solution
Run
anaconda token install
to issue and set a new token for yourself, then try again.
If the
403 Forbidden
error persists, ensure you are not blocked by a Terms of Service violation by consulting our
Terms of Service error
page.
If you believe you have been blocked in error, please
open a support ticket
.
HTTP 000 CONNECTION FAILED
Cause
This is generally caused by a proxy misconfiguration.
Solution
Follow instructions on
Using Anaconda behind a company proxy
to configure your proxy correctly.
conda update anaconda
command does not install the latest version of the
anaconda
metapackage
Cause
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.
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.
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
<
PACKAG
E
>
Update to the latest version of the
anaconda
metapackage:
conda
update
anaconda
Recovering your Anaconda installation
Cause
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.
Windows
macOS
Linux
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
Open a terminal application.
Change your original installer’s name so you do not overwrite it:
mv
anaconda3
anaconda_old
Install to same directory as your original installer:
# Replace <INSTALLER> the name of your installer file
bash
~/Downloads/
<
INSTALLE
R
>
rsync
-a
anaconda_old/
anaconda3/
Delete your old Anaconda installation directory:
rm
-rf
anaconda_old
Open a terminal application.
Change your original installer’s name so you do not overwrite it:
mv
anaconda3
anaconda_old
Install to same directory as your original installer:
# Replace <INSTALLER> the name of your installer file
bash
~/Downloads/
<
INSTALLE
R
>
rsync
-a
anaconda_old/
anaconda3/
Delete your old Anaconda installation directory:
rm
-rf
anaconda_old
Run
conda list
to view the packages from the previous installation.
Run
conda info --envs
to list the environments created in the previous installation, which are now available in the new installation.
Channels list adding extra channels
Cause
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
section of the official conda documentation.
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.
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.
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
Solution
There 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
Windows
Linux/macOS
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
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
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:
conda
config
--add
default_channels
<
CHANNE
L
>
To remove a channel instead, replace
--add
with
--remove
.
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.
Make sure that you always have at least one
.condarc
file with a
channels:
list defined. Conda requires this to function.
Locate the installation directory
.condarc
file using
conda config --show-sources
.
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.
You can view hidden files and folders using the following guidance for your operating system:
macOS
Linux
To view hidden files on macOS, use Shift+Cmd+. in your Finder.
To view hidden files on Linux, use Alt+. or Ctrl+H (depending on your file manager).
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.
If you continue to experience issues, please
open a support ticket
.
Uninstall.sh not found
Cause
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.
Solution
Use the following instructions to find your
uninstall.sh
file and use it:
Open a new Terminal window.
Run the following command to find your installation folder:
conda
info
--base
Check the contents of your installation folder for the
uninstall.sh
script:
ls
<
PATH/TO/INSTALLE
R
>
If your install is in your home directory (
\Users\<USERNAME>\
or
\home\<USERNAME>
), use the macOS/Linux
Basic uninstall
instructions.
If your install is in your
\opt\
folder, use the macOS/Linux
System uninstall
instructions.
If your install folder does not contain the
uninstall.sh
file, use the macOS/Linux
Manual uninstall
instructions.
Anaconda Distribution uninstall instructions
Miniconda uninstall instructions
Not receiving Anaconda.com account verification email
Cause
Your browser may have cached data from a previous signup session or authentication attempt, which can interfere with the verification email being triggered.
Alternatively, the verification email may have been sent but filtered to your spam, junk, or promotions folder by your email provider.
Solution
First, check your junk mailbox or any other folders where emails may be automatically filtered. If the email is not there, clear your browser cache and cookies, then try logging in again at
https://auth.anaconda.com/ui/login/
.
If you still do not receive the email, please
submit a support ticket
.
I can’t access my learning courses
Cause
Your browser session may not be properly synced with your subscription status, or cached authentication data may be outdated.
Solution
Clear your browser cache and cookies, then try accessing the courses again.
If the issue persists,
sign out completely
, then
sign back in
.
If you still cannot access your courses, navigate to
https://auth.anaconda.com/api/auth/sessions/whoami
, copy the contents displayed, and include them when you
submit a support ticket
.
Unable to reset Anaconda.com account password
Cause
Your email address must be verified before you can reset your password.
Solution
Follow the instructions in your verification email. If the verification link has expired, request a new verification email.
If you still have trouble resetting your password after verifying your account,
submit a support ticket
.
Subscribed to Academic plan but seeing Starter plan
Cause
This is expected behavior. The Academic plan is essentially the Starter plan, provided free of charge based on your status as a student.
Solution
No action is required. For details on what is included in your plan, see
Anaconda Pricing
.
Anaconda Distribution issues
Using Anaconda behind a firewall or proxy
Cause
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 might need to connect to a firewall/proxy. Additionally, your IT team might 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
InsecurePlatformWarning
appears only when the installed version of Python is older than version 2.7.9. This message warns only that the validity of the SSL connection is not being verified. It should not affect your package downloads.
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:
anaconda
search
--package-type
conda
<
PACKAG
E
>
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:
anaconda
search
--package-type
conda
<
PACKAG
E
>
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
Verify that you have enough disk space and memory on your system to install and use Anaconda packages. The minimum system requirements for Miniconda and Anaconda installers can be found in the
conda
user guide
.
Error message: Unable to remove files
Cause
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.
Generally, this is caused by a file lock issue.
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:
conda
install
--force-reinstall
<
PACKAG
E
>
Using 32- and 64-bit libraries and CONDA_FORCE_32BIT
Cause
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
--all
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.
Proxy request sent, not found
Cause
Your company likely has security policies or a firewall in place that prevent communications with external servers or certain URLs.
Solution
First, work with your IT team to allowlist connections to the following URLs:
https://anaconda.org
https://repo.anaconda.com
https://repo.anaconda.cloud
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.
Install
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
.
Installation issues
Anaconda installer download problems
Cause
The Anaconda installer files are large (over 600 MB), and some users have problems with errors and interrupted downloads when downloading large files.
Solution
Download Miniconda
Restart the download
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.
Download the large Anaconda installer file, and restart it if the download is interrupted or you need to pause it.
Windows
macOS/Linux
Chrome
Edge
Find the latest installer at
anaconda.com
, or an older installer at
repo.anaconda.com/archive
.
In Chrome, use Ctrl+J to open the Chrome download manager.
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.
Find the latest installer at
anaconda.com
, or an older installer at
repo.anaconda.com/archive
.
In Edge, click
Settings and more
.
Click
Downloads
to open the Downloads dialog.
From here, you can use the play, pause, and cancel buttons to control downloads in progress.
Go to
edge://downloads/all
to open the full page of recent downloads. From here, you can retry cancelled downloads.
Open a terminal window.
To download the file, use the following command:
# 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/
<
INSTALLE
R
>
To pause the download, use Ctrl+C.
While a download is paused, you can shut down or restart your computer.
When you are ready to resume your download, use the following command:
curl
-O
-C
https://repo.anaconda.com/archive/
<
INSTALLE
R
>
The
-C
flag is the option for “continue”. You can pause and restart a download as many times as you wish.
Error message on install: Already installed
Cause
This situation can occur if you are getting a conda error and you want to reinstall Miniconda to fix it.
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:
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.
macOS installation failure - x86_64 (Intel chip)
Cause
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.
Solution
To check what architecture your macOS computer has:
Select the
Apple
icon on your title bar.
Select
About This Mac
.
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
Miniconda installer archive
Windows-specific issues
Cannot see Anaconda menu shortcuts after installation on Windows
Cause
After installing on Windows, the Anaconda Prompt and Anaconda Navigator shortcuts do not appear in the Windows Start menu.
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.
Solution
If Start menu shortcuts are missing, Microsoft recommends rebooting your computer or
restarting Windows Explorer
.
If that doesn’t work, clear your
$PYTHONPATH
environment variable, if applicable, and re-install Anaconda.
Other potential solutions are covered in the “Conflicts with system state” section of the following
blog post
.
Windows error: Failed to create Anaconda menus or Failed to add Anaconda to the system PATH
Cause
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.
Solution
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.
To find your path variable:
Search for “environment variables” in the search in your taskbar.
Select
Edit the System Environment Variables
in the sidebar.
Click
Environment Variables
in the System Properties dialog.
Highlight the
path
variable for your user.
Click
Edit
.
Anaconda interfering with other software on Windows
Cause
If a user chooses to add Anaconda to the Windows PATH, this can cause programs to use the new Anaconda versions of software (like Python) and not the versions that were already in place. In some cases, this can cause incompatibility and errors.
Solution
Anaconda does NOT recommend adding Anaconda to the Windows PATH manually. Instead, use Anaconda software by opening Anaconda Navigator or Anaconda Prompt from the Start Menu.
Files left behind after uninstalling Anaconda on Windows
Cause
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>
.
Replace
<USERNAME>
with your Windows username as it appears in the
Documents and Settings
or
Users
folder.
Solution
Manually delete any unneeded settings files.
Spyder errors or failure to launch on Windows
Cause
This may be caused by errors in the Spyder setting and configuration files.
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
Cause
After installing Anaconda or Miniconda as a non-administrative user on Windows, uninstalling may prompt for administrative privileges.
This occurs when running the uninstaller by choosing Control Panel > Uninstall a program, selecting Anaconda or Miniconda from the list of programs, and clicking
Uninstall
.
Solution
Open the
anaconda3
or
miniconda3
installation folders and run the
.exe
file uninstaller from that location. Uninstallation will complete without prompting for administrative privileges.
EXAMPLE: If you installed Miniconda3, the uninstall file will be
Uninstall-Miniconda3.exe
. Users who installed Miniconda2 or Anaconda will find a similar file with the appropriate name.
Windows permission errors when installing from Favorites folder
Cause
The Windows Favorites folder has unusual permissions and may cause permission errors with installers of any software. If you try launching the installer from the Favorites folder, you may see errors such as “Setup was unable to create the directory”, “Access is denied”, or “Error opening file for writing”.
Solution
Move the installer to a different folder and run the installer from the new folder.
Trouble with activation on PowerShell on Windows
Cause
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:
\U
sers
\<
USERNAM
E
>
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
Linking problems when Python extensions are compiled with gcc
Cause
When compiling Python extensions with gcc on Windows, linking problems may result.
Solution
To resolve these linking problems, use the conda package
libpython
, a mingw import library that Anaconda builds and includes with the Anaconda Distribution.
macOS-specific issues
This package is incompatible with this version of macOS error when running a .pkg installer on OSX
Cause
When running the
.pkg
installer, you may encounter this error during the “Installation” step:
This error occurs when the installation attempts to write to a directory for which it does not have write permissions.
Solution
Manually select an appropriate install location. The following example shows how to select your user’s home directory.
Re-run the installer and click through until you reach either the Installation Type or Destination Select page.
If you reach the Installation Type page first, click
Change Install Location…
. This will take you to the Destination Select page.
Click
Install on a specific disk…
.
Select the appropriate destination drive. Then click
Choose Folder…
.
Select your user’s home directory (for example, /Users/john.doe/). Then click
Choose
.
In the message box, confirm the name of the install folder you chose in the previous step. Then click
Continue
.
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
, and be sure to include the installation log output from your
install.log
file, which can be found at
/var/log/install.log
.
Linux-specific issues
Missing libgomp on Power8
Cause
If the Python command
import numpy
fails, the system is likely missing the
libgomp
system library. Most Power8 Linux distributions include
libgomp
, but some may not.
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
Anaconda on Power8 only supports little endian mode. The little endian Python binary will not execute on a big endian operating system.
Solution
Install Anaconda on Power8 on a little endian Linux installation or VM.
Anaconda Distribution installation failed with “‘ascii’ codec can’t encode character ‘xe4’ in position 96” error
Cause
The package
conda-package-streaming
requires certain encoding variables that fresh installations of Linux may not have properly set, causing an ASCII error and a failed installation of Anaconda Distribution.
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.
Desktop issues
Model won’t load (exit code 3221225781)
Cause
The model you are trying to load requires a C++ runtime environment, but Microsoft does not include one in their operating systems by default.
Solution
Install the Latest
Microsoft Visual C++ Redistributable Version
.
Navigator issues
Custom Navigator app isn’t appearing on the Home page
Cause
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.
Solution
Check that the conda package has been uploaded to your Anaconda.org channel.
Check that your channel has been added to the Channels list.
Remove the
.anaconda/navigator
folder from your home directory to reset Navigator’s configuration information, then restart Navigator.
Custom Navigator app won’t launch
Cause
The app can fail to launch due to Navigator configuration issues, even if the application itself is functioning correctly.
Solution
If the application does not launch after installation, confirm that it works via the command line by running the following command:
conda
run
jupyter
lab
If you are not using the example feedstock, the command after
run
will be the
entry:
command you have designated.
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.
Navigator fails to update to version 2.6.4
Cause
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.)
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.
Navigator error on start up
Cause
This is often the result of a corrupted
.condarc
file.
Solution
To resolve, delete the
.condarc
file and restart Navigator.
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.
The
.condarc
file is frequently found in:
C:\Users\
<USERNAME>
Optional: Save custom configurations.
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.
Delete the
.condarc
file.
Restart Navigator.
Issues launching or initializing
Cause
Issues launching or initializing Anaconda Navigator may be caused by permission or licensing problems.
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
macOS Catalina users may experience permission errors where the system does not prompt you for permission to folders requiring access.
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:
import
os
os.listdir(
'<DIRECTORY>'
)
Access denied error
Cause
A lock file wasn’t removed when it should have been.
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
The disappearance of Navigator buttons may be caused by an out of sync repodata, a corrupt
.condarc
file, or an unknown issue.
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 (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:
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 Package Security Manager (On-prem) in Navigator
Cause
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.
Solution
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:
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 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.
Remove the
channel_alias:
entry from the conda configuration file (
.condarc
).
Try signing in again.
VS Code is not appearing on the Navigator Home tab
Cause
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):
C:\Users\User\AppData\Local\Programs\Microsoft
VS
Code
Solution
There are two options for solving this issue:
Ensure that executable is installed in the default location
Reinstall VS Code to ensure that executable is installed in the default location.
Close Navigator.
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.
Re-open Navigator.
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.
Open the Anaconda Navigator Preferences dialog from the top menu bar (such as
File
>
Preferences
or
Anaconda Navigator
>
Preferences
).
Scroll down to the VS Code path setting.
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.
You do not need to enter the name of the executable file itself. Just the path to the folder that contains that file.
Close and reopen Navigator.
Anaconda Navigator fails to start and gives Permission denied error
Cause
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.
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 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.
Windows
macOS/Linux
Search for “powershell”.
Right-click the Windows PowerShell app and select
Run as administrator
.
Run the following command:
icacls C:\Users\<USERNAME>\.continuum /grant:r <USERNAME>:(i,f) /t
Open your terminal application.
Run the following command:
sudo
chmod
766
/.continuum
Navigator gives ‘Email verification failed’ error 403
Cause
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.
Solution
To connect to Anaconda.org again through Navigator,
update your Navigator version
or verify your Anaconda.org account.
Verify your anaconda.org account
To fully resolve the issue, we recommend verifying your account on Anaconda.org:
Log in to your Anaconda.org account.
If your email is unverified, you will be prompted to verify it.
Click
Resend Confirmation Email
.
Follow the instructions in the email you receive to complete the verification process.
Navigator fails to start due to “Could not load the Qt platform plugin “xcb” in "" even though it was found” error
Cause
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.”
Solution
Open a terminal application.
Install the missing system libraries and run updates:
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.
Disable Anaconda.com login reminder
Cause
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.
Solution
There are a few ways to disable the Anaconda.com login reminder, depending on your version of Navigator:
2.6.1 and later
2.5.2 to 2.6.0
2.5.0
Work in
offline mode
or
log in to another repository
.
Open the Navigator configuration file
.
Edit the
cloud_login_popup_state
to be
0
in the
[internal]
section of the configuration file.
[internal]
anaconda_toolbox_installed
=
True
cloud_login_popup_state
=
0
Open the Navigator configuration file
.
Edit the
welcome_state
to be
0
in the
[internal]
section of the configuration file.
[internal]
welcome_state
=
0
Update popup not automatically appearing
Cause
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
Solution
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, select
Update now.
To have the
Update
popup appear automatically again:
Open
Preferences
from the
File
or
Anaconda Navigator
menu.
Deselect
Hide update dialog on startup
.
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…
.
defaults is missing from your channels list
This issue specifically impacts users without a subscription to our premium repository.
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:
Click
Channels
on the
Home
or
Environments
page.
Click
Add
.
Enter
defaults
, then press Enter (Windows)/Return (Mac) on your keyboard.
Click
Update channels
.
Close and reopen Navigator.
Environment backup not working in Navigator with Unable to create requested file error
Cause
An update to the environment export option in conda v25.7.0 is incompatible with the existing Navigator implementation for backing up environments.
Solution
Upgrade conda to the latest version by running the following command:
conda
update
--name
base
conda
Confirm your installed version of conda by running the following command:
conda
--version
Anaconda.org issues
Captcha not appearing when trying to create an Anaconda.org account on Firefox
Cause
The captcha at the bottom of the
Sign In
panel on
Anaconda.org
sometimes fails to appear on Firefox browsers. The captcha may be blocked by an ad blocker extension, tracking blocker extension, or Firefox’s privacy settings.
Solution
Refresh your browser and try again. If refreshing multiple times, wait a few seconds between each refresh.
Check your extensions. Extensions that block tracking or ads may also block the captcha.
Check your browser settings. Privacy settings may block the captcha.
Open the
sign in page
in a
private browsing window
.
”URI no longer exists and has been permanently removed” 410 error when attempting to upload notebooks or environments to Anaconda.org
Cause
The Notebooks and Environments features have been removed from Anaconda.org as part of an initiative to streamline and improve Anaconda.org and enable the site to focus on package hosting and management. Because of this, notebook and environment files can no longer be uploaded to Anaconda.org using the
anaconda upload
command.
Solution
Although you can no longer upload notebooks to Anaconda.org, you can share your notebooks with others using
Anaconda Notebooks
instead. Anaconda Notebooks come with their own preloaded Environments and allow you to create your own custom environments as well. For more information on sharing notebooks with Anaconda Notebooks, see
Sharing notebooks
.
Users don’t have passwords for
anaconda-client
login to Anaconda.org
Cause
If you created an account on Anaconda.org and used the Google, Microsoft, or GitHub authorization options to sign up, you do not have a password associated with your account.
anaconda-client
v1.13.1 and older require a username and password to log in to anaconda.org.
Solution
To log in to anaconda.org without a password using
anaconda-client
, you must update
anaconda-client
to v1.14.0 or later in your base environment:
Open Anaconda Prompt (Terminal in macOS/Linux).
Update or install
anaconda-client
by running the following command:
conda
install
--name
base
"anaconda-client>=1.14.0"
Log into Anaconda.org:
anaconda
org
login
A browser window opens to authenticate you to Anaconda.org. Sign in with your account credentials to complete authentication in the browser.
Notebooks issues
Toolbox environment card says the environment is installed, but no environment in the Launcher or runtime selector
Cause
The environment might not have fully synchronized with the Launcher or runtime selector yet.
Solution
First, try refreshing the browser page. If the environment still doesn’t appear after refreshing, check the Environments page in Navigator to see if it’s available. If the environment is still unavailable after waiting two minutes, close all open Jupyter sessions and restart Jupyter from Navigator or the command line.
Quickstart environment installation errored
Cause
Installation errors can occur due to misconfigured channels in your
.condarc
file, organizational policies blocking installation, connectivity issues, or stale Jupyter kernel states.
Solution
First, check your
.condarc
file and verify that your channels are set to either
defaults
or
conda-forge
. If your channels are set correctly and you’re still experiencing issues, check with your administrator to see if they have defined any policies that could be blocking installation.
If neither of the above resolves the issue, you can try:
Refreshing the page
Checking your internet connection
Shutting down all running Jupyter kernels and restarting your Jupyter instance
CLI or Navigator gives “error starting kernel” message
Cause
Uninstalling a quick start environment using either the CLI or Navigator can result in an
Error starting kernel: [Errno 2] No such file or directory
message, because the Jupyter kernel references aren’t properly removed when the environment is deleted.
Solution
To resolve this issue:
Open Anaconda Prompt (Terminal in macOS/Linux)
Run:
jupyter
kernelspec
list
Find the name of the quick start environment you deleted.
Then run:
jupyter
kernelspec
uninstall
<
ENV_NAM
E
>
Published Panel app is blank
Cause
The app can appear blank if the notebook cannot be executed sequentially from top to bottom, which can happen when cells have dependencies that aren’t met or are out of order.
Solution
If you added content to your app but there’s still nothing showing up, ensure that your notebook can be run from top to bottom. The easiest way to test this is to select
Run
in the top menu, then select
Run All Cells
.
All CPU seconds have been used up in Notebooks
Cause
You’ve used up all your available CPU seconds.
Solution
CPU seconds are consumed by active runtimes, which can continue to run in the background even after you’ve logged out of Notebooks or switched to a different browser tab.
To prevent your CPU seconds from being used while you are not actively using Notebooks, make sure you shut down all runtimes in all open instances of Notebooks before logging off for the day. You can do this from the
Running Terminals and Kernels
tab:
If the problem persists, please raise the issue in the
Anaconda community forums
or
file a support ticket
.
You can upgrade your subscription plan to access additional CPU seconds. See our
pricing page
for further details.
Error when importing packages in Notebooks
Cause
The most common cause of errors is a lack of required package(s) installed in your environment. The default environment we provide, based on the Anaconda distribution, contains hundreds of the most common python packages for data science, but it doesn’t include everything. You might need to create a custom environment to install the package you need.
Solution
Make sure you have the right runtime selected
The default
anaconda-<YEAR>.<MONTH>-py<PYTHON_VERSION>
runtimes have a broad selection of packages, but you might have created a custom environment for your notebook. Separate environments are represented as “runtimes” in JupyterLab. You can view and switch between available runtimes by clicking the runtime name in the upper-right corner of the content pane.
List the packages available in an environment
If one of your imports is failing, start by verifying that the package is present in the runtime environment. You can view which packages are available in your current environment from the terminal by running
conda list
.
To view packages in a specific environment, run
conda list --name <ENV_NAME>
.
To see a list of available environments, run
conda info --envs
. An asterisk appears beside your current active environment.
Create a custom runtime
If none of the Anaconda provided environments contain the package(s) you need, create a
custom runtime
for your notebook project.
”Missing ipykernel dependency” error
Cause
A
missing ipykernel dependency
error is caused by an environment dependency list not including the required
ipykernel
package.
Solution
To resolve this issue, add the
ipykernel
package to your environment’s dependency list. For example:
channels
:
-
defaults
dependencies
:
-
python=3.11
-
numpy
-
pandas
-
ipykernel
Custom runtime not appearing in Launcher or Assign a Runtime modal
Cause
The most common reason a runtime or environment is not appearing in the Launcher or Assign a Runtime modal is that it doesn’t contain a
.
Solution
For more information and instructions on installing a kernel package in your runtime/environment, see
Creating custom runtimes
.
”File load error,” “unhandled error,” or “unexpected error” message
Cause
If you receive a “file load error,” “unhandled error,” or “unexpected error,” like in the following figure, you have most likely exceeded the storage space for your current plan.
Solution
Follow the steps in the storage question above to remove items from your Notebooks instance, or upgrade to a higher subscription plan.
Notebooks won’t open from Anaconda Platform
Cause
Your browser’s pop-up blocker (automatically enabled on Firefox and Safari) can prevent Notebooks from opening.
Solution
Disable your pop-up blocker and try opening Notebooks again from Anaconda Platform.
Notebook cannot access external sites after subscription upgrade
Cause
Notebook kernels inherit network permissions when a session is started. Any notebook sessions that were started while your account was using the Free plan are still operating under PythonAnywhere’s
allowlist
restrictions.
Solution
Stop and restart all Notebook sessions to establish a kernel with unrestricted internet access.
It can take up to an hour for the upgrade to take effect.
AI Navigator issues
Model won’t load (exit code 3221225781)
Cause
The model you are trying to load requires a C++ runtime environment, but Microsoft does not include one in their operating systems by default.
Solution
Install the Latest
Microsoft Visual C++ Redistributable Version
.
Toolbox Excel add-in issues
Error installing functions in Excel
Cause
This error can occur when Excel loads the Anaconda Toolbox add-in and registers its custom functions. This error happens within Excel and cannot be resolved by the Anaconda Toolbox.
Solution
Close and reopen Excel. If the issue persists, uninstall the Anaconda Toolbox add-in, then reinstall. |
| Markdown | [Skip to main content](https://www.anaconda.com/docs/reference/troubleshooting#content-area)
[Anaconda home page](https://www.anaconda.com/)
Search...
Ctrl K
Ask AI
- [Pricing](https://www.anaconda.com/pricing)
- [Download](https://www.anaconda.com/download)
- [Download](https://www.anaconda.com/download)
Search...
Navigation
Reference
Troubleshooting
[Home](https://www.anaconda.com/docs/main)
[Getting Started](https://www.anaconda.com/docs/getting-started/main)
[Anaconda Tools](https://www.anaconda.com/docs/tools/main)
[Anaconda Platform](https://www.anaconda.com/docs/anaconda-platform/cloud/main)
[Data Science & AI Workbench](https://www.anaconda.com/docs/data-science/latest/main)
[Developer Resources](https://www.anaconda.com/docs/developer-reference/library)
[Reference](https://www.anaconda.com/docs/reference/main)
##### Reference
- [Overview](https://www.anaconda.com/docs/reference/main)
- [Glossary](https://www.anaconda.com/docs/reference/glossary)
- [Release notes](https://www.anaconda.com/docs/reference/release-notes)
- [Troubleshooting](https://www.anaconda.com/docs/reference/troubleshooting)
- [Help and support](https://www.anaconda.com/docs/reference/help-support)
- Policies and practices
- Data collection
- API
On this page
- [Most common issues](https://www.anaconda.com/docs/reference/troubleshooting#most-common-issues)
- [command not found: conda](https://www.anaconda.com/docs/reference/troubleshooting#command-not-found-conda)
- [CondaHTTPError: HTTP 400 Bad Request for URL](https://www.anaconda.com/docs/reference/troubleshooting#condahttperror-http-400-bad-request-for-url)
- [UnavailableInvalidChannel: HTTP 404 Not Found for channel](https://www.anaconda.com/docs/reference/troubleshooting#unavailableinvalidchannel-http-404-not-found-for-channel)
- [PackagesNotFoundError: The following packages are not available from current channels](https://www.anaconda.com/docs/reference/troubleshooting#packagesnotfounderror-the-following-packages-are-not-available-from-current-channels)
- [DirectoryNotACondaEnvironmentError: The target directory exists, but it is not a conda environment](https://www.anaconda.com/docs/reference/troubleshooting#directorynotacondaenvironmenterror-the-target-directory-exists-but-it-is-not-a-conda-environment)
- [EnvironmentNotWriteableError](https://www.anaconda.com/docs/reference/troubleshooting#environmentnotwriteableerror)
- [ModuleNotFoundError: No module named X](https://www.anaconda.com/docs/reference/troubleshooting#modulenotfounderror-no-module-named-x)
- [Receiving a 403 Forbidden error from an Anaconda channel](https://www.anaconda.com/docs/reference/troubleshooting#receiving-a-403-forbidden-error-from-an-anaconda-channel)
- [HTTP 000 CONNECTION FAILED](https://www.anaconda.com/docs/reference/troubleshooting#http-000-connection-failed)
- [conda update anaconda command does not install the latest version of the anaconda metapackage](https://www.anaconda.com/docs/reference/troubleshooting#conda-update-anaconda-command-does-not-install-the-latest-version-of-the-anaconda-metapackage)
- [Recovering your Anaconda installation](https://www.anaconda.com/docs/reference/troubleshooting#recovering-your-anaconda-installation)
- [Channels list adding extra channels](https://www.anaconda.com/docs/reference/troubleshooting#channels-list-adding-extra-channels)
- [Uninstall.sh not found](https://www.anaconda.com/docs/reference/troubleshooting#uninstall-sh-not-found)
- [Anaconda.com account issues](https://www.anaconda.com/docs/reference/troubleshooting#anaconda-com-account-issues)
- [Not receiving Anaconda.com account verification email](https://www.anaconda.com/docs/reference/troubleshooting#not-receiving-anaconda-com-account-verification-email)
- [I can’t access my learning courses](https://www.anaconda.com/docs/reference/troubleshooting#i-can%E2%80%99t-access-my-learning-courses)
- [Unable to reset Anaconda.com account password](https://www.anaconda.com/docs/reference/troubleshooting#unable-to-reset-anaconda-com-account-password)
- [Subscribed to Academic plan but seeing Starter plan](https://www.anaconda.com/docs/reference/troubleshooting#subscribed-to-academic-plan-but-seeing-starter-plan)
- [Anaconda Distribution issues](https://www.anaconda.com/docs/reference/troubleshooting#anaconda-distribution-issues)
- [Using Anaconda behind a firewall or proxy](https://www.anaconda.com/docs/reference/troubleshooting#using-anaconda-behind-a-firewall-or-proxy)
- [InsecurePlatformWarning error](https://www.anaconda.com/docs/reference/troubleshooting#insecureplatformwarning-error)
- [Anaconda search error: not recognized as an internal or external command/unrecognized arguments](https://www.anaconda.com/docs/reference/troubleshooting#anaconda-search-error-not-recognized-as-an-internal-or-external-command%2Funrecognized-arguments)
- [Collecting package metadata (repodata.json): - Killed](https://www.anaconda.com/docs/reference/troubleshooting#collecting-package-metadata-repodata-json--killed)
- [Error message: Unable to remove files](https://www.anaconda.com/docs/reference/troubleshooting#error-message-unable-to-remove-files)
- [Using 32- and 64-bit libraries and CONDA\_FORCE\_32BIT](https://www.anaconda.com/docs/reference/troubleshooting#using-32-and-64-bit-libraries-and-conda_force_32bit)
- [Proxy request sent, not found](https://www.anaconda.com/docs/reference/troubleshooting#proxy-request-sent-not-found)
- [Installation issues](https://www.anaconda.com/docs/reference/troubleshooting#installation-issues)
- [Anaconda installer download problems](https://www.anaconda.com/docs/reference/troubleshooting#anaconda-installer-download-problems)
- [Error message on install: Already installed](https://www.anaconda.com/docs/reference/troubleshooting#error-message-on-install-already-installed)
- [macOS installation failure - x86\_64 (Intel chip)](https://www.anaconda.com/docs/reference/troubleshooting#macos-installation-failure-x86_64-intel-chip)
- [Windows-specific issues](https://www.anaconda.com/docs/reference/troubleshooting#windows-specific-issues)
- [Cannot see Anaconda menu shortcuts after installation on Windows](https://www.anaconda.com/docs/reference/troubleshooting#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](https://www.anaconda.com/docs/reference/troubleshooting#windows-error-failed-to-create-anaconda-menus-or-failed-to-add-anaconda-to-the-system-path)
- [Anaconda interfering with other software on Windows](https://www.anaconda.com/docs/reference/troubleshooting#anaconda-interfering-with-other-software-on-windows)
- [Files left behind after uninstalling Anaconda on Windows](https://www.anaconda.com/docs/reference/troubleshooting#files-left-behind-after-uninstalling-anaconda-on-windows)
- [Spyder errors or failure to launch on Windows](https://www.anaconda.com/docs/reference/troubleshooting#spyder-errors-or-failure-to-launch-on-windows)
- [Uninstaller requests admin privileges on Windows](https://www.anaconda.com/docs/reference/troubleshooting#uninstaller-requests-admin-privileges-on-windows)
- [Windows permission errors when installing from Favorites folder](https://www.anaconda.com/docs/reference/troubleshooting#windows-permission-errors-when-installing-from-favorites-folder)
- [Trouble with activation on PowerShell on Windows](https://www.anaconda.com/docs/reference/troubleshooting#trouble-with-activation-on-powershell-on-windows)
- [Linking problems when Python extensions are compiled with gcc](https://www.anaconda.com/docs/reference/troubleshooting#linking-problems-when-python-extensions-are-compiled-with-gcc)
- [macOS-specific issues](https://www.anaconda.com/docs/reference/troubleshooting#macos-specific-issues)
- [This package is incompatible with this version of macOS error when running a .pkg installer on OSX](https://www.anaconda.com/docs/reference/troubleshooting#this-package-is-incompatible-with-this-version-of-macos-error-when-running-a-pkg-installer-on-osx)
- [Linux-specific issues](https://www.anaconda.com/docs/reference/troubleshooting#linux-specific-issues)
- [Missing libgomp on Power8](https://www.anaconda.com/docs/reference/troubleshooting#missing-libgomp-on-power8)
- [Anaconda on Power8 reports “can not execute binary file”](https://www.anaconda.com/docs/reference/troubleshooting#anaconda-on-power8-reports-%E2%80%9Ccan-not-execute-binary-file%E2%80%9D)
- [Anaconda Distribution installation failed with “‘ascii’ codec can’t encode character ‘xe4’ in position 96” error](https://www.anaconda.com/docs/reference/troubleshooting#anaconda-distribution-installation-failed-with-%E2%80%9C%E2%80%98ascii%E2%80%99-codec-can%E2%80%99t-encode-character-%E2%80%98xe4%E2%80%99-in-position-96%E2%80%9D-error)
- [Desktop issues](https://www.anaconda.com/docs/reference/troubleshooting#desktop-issues)
- [Model won’t load (exit code 3221225781)](https://www.anaconda.com/docs/reference/troubleshooting#model-won%E2%80%99t-load-exit-code-3221225781)
- [Navigator issues](https://www.anaconda.com/docs/reference/troubleshooting#navigator-issues)
- [Custom Navigator app isn’t appearing on the Home page](https://www.anaconda.com/docs/reference/troubleshooting#custom-navigator-app-isn%E2%80%99t-appearing-on-the-home-page)
- [Custom Navigator app won’t launch](https://www.anaconda.com/docs/reference/troubleshooting#custom-navigator-app-won%E2%80%99t-launch)
- [Navigator fails to update to version 2.6.4](https://www.anaconda.com/docs/reference/troubleshooting#navigator-fails-to-update-to-version-2-6-4)
- [Navigator error on start up](https://www.anaconda.com/docs/reference/troubleshooting#navigator-error-on-start-up)
- [Issues launching or initializing](https://www.anaconda.com/docs/reference/troubleshooting#issues-launching-or-initializing)
- [PermissionError on macOS Catalina](https://www.anaconda.com/docs/reference/troubleshooting#permissionerror-on-macos-catalina)
- [Access denied error](https://www.anaconda.com/docs/reference/troubleshooting#access-denied-error)
- [Navigator buttons are missing](https://www.anaconda.com/docs/reference/troubleshooting#navigator-buttons-are-missing)
- [Trouble logging in to Package Security Manager (On-prem) in Navigator](https://www.anaconda.com/docs/reference/troubleshooting#trouble-logging-in-to-package-security-manager-on-prem-in-navigator)
- [VS Code is not appearing on the Navigator Home tab](https://www.anaconda.com/docs/reference/troubleshooting#vs-code-is-not-appearing-on-the-navigator-home-tab)
- [Anaconda Navigator fails to start and gives Permission denied error](https://www.anaconda.com/docs/reference/troubleshooting#anaconda-navigator-fails-to-start-and-gives-permission-denied-error)
- [Navigator gives ‘Email verification failed’ error 403](https://www.anaconda.com/docs/reference/troubleshooting#navigator-gives-%E2%80%98email-verification-failed%E2%80%99-error-403)
- [Navigator fails to start due to “Could not load the Qt platform plugin “xcb” in "" even though it was found” error](https://www.anaconda.com/docs/reference/troubleshooting#navigator-fails-to-start-due-to-%E2%80%9Ccould-not-load-the-qt-platform-plugin-%E2%80%9Cxcb%E2%80%9D-in--even-though-it-was-found%E2%80%9D-error)
- [Disable Anaconda.com login reminder](https://www.anaconda.com/docs/reference/troubleshooting#disable-anaconda-com-login-reminder)
- [Update popup not automatically appearing](https://www.anaconda.com/docs/reference/troubleshooting#update-popup-not-automatically-appearing)
- [Environment backup not working in Navigator with Unable to create requested file error](https://www.anaconda.com/docs/reference/troubleshooting#environment-backup-not-working-in-navigator-with-unable-to-create-requested-file-error)
- [Anaconda.org issues](https://www.anaconda.com/docs/reference/troubleshooting#anaconda-org-issues)
- [Captcha not appearing when trying to create an Anaconda.org account on Firefox](https://www.anaconda.com/docs/reference/troubleshooting#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](https://www.anaconda.com/docs/reference/troubleshooting#%E2%80%9Duri-no-longer-exists-and-has-been-permanently-removed%E2%80%9D-410-error-when-attempting-to-upload-notebooks-or-environments-to-anaconda-org)
- [Users don’t have passwords for anaconda-client login to Anaconda.org](https://www.anaconda.com/docs/reference/troubleshooting#users-don%E2%80%99t-have-passwords-for-anaconda-client-login-to-anaconda-org)
- [Notebooks issues](https://www.anaconda.com/docs/reference/troubleshooting#notebooks-issues)
- [Toolbox environment card says the environment is installed, but no environment in the Launcher or runtime selector](https://www.anaconda.com/docs/reference/troubleshooting#toolbox-environment-card-says-the-environment-is-installed-but-no-environment-in-the-launcher-or-runtime-selector)
- [Quickstart environment installation errored](https://www.anaconda.com/docs/reference/troubleshooting#quickstart-environment-installation-errored)
- [CLI or Navigator gives “error starting kernel” message](https://www.anaconda.com/docs/reference/troubleshooting#cli-or-navigator-gives-%E2%80%9Cerror-starting-kernel%E2%80%9D-message)
- [Published Panel app is blank](https://www.anaconda.com/docs/reference/troubleshooting#published-panel-app-is-blank)
- [All CPU seconds have been used up in Notebooks](https://www.anaconda.com/docs/reference/troubleshooting#all-cpu-seconds-have-been-used-up-in-notebooks)
- [Error when importing packages in Notebooks](https://www.anaconda.com/docs/reference/troubleshooting#error-when-importing-packages-in-notebooks)
- [”Missing ipykernel dependency” error](https://www.anaconda.com/docs/reference/troubleshooting#%E2%80%9Dmissing-ipykernel-dependency%E2%80%9D-error)
- [Custom runtime not appearing in Launcher or Assign a Runtime modal](https://www.anaconda.com/docs/reference/troubleshooting#custom-runtime-not-appearing-in-launcher-or-assign-a-runtime-modal)
- [”File load error,” “unhandled error,” or “unexpected error” message](https://www.anaconda.com/docs/reference/troubleshooting#%E2%80%9Dfile-load-error%E2%80%9D-%E2%80%9Cunhandled-error%E2%80%9D-or-%E2%80%9Cunexpected-error%E2%80%9D-message)
- [Notebooks won’t open from Anaconda Platform](https://www.anaconda.com/docs/reference/troubleshooting#notebooks-won%E2%80%99t-open-from-anaconda-platform)
- [Notebook cannot access external sites after subscription upgrade](https://www.anaconda.com/docs/reference/troubleshooting#notebook-cannot-access-external-sites-after-subscription-upgrade)
- [AI Navigator issues](https://www.anaconda.com/docs/reference/troubleshooting#ai-navigator-issues)
- [Model won’t load (exit code 3221225781)](https://www.anaconda.com/docs/reference/troubleshooting#model-won%E2%80%99t-load-exit-code-3221225781-2)
- [Toolbox Excel add-in issues](https://www.anaconda.com/docs/reference/troubleshooting#toolbox-excel-add-in-issues)
- [Error installing functions in Excel](https://www.anaconda.com/docs/reference/troubleshooting#error-installing-functions-in-excel)
[Reference](https://www.anaconda.com/docs/reference/main)
# Troubleshooting
Copy page
Copy page
This page includes common troubleshooting topics for Anaconda products. Issues are grouped by product and category.
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).
## [](https://www.anaconda.com/docs/reference/troubleshooting#most-common-issues)Most common issues
### [](https://www.anaconda.com/docs/reference/troubleshooting#command-not-found-conda)command not found: conda
***
Cause
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.
These issues primarily occur on macOS/Linux computers. Anaconda Distribution and Miniconda installations on Windows include [Anaconda Prompt](https://www.anaconda.com/docs/reference/glossary#anaconda-prompt), which opens with conda initialized by default.
***
Solution
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.
If you don’t want to close your CLI, you can also use one of the following `source` commands to refresh your shell:
bash
zsh
fish
cshrc
xonshrc
```
source ~/.bashrc
```
You can also initialize conda directly from its `bin` directory:
Initialization command
Examples
```
<PATH_TO_CONDA>/bin/conda init
```
Set auto\_activate\_base to true
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` to `true`, run the following command:
```
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`.
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.
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](https://www.anaconda.com/docs/getting-started/anaconda/main) or [Miniconda](https://www.anaconda.com/docs/getting-started/miniconda/main).
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](https://www.anaconda.com/docs/reference/troubleshooting#initialize-conda-in-your-shell).
### [](https://www.anaconda.com/docs/reference/troubleshooting#condahttperror-http-400-bad-request-for-url)CondaHTTPError: HTTP 400 Bad Request for URL
***
Cause
A **400 Bad Request** error typically means there’s a typo in your channel URL. When you pass a full URL with the `-c` flag, conda doesn’t validate whether the channel exists—it just makes the request. If the path is wrong, the server returns a 400 error.
***
Solution
Double-check your channel URL for typos and try again.
### [](https://www.anaconda.com/docs/reference/troubleshooting#unavailableinvalidchannel-http-404-not-found-for-channel)UnavailableInvalidChannel: HTTP 404 Not Found for channel
***
Cause
A **404 Not Found** error means the channel you specified doesn’t exist. This is usually caused by a typo in the channel name, either in your `.condarc` file or when using the `-c` flag.
***
Solution
Check your command for typos and try again.To see which channels are currently configured, run:
```
conda config --show channels
```
If you see a misspelled channel in your configuration, remove it with:
```
conda config --remove channels <MISSPELLED_CHANNEL>
```
For help adding adding and removing channels to your `.condarc` file, see [Managing channels](https://www.anaconda.com/docs/getting-started/working-with-conda/channels#managing-channels).
### [](https://www.anaconda.com/docs/reference/troubleshooting#packagesnotfounderror-the-following-packages-are-not-available-from-current-channels)PackagesNotFoundError: The following packages are not available from current channels
***
Cause
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.
***
Solution
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](https://www.anaconda.com/docs/getting-started/working-with-conda/packages/install-packages#using-conda-install).
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](https://www.anaconda.com/docs/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.
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](https://www.anaconda.com/docs/getting-started/working-with-conda/channels#installing-packages-from-a-specific-channel).
Add the missing channel to your .condarc file
[Add the missing channel to your .condarc file](https://www.anaconda.com/docs/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.
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.
```
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.
### [](https://www.anaconda.com/docs/reference/troubleshooting#directorynotacondaenvironmenterror-the-target-directory-exists-but-it-is-not-a-conda-environment)DirectoryNotACondaEnvironmentError: The target directory exists, but it is not a conda environment
***
Cause
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.
***
Solution
Activate your `base` environment or another environment:
```
# Activate your base environment
conda activate
# Activate an environment by name
conda activate <ENV_NAME>
```
### [](https://www.anaconda.com/docs/reference/troubleshooting#environmentnotwriteableerror)EnvironmentNotWriteableError
***
Cause
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*.
***
Solution
Create your own environment instead, in a directory you don’t need admin permissions to work in, such as your home directory:
```
conda create --name <ENV_NAME> --prefix <PATH_TO_USER_DIRECTORY>
```
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](https://www.anaconda.com/docs/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:
```
conda create --file environment.yml --prefix <PATH_TO_USER_DIRECTORY>
```
### [](https://www.anaconda.com/docs/reference/troubleshooting#modulenotfounderror-no-module-named-x)ModuleNotFoundError: No module named X
***
Cause
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.
***
Solution
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:
```
conda info --envs
```
An asterisk is displayed next to your currently active environment:
Environment list example
```
(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](https://www.anaconda.com/docs/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](https://www.anaconda.com/docs/getting-started/working-with-conda/packages/install-packages).
### [](https://www.anaconda.com/docs/reference/troubleshooting#receiving-a-403-forbidden-error-from-an-anaconda-channel)Receiving a 403 Forbidden error from an Anaconda channel
***
Cause
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.
The 403 error you are receiving may look like the following:
```
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.
***
Solution
Run `anaconda token install` to issue and set a new token for yourself, then try again.
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.
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).
### [](https://www.anaconda.com/docs/reference/troubleshooting#http-000-connection-failed)HTTP 000 CONNECTION FAILED
***
Cause
This is generally caused by a proxy misconfiguration.
***
Solution
Follow instructions on [Using Anaconda behind a company proxy](https://www.anaconda.com/docs/getting-started/working-with-conda/reference/proxy) to configure your proxy correctly.
### [](https://www.anaconda.com/docs/reference/troubleshooting#conda-update-anaconda-command-does-not-install-the-latest-version-of-the-anaconda-metapackage)`conda update anaconda` command does not install the latest version of the `anaconda` metapackage
***
Cause
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.
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.
***
Solution
1. 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.
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:
```
conda remove anaconda
```
2. 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:
1. Remove the conflicting packages by running the following command for each one:
```
conda remove <PACKAGE>
```
2. Update to the latest version of the `anaconda` metapackage:
```
conda update anaconda
```
### [](https://www.anaconda.com/docs/reference/troubleshooting#recovering-your-anaconda-installation)Recovering your Anaconda installation
***
Cause
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
1. Download a [new installer](https://repo.anaconda.com/archive/), then follow the instructions for your operating system.
Use the actual path, filename, and directory name for your installation.
- Windows
- macOS
- Linux
1. Open a terminal application, such as Command Prompt.
2. Change your original installer’s name so you do not overwrite it:
```
move anaconda3 anaconda_old
```
3. Run the Anaconda.exe installer as usual and use robocopy to sync the directories:
```
robocopy anaconda_old anaconda3 /S
```
4. Delete your old Anaconda installation directory:
```
rd /s anaconda_old
```
1. Open a terminal application.
2. Change your original installer’s name so you do not overwrite it:
```
mv anaconda3 anaconda_old
```
3. Install to same directory as your original installer:
```
# Replace <INSTALLER> the name of your installer file
bash ~/Downloads/<INSTALLER>
rsync -a anaconda_old/ anaconda3/
```
4. Delete your old Anaconda installation directory:
```
rm -rf anaconda_old
```
1. Open a terminal application.
2. Change your original installer’s name so you do not overwrite it:
```
mv anaconda3 anaconda_old
```
3. Install to same directory as your original installer:
```
# Replace <INSTALLER> the name of your installer file
bash ~/Downloads/<INSTALLER>
rsync -a anaconda_old/ anaconda3/
```
4. Delete your old Anaconda installation directory:
```
rm -rf anaconda_old
```
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.
### [](https://www.anaconda.com/docs/reference/troubleshooting#channels-list-adding-extra-channels)Channels list adding extra channels
***
Cause
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.
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.
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.
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
```
***
Solution
There 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.
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:
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
- Windows
- Linux/macOS
```
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
```
```
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
```
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:
```
conda config --add default_channels <CHANNEL>
```
To remove a channel instead, replace `--add` with `--remove`.
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.
Make sure that you always have at least one `.condarc` file with a `channels:` list defined. Conda requires this to function.
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. You can view hidden files and folders using the following guidance for your operating system:
- macOS
- Linux
To view hidden files on macOS, use Shift+Cmd+. in your Finder.
To view hidden files on Linux, use Alt+. or Ctrl+H (depending on your file manager).
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.
If you continue to experience issues, please [open a support ticket](https://support.anaconda.com/hc/en-us/requests/new?ticket_form_id=360000993773).
### [](https://www.anaconda.com/docs/reference/troubleshooting#uninstall-sh-not-found)Uninstall.sh not found
***
Cause
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.
***
Solution
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:
```
conda info --base
```
3. Check the contents of your installation folder for the `uninstall.sh` script:
```
ls <PATH/TO/INSTALLER>
```
4. If your install is in your home directory (`\Users\<USERNAME>\` or `\home\<USERNAME>`), use the macOS/Linux **Basic uninstall** instructions.
If your install is in your `\opt\` folder, use the macOS/Linux **System uninstall** instructions.
If your install folder does not contain the `uninstall.sh` file, use the macOS/Linux **Manual uninstall** instructions.
- [Anaconda Distribution uninstall instructions](https://www.anaconda.com/docs/getting-started/anaconda/uninstall#uninstall-procedure)
- [Miniconda uninstall instructions](https://www.anaconda.com/docs/getting-started/miniconda/uninstall#uninstall-procedure)
## [](https://www.anaconda.com/docs/reference/troubleshooting#anaconda-com-account-issues)Anaconda.com account issues
### [](https://www.anaconda.com/docs/reference/troubleshooting#not-receiving-anaconda-com-account-verification-email)Not receiving Anaconda.com account verification email
***
Cause
Your browser may have cached data from a previous signup session or authentication attempt, which can interfere with the verification email being triggered.
Alternatively, the verification email may have been sent but filtered to your spam, junk, or promotions folder by your email provider.
***
Solution
First, check your junk mailbox or any other folders where emails may be automatically filtered. If the email is not there, clear your browser cache and cookies, then try logging in again at <https://auth.anaconda.com/ui/login/>.
If you still do not receive the email, please [submit a support ticket](https://support.anaconda.com/hc/en-us/requests/new).
### [](https://www.anaconda.com/docs/reference/troubleshooting#i-can%E2%80%99t-access-my-learning-courses)I can’t access my learning courses
***
Cause
Your browser session may not be properly synced with your subscription status, or cached authentication data may be outdated.
***
Solution
Clear your browser cache and cookies, then try accessing the courses again.
If the issue persists, [sign out completely](https://learning.anaconda.com/users/sign_out), then [sign back in](https://learning.anaconda.com/users/sign_in).
If you still cannot access your courses, navigate to <https://auth.anaconda.com/api/auth/sessions/whoami>, copy the contents displayed, and include them when you [submit a support ticket](https://support.anaconda.com/hc/en-us/requests/new).
### [](https://www.anaconda.com/docs/reference/troubleshooting#unable-to-reset-anaconda-com-account-password)Unable to reset Anaconda.com account password
***
Cause
Your email address must be verified before you can reset your password.
***
Solution
Follow the instructions in your verification email. If the verification link has expired, request a new verification email.
If you still have trouble resetting your password after verifying your account, [submit a support ticket](https://support.anaconda.com/hc/en-us/requests/new).
### [](https://www.anaconda.com/docs/reference/troubleshooting#subscribed-to-academic-plan-but-seeing-starter-plan)Subscribed to Academic plan but seeing Starter plan
***
Cause
This is expected behavior. The Academic plan is essentially the Starter plan, provided free of charge based on your status as a student.
***
Solution
No action is required. For details on what is included in your plan, see [Anaconda Pricing](https://www.anaconda.com/pricing).
## [](https://www.anaconda.com/docs/reference/troubleshooting#anaconda-distribution-issues)Anaconda Distribution issues
### [](https://www.anaconda.com/docs/reference/troubleshooting#using-anaconda-behind-a-firewall-or-proxy)Using Anaconda behind a firewall or proxy
***
Cause
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 might need to connect to a firewall/proxy. Additionally, your IT team might 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](https://docs.conda.io/projects/conda/en/latest/user-guide/configuration/settings.html#proxy-servers-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.
Windows
macOS/Linux
```
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>.
### [](https://www.anaconda.com/docs/reference/troubleshooting#insecureplatformwarning-error)InsecurePlatformWarning error
***
Cause
`InsecurePlatformWarning` appears only when the installed version of Python is older than version 2.7.9. This message warns only that the validity of the SSL connection is not being verified. It should not affect your package downloads.
***
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.
### [](https://www.anaconda.com/docs/reference/troubleshooting#anaconda-search-error-not-recognized-as-an-internal-or-external-command/unrecognized-arguments)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:
```
anaconda search --package-type conda <PACKAGE>
```
You will receive the following error message:
Windows
macOS/Linux
```
'anaconda' is not recognized as an internal or external command,
operable program or batch file.
```
***
Solution
To resolve the error:
1. Install `anaconda-client` by running the following command:
```
conda install anaconda-client
```
2. Search for a package:
```
anaconda search --package-type conda <PACKAGE>
```
### [](https://www.anaconda.com/docs/reference/troubleshooting#collecting-package-metadata-repodata-json--killed)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
Verify that you have enough disk space and memory on your system to install and use Anaconda packages. The minimum system requirements for Miniconda and Anaconda installers can be found in the `conda` [user guide](https://docs.conda.io/projects/conda/en/stable/user-guide/install/index.html#system-requirements).
### [](https://www.anaconda.com/docs/reference/troubleshooting#error-message-unable-to-remove-files)Error message: Unable to remove files
***
Cause
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.
```
Generally, this is caused by a file lock issue.
***
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:
```
conda install --force-reinstall <PACKAGE>
```
### [](https://www.anaconda.com/docs/reference/troubleshooting#using-32-and-64-bit-libraries-and-conda_force_32bit)Using 32- and 64-bit libraries and CONDA\_FORCE\_32BIT
***
Cause
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 --all
```
- 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.
### [](https://www.anaconda.com/docs/reference/troubleshooting#proxy-request-sent-not-found)Proxy request sent, not found
***
Cause
Your company likely has security policies or a firewall in place that prevent communications with external servers or certain URLs.
***
Solution
1. First, work with your IT team to allowlist connections to the following URLs:
```
https://anaconda.org
https://repo.anaconda.com
https://repo.anaconda.cloud
```
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.
2. [Install](https://www.anaconda.com/docs/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](https://www.anaconda.com/docs/anaconda-platform/cloud/getting-started-with-anaconda-platform#using-anaconda-behind-a-firewall-or-proxy-optional).
## [](https://www.anaconda.com/docs/reference/troubleshooting#installation-issues)Installation issues
### [](https://www.anaconda.com/docs/reference/troubleshooting#anaconda-installer-download-problems)Anaconda installer download problems
***
Cause
The Anaconda installer files are large (over 600 MB), and some users have problems with errors and interrupted downloads when downloading large files.
***
Solution
- Download Miniconda
- Restart the download
1. Download and install the smaller [Miniconda](https://www.anaconda.com/docs/getting-started/miniconda/main) (between 70 and 100 MB).
2. 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.
Download the large Anaconda installer file, and restart it if the download is interrupted or you need to pause it.
- Windows
- macOS/Linux
- Chrome
- 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 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.
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.
Go to `edge://downloads/all` to open the full page of recent downloads. From here, you can retry cancelled downloads.
1. Open a terminal window.
2. To download the file, use the following command:
```
# 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.
While a download is paused, you can shut down or restart your computer.
4. When you are ready to resume your download, use the following command:
```
curl -O -C https://repo.anaconda.com/archive/<INSTALLER>
```
The `-C` flag is the option for “continue”. You can pause and restart a download as many times as you wish.
### [](https://www.anaconda.com/docs/reference/troubleshooting#error-message-on-install-already-installed)Error message on install: Already installed
***
Cause
This situation can occur if you are getting a conda error and you want to reinstall Miniconda to fix it.
***
Solution
For macOS and Linux, download and install the appropriate Miniconda for your operating system from the [Miniconda download page](https://www.anaconda.com/docs/getting-started/miniconda/main) using the `--force` or `-f` option by running the following command:
```
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.
### [](https://www.anaconda.com/docs/reference/troubleshooting#macos-installation-failure-x86_64-intel-chip)macOS installation failure - x86\_64 (Intel chip)
***
Cause
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.
***
Solution
To check what architecture your macOS computer has:
1. Select the
**Apple** icon on your title bar.
2. Select **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)
## [](https://www.anaconda.com/docs/reference/troubleshooting#windows-specific-issues)Windows-specific issues
### [](https://www.anaconda.com/docs/reference/troubleshooting#cannot-see-anaconda-menu-shortcuts-after-installation-on-windows)Cannot see Anaconda menu shortcuts after installation on Windows
***
Cause
After installing on Windows, the Anaconda Prompt and Anaconda Navigator shortcuts do not appear in the Windows Start menu.
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.
***
Solution
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).
If that doesn’t work, clear your `$PYTHONPATH` environment variable, if applicable, and re-install Anaconda.
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).
### [](https://www.anaconda.com/docs/reference/troubleshooting#windows-error-failed-to-create-anaconda-menus-or-failed-to-add-anaconda-to-the-system-path)Windows error: Failed to create Anaconda menus or Failed to add Anaconda to the system PATH
***
Cause
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.
***
Solution
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.
To find your path variable:
1. Search for “environment variables” in the search in your taskbar.
2. Select **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**.
### [](https://www.anaconda.com/docs/reference/troubleshooting#anaconda-interfering-with-other-software-on-windows)Anaconda interfering with other software on Windows
***
Cause
If a user chooses to add Anaconda to the Windows PATH, this can cause programs to use the new Anaconda versions of software (like Python) and not the versions that were already in place. In some cases, this can cause incompatibility and errors.
***
Solution
Anaconda does NOT recommend adding Anaconda to the Windows PATH manually. Instead, use Anaconda software by opening Anaconda Navigator or Anaconda Prompt from the Start Menu.
### [](https://www.anaconda.com/docs/reference/troubleshooting#files-left-behind-after-uninstalling-anaconda-on-windows)Files left behind after uninstalling Anaconda on Windows
***
Cause
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>`.
Replace `<USERNAME>` with your Windows username as it appears in the `Documents and Settings` or `Users` folder.
***
Solution
Manually delete any unneeded settings files.
### [](https://www.anaconda.com/docs/reference/troubleshooting#spyder-errors-or-failure-to-launch-on-windows)Spyder errors or failure to launch on Windows
***
Cause
This may be caused by errors in the Spyder setting and configuration files.
***
Solution
1. Close and relaunch Spyder and see if the problem remains.
2. Open the Start Menu and then click **Reset Spyder Settings** and see if the problem remains.
3. Close Spyder and relaunch it from Anaconda Prompt with the following command:
```
spyder
```
4. 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.
### [](https://www.anaconda.com/docs/reference/troubleshooting#uninstaller-requests-admin-privileges-on-windows)Uninstaller requests admin privileges on Windows
***
Cause
After installing Anaconda or Miniconda as a non-administrative user on Windows, uninstalling may prompt for administrative privileges.
This occurs when running the uninstaller by choosing Control Panel \> Uninstall a program, selecting Anaconda or Miniconda from the list of programs, and clicking **Uninstall**.
***
Solution
Open the `anaconda3` or `miniconda3` installation folders and run the `.exe` file uninstaller from that location. Uninstallation will complete without prompting for administrative privileges.
EXAMPLE: If you installed Miniconda3, the uninstall file will be `Uninstall-Miniconda3.exe`. Users who installed Miniconda2 or Anaconda will find a similar file with the appropriate name.
### [](https://www.anaconda.com/docs/reference/troubleshooting#windows-permission-errors-when-installing-from-favorites-folder)Windows permission errors when installing from Favorites folder
***
Cause
The Windows Favorites folder has unusual permissions and may cause permission errors with installers of any software. If you try launching the installer from the Favorites folder, you may see errors such as “Setup was unable to create the directory”, “Access is denied”, or “Error opening file for writing”.
***
Solution
Move the installer to a different folder and run the installer from the new folder.
### [](https://www.anaconda.com/docs/reference/troubleshooting#trouble-with-activation-on-powershell-on-windows)Trouble with activation on PowerShell on Windows
***
Cause
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
1. Open a Command Prompt window.
2. Navigate to where you installed conda. The following command shows the default:
```
cd C:\Users\<USERNAME>
```
3. Run the following command:
```
python -m conda init
```
4. Close the Command Prompt window.
If the above method didn’t work, try running:
```
conda update conda
```
### [](https://www.anaconda.com/docs/reference/troubleshooting#linking-problems-when-python-extensions-are-compiled-with-gcc)Linking problems when Python extensions are compiled with gcc
***
Cause
When compiling Python extensions with gcc on Windows, linking problems may result.
***
Solution
To resolve these linking problems, use the conda package `libpython`, a mingw import library that Anaconda builds and includes with the Anaconda Distribution.
## [](https://www.anaconda.com/docs/reference/troubleshooting#macos-specific-issues)macOS-specific issues
### [](https://www.anaconda.com/docs/reference/troubleshooting#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
***
Cause
When running the `.pkg` installer, you may encounter this error during the “Installation” step:
This error occurs when the installation attempts to write to a directory for which it does not have write permissions.
***
Solution
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.
3. Click **Install on a specific disk…**.
4. Select the appropriate destination drive. Then click **Choose Folder…**.
5. Select 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**.
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`.
## [](https://www.anaconda.com/docs/reference/troubleshooting#linux-specific-issues)Linux-specific issues
### [](https://www.anaconda.com/docs/reference/troubleshooting#missing-libgomp-on-power8)Missing libgomp on Power8
***
Cause
If the Python command `import numpy` fails, the system is likely missing the `libgomp` system library. Most Power8 Linux distributions include `libgomp`, but some may not.
***
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
```
### [](https://www.anaconda.com/docs/reference/troubleshooting#anaconda-on-power8-reports-%E2%80%9Ccan-not-execute-binary-file%E2%80%9D)Anaconda on Power8 reports “can not execute binary file”
***
Cause
Anaconda on Power8 only supports little endian mode. The little endian Python binary will not execute on a big endian operating system.
***
Solution
Install Anaconda on Power8 on a little endian Linux installation or VM.
### [](https://www.anaconda.com/docs/reference/troubleshooting#anaconda-distribution-installation-failed-with-%E2%80%9C%E2%80%98ascii%E2%80%99-codec-can%E2%80%99t-encode-character-%E2%80%98xe4%E2%80%99-in-position-96%E2%80%9D-error)Anaconda Distribution installation failed with “‘ascii’ codec can’t encode character ‘xe4’ in position 96” error
***
Cause
The package `conda-package-streaming` requires certain encoding variables that fresh installations of Linux may not have properly set, causing an ASCII error and a failed installation of Anaconda Distribution.
***
Solution
1. 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"
```
2. If your installer partially ran before failing, your installation directory may not be empty. If so, delete your installation directory.
3. Rerun your installer.
## [](https://www.anaconda.com/docs/reference/troubleshooting#desktop-issues)Desktop issues
### [](https://www.anaconda.com/docs/reference/troubleshooting#model-won%E2%80%99t-load-exit-code-3221225781)Model won’t load (exit code 3221225781)
***
Cause
The model you are trying to load requires a C++ runtime environment, but Microsoft does not include one in their operating systems by default.
***
Solution
Install the Latest [Microsoft Visual C++ Redistributable Version](https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170#latest-microsoft-visual-c-redistributable-version).
## [](https://www.anaconda.com/docs/reference/troubleshooting#navigator-issues)Navigator issues
### [](https://www.anaconda.com/docs/reference/troubleshooting#custom-navigator-app-isn%E2%80%99t-appearing-on-the-home-page)Custom Navigator app isn’t appearing on the Home page
***
Cause
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.
***
Solution
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.
### [](https://www.anaconda.com/docs/reference/troubleshooting#custom-navigator-app-won%E2%80%99t-launch)Custom Navigator app won’t launch
***
Cause
The app can fail to launch due to Navigator configuration issues, even if the application itself is functioning correctly.
***
Solution
1. If the application does not launch after installation, confirm that it works via the command line by running the following command:
```
conda run jupyter lab
```
If you are not using the example feedstock, the command after `run` will be the `entry:` command you have designated.
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.
### [](https://www.anaconda.com/docs/reference/troubleshooting#navigator-fails-to-update-to-version-2-6-4)Navigator fails to update to version 2.6.4
***
Cause
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.)
***
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`:
1. Close Navigator, if open.
2. Open Anaconda Prompt (Terminal on macOS/Linux).
3. Run the following command:
```
conda install --name base anaconda-navigator=2.6.4 anaconda-toolbox=4.1.0
```
4. Enter `y` to approve the package changes.
Once your base environment is updated, it is safe to close Anaconda Prompt/Terminal.
5. Reopen Navigator.
Once this dependency conflict is resolved, any future updates to Navigator can be accomplished as usual.
### [](https://www.anaconda.com/docs/reference/troubleshooting#navigator-error-on-start-up)Navigator error on start up
***
Cause
This is often the result of a corrupted `.condarc` file.
***
Solution
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.
The `.condarc` file is frequently found in:
Windows
macOS
Linux
```
C:\Users\<USERNAME>
```
2. Optional: Save custom configurations.
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.
3. Delete the `.condarc` file.
4. Restart Navigator.
### [](https://www.anaconda.com/docs/reference/troubleshooting#issues-launching-or-initializing)Issues launching or initializing
***
Cause
Issues launching or initializing Anaconda Navigator may be caused by permission or licensing problems.
***
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:
Windows
macOS/Linux
```
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
```
### [](https://www.anaconda.com/docs/reference/troubleshooting#permissionerror-on-macos-catalina)PermissionError on macOS Catalina
***
Cause
macOS Catalina users may experience permission errors where the system does not prompt you for permission to folders requiring access.
***
Solution
1. Update Navigator by opening Anaconda Prompt (Terminal on macOS/Linux) and running the following command:
```
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:
```
import os
os.listdir('<DIRECTORY>')
```
### [](https://www.anaconda.com/docs/reference/troubleshooting#access-denied-error)Access denied error
***
Cause
A lock file wasn’t removed when it should have been.
***
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
```
### [](https://www.anaconda.com/docs/reference/troubleshooting#navigator-buttons-are-missing)Navigator buttons are missing
***
Cause
The disappearance of Navigator buttons may be caused by an out of sync repodata, a corrupt `.condarc` file, or an unknown issue.
***
Solution
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:
```
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.
### [](https://www.anaconda.com/docs/reference/troubleshooting#trouble-logging-in-to-package-security-manager-on-prem-in-navigator)Trouble logging in to Package Security Manager (On-prem) in Navigator
***
Cause
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.
***
Solution
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**.
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.
2. Remove the `channel_alias:` entry from the conda configuration file (`.condarc`).
3. Try signing in again.
### [](https://www.anaconda.com/docs/reference/troubleshooting#vs-code-is-not-appearing-on-the-navigator-home-tab)VS Code is not appearing on the Navigator Home tab
***
Cause
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):
Windows User-Only Installation
Windows System-Wide Installation
macOS
Linux-64
```
C:\Users\User\AppData\Local\Programs\Microsoft VS Code
```
***
Solution
There are two options for solving this issue:
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/).
On macOS, make sure the VS Code application is moved from your Downloads folder to your Applications folder.
3. Re-open Navigator.
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.
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 Navigator.
### [](https://www.anaconda.com/docs/reference/troubleshooting#anaconda-navigator-fails-to-start-and-gives-permission-denied-error)Anaconda Navigator fails to start and gives Permission denied error
***
Cause
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.
***
Solution
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](https://www.anaconda.com/docs/getting-started/anaconda/uninstall) and then [reinstall Anaconda](https://www.anaconda.com/docs/getting-started/anaconda/install/overview) without admin privileges.
Manually change the .continuum folder's user permissions
You will need administrator privileges to do this.
- Windows
- macOS/Linux
1. Search for “powershell”.
2. Right-click the Windows PowerShell app and select **Run as administrator**.
3. Run the following command:
```
icacls C:\Users\<USERNAME>\.continuum /grant:r <USERNAME>:(i,f) /t
```
1. Open your terminal application.
2. Run the following command:
```
sudo chmod 766 /.continuum
```
### [](https://www.anaconda.com/docs/reference/troubleshooting#navigator-gives-%E2%80%98email-verification-failed%E2%80%99-error-403)Navigator gives ‘Email verification failed’ error 403
***
Cause
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.
***
Solution
To connect to Anaconda.org again through Navigator, [update your Navigator version](https://www.anaconda.com/docs/tools/anaconda-navigator/update-navigator) or verify your Anaconda.org account.
**Verify your anaconda.org account**
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.
### [](https://www.anaconda.com/docs/reference/troubleshooting#navigator-fails-to-start-due-to-%E2%80%9Ccould-not-load-the-qt-platform-plugin-%E2%80%9Cxcb%E2%80%9D-in--even-though-it-was-found%E2%80%9D-error)Navigator fails to start due to “Could not load the Qt platform plugin “xcb” in "" even though it was found” error
***
Cause
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.”
***
Solution
1. Open a terminal application.
2. Install the missing system libraries and run updates:
```
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.
### [](https://www.anaconda.com/docs/reference/troubleshooting#disable-anaconda-com-login-reminder)Disable Anaconda.com login reminder
***
Cause
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.
***
Solution
There are a few ways to disable the Anaconda.com login reminder, depending on your version of Navigator:
- 2\.6.1 and later
- 2\.5.2 to 2.6.0
- 2\.5.0
Work in [offline mode](https://www.anaconda.com/docs/tools/anaconda-navigator/tutorials/offline-mode) or [log in to another repository](https://www.anaconda.com/docs/tools/anaconda-navigator/tutorials/connecting-to-other-repos).
1. [Open the Navigator configuration file](https://www.anaconda.com/docs/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.
```
[internal]
anaconda_toolbox_installed = True
cloud_login_popup_state = 0
```
1. [Open the Navigator configuration file](https://www.anaconda.com/docs/tools/anaconda-navigator/tutorials/editing-config-files).
2. Edit the `welcome_state` to be `0` in the `[internal]` section of the configuration file.
```
[internal]
welcome_state = 0
```
### [](https://www.anaconda.com/docs/reference/troubleshooting#update-popup-not-automatically-appearing)Update popup not automatically appearing
***
Cause
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
***
Solution
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, select **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**.
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…**.
defaults is missing from your channels list
This issue specifically impacts users without a subscription to our premium repository.
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.
### [](https://www.anaconda.com/docs/reference/troubleshooting#environment-backup-not-working-in-navigator-with-unable-to-create-requested-file-error)Environment backup not working in Navigator with Unable to create requested file error
***
Cause
An update to the environment export option in conda v25.7.0 is incompatible with the existing Navigator implementation for backing up environments.
***
Solution
Upgrade conda to the latest version by running the following command:
```
conda update --name base conda
```
Confirm your installed version of conda by running the following command:
```
conda --version
```
## [](https://www.anaconda.com/docs/reference/troubleshooting#anaconda-org-issues)Anaconda.org issues
### [](https://www.anaconda.com/docs/reference/troubleshooting#captcha-not-appearing-when-trying-to-create-an-anaconda-org-account-on-firefox)Captcha not appearing when trying to create an Anaconda.org account on Firefox
***
Cause
The captcha at the bottom of the **Sign In** panel on [Anaconda.org](https://anaconda.org/) sometimes fails to appear on Firefox browsers. The captcha may be blocked by an ad blocker extension, tracking blocker extension, or Firefox’s privacy settings.
***
Solution
1. Refresh your browser and try again. If refreshing multiple times, wait a few seconds between each refresh.
2. Check your extensions. Extensions that block tracking or ads may also block the captcha.
3. Check your browser settings. Privacy settings may block the captcha.
4. Open the [sign in page](https://anaconda.org/) in a [private browsing window](https://www.mozilla.org/en-US/firefox/features/private-browsing/).
### [](https://www.anaconda.com/docs/reference/troubleshooting#%E2%80%9Duri-no-longer-exists-and-has-been-permanently-removed%E2%80%9D-410-error-when-attempting-to-upload-notebooks-or-environments-to-anaconda-org)”URI no longer exists and has been permanently removed” 410 error when attempting to upload notebooks or environments to Anaconda.org
***
Cause
The Notebooks and Environments features have been removed from Anaconda.org as part of an initiative to streamline and improve Anaconda.org and enable the site to focus on package hosting and management. Because of this, notebook and environment files can no longer be uploaded to Anaconda.org using the `anaconda upload` command.
***
Solution
Although you can no longer upload notebooks to Anaconda.org, you can share your notebooks with others using [Anaconda Notebooks](https://nb.anaconda.com/) instead. Anaconda Notebooks come with their own preloaded Environments and allow you to create your own custom environments as well. For more information on sharing notebooks with Anaconda Notebooks, see [Sharing notebooks](https://www.anaconda.com/docs/tools/anaconda-notebooks/sharing-notebooks).
### [](https://www.anaconda.com/docs/reference/troubleshooting#users-don%E2%80%99t-have-passwords-for-anaconda-client-login-to-anaconda-org)Users don’t have passwords for `anaconda-client` login to Anaconda.org
***
Cause
If you created an account on Anaconda.org and used the Google, Microsoft, or GitHub authorization options to sign up, you do not have a password associated with your account. `anaconda-client` v1.13.1 and older require a username and password to log in to anaconda.org.
***
Solution
To log in to anaconda.org without a password using `anaconda-client`, you must update `anaconda-client` to v1.14.0 or later in your base environment:
1. Open Anaconda Prompt (Terminal in macOS/Linux).
2. Update or install `anaconda-client` by running the following command:
```
conda install --name base "anaconda-client>=1.14.0"
```
3. Log into Anaconda.org:
```
anaconda org login
```
4. A browser window opens to authenticate you to Anaconda.org. Sign in with your account credentials to complete authentication in the browser.
## [](https://www.anaconda.com/docs/reference/troubleshooting#notebooks-issues)Notebooks issues
### [](https://www.anaconda.com/docs/reference/troubleshooting#toolbox-environment-card-says-the-environment-is-installed-but-no-environment-in-the-launcher-or-runtime-selector)Toolbox environment card says the environment is installed, but no environment in the Launcher or runtime selector
***
Cause
The environment might not have fully synchronized with the Launcher or runtime selector yet.
***
Solution
First, try refreshing the browser page. If the environment still doesn’t appear after refreshing, check the Environments page in Navigator to see if it’s available. If the environment is still unavailable after waiting two minutes, close all open Jupyter sessions and restart Jupyter from Navigator or the command line.
### [](https://www.anaconda.com/docs/reference/troubleshooting#quickstart-environment-installation-errored)Quickstart environment installation errored
***
Cause
Installation errors can occur due to misconfigured channels in your `.condarc` file, organizational policies blocking installation, connectivity issues, or stale Jupyter kernel states.
***
Solution
First, check your `.condarc` file and verify that your channels are set to either `defaults` or `conda-forge`. If your channels are set correctly and you’re still experiencing issues, check with your administrator to see if they have defined any policies that could be blocking installation.
If neither of the above resolves the issue, you can try:
- Refreshing the page
- Checking your internet connection
- Shutting down all running Jupyter kernels and restarting your Jupyter instance
### [](https://www.anaconda.com/docs/reference/troubleshooting#cli-or-navigator-gives-%E2%80%9Cerror-starting-kernel%E2%80%9D-message)CLI or Navigator gives “error starting kernel” message
***
Cause
Uninstalling a quick start environment using either the CLI or Navigator can result in an `Error starting kernel: [Errno 2] No such file or directory` message, because the Jupyter kernel references aren’t properly removed when the environment is deleted.
***
Solution
To resolve this issue:
1. Open Anaconda Prompt (Terminal in macOS/Linux)
2. Run:
```
jupyter kernelspec list
```
3. Find the name of the quick start environment you deleted.
4. Then run:
```
jupyter kernelspec uninstall <ENV_NAME>
```
### [](https://www.anaconda.com/docs/reference/troubleshooting#published-panel-app-is-blank)Published Panel app is blank
***
Cause
The app can appear blank if the notebook cannot be executed sequentially from top to bottom, which can happen when cells have dependencies that aren’t met or are out of order.
***
Solution
If you added content to your app but there’s still nothing showing up, ensure that your notebook can be run from top to bottom. The easiest way to test this is to select **Run** in the top menu, then select *Run All Cells*.
### [](https://www.anaconda.com/docs/reference/troubleshooting#all-cpu-seconds-have-been-used-up-in-notebooks)All CPU seconds have been used up in Notebooks
***
Cause
You’ve used up all your available CPU seconds.
***
Solution
CPU seconds are consumed by active runtimes, which can continue to run in the background even after you’ve logged out of Notebooks or switched to a different browser tab.
To prevent your CPU seconds from being used while you are not actively using Notebooks, make sure you shut down all runtimes in all open instances of Notebooks before logging off for the day. You can do this from the
**Running Terminals and Kernels** tab:
If the problem persists, please raise the issue in the [Anaconda community forums](https://forum.anaconda.com/) or [file a support ticket](https://support.anaconda.com/hc/en-us/requests/new?ticket_form_id=360000993773).
You can upgrade your subscription plan to access additional CPU seconds. See our [pricing page](https://www.anaconda.com/pricing) for further details.
### [](https://www.anaconda.com/docs/reference/troubleshooting#error-when-importing-packages-in-notebooks)Error when importing packages in Notebooks
***
Cause
The most common cause of errors is a lack of required package(s) installed in your environment. The default environment we provide, based on the Anaconda distribution, contains hundreds of the most common python packages for data science, but it doesn’t include everything. You might need to create a custom environment to install the package you need.
***
Solution
Make sure you have the right runtime selected
The default `anaconda-<YEAR>.<MONTH>-py<PYTHON_VERSION>` runtimes have a broad selection of packages, but you might have created a custom environment for your notebook. Separate environments are represented as “runtimes” in JupyterLab. You can view and switch between available runtimes by clicking the runtime name in the upper-right corner of the content pane.
List the packages available in an environment
If one of your imports is failing, start by verifying that the package is present in the runtime environment. You can view which packages are available in your current environment from the terminal by running `conda list`.To view packages in a specific environment, run `conda list --name <ENV_NAME>`.To see a list of available environments, run `conda info --envs`. An asterisk appears beside your current active environment.
Create a custom runtime
If none of the Anaconda provided environments contain the package(s) you need, create a [custom runtime](https://www.anaconda.com/docs/tools/anaconda-notebooks/notebook-runtimes#creating-custom-runtimes) for your notebook project.
### [](https://www.anaconda.com/docs/reference/troubleshooting#%E2%80%9Dmissing-ipykernel-dependency%E2%80%9D-error)”Missing ipykernel dependency” error
***
Cause
A `missing ipykernel dependency` error is caused by an environment dependency list not including the required `ipykernel` package.
***
Solution
To resolve this issue, add the `ipykernel` package to your environment’s dependency list. For example:
```
channels:
- defaults
dependencies:
- python=3.11
- numpy
- pandas
- ipykernel
```
### [](https://www.anaconda.com/docs/reference/troubleshooting#custom-runtime-not-appearing-in-launcher-or-assign-a-runtime-modal)Custom runtime not appearing in Launcher or Assign a Runtime modal
***
Cause
The most common reason a runtime or environment is not appearing in the Launcher or Assign a Runtime modal is that it doesn’t contain a
kernel package
.
***
Solution
For more information and instructions on installing a kernel package in your runtime/environment, see [Creating custom runtimes](https://www.anaconda.com/docs/tools/anaconda-notebooks/notebook-runtimes#creating-custom-runtimes).
### [](https://www.anaconda.com/docs/reference/troubleshooting#%E2%80%9Dfile-load-error%E2%80%9D-%E2%80%9Cunhandled-error%E2%80%9D-or-%E2%80%9Cunexpected-error%E2%80%9D-message)”File load error,” “unhandled error,” or “unexpected error” message
***
Cause
If you receive a “file load error,” “unhandled error,” or “unexpected error,” like in the following figure, you have most likely exceeded the storage space for your current plan.
***
Solution
Follow the steps in the storage question above to remove items from your Notebooks instance, or upgrade to a higher subscription plan.
### [](https://www.anaconda.com/docs/reference/troubleshooting#notebooks-won%E2%80%99t-open-from-anaconda-platform)Notebooks won’t open from Anaconda Platform
***
Cause
Your browser’s pop-up blocker (automatically enabled on Firefox and Safari) can prevent Notebooks from opening.
***
Solution
Disable your pop-up blocker and try opening Notebooks again from Anaconda Platform.
### [](https://www.anaconda.com/docs/reference/troubleshooting#notebook-cannot-access-external-sites-after-subscription-upgrade)Notebook cannot access external sites after subscription upgrade
***
Cause
Notebook kernels inherit network permissions when a session is started. Any notebook sessions that were started while your account was using the Free plan are still operating under PythonAnywhere’s [allowlist](https://www.pythonanywhere.com/whitelist/) restrictions.
***
Solution
Stop and restart all Notebook sessions to establish a kernel with unrestricted internet access.
It can take up to an hour for the upgrade to take effect.
## [](https://www.anaconda.com/docs/reference/troubleshooting#ai-navigator-issues)AI Navigator issues
### [](https://www.anaconda.com/docs/reference/troubleshooting#model-won%E2%80%99t-load-exit-code-3221225781-2)Model won’t load (exit code 3221225781)
***
Cause
The model you are trying to load requires a C++ runtime environment, but Microsoft does not include one in their operating systems by default.
***
Solution
Install the Latest [Microsoft Visual C++ Redistributable Version](https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170#latest-microsoft-visual-c-redistributable-version).
## [](https://www.anaconda.com/docs/reference/troubleshooting#toolbox-excel-add-in-issues)Toolbox Excel add-in issues
### [](https://www.anaconda.com/docs/reference/troubleshooting#error-installing-functions-in-excel)Error installing functions in Excel
***
Cause
This error can occur when Excel loads the Anaconda Toolbox add-in and registers its custom functions. This error happens within Excel and cannot be resolved by the Anaconda Toolbox.
***
Solution
Close and reopen Excel. If the issue persists, uninstall the Anaconda Toolbox add-in, then reinstall.
Was this page helpful?
Yes
No
[Release notes](https://www.anaconda.com/docs/reference/release-notes)
[Help and support](https://www.anaconda.com/docs/reference/help-support)
Ctrl+I
[Anaconda home page](https://www.anaconda.com/)
[bluesky](https://bsky.app/profile/anacondainc.bsky.social)
[linkedin](https://www.linkedin.com/company/anacondainc)
[github](https://github.com/ContinuumIO)
[youtube](https://www.youtube.com/c/ContinuumIo)
[Anaconda Newsletter](https://www.anaconda.com/newsletter)
[bluesky](https://bsky.app/profile/anacondainc.bsky.social)
[linkedin](https://www.linkedin.com/company/anacondainc)
[github](https://github.com/ContinuumIO)
[youtube](https://www.youtube.com/c/ContinuumIo)
Assistant
Responses are generated using AI and may contain mistakes. |
| Readable Markdown | This page includes common troubleshooting topics for Anaconda products. Issues are grouped by product and category.
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).
## [](https://www.anaconda.com/docs/reference/troubleshooting#most-common-issues)Most common issues
[](https://www.anaconda.com/docs/reference/troubleshooting#command-not-found-conda)command not found: conda
***
Cause
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.
These issues primarily occur on macOS/Linux computers. Anaconda Distribution and Miniconda installations on Windows include [Anaconda Prompt](https://www.anaconda.com/docs/reference/glossary#anaconda-prompt), which opens with conda initialized by default.
***
Solution
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.
If you don’t want to close your CLI, you can also use one of the following `source` commands to refresh your shell:
```
source ~/.bashrc
```
You can also initialize conda directly from its `bin` directory:
```
<PATH_TO_CONDA>/bin/conda init
```
Set auto\_activate\_base to true
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` to `true`, run the following command:
```
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`.
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.
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](https://www.anaconda.com/docs/getting-started/anaconda/main) or [Miniconda](https://www.anaconda.com/docs/getting-started/miniconda/main).
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](https://www.anaconda.com/docs/reference/troubleshooting#initialize-conda-in-your-shell).
[](https://www.anaconda.com/docs/reference/troubleshooting#condahttperror-http-400-bad-request-for-url)CondaHTTPError: HTTP 400 Bad Request for URL
***
Cause
A **400 Bad Request** error typically means there’s a typo in your channel URL. When you pass a full URL with the `-c` flag, conda doesn’t validate whether the channel exists—it just makes the request. If the path is wrong, the server returns a 400 error.
***
Solution
Double-check your channel URL for typos and try again.
[](https://www.anaconda.com/docs/reference/troubleshooting#unavailableinvalidchannel-http-404-not-found-for-channel)UnavailableInvalidChannel: HTTP 404 Not Found for channel
***
Cause
A **404 Not Found** error means the channel you specified doesn’t exist. This is usually caused by a typo in the channel name, either in your `.condarc` file or when using the `-c` flag.
***
Solution
Check your command for typos and try again.To see which channels are currently configured, run:
```
conda config --show channels
```
If you see a misspelled channel in your configuration, remove it with:
```
conda config --remove channels <MISSPELLED_CHANNEL>
```
For help adding adding and removing channels to your `.condarc` file, see [Managing channels](https://www.anaconda.com/docs/getting-started/working-with-conda/channels#managing-channels).
[](https://www.anaconda.com/docs/reference/troubleshooting#packagesnotfounderror-the-following-packages-are-not-available-from-current-channels)PackagesNotFoundError: The following packages are not available from current channels
***
Cause
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.
***
Solution
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](https://www.anaconda.com/docs/getting-started/working-with-conda/packages/install-packages#using-conda-install).
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](https://www.anaconda.com/docs/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.
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](https://www.anaconda.com/docs/getting-started/working-with-conda/channels#installing-packages-from-a-specific-channel).
Add the missing channel to your .condarc file
[Add the missing channel to your .condarc file](https://www.anaconda.com/docs/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.
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.
```
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.
[](https://www.anaconda.com/docs/reference/troubleshooting#directorynotacondaenvironmenterror-the-target-directory-exists-but-it-is-not-a-conda-environment)DirectoryNotACondaEnvironmentError: The target directory exists, but it is not a conda environment
***
Cause
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.
***
Solution
Activate your `base` environment or another environment:
```
# Activate your base environment
conda activate
# Activate an environment by name
conda activate <ENV_NAME>
```
[](https://www.anaconda.com/docs/reference/troubleshooting#environmentnotwriteableerror)EnvironmentNotWriteableError
***
Cause
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*.
***
Solution
Create your own environment instead, in a directory you don’t need admin permissions to work in, such as your home directory:
```
conda create --name <ENV_NAME> --prefix <PATH_TO_USER_DIRECTORY>
```
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](https://www.anaconda.com/docs/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:
```
conda create --file environment.yml --prefix <PATH_TO_USER_DIRECTORY>
```
[](https://www.anaconda.com/docs/reference/troubleshooting#modulenotfounderror-no-module-named-x)ModuleNotFoundError: No module named X
***
Cause
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.
***
Solution
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:
```
conda info --envs
```
An asterisk is displayed next to your currently active environment:
Environment list example
```
(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](https://www.anaconda.com/docs/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](https://www.anaconda.com/docs/getting-started/working-with-conda/packages/install-packages).
[](https://www.anaconda.com/docs/reference/troubleshooting#receiving-a-403-forbidden-error-from-an-anaconda-channel)Receiving a 403 Forbidden error from an Anaconda channel
***
Cause
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.The 403 error you are receiving may look like the following:
```
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.
***
Solution
Run `anaconda token install` to issue and set a new token for yourself, then try again.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.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).
[](https://www.anaconda.com/docs/reference/troubleshooting#http-000-connection-failed)HTTP 000 CONNECTION FAILED
***
Cause
This is generally caused by a proxy misconfiguration.
***
Solution
Follow instructions on [Using Anaconda behind a company proxy](https://www.anaconda.com/docs/getting-started/working-with-conda/reference/proxy) to configure your proxy correctly.
[](https://www.anaconda.com/docs/reference/troubleshooting#conda-update-anaconda-command-does-not-install-the-latest-version-of-the-anaconda-metapackage)`conda update anaconda` command does not install the latest version of the `anaconda` metapackage
***
Cause
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.
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.
***
Solution
1. 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.
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:
```
conda remove anaconda
```
2. 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:
1. Remove the conflicting packages by running the following command for each one:
```
conda remove <PACKAGE>
```
2. Update to the latest version of the `anaconda` metapackage:
```
conda update anaconda
```
[](https://www.anaconda.com/docs/reference/troubleshooting#recovering-your-anaconda-installation)Recovering your Anaconda installation
***
Cause
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
1. Download a [new installer](https://repo.anaconda.com/archive/), then follow the instructions for your operating system.
Use the actual path, filename, and directory name for your installation.
- Windows
- macOS
- Linux
1. Open a terminal application, such as Command Prompt.
2. Change your original installer’s name so you do not overwrite it:
```
move anaconda3 anaconda_old
```
3. Run the Anaconda.exe installer as usual and use robocopy to sync the directories:
```
robocopy anaconda_old anaconda3 /S
```
4. Delete your old Anaconda installation directory:
```
rd /s anaconda_old
```
1. Open a terminal application.
2. Change your original installer’s name so you do not overwrite it:
```
mv anaconda3 anaconda_old
```
3. Install to same directory as your original installer:
```
# Replace <INSTALLER> the name of your installer file
bash ~/Downloads/<INSTALLER>
rsync -a anaconda_old/ anaconda3/
```
4. Delete your old Anaconda installation directory:
```
rm -rf anaconda_old
```
1. Open a terminal application.
2. Change your original installer’s name so you do not overwrite it:
```
mv anaconda3 anaconda_old
```
3. Install to same directory as your original installer:
```
# Replace <INSTALLER> the name of your installer file
bash ~/Downloads/<INSTALLER>
rsync -a anaconda_old/ anaconda3/
```
4. Delete your old Anaconda installation directory:
```
rm -rf anaconda_old
```
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.
[](https://www.anaconda.com/docs/reference/troubleshooting#channels-list-adding-extra-channels)Channels list adding extra channels
***
Cause
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.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.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.
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
```
***
Solution
There 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.
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:
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
- Windows
- Linux/macOS
```
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
```
```
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
```
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:
```
conda config --add default_channels <CHANNEL>
```
To remove a channel instead, replace `--add` with `--remove`.
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.
Make sure that you always have at least one `.condarc` file with a `channels:` list defined. Conda requires this to function.
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. You can view hidden files and folders using the following guidance for your operating system:
- macOS
- Linux
To view hidden files on macOS, use Shift+Cmd+. in your Finder.
To view hidden files on Linux, use Alt+. or Ctrl+H (depending on your file manager).
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.
If you continue to experience issues, please [open a support ticket](https://support.anaconda.com/hc/en-us/requests/new?ticket_form_id=360000993773).
[](https://www.anaconda.com/docs/reference/troubleshooting#uninstall-sh-not-found)Uninstall.sh not found
***
Cause
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.
***
Solution
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:
```
conda info --base
```
3. Check the contents of your installation folder for the `uninstall.sh` script:
```
ls <PATH/TO/INSTALLER>
```
4. If your install is in your home directory (`\Users\<USERNAME>\` or `\home\<USERNAME>`), use the macOS/Linux **Basic uninstall** instructions. If your install is in your `\opt\` folder, use the macOS/Linux **System uninstall** instructions. If your install folder does not contain the `uninstall.sh` file, use the macOS/Linux **Manual uninstall** instructions.
- [Anaconda Distribution uninstall instructions](https://www.anaconda.com/docs/getting-started/anaconda/uninstall#uninstall-procedure)
- [Miniconda uninstall instructions](https://www.anaconda.com/docs/getting-started/miniconda/uninstall#uninstall-procedure)
[](https://www.anaconda.com/docs/reference/troubleshooting#not-receiving-anaconda-com-account-verification-email)Not receiving Anaconda.com account verification email
***
Cause
Your browser may have cached data from a previous signup session or authentication attempt, which can interfere with the verification email being triggered.Alternatively, the verification email may have been sent but filtered to your spam, junk, or promotions folder by your email provider.
***
Solution
First, check your junk mailbox or any other folders where emails may be automatically filtered. If the email is not there, clear your browser cache and cookies, then try logging in again at <https://auth.anaconda.com/ui/login/>.If you still do not receive the email, please [submit a support ticket](https://support.anaconda.com/hc/en-us/requests/new).
[](https://www.anaconda.com/docs/reference/troubleshooting#i-can%E2%80%99t-access-my-learning-courses)I can’t access my learning courses
***
Cause
Your browser session may not be properly synced with your subscription status, or cached authentication data may be outdated.
***
Solution
Clear your browser cache and cookies, then try accessing the courses again.If the issue persists, [sign out completely](https://learning.anaconda.com/users/sign_out), then [sign back in](https://learning.anaconda.com/users/sign_in).If you still cannot access your courses, navigate to <https://auth.anaconda.com/api/auth/sessions/whoami>, copy the contents displayed, and include them when you [submit a support ticket](https://support.anaconda.com/hc/en-us/requests/new).
[](https://www.anaconda.com/docs/reference/troubleshooting#unable-to-reset-anaconda-com-account-password)Unable to reset Anaconda.com account password
***
Cause
Your email address must be verified before you can reset your password.
***
Solution
Follow the instructions in your verification email. If the verification link has expired, request a new verification email.If you still have trouble resetting your password after verifying your account, [submit a support ticket](https://support.anaconda.com/hc/en-us/requests/new).
[](https://www.anaconda.com/docs/reference/troubleshooting#subscribed-to-academic-plan-but-seeing-starter-plan)Subscribed to Academic plan but seeing Starter plan
***
Cause
This is expected behavior. The Academic plan is essentially the Starter plan, provided free of charge based on your status as a student.
***
Solution
No action is required. For details on what is included in your plan, see [Anaconda Pricing](https://www.anaconda.com/pricing).
## [](https://www.anaconda.com/docs/reference/troubleshooting#anaconda-distribution-issues)Anaconda Distribution issues
[](https://www.anaconda.com/docs/reference/troubleshooting#using-anaconda-behind-a-firewall-or-proxy)Using Anaconda behind a firewall or proxy
***
Cause
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 might need to connect to a firewall/proxy. Additionally, your IT team might need to allow connections to [https://anaconda.org](https://anaconda.org/) and [https://repo.anaconda.com](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](https://docs.conda.io/projects/conda/en/latest/user-guide/configuration/settings.html#proxy-servers-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](https://anaconda.com/) or [https://repo.continuum.io](https://repo.continuum.io/).
[](https://www.anaconda.com/docs/reference/troubleshooting#insecureplatformwarning-error)InsecurePlatformWarning error
***
Cause
`InsecurePlatformWarning` appears only when the installed version of Python is older than version 2.7.9. This message warns only that the validity of the SSL connection is not being verified. It should not affect your package downloads.
***
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.
[](https://www.anaconda.com/docs/reference/troubleshooting#anaconda-search-error-not-recognized-as-an-internal-or-external-command/unrecognized-arguments)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:
```
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:
1. Install `anaconda-client` by running the following command:
```
conda install anaconda-client
```
2. Search for a package:
```
anaconda search --package-type conda <PACKAGE>
```
[](https://www.anaconda.com/docs/reference/troubleshooting#collecting-package-metadata-repodata-json--killed)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
Verify that you have enough disk space and memory on your system to install and use Anaconda packages. The minimum system requirements for Miniconda and Anaconda installers can be found in the `conda` [user guide](https://docs.conda.io/projects/conda/en/stable/user-guide/install/index.html#system-requirements).
[](https://www.anaconda.com/docs/reference/troubleshooting#error-message-unable-to-remove-files)Error message: Unable to remove files
***
Cause
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.
```
Generally, this is caused by a file lock issue.
***
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:
```
conda install --force-reinstall <PACKAGE>
```
[](https://www.anaconda.com/docs/reference/troubleshooting#using-32-and-64-bit-libraries-and-conda_force_32bit)Using 32- and 64-bit libraries and CONDA\_FORCE\_32BIT
***
Cause
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 --all
```
- 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.
[](https://www.anaconda.com/docs/reference/troubleshooting#proxy-request-sent-not-found)Proxy request sent, not found
***
Cause
Your company likely has security policies or a firewall in place that prevent communications with external servers or certain URLs.
***
Solution
1. First, work with your IT team to allowlist connections to the following URLs:
```
https://anaconda.org
https://repo.anaconda.com
https://repo.anaconda.cloud
```
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.
2. [Install](https://www.anaconda.com/docs/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](https://www.anaconda.com/docs/anaconda-platform/cloud/getting-started-with-anaconda-platform#using-anaconda-behind-a-firewall-or-proxy-optional).
## [](https://www.anaconda.com/docs/reference/troubleshooting#installation-issues)Installation issues
[](https://www.anaconda.com/docs/reference/troubleshooting#anaconda-installer-download-problems)Anaconda installer download problems
***
Cause
The Anaconda installer files are large (over 600 MB), and some users have problems with errors and interrupted downloads when downloading large files.
***
Solution
- Download Miniconda
- Restart the download
1. Download and install the smaller [Miniconda](https://www.anaconda.com/docs/getting-started/miniconda/main) (between 70 and 100 MB).
2. 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.
Download the large Anaconda installer file, and restart it if the download is interrupted or you need to pause it.
- Windows
- macOS/Linux
- Chrome
- 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 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.
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.
Go to `edge://downloads/all` to open the full page of recent downloads. From here, you can retry cancelled downloads.
1. Open a terminal window.
2. To download the file, use the following command:
```
# 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.
While a download is paused, you can shut down or restart your computer.
4. When you are ready to resume your download, use the following command:
```
curl -O -C https://repo.anaconda.com/archive/<INSTALLER>
```
The `-C` flag is the option for “continue”. You can pause and restart a download as many times as you wish.
[](https://www.anaconda.com/docs/reference/troubleshooting#error-message-on-install-already-installed)Error message on install: Already installed
***
Cause
This situation can occur if you are getting a conda error and you want to reinstall Miniconda to fix it.
***
Solution
For macOS and Linux, download and install the appropriate Miniconda for your operating system from the [Miniconda download page](https://www.anaconda.com/docs/getting-started/miniconda/main) using the `--force` or `-f` option by running the following command:
```
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.
[](https://www.anaconda.com/docs/reference/troubleshooting#macos-installation-failure-x86_64-intel-chip)macOS installation failure - x86\_64 (Intel chip)
***
Cause
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.
***
Solution
To check what architecture your macOS computer has:
1. Select the
**Apple** icon on your title bar.
2. Select **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)
## [](https://www.anaconda.com/docs/reference/troubleshooting#windows-specific-issues)Windows-specific issues
[](https://www.anaconda.com/docs/reference/troubleshooting#cannot-see-anaconda-menu-shortcuts-after-installation-on-windows)Cannot see Anaconda menu shortcuts after installation on Windows
***
Cause
After installing on Windows, the Anaconda Prompt and Anaconda Navigator shortcuts do not appear in the Windows Start menu.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.
***
Solution
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).If that doesn’t work, clear your `$PYTHONPATH` environment variable, if applicable, and re-install Anaconda.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).
[](https://www.anaconda.com/docs/reference/troubleshooting#windows-error-failed-to-create-anaconda-menus-or-failed-to-add-anaconda-to-the-system-path)Windows error: Failed to create Anaconda menus or Failed to add Anaconda to the system PATH
***
Cause
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.
***
Solution
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.
To find your path variable:
1. Search for “environment variables” in the search in your taskbar.
2. Select **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**.
[](https://www.anaconda.com/docs/reference/troubleshooting#anaconda-interfering-with-other-software-on-windows)Anaconda interfering with other software on Windows
***
Cause
If a user chooses to add Anaconda to the Windows PATH, this can cause programs to use the new Anaconda versions of software (like Python) and not the versions that were already in place. In some cases, this can cause incompatibility and errors.
***
Solution
Anaconda does NOT recommend adding Anaconda to the Windows PATH manually. Instead, use Anaconda software by opening Anaconda Navigator or Anaconda Prompt from the Start Menu.
[](https://www.anaconda.com/docs/reference/troubleshooting#files-left-behind-after-uninstalling-anaconda-on-windows)Files left behind after uninstalling Anaconda on Windows
***
Cause
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>`.
Replace `<USERNAME>` with your Windows username as it appears in the `Documents and Settings` or `Users` folder.
***
Solution
Manually delete any unneeded settings files.
[](https://www.anaconda.com/docs/reference/troubleshooting#spyder-errors-or-failure-to-launch-on-windows)Spyder errors or failure to launch on Windows
***
Cause
This may be caused by errors in the Spyder setting and configuration files.
***
Solution
1. Close and relaunch Spyder and see if the problem remains.
2. Open the Start Menu and then click **Reset Spyder Settings** and see if the problem remains.
3. Close Spyder and relaunch it from Anaconda Prompt with the following command:
```
spyder
```
4. 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.
[](https://www.anaconda.com/docs/reference/troubleshooting#uninstaller-requests-admin-privileges-on-windows)Uninstaller requests admin privileges on Windows
***
Cause
After installing Anaconda or Miniconda as a non-administrative user on Windows, uninstalling may prompt for administrative privileges.This occurs when running the uninstaller by choosing Control Panel \> Uninstall a program, selecting Anaconda or Miniconda from the list of programs, and clicking **Uninstall**.
***
Solution
Open the `anaconda3` or `miniconda3` installation folders and run the `.exe` file uninstaller from that location. Uninstallation will complete without prompting for administrative privileges.EXAMPLE: If you installed Miniconda3, the uninstall file will be `Uninstall-Miniconda3.exe`. Users who installed Miniconda2 or Anaconda will find a similar file with the appropriate name.
[](https://www.anaconda.com/docs/reference/troubleshooting#windows-permission-errors-when-installing-from-favorites-folder)Windows permission errors when installing from Favorites folder
***
Cause
The Windows Favorites folder has unusual permissions and may cause permission errors with installers of any software. If you try launching the installer from the Favorites folder, you may see errors such as “Setup was unable to create the directory”, “Access is denied”, or “Error opening file for writing”.
***
Solution
Move the installer to a different folder and run the installer from the new folder.
[](https://www.anaconda.com/docs/reference/troubleshooting#trouble-with-activation-on-powershell-on-windows)Trouble with activation on PowerShell on Windows
***
Cause
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
1. Open a Command Prompt window.
2. Navigate to where you installed conda. The following command shows the default:
```
cd C:\Users\<USERNAME>
```
3. Run the following command:
```
python -m conda init
```
4. Close the Command Prompt window.
If the above method didn’t work, try running:
```
conda update conda
```
[](https://www.anaconda.com/docs/reference/troubleshooting#linking-problems-when-python-extensions-are-compiled-with-gcc)Linking problems when Python extensions are compiled with gcc
***
Cause
When compiling Python extensions with gcc on Windows, linking problems may result.
***
Solution
To resolve these linking problems, use the conda package `libpython`, a mingw import library that Anaconda builds and includes with the Anaconda Distribution.
## [](https://www.anaconda.com/docs/reference/troubleshooting#macos-specific-issues)macOS-specific issues
[](https://www.anaconda.com/docs/reference/troubleshooting#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
***
Cause
When running the `.pkg` installer, you may encounter this error during the “Installation” step:
This error occurs when the installation attempts to write to a directory for which it does not have write permissions.
***
Solution
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.
3. Click **Install on a specific disk…**.
4. Select the appropriate destination drive. Then click **Choose Folder…**.
5. Select 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**.
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`.
## [](https://www.anaconda.com/docs/reference/troubleshooting#linux-specific-issues)Linux-specific issues
[](https://www.anaconda.com/docs/reference/troubleshooting#missing-libgomp-on-power8)Missing libgomp on Power8
***
Cause
If the Python command `import numpy` fails, the system is likely missing the `libgomp` system library. Most Power8 Linux distributions include `libgomp`, but some may not.
***
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
```
[](https://www.anaconda.com/docs/reference/troubleshooting#anaconda-on-power8-reports-%E2%80%9Ccan-not-execute-binary-file%E2%80%9D)Anaconda on Power8 reports “can not execute binary file”
***
Cause
Anaconda on Power8 only supports little endian mode. The little endian Python binary will not execute on a big endian operating system.
***
Solution
Install Anaconda on Power8 on a little endian Linux installation or VM.
[](https://www.anaconda.com/docs/reference/troubleshooting#anaconda-distribution-installation-failed-with-%E2%80%9C%E2%80%98ascii%E2%80%99-codec-can%E2%80%99t-encode-character-%E2%80%98xe4%E2%80%99-in-position-96%E2%80%9D-error)Anaconda Distribution installation failed with “‘ascii’ codec can’t encode character ‘xe4’ in position 96” error
***
Cause
The package `conda-package-streaming` requires certain encoding variables that fresh installations of Linux may not have properly set, causing an ASCII error and a failed installation of Anaconda Distribution.
***
Solution
1. 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"
```
2. If your installer partially ran before failing, your installation directory may not be empty. If so, delete your installation directory.
3. Rerun your installer.
## [](https://www.anaconda.com/docs/reference/troubleshooting#desktop-issues)Desktop issues
[](https://www.anaconda.com/docs/reference/troubleshooting#model-won%E2%80%99t-load-exit-code-3221225781)Model won’t load (exit code 3221225781)
***
Cause
The model you are trying to load requires a C++ runtime environment, but Microsoft does not include one in their operating systems by default.
***
Solution
Install the Latest [Microsoft Visual C++ Redistributable Version](https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170#latest-microsoft-visual-c-redistributable-version).
## [](https://www.anaconda.com/docs/reference/troubleshooting#navigator-issues)Navigator issues
[](https://www.anaconda.com/docs/reference/troubleshooting#custom-navigator-app-isn%E2%80%99t-appearing-on-the-home-page)Custom Navigator app isn’t appearing on the Home page
***
Cause
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.
***
Solution
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.
[](https://www.anaconda.com/docs/reference/troubleshooting#custom-navigator-app-won%E2%80%99t-launch)Custom Navigator app won’t launch
***
Cause
The app can fail to launch due to Navigator configuration issues, even if the application itself is functioning correctly.
***
Solution
1. If the application does not launch after installation, confirm that it works via the command line by running the following command:
```
conda run jupyter lab
```
If you are not using the example feedstock, the command after `run` will be the `entry:` command you have designated.
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.
[](https://www.anaconda.com/docs/reference/troubleshooting#navigator-fails-to-update-to-version-2-6-4)Navigator fails to update to version 2.6.4
***
Cause
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.)
***
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`:
1. Close Navigator, if open.
2. Open Anaconda Prompt (Terminal on macOS/Linux).
3. Run the following command:
```
conda install --name base anaconda-navigator=2.6.4 anaconda-toolbox=4.1.0
```
4. Enter `y` to approve the package changes.
Once your base environment is updated, it is safe to close Anaconda Prompt/Terminal.
5. Reopen Navigator.
Once this dependency conflict is resolved, any future updates to Navigator can be accomplished as usual.
[](https://www.anaconda.com/docs/reference/troubleshooting#navigator-error-on-start-up)Navigator error on start up
***
Cause
This is often the result of a corrupted `.condarc` file.
***
Solution
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. The `.condarc` file is frequently found in:
```
C:\Users\<USERNAME>
```
2. Optional: Save custom configurations. 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.
3. Delete the `.condarc` file.
4. Restart Navigator.
[](https://www.anaconda.com/docs/reference/troubleshooting#issues-launching-or-initializing)Issues launching or initializing
***
Cause
Issues launching or initializing Anaconda Navigator may be caused by permission or licensing problems.
***
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
```
[](https://www.anaconda.com/docs/reference/troubleshooting#permissionerror-on-macos-catalina)PermissionError on macOS Catalina
***
Cause
macOS Catalina users may experience permission errors where the system does not prompt you for permission to folders requiring access.
***
Solution
1. Update Navigator by opening Anaconda Prompt (Terminal on macOS/Linux) and running the following command:
```
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:
```
import os
os.listdir('<DIRECTORY>')
```
[](https://www.anaconda.com/docs/reference/troubleshooting#access-denied-error)Access denied error
***
Cause
A lock file wasn’t removed when it should have been.
***
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
```
[](https://www.anaconda.com/docs/reference/troubleshooting#navigator-buttons-are-missing)Navigator buttons are missing
***
Cause
The disappearance of Navigator buttons may be caused by an out of sync repodata, a corrupt `.condarc` file, or an unknown issue.
***
Solution
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:
```
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.
[](https://www.anaconda.com/docs/reference/troubleshooting#trouble-logging-in-to-package-security-manager-on-prem-in-navigator)Trouble logging in to Package Security Manager (On-prem) in Navigator
***
Cause
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.
***
Solution
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**.
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.
2. Remove the `channel_alias:` entry from the conda configuration file (`.condarc`).
3. Try signing in again.
[](https://www.anaconda.com/docs/reference/troubleshooting#vs-code-is-not-appearing-on-the-navigator-home-tab)VS Code is not appearing on the Navigator Home tab
***
Cause
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):
```
C:\Users\User\AppData\Local\Programs\Microsoft VS Code
```
***
Solution
There are two options for solving this issue:
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/).
On macOS, make sure the VS Code application is moved from your Downloads folder to your Applications folder.
3. Re-open Navigator.
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.
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 Navigator.
[](https://www.anaconda.com/docs/reference/troubleshooting#anaconda-navigator-fails-to-start-and-gives-permission-denied-error)Anaconda Navigator fails to start and gives Permission denied error
***
Cause
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.
***
Solution
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](https://www.anaconda.com/docs/getting-started/anaconda/uninstall) and then [reinstall Anaconda](https://www.anaconda.com/docs/getting-started/anaconda/install/overview) without admin privileges.
Manually change the .continuum folder's user permissions
You will need administrator privileges to do this.
- Windows
- macOS/Linux
1. Search for “powershell”.
2. Right-click the Windows PowerShell app and select **Run as administrator**.
3. Run the following command:
```
icacls C:\Users\<USERNAME>\.continuum /grant:r <USERNAME>:(i,f) /t
```
1. Open your terminal application.
2. Run the following command:
```
sudo chmod 766 /.continuum
```
[](https://www.anaconda.com/docs/reference/troubleshooting#navigator-gives-%E2%80%98email-verification-failed%E2%80%99-error-403)Navigator gives ‘Email verification failed’ error 403
***
Cause
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.
***
Solution
To connect to Anaconda.org again through Navigator, [update your Navigator version](https://www.anaconda.com/docs/tools/anaconda-navigator/update-navigator) or verify your Anaconda.org account.**Verify your anaconda.org account**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.
[](https://www.anaconda.com/docs/reference/troubleshooting#navigator-fails-to-start-due-to-%E2%80%9Ccould-not-load-the-qt-platform-plugin-%E2%80%9Cxcb%E2%80%9D-in--even-though-it-was-found%E2%80%9D-error)Navigator fails to start due to “Could not load the Qt platform plugin “xcb” in "" even though it was found” error
***
Cause
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.”
***
Solution
1. Open a terminal application.
2. Install the missing system libraries and run updates:
```
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.
[](https://www.anaconda.com/docs/reference/troubleshooting#disable-anaconda-com-login-reminder)Disable Anaconda.com login reminder
***
Cause
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.
***
Solution
There are a few ways to disable the Anaconda.com login reminder, depending on your version of Navigator:
- 2\.6.1 and later
- 2\.5.2 to 2.6.0
- 2\.5.0
Work in [offline mode](https://www.anaconda.com/docs/tools/anaconda-navigator/tutorials/offline-mode) or [log in to another repository](https://www.anaconda.com/docs/tools/anaconda-navigator/tutorials/connecting-to-other-repos).
1. [Open the Navigator configuration file](https://www.anaconda.com/docs/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.
```
[internal]
anaconda_toolbox_installed = True
cloud_login_popup_state = 0
```
1. [Open the Navigator configuration file](https://www.anaconda.com/docs/tools/anaconda-navigator/tutorials/editing-config-files).
2. Edit the `welcome_state` to be `0` in the `[internal]` section of the configuration file.
```
[internal]
welcome_state = 0
```
[](https://www.anaconda.com/docs/reference/troubleshooting#update-popup-not-automatically-appearing)Update popup not automatically appearing
***
Cause
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
***
Solution
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, select **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**.
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…**.
defaults is missing from your channels list
This issue specifically impacts users without a subscription to our premium repository.
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.
[](https://www.anaconda.com/docs/reference/troubleshooting#environment-backup-not-working-in-navigator-with-unable-to-create-requested-file-error)Environment backup not working in Navigator with Unable to create requested file error
***
Cause
An update to the environment export option in conda v25.7.0 is incompatible with the existing Navigator implementation for backing up environments.
***
Solution
Upgrade conda to the latest version by running the following command:
```
conda update --name base conda
```
Confirm your installed version of conda by running the following command:
```
conda --version
```
## [](https://www.anaconda.com/docs/reference/troubleshooting#anaconda-org-issues)Anaconda.org issues
[](https://www.anaconda.com/docs/reference/troubleshooting#captcha-not-appearing-when-trying-to-create-an-anaconda-org-account-on-firefox)Captcha not appearing when trying to create an Anaconda.org account on Firefox
***
Cause
The captcha at the bottom of the **Sign In** panel on [Anaconda.org](https://anaconda.org/) sometimes fails to appear on Firefox browsers. The captcha may be blocked by an ad blocker extension, tracking blocker extension, or Firefox’s privacy settings.
***
Solution
1. Refresh your browser and try again. If refreshing multiple times, wait a few seconds between each refresh.
2. Check your extensions. Extensions that block tracking or ads may also block the captcha.
3. Check your browser settings. Privacy settings may block the captcha.
4. Open the [sign in page](https://anaconda.org/) in a [private browsing window](https://www.mozilla.org/en-US/firefox/features/private-browsing/).
[](https://www.anaconda.com/docs/reference/troubleshooting#%E2%80%9Duri-no-longer-exists-and-has-been-permanently-removed%E2%80%9D-410-error-when-attempting-to-upload-notebooks-or-environments-to-anaconda-org)”URI no longer exists and has been permanently removed” 410 error when attempting to upload notebooks or environments to Anaconda.org
***
Cause
The Notebooks and Environments features have been removed from Anaconda.org as part of an initiative to streamline and improve Anaconda.org and enable the site to focus on package hosting and management. Because of this, notebook and environment files can no longer be uploaded to Anaconda.org using the `anaconda upload` command.
***
Solution
Although you can no longer upload notebooks to Anaconda.org, you can share your notebooks with others using [Anaconda Notebooks](https://nb.anaconda.com/) instead. Anaconda Notebooks come with their own preloaded Environments and allow you to create your own custom environments as well. For more information on sharing notebooks with Anaconda Notebooks, see [Sharing notebooks](https://www.anaconda.com/docs/tools/anaconda-notebooks/sharing-notebooks).
[](https://www.anaconda.com/docs/reference/troubleshooting#users-don%E2%80%99t-have-passwords-for-anaconda-client-login-to-anaconda-org)Users don’t have passwords for `anaconda-client` login to Anaconda.org
***
Cause
If you created an account on Anaconda.org and used the Google, Microsoft, or GitHub authorization options to sign up, you do not have a password associated with your account. `anaconda-client` v1.13.1 and older require a username and password to log in to anaconda.org.
***
Solution
To log in to anaconda.org without a password using `anaconda-client`, you must update `anaconda-client` to v1.14.0 or later in your base environment:
1. Open Anaconda Prompt (Terminal in macOS/Linux).
2. Update or install `anaconda-client` by running the following command:
```
conda install --name base "anaconda-client>=1.14.0"
```
3. Log into Anaconda.org:
```
anaconda org login
```
4. A browser window opens to authenticate you to Anaconda.org. Sign in with your account credentials to complete authentication in the browser.
## [](https://www.anaconda.com/docs/reference/troubleshooting#notebooks-issues)Notebooks issues
[](https://www.anaconda.com/docs/reference/troubleshooting#toolbox-environment-card-says-the-environment-is-installed-but-no-environment-in-the-launcher-or-runtime-selector)Toolbox environment card says the environment is installed, but no environment in the Launcher or runtime selector
***
Cause
The environment might not have fully synchronized with the Launcher or runtime selector yet.
***
Solution
First, try refreshing the browser page. If the environment still doesn’t appear after refreshing, check the Environments page in Navigator to see if it’s available. If the environment is still unavailable after waiting two minutes, close all open Jupyter sessions and restart Jupyter from Navigator or the command line.
[](https://www.anaconda.com/docs/reference/troubleshooting#quickstart-environment-installation-errored)Quickstart environment installation errored
***
Cause
Installation errors can occur due to misconfigured channels in your `.condarc` file, organizational policies blocking installation, connectivity issues, or stale Jupyter kernel states.
***
Solution
First, check your `.condarc` file and verify that your channels are set to either `defaults` or `conda-forge`. If your channels are set correctly and you’re still experiencing issues, check with your administrator to see if they have defined any policies that could be blocking installation.If neither of the above resolves the issue, you can try:
- Refreshing the page
- Checking your internet connection
- Shutting down all running Jupyter kernels and restarting your Jupyter instance
[](https://www.anaconda.com/docs/reference/troubleshooting#cli-or-navigator-gives-%E2%80%9Cerror-starting-kernel%E2%80%9D-message)CLI or Navigator gives “error starting kernel” message
***
Cause
Uninstalling a quick start environment using either the CLI or Navigator can result in an `Error starting kernel: [Errno 2] No such file or directory` message, because the Jupyter kernel references aren’t properly removed when the environment is deleted.
***
Solution
To resolve this issue:
1. Open Anaconda Prompt (Terminal in macOS/Linux)
2. Run:
```
jupyter kernelspec list
```
3. Find the name of the quick start environment you deleted.
4. Then run:
```
jupyter kernelspec uninstall <ENV_NAME>
```
[](https://www.anaconda.com/docs/reference/troubleshooting#published-panel-app-is-blank)Published Panel app is blank
***
Cause
The app can appear blank if the notebook cannot be executed sequentially from top to bottom, which can happen when cells have dependencies that aren’t met or are out of order.
***
Solution
If you added content to your app but there’s still nothing showing up, ensure that your notebook can be run from top to bottom. The easiest way to test this is to select **Run** in the top menu, then select *Run All Cells*.
[](https://www.anaconda.com/docs/reference/troubleshooting#all-cpu-seconds-have-been-used-up-in-notebooks)All CPU seconds have been used up in Notebooks
***
Cause
You’ve used up all your available CPU seconds.
***
Solution
CPU seconds are consumed by active runtimes, which can continue to run in the background even after you’ve logged out of Notebooks or switched to a different browser tab.To prevent your CPU seconds from being used while you are not actively using Notebooks, make sure you shut down all runtimes in all open instances of Notebooks before logging off for the day. You can do this from the **Running Terminals and Kernels** tab:
If the problem persists, please raise the issue in the [Anaconda community forums](https://forum.anaconda.com/) or [file a support ticket](https://support.anaconda.com/hc/en-us/requests/new?ticket_form_id=360000993773).You can upgrade your subscription plan to access additional CPU seconds. See our [pricing page](https://www.anaconda.com/pricing) for further details.
[](https://www.anaconda.com/docs/reference/troubleshooting#error-when-importing-packages-in-notebooks)Error when importing packages in Notebooks
***
Cause
The most common cause of errors is a lack of required package(s) installed in your environment. The default environment we provide, based on the Anaconda distribution, contains hundreds of the most common python packages for data science, but it doesn’t include everything. You might need to create a custom environment to install the package you need.
***
Solution
Make sure you have the right runtime selected
The default `anaconda-<YEAR>.<MONTH>-py<PYTHON_VERSION>` runtimes have a broad selection of packages, but you might have created a custom environment for your notebook. Separate environments are represented as “runtimes” in JupyterLab. You can view and switch between available runtimes by clicking the runtime name in the upper-right corner of the content pane.
List the packages available in an environment
If one of your imports is failing, start by verifying that the package is present in the runtime environment. You can view which packages are available in your current environment from the terminal by running `conda list`.To view packages in a specific environment, run `conda list --name <ENV_NAME>`.To see a list of available environments, run `conda info --envs`. An asterisk appears beside your current active environment.
Create a custom runtime
If none of the Anaconda provided environments contain the package(s) you need, create a [custom runtime](https://www.anaconda.com/docs/tools/anaconda-notebooks/notebook-runtimes#creating-custom-runtimes) for your notebook project.
[](https://www.anaconda.com/docs/reference/troubleshooting#%E2%80%9Dmissing-ipykernel-dependency%E2%80%9D-error)”Missing ipykernel dependency” error
***
Cause
A `missing ipykernel dependency` error is caused by an environment dependency list not including the required `ipykernel` package.
***
Solution
To resolve this issue, add the `ipykernel` package to your environment’s dependency list. For example:
```
channels:
- defaults
dependencies:
- python=3.11
- numpy
- pandas
- ipykernel
```
[](https://www.anaconda.com/docs/reference/troubleshooting#custom-runtime-not-appearing-in-launcher-or-assign-a-runtime-modal)Custom runtime not appearing in Launcher or Assign a Runtime modal
***
Cause
The most common reason a runtime or environment is not appearing in the Launcher or Assign a Runtime modal is that it doesn’t contain a .
***
Solution
For more information and instructions on installing a kernel package in your runtime/environment, see [Creating custom runtimes](https://www.anaconda.com/docs/tools/anaconda-notebooks/notebook-runtimes#creating-custom-runtimes).
[](https://www.anaconda.com/docs/reference/troubleshooting#%E2%80%9Dfile-load-error%E2%80%9D-%E2%80%9Cunhandled-error%E2%80%9D-or-%E2%80%9Cunexpected-error%E2%80%9D-message)”File load error,” “unhandled error,” or “unexpected error” message
***
Cause
If you receive a “file load error,” “unhandled error,” or “unexpected error,” like in the following figure, you have most likely exceeded the storage space for your current plan.
***
Solution
Follow the steps in the storage question above to remove items from your Notebooks instance, or upgrade to a higher subscription plan.
[](https://www.anaconda.com/docs/reference/troubleshooting#notebooks-won%E2%80%99t-open-from-anaconda-platform)Notebooks won’t open from Anaconda Platform
***
Cause
Your browser’s pop-up blocker (automatically enabled on Firefox and Safari) can prevent Notebooks from opening.
***
Solution
Disable your pop-up blocker and try opening Notebooks again from Anaconda Platform.
[](https://www.anaconda.com/docs/reference/troubleshooting#notebook-cannot-access-external-sites-after-subscription-upgrade)Notebook cannot access external sites after subscription upgrade
***
Cause
Notebook kernels inherit network permissions when a session is started. Any notebook sessions that were started while your account was using the Free plan are still operating under PythonAnywhere’s [allowlist](https://www.pythonanywhere.com/whitelist/) restrictions.
***
Solution
Stop and restart all Notebook sessions to establish a kernel with unrestricted internet access.
It can take up to an hour for the upgrade to take effect.
## [](https://www.anaconda.com/docs/reference/troubleshooting#ai-navigator-issues)AI Navigator issues
[](https://www.anaconda.com/docs/reference/troubleshooting#model-won%E2%80%99t-load-exit-code-3221225781-2)Model won’t load (exit code 3221225781)
***
Cause
The model you are trying to load requires a C++ runtime environment, but Microsoft does not include one in their operating systems by default.
***
Solution
Install the Latest [Microsoft Visual C++ Redistributable Version](https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170#latest-microsoft-visual-c-redistributable-version).
## [](https://www.anaconda.com/docs/reference/troubleshooting#toolbox-excel-add-in-issues)Toolbox Excel add-in issues
[](https://www.anaconda.com/docs/reference/troubleshooting#error-installing-functions-in-excel)Error installing functions in Excel
***
Cause
This error can occur when Excel loads the Anaconda Toolbox add-in and registers its custom functions. This error happens within Excel and cannot be resolved by the Anaconda Toolbox.
***
Solution
Close and reopen Excel. If the issue persists, uninstall the Anaconda Toolbox add-in, then reinstall. |
| Shard | 158 (laksa) |
| Root Hash | 5660333164590519358 |
| Unparsed URL | com,anaconda!www,/docs/reference/troubleshooting s443 |