If you have a troubleshooting issue that is not listed here, obtain free supportfor Anaconda through theAnaconda mailing list.For Anaconda installation or technical support options, visit oursupport offerings page.
You may also wish to see the Anaconda Navigator Troubleshooting guide.
Cause¶
There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor.
The Anaconda installer files are large (over 300 MB), and some users haveproblems with errors and interrupted downloads when downloading large files.
Solution¶
One option is to download and install the smaller Miniconda (under 60MB) and then use the command
condainstallanaconda
to download and install all the remaining packagesin Anaconda. If the package downloads are interrupted, just runcondainstallanaconda
again. Conda only downloads the packages that werenot finished in any previous attempts.A second option is to download the large Anaconda installer file, and restartit if the download is interrupted or you need to pause it.
Windows
If you use Internet Explorer:
- Click the Settings icon.
- Click “View Downloads” to open the Download Manager.
- Click on the “Resume” button next to the stopped download to restartdownloading. The download resumes at the point where it stopped.
If you use Edge browser:
- In Windows Explorer, open your downloads folder. There will betemporary files there associated with the partial downloads. Delete all ofthe temporary files except for the download you want to resume.
- In Edge, click the file to download it again. Pause the download but do notcancel it.
- In Windows Explorer, open your downloads folder. You will see two files: thepartially downloaded file from earlier, and the paused download you juststarted. Copy the name of the file you just started, delete this file, andrename the other file with the copied name.
- In Edge, resume the download.
If you use Chrome browser:
Download the plugin for Chrome called Chrono Download manager. In your Chromebrowser, go to https://chrome.google.com/webstore/category/extensions, searchon “Chrono Download” and select, “Add to Chrome.”
To resume the download using Chrono Download, from your top browser menu, clickon the Chrome menu button, then click “Downloads.” Select the filename, thenclick “Resume” to restart your download.
macOS and Linux
- In your terminal window, download the file with the command
curl-OFILENAME
.NoteReplace FILENAME with the full path and name of the file, includinghttp://
orhttps://
. - To pause the download, use
CTRL-c
.NoteWhile a download is paused, you can shut down or restart your computer. - When ready to resume your download, use
curl-O-CFILENAME
.Where “-C” is the option for “continue”. You can pause and restart a downloadas many times as you wish.
I get an error message that says “activate.bat is not a recognized file or command”.
Cause¶
Anaconda 5.0.1 sometimes does not install completely on Windows.
Solution¶
Until a new version is released, you can install Miniconda, and then use condato install the rest of the packages in Anaconda with these instructions:
Open the command prompt (Windows key + the R key on your keyboard) which bringsup the Run… dialog box. Enter
cmd.exe
and then press enter)Copy the following text:
Then paste it into the command prompt window.
Note
This installs to a subdirectory in your User directory named
anaconda3
.If you use a different directory, replace anaconda3
with the actual name.After installing on Windows, in the Windows Start menu I cannot see Anacondaprompt, Anaconda Cloud and Navigator shortcuts.
Cause¶
This may be caused by the way Windows updates the Start menu, or by having multiple versions of Python installed, where they 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 yourcomputer or restarting Windows Explorer.
If that doesn’t work, clear
$PYTHONPATH
and re-install Anaconda. Other potential solutions are covered in the “Conflicts with system state” section of this blog post.During installation on a Windows system, a dialog box appears that says “Failed to create Anaconda menus, Abort Retry Ignore” or “Failed to add Anaconda to the system PATH.” There are many possible Windows causes for this.
Solution¶
Try these solutions, in order:
- Do not install on a PATH longer than 1024 characters.
- Turn off anti-virus programs during install, then turn 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.
Solution¶
Anaconda 4.4 added a feature to the Windows installer so that the “verbose” install information is printed out to a special debug stream via the Win32 API function OutputDebugStream. To see these messages, during installation you need to run the Microsoft utility https://technet.microsoft.com/en-us/sysinternals/debugview.aspx. This may provide useful clues for troubleshooting or submitting bug reports.
You may get “conda not found” or “conda is not recognized as an internal or external command” or a similar message, and you cannot execute conda in a terminal window regardless of what path you are on.
Cause¶
Most likely when you were installing Anaconda or Miniconda, you answered “NO” to the question whether or not to prepend the conda prompt to your path.
Solution¶
Uninstall and then reinstall Anaconda or Miniconda, answering “YES” to the question about prepending the conda prompt.
Or, you can manually edit your .bashrc file to prepend the Anaconda or Miniconda install location. Open a text editor and in your home directory, locate the hidden file .bashrc. Add this line to it and save:
Close your terminal window and re-open before running a conda command.
If your Anaconda installation is in a state where normal conda commandsare not functioning, use the following steps to repair Anaconda andpreserve your installed packages and environments.
Step 1¶
Download a new installer, then followthe instructions for your system Windows, macOS, or Linux.
Note
Use the actual path, filename, and directory name for your installation.
Windows¶
Change your original installer’s name so you do not overwrite it:
moveAnacondaAnaconda_old
Run the Anaconda.exe installer as usual and use robocopy to sync thedirectories:
macOS¶
Change your original installer’s name so you do not overwrite it:
mvanacondaanaconda_orig
Install to same directory as your original installer:
Linux¶
Change your original installer’s name so you do not overwrite it:
mvanacondaanaconda_orig
Install to same directory as your original installer:
Step 2¶
Run
condalist
to view the packages from the previous installation.Run
condainfo-e
to list the environments created in the previous installation which are now available in the new installation.Corporate security policies may prevent a new Anaconda installation fromdownloading packages and other functionality that requires connectingto an external server. To make external connections you may need to connect to afirewall/proxy. Additionally, your IT team may need to allow connectionsto https://anaconda.org and https://repo.anaconda.com as these are themain 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 informationshould be made available by your IT team and may contain a username andpassword that is included in the URL. Read more about the.condarc configuration.
Example configuration:
In some situations it may be necessary to export the HTTP_PROXY andHTTPS_PROXY environment variables.
MacOS/Linux
Windows
If these steps have not allowed connections you should speak to your ITteam to verify that security policies are not blocking connections tohttps://anaconda.com and https://repo.continuum.io.
Cause¶
MacOS Catalina changed the default shell from Bash to zsh.
Solution¶
Run
bash-c'condainitzsh'
and then restart your shell to initialize conda for zsh.Cause¶
“InsecurePlatformWarning” appears only when the installed version of Python isolder than version 2.7.9. This message warns only that the validity of the SSLconnection is not being verified. It should not affect your package downloads.
Solution¶
To resolve this on Windows, install the updated package
ndg-httpsclient
:Note
When initially installing this package, you receive the SSL warning again. Once it is installed, the package will prevent the warnings.
Cause¶
The conda shell function is not available, or is not workingproperly. Some causes:
- You have set
conda_auto_activate_base
to false. You need to runcondaactivate[env]
. Env is optional, the default if not provided is base. - You haven’t started a new shell after installing Anaconda/Miniconda (assuming you allow it to modify your startup script)
- You didn’t allow the installer to modify your startup script
- Conda has been corrupted, usually by a change in the Python package (e.g. 3.6->3.7)
Solution¶
Run
/full/path/to/bin/condainit
to modify ~/.bashrc.Either start a new shell or source the modified ~/.bash_profile(Windows/MSYS2, Windows/Cygwin and macOS) or ~/.bashrc (Linux and Windows Subsystem for Linux).Source them via
.~/.bash_profile
.You may prefer that conda not automatically activate your baseenvironment when a new shell is started. This behavior shadowsyour system Python, and some users prefer to have their condaenvironment be inactive until they need it. To achieve this,you can set a .condarc setting:
If you have this set, the conda command will still be availableas a shell function, but your base environment will not beactive when a new shell is started. To activate your baseenvironment, run
condaactivate
.Cause¶
If a user chooses to add Anaconda to the Windows PATH, this can cause programsto use the new Anaconda versions of software such as Python and not theversions that were already in place. In some cases this can causeincompatibility and errors.
Solution¶
We recommend not adding Anaconda to the Windows PATH. Instead, use Anacondasoftware by opening Anaconda Navigator or the Anaconda Prompt from theStart Menu.
If anaconda-client is not installed and you search for a package onanaconda.org using the Anaconda search command:
anacondasearch-tcondapackagename
You will receive the following error message:
Anaconda on Windows contains an anaconda.bat file, which is used for settingenvironment paths and switching environments. If anaconda-client is notinstalled, this batch file is called instead and produces the error.
To resolve the error, install anaconda-client:
condainstallanaconda-client
And then search for a package:
anacondasearch-tcondapackagename
See Dismissing MKL Trialwarnings.
See Resolving MKL shared library permission deniederrors.
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:
Note
For
Miniconda3-latest-MacOSX-x86_64,
substitute the appropriate filename and version for your operating system.Be sure that you install to the same location as your existing install so it overwrites the core conda files and does not install a duplicate in a new folder.
Cause¶
For users who have installed packages that are not compatible with the latest version of the Anaconda metapackage, running
condaupdateanaconda
updates the Anaconda metapackage to the latest compatible version, but this may not be the latest version.Solution¶
Obtain a list of the conflicting packages by running
condaupdateanaconda
or condainstallanaconda=5.2
.Once you know which packages are conflicting, you can update all current packages without upgrading to the latest version of Anaconda, or you can remove the conflicting packages and then upgrade to the latest version of Anaconda.
To update all current packages without upgrading to the latest version of Anaconda:
- Use
condaremoveanaconda
to remove the Anaconda metapackage itself. (This will not remove any of the packages included with Anaconda.) - Use
condaupdate--all
to update all currently installed packages.
To remove the conflicting packages and upgrade to the latest version of Anaconda:
- Remove the conflicting packages by running
condaremovepackage-name
for each one.NoteReplacepackage-name
with the name of the package. - Run
condaupdateanaconda
.
Cause¶
When compiling Python extensions with gcc on Windows, linking problems may result.
Solution¶
To resolve these linking problems, use the mingw import library–the conda package libpython–which Anaconda builds and includes with the Anaconda Distribution.
When trying to update or install packages with conda, you may see an error message such as:
Cause¶
This may be 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 Spyder or IPython.
You can also force the installation of the package:
condainstall-fpackage-name
.Note
Replace
package-name
with the name of the package that you want to install.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:DocumentsandSettingsYour_User_Name
or in C:UsersYour_User_Name
.Note
Replace
Your_User_Name
with your Windows user name as it appears in the DocumentsandSettings
or Users
folder.Solution¶
Manually delete any unneeded settings files.
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.
- On the menu, select Start, then select Reset Spyder Settings and see if the problem remains.
- Close Spyder and relaunch it from the Anaconda Prompt:
- From the Start menu, open the Anaconda Prompt.
- At the Anaconda Prompt, enter
Spyder
. - See if the problem remains.
- Delete the directory
.spyder2
and then repeat the previous steps from Step 1. Depending on your version of Windows,.spyder2
may be inC:DocumentsandSettingsYour_User_Name
or inC:UsersYour_User_Name
.NoteReplaceYour_User_Name
, with your Windows user name as it appears in the Documents and Settings folder.
Cause¶
Some installations of Anaconda on macOS 10.12.2 experienced incorrect file anddirectory permissions, which caused a range of errors with Navigator and otherparts of Anaconda.
Solution¶
We recommend that any users with Anaconda on macOS 10.12.2 follow these steps:
- Uninstall Anaconda. Open the Terminal.app or iTerm2 terminal application andremove your Anaconda directory, which will have a name such as “anaconda2”or “anaconda3”, by entering a command such as this:
rm-rf~/anaconda3
- Use a text editor such as TextEdit to open the file named
.bash_profile
in your home directory. If you see a line that adds Anaconda or Miniconda toyour PATH environment variable, remove this line, and then save and closethe file. For example, if you see a line such asexportPATH='/Users/jsmith/anaconda3/bin:$PATH'
, remove that line. - Update to macOS 10.12.3 or later.
- Reinstall Anaconda.
Cause¶
This version of macOS seems to have a bug affecting some of the ways for a program to open a web page in a browser.
Solution¶
Several possible workarounds have been found for this bug.
You can explicitly set the browser in
~/.jupyter/jupyter_notebook_config.py
with a line such as this:Or you can copy the Jupyter notebook URL from the log messages on the command line and paste it into your browser.
Or you can set the BROWSER environment variable:
exportBROWSER=/Applications/GoogleChrome.app/Contents/MacOS/GoogleChrome
Further information is available at the Jupyter bug tracker, the Python bug tracker, and this blog post.
Cause¶
Anaconda 4.4.0.0 for Power8 did not include libgfortran.
Solution¶
Anaconda 4.4.0.1 and later for Power8 do include libgfortran.
Upgrade to the latest version of Anaconda:
Anaconda 4.4.0.0 users who do not wish to upgrade may instead install libgfortran with this command:
If the Python command “import numpy” fails, the system is likely missing thelibgomp system library.
Cause¶
Most Power8 Linux distributions include libgomp, but some may not.
Solution¶
Check whether the system is missing libgomp with this command:
If libgomp.so.1 is listed in the “not found:” section, it must be installed.
Install libgomp on Ubuntu with this command:
Install libgomp on Red Hat Enterprise Linux (RHEL) or CentOS with this command:
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.
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, System,Apps & features, Python x.x.x (Miniconda3 4.3.xx 64-bit), Uninstall.
Solution¶
Open the Anaconda or Miniconda installation folder and run the
.exe
fileuninstaller from that location. Uninstallation will complete without promptingfor administrative privileges.EXAMPLE: If you installed Miniconda3, the uninstall file will be
Uninstall-Miniconda3.exe
. Users who installed Miniconda2 or Anaconda willfind a similar file with the appropriate name.Cause¶
The Windows Favorites folder has unusual permissions and may cause permissionerrors with installers of any software. If you try launching the installer fromthe Favorites folder you may see errors such as “Setup was unable to create thedirectory”, “Access is denied”, or “Error opening file for writing”.
Solution¶
Move the installer to a different folder and run the installer from the newfolder.
Solution¶
If you run into the following backtrace on Windows:
Open a cmd.exe prompt.
cd
to where you installed conda and run:Close the cmd.exe prompt and the Anaconda Prompt or the AnacondaPowerShell Prompt as usual.
If this doesn’t work, try running:
You may receive an error when trying to installDistribution 2019.07 for Linux on a webfaction server:
Cause¶
This is caused by having TMP as a noexec.
Solution¶
To enable installation, you can temporarilyset TMP to somewhere else from which you can execute software.
For example:
After installing, set the TMP folder back to its initial location.
In CPython < 3.8, using
python3-config
to determine a linking command line tocompile an extension module will cause that extension module to segfault upon import.python3-config
does provide command-line flags but for the different purpose ofembedding a Python interpreter.Cause¶
This is because of the command-line flags returned by
python3-config
. Before Python 3.8,those are needed to embed the core Python interpreter into a different project altogetherand not those that should be used when linking a Python extension module.Python modules should never link to the core Python interpreter library directly,either statically at build time or dynamically at runtime. This is because the Pythonexecutable itself provides all the necessary functions and symbols.
Solution¶
You should only use
python*-config—ldflags
when linking to an interpreter library (either static or shared).Action | Python < 3.8 | Python >= 3.8 |
---|---|---|
Get command line to link to extension module | python-c'importsysconfig;print(sysconfig.get_config_var('LDSHARED'))' | python3-config--ldflags |
Get command line to embed Python interpreter | python3-config--ldflags | python3-config--ldflags--embed |
python3-config
doesn’t include the command/compiler name whereas the sysconfig waydoes. This works provided none of your arguments have spaces:To work with both 32- and 64-bit libraries, we recommend that you havetwo separate installs: Anaconda32 and Anaconda64 or Miniconda32 and Miniconda64.
When working with both versions, add the path to your installer files to the PATH.
Note
Always specify which version you want to work with because mixing 32- and 64-bitpackages can cause problems in your environment.
To get the information about conda including your PATH, run:
condainfo-a
Using
CONDA_FORCE_32BIT
is not recommended because it forces 32-bit packages tobe installed in the environment, but does not force 32-bit libraries to load atruntime.CONDA_FORCE_32BIT
should be used only when running conda-build to build 32-bitpackages on a 64-bit system.