Troubleshooting¶
- Anaconda installer download problems
- Cannot open Anaconda Prompt after installation
- 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
- I’m having trouble with the Anaconda installer on Windows. How can I debug my issue?
- Cannot get conda to run after installing
- Insecure Platform Warning
- Error message: Conda: command not found, on macOS or Linux
- Anaconda interfering with other software on Windows
- MKL Trial warning is displayed even though MKL-linked packages are now free and installed by default
- Error message: Permission denied, when loading MKL shared libraries
- Error message on Miniconda install: Already installed
- Conda update anaconda command does not install the latest version of Anaconda
- Linking problems when Python extensions are compiled with gcc
- Error message: Unable to remove files
- Files left behind after uninstalling Anaconda on Windows
- Spyder errors or failure to launch on Windows
- Problems running Anaconda on macOS 10.12.2
- “execution error: localhost doesn’t understand the “open location” message. (-1708)” when opening a Jupyter notebook on macOS 10.12.5
- Missing libgfortran on Power8
- Missing libgomp on Power8
- Anaconda on Power8 reports “can not execute binary file”
- Uninstaller requests admin privileges on Windows
- Windows permission errors when installing from Favorites folder
If you have a troubleshooting issue that is not listed here, obtain free support for Anaconda through the Anaconda mailing list. For Anaconda installation or technical support options, visit our support offerings page.
Anaconda installer download problems¶
Cause¶
The Anaconda installer files are large (over 300 MB), and some users have problems 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
conda install anaconda
to download and install all the remaining packages
in 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.
A second option is to download the large Anaconda installer file, and restart it 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 restart downloading. The download resumes at the point where it stopped.
If you use Edge browser:
- In Windows Explorer, open your downloads folder. There will be temporary files there associated with the partial downloads. Delete all of the temporary files except for the download you want to resume.
- In Edge, click the file to download it again. Pause the download but do not cancel it.
- In Windows Explorer, open your downloads folder. You will see two files: the partially downloaded file from earlier, and the paused download you just started. Copy the name of the file you just started, delete this file, and rename 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 Chrome browser, go to https://chrome.google.com/webstore/category/extensions, search on “Chrono Download” and select, “Add to Chrome.”
To resume the download using Chrono Download, from your top browser menu, click on the Chrome menu button, then click “Downloads.” Select the filename, then click “Resume” to restart your download.
macOS and Linux
In your terminal window, download the file with the command
curl -O FILENAME
.NOTE: Replace FILENAME with the full path and name of the file, including
http://
orhttps://
.To pause the download, use
CTRL-c
.NOTE: While a download is paused, you can shut down or restart your computer.
When ready to resume your download, use
curl -O -C FILENAME
.Where “-C” is the option for “continue”. You can pause and restart a download as many times as you wish.
Cannot open Anaconda Prompt after installation¶
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 conda to install the rest of the packages in Anaconda with these instructions:
Open the command prompt (Windows key + the R key on your keyboard) which brings
up the Run... dialog box. Enter cmd.exe
and then press enter)
Copy the following text:
cd %UserProfile%
powershell -command "& { (New-Object Net.WebClient).DownloadFile('https://repo.continuum.io/miniconda/Miniconda3-latest-Windows-x86_64.exe', 'mc3.exe') }"
start /wait "" mc3.exe /InstallationType=JustMe /AddToPath=0 /RegisterPython=0 /NoRegistry=0 /S /D=%UserProfile%\anaconda3
%UserProfile%\anaconda3\Scripts\activate.bat
conda install -y anaconda=5.0.1 conda-build _ipyw_jlab_nb_ext_conf
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.
I’m having trouble with the Anaconda installer on Windows. How can I debug my issue?¶
Cause¶
The cause could be any number of issues.
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.
Cannot get conda to run after installing¶
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:
export PATH=/Users/your-username/anaconda3/bin:$PATH
NOTE: Replace “your-username” with your username.
Close your terminal window and re-open before running a conda command.
Insecure Platform Warning¶
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 on Windows, install the updated package ndg-httpsclient
:
conda install ndg-httpsclient
NOTE: When initially installing this package, you receive the SSL warning again. Once it is installed, the package will prevent the warnings.
Error message: Conda: command not found, on macOS or Linux¶
Cause¶
Problems with the PATH environment variable can cause “conda: command not found” errors or a failure to load the correct versions of python or ipython.
Solution¶
- Find the location of your Anaconda binary directory.
- In your home directory, in the
.bashrc
file, add a line to add that location to your PATH. - Close and then re-open your terminal windows.
EXAMPLE: A user with the user name “jsmith” on a Linux machine whose Anaconda
binary directory is ~/anaconda
would add this line to the .bashrc
file:
export PATH="/home/jsmith/anaconda/bin:$PATH"
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 such as Python and not the versions that were already in place. In some cases this can cause incompatibility and errors.
Solution¶
We recommend not adding Anaconda to the Windows PATH. Instead, use Anaconda software by opening Anaconda Navigator or the Anaconda Prompt from the Start Menu.
MKL Trial warning is displayed even though MKL-linked packages are now free and installed by default¶
Error message on Miniconda 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:
bash Miniconda3-latest-MacOSX-x86_64.sh -f
NOTE: For Miniconda3-latest-MacOSX-x86_64,
substitute the appropriate filename and version for your operating system.
NOTE: 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.
Conda update anaconda command does not install the latest version of Anaconda¶
Cause¶
For users who have installed packages that are not compatible with the latest version of the Anaconda metapackage, running conda update anaconda
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 conda update anaconda
or conda install anaconda=5.0
.
NOTE: Replace 5.0
with the latest version number.
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
conda remove anaconda
to remove the Anaconda metapackage itself. (This will not remove any of the packages included with Anaconda.) - Use
conda update --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
conda remove package-name
for each one.NOTE: Replace
package-name
with the name of the package.Run
conda update anaconda
.
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 mingw import library–the conda package libpython–which Anaconda builds and includes with the Anaconda Distribution.
Error message: Unable to remove files¶
When trying to update or install packages with conda, you may see an error message such as:
Error: Unable to remove files for package: <package-name>
Please close all processes running code from conda and try again.
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: conda install -f package-name
.
NOTE: Replace package-name
with the name of the package that you want to install.
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\Your_User_Name
or in C:\Users\Your_User_Name
.
NOTE: Replace Your_User_Name
with your Windows user name 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.
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:\Documents and Settings\Your_User_Name
or inC:\Users\Your_User_Name
.NOTE: Replace
Your_User_Name
, with your Windows user name as it appears in the Documents and Settings folder.
Problems running Anaconda on macOS 10.12.2¶
Cause¶
Some installations of Anaconda on macOS 10.12.2 experienced incorrect file and directory permissions, which caused a range of errors with Navigator and other parts 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 and
remove 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 to your PATH environment variable, remove this line, and then save and close the file. For example, if you see a line such asexport PATH="/Users/jsmith/anaconda3/bin:$PATH"
, remove that line. - Update to macOS 10.12.3 or later.
- Reinstall Anaconda.
“execution error: localhost doesn’t understand the “open location” message. (-1708)” when opening a Jupyter notebook on macOS 10.12.5¶
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:
c.NotebookApp.browser = u'Safari'
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: export BROWSER=/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome
Further information is available at the Jupyter bug tracker, the Python bug tracker, and this blog post.
Missing libgfortran on Power8¶
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:
conda update anaconda
Anaconda 4.4.0.0 users who do not wish to upgrade may instead install libgfortran with this command:
conda install libgfortran
Missing libgomp on Power8¶
If the Python command “import numpy” fails, the system is likely missing the libgomp system library.
Cause¶
Most Power8 Linux distributions include libgomp, but some may not.
Solution¶
Check whether the system is missing libgomp with this command:
conda inspect linkages -n root numpy
If libgomp.so.1 is listed in the “not found:” section, it must be installed.
Install libgomp on Ubuntu with this command:
apt install libgomp1
Install libgomp on Red Hat Enterprise Linux (RHEL) or CentOS with this 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.
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, 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
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.