Windows 10/11 Miniconda Anaconda
Conda is a cross-platform package and environment management system that plays two roles simultaneously: it installs packages (like pip) and manages isolated Python environments (like venv). More importantly, it is not limited to Python packages — C/C++ libraries, CUDA runtimes, and even R language packages all fall within its scope.
This guide covers installation, configuration, customization, and troubleshooting.
Anaconda vs Miniconda
The official website offers two options: Anaconda and Miniconda. Both includeconda as their core tool; the difference is how much comes pre-bundled.
Anaconda
Full bundle — ships with 300+ pre-installed packages (NumPy, Pandas, Jupyter, Scikit-learn, …), ready to use out of the box.
- Installation size: approximately 4.4 GB
- Includes Anaconda Navigator (GUI management interface)
- Best for: beginners and those who prefer not to worry about package installation
Miniconda
Personally recommended.Minimal installation — only conda + Python + essential dependencies, giving you a clean starting point.
- Installation size: approximately 80 MB
- CLI-only operation
- Best for: experienced developers, CI/CD pipelines, container environments, disk-space-constrained setups, and avoiding Anaconda licensing concerns
| Comparison | Anaconda | Miniconda |
|---|---|---|
| Installation size | ~1.1 GB | ~90 MB |
| Pre-installed packages | 300+ data science packages | conda + Python only |
| GUI management | Anaconda Navigator | None |
| Use case | Quick start, teaching environments | Precise control, production environments |
| Customization flexibility | Lower (many pre-installed packages you may not need) | Maximum (install only what you need) |
Which should I choose?Plenty of disk space and want to get started quickly → Anaconda.Want precise environment control, or need to conserve SSD space → Miniconda.
RecommendedIn practice, most professional developers prefer Miniconda, because of the 300+ packages Anaconda pre-installs, typically only a few dozen are ever used.Installation
- Miniconda
- Anaconda
- CLI (Silent Install)
Download Miniconda
Go to the Miniconda official download page and select the Windows 64-bit Miniconda.exe installer.-
Run the installer
Double-click the downloaded
Miniconda3-latest-Windows-x86_64.exeand click Next. - Accept the license agreement Read and accept the License Agreement.
-
Choose the installation type
- Just Me (recommended): Installs for the current user only; no administrator privileges required.
- All Users: System-wide installation; requires administrator privileges.
-
Choose the installation path
The default path is
C:\Users\<your-username>\miniconda3. To install to a different location (such as the D drive), change the path at this step. See the Installing to the D Drive section below for details. -
Advanced options
The installer will ask about two options:
Option Recommendation Description Create start menu shortcuts Check Creates an Anaconda Prompt shortcut in the Start Menu Add Miniconda3 to my PATH Leave unchecked Not recommended officially: conda’s binary directory contains other package binaries; permanently adding it to PATH can conflict with other software. Use Anaconda Prompt or conda initinsteadRegister Miniconda3 as default Python Situational Check if there is no other Python on the system (checked by default) Clear the package cache upon completion Check Runs conda clean --all --force-pkgs-dirsafter installation to save space - Complete the installation Click Install, wait for the installation to finish, then click Finish.
Post-installation Verification
After installation, open PowerShell or Anaconda Prompt (search from the Start Menu) and run the following verification commands:
If conda is not recognized, see Troubleshooting.
.condarc (conda run configuration) is conda’s configuration file, written in YAML syntax. It controls channels, default paths, behavioral preferences, and all other conda settings. Conda allows multiple .condarc files to coexist at different locations:
| Field | Description |
|---|---|
| user config file | The user-level .condarc, always located at C:\Users\<username>\.condarc. This path is shown even if the file does not yet exist |
| populated config files | .condarc files that actually contain content. When installed on the D drive, this is typically D:\miniconda3\.condarc |
Which .condarc takes effect?Conda reads all
.condarc files it finds simultaneously and merges their settings. If two files have conflicting settings, the user-level file (C:\Users\...) takes priority.It is generally best to maintain only one .condarc to avoid scattered configuration. You can edit the one under the installation directory (D:\miniconda3\.condarc) directly, or use conda config commands (which write to the user-level file by default):Create a test environment
Verify that conda can correctly create an isolated environment and install packages:Custom Configuration
Installing to the D Drive
Why install to the D drive?
Many Windows users have a disk layout like this:| Drive | Purpose | Characteristics |
|---|---|---|
| C drive (SSD) | Operating system + core applications | Smaller capacity (128–512 GB), fast |
| D drive (HDD/SSD) | Data and development tools | Larger capacity (1 TB+) |
- Avoid system instability caused by a full C drive
- Preserve development environments when reinstalling the OS
- Keep environments separate from the system for cleaner maintenance
How to do it
- CLI silent install (recommended)
- GUI install
Use the
/D= parameter to specify the path (you can pre-create a miniconda3 folder on the D drive):- D:\
- miniconda3/ Conda base installation directory
- condabin/
- Scripts/
- conda.exe
- activate.bat
- python.exe
- Lib/
- Library/
- envs/ Default environment storage location
- ml_project/
- python.exe
- Lib/
- web_dev/
- ml_project/
- pkgs/ Package cache
- .condarc
- miniconda3/ Conda base installation directory
Advanced: custom environment and cache paths
If you want to store environments and caches outside the Miniconda3 directory — for example, to share environments across multiple Conda installations or for finer-grained disk management — you can configure this in the.condarc configuration file:
.condarc
.condarc locationThe
.condarc file lives in the user home directory: C:\Users\<your-username>\.condarc. If it does not exist, you can create it manually, or run conda config --set envs_dirs D:\conda_envs to have conda create it automatically.The Channel Mechanism
What is a channel?
A channel is a source repository for conda packages — essentially a remote directory (URL) containing pre-compiled packages. When you runconda install numpy, conda searches channels in priority order and downloads the first matching package version it finds.
Think of it like an app store for your phone:
| Concept | Analogy |
|---|---|
| Channel | App Store (package source) |
| conda install | Downloading an app from the store |
| Channel priority | Which store to search first |
Major channels
| Channel | Maintainer | Highlights | License |
|---|---|---|---|
| defaults | Anaconda, Inc. | Stable, the default channel | May require a paid license for commercial use |
| conda-forge | Community-maintained | Largest package selection, fastest updates | Completely free |
| pytorch | PyTorch team | Official latest PyTorch releases | Free |
| nvidia | NVIDIA | CUDA toolkit, cuDNN | Free |
Configuring channels
.condarc Configuration File
.condarc is conda’s global configuration file, written in YAML syntax. The following is a complete example of commonly used settings:
.condarc
auto_activate_base: falseBy default, opening a new terminal activates the
(base) environment. Setting this to false requires a manual conda activate base to enter it. This prevents accidental pollution of the base environment and is a good practice.Quick Reference
Environment management
Package management
Troubleshooting
Q: conda command not found?
A: If you did not check “Add to PATH” during installation, a regular CMD or PowerShell session will not recognize the conda command.
There are two solutions:
Method 1: Use conda init (recommended)
Run this once from Anaconda Prompt — after that, all PowerShell sessions will recognize conda:
conda init does not work correctly, add conda’s paths to the system PATH manually:
- Type “environment variables” in the Windows search bar and open “Edit the system environment variables”
- Click the “Environment Variables” button
- Find Path under “User variables” or “System variables” and click “Edit”
-
Click “New” and add the following paths in order (adjust to match your actual installation location):
Anaconda usersReplace
Miniconda3withAnaconda3in the paths above. - Click “OK” repeatedly to close all windows
-
Reopen the terminal and run
conda --versionto verify
Q: CommandNotFoundError after activating an environment?
A: This is commonly caused by PowerShell’s execution policy blocking conda’s initialization script. Run:
Q: conda install is extremely slow at dependency resolution (Solving environment)?
A: This is a classic conda pain point. Solutions:
- Use the libmamba solver (built in for conda >= 22.11):
- Set strict channel priority (reduces the search scope):
- Avoid installing packages in the base environment: Keep base clean and create a separate environment for each project.
Q: CondaHTTPError during installation or update?
A: This is usually a network or proxy configuration issue. Set a proxy in .condarc:
.condarc
Q: Can Anaconda and Miniconda be installed at the same time?
A: Technically yes, but it is strongly not recommended. Both share the sameconda core, and having both installed causes PATH and environment variable conflicts. Choose one.