Miniconda installer doesn't create Anaconda Command Prompt under Windows Start Menu

[bzindovic]

Miniconda installer doesn't create "anaconda.bat" nor "Anaconda Command Prompt" under Windows Start Menu despite the installer text suggesting this.

To reproduce this bug, run the Miniconda installer, untick the "Add Anaconda to my PATH environment variable". After install, neither "anaconda.bat" nor "Anaconda Command Prompt" are available.

[ccordoba12]

Add Anaconda to my PATH environment variable means that you can use the conda commands directly from your command prompt, i.e. that you can run something like

conda install pandas

from any directory, and it'll work without saying that conda is not recognized as a command.

So, that option doesn't mean the installer is going (or not going) to create menu entries in your Start Menu. That's only done by the Anaconda installer, but not by the Miniconda one.

[bzindovic]

Dear Carlos,

Thank you for the info, I'm aware of the meaning of adding it to my PATH variable.

The problem is that the text below the checkbox (seen in the Miniconda installer) indicates that to install packages, one should use "Anaconda Command Prompt". Maybe Miniconda installer is a repacked version of Anaconda installer so the text is the same in both of them. I've attached the screenshot below.

[rsignell-usgs]

Did this get resolved or is it being worked on?

It would indeed be very useful for folks installing miniconda on windows who have not checked the boxes above to get an Anaconda Command Prompt from which they could type "conda list", "activate", etc.

Otherwise, they have to open a regular command prompt, figure out where miniconda got installed, cd to the miniconda\Scripts directory and type "activate".

For folks not used to using the command line on windows, this is challenging. 😢

[ccordoba12]

Hi,

I think Miniconda just comes with the most minimal requirements to get
conda and Python installed in your system. So it's not in our plans to
add support for menu entries and things like that it.

I think Miniconda is mostly used to do testing in Continuous integration
services and by power users who know what they are doing.

Cheers,
Carlos

El 18/11/15 a las 11:06, Rich Signell escribió:

Did this get resolved or is it being worked on? It would indeed be
/very/ useful for folks installing miniconda on windows who have /not/
checked the boxes above to get an Anaconda Command Prompt from which
they could type "conda list", "activate", etc.

Otherwise, they have to open a regular command prompt, figure out
where anaconda got installed, cd to the Scripts directory and type
"activate". For folks not used to using the command line on windows,
this is challenging.

—
Reply to this email directly or view it on GitHub
#352 (comment).

[rsignell-usgs]

Well, the miniconda installer screen shot, shown above, certainly indicates that there will be an Anaconda command prompt. Shouldn't this be super easy?

I don't agree that miniconda is just for power users: we use it for our community to have even first time users create the custom environment they need, without a bunch of packages they don't need.

Some of these folks are in developing countries where the bandwidth is limited, and the difference between 22MB (miniconda) and 400MB (anaconda) is the difference between a 5 minute download or a 2 hour download (which may fail!).

[ocefpaf]

bandwidth is limited

From someone that lives outside the US I can say that miniconda is my main option just for that reason and not because I am a power user. In fact I use it to teach beginners.

The "Anaconda Command Prompt" (AKA path ready python) would be very helpful in that regard.

My work around is to tell student to download console_portable and do that themselves. But that is too much for some audiences.

[ccordoba12]

Hi,

We were not aware of that use case, so it's good to know about it.
Please open an issue for this problem in our issues repository:

 https://github.com/ContinuumIO/anaconda-issues/issues/

so we don't forget to address it in the future.

Cheers,
Carlos

El 18/11/15 a las 11:45, Filipe escribió:

bandwidth is limited

From someone that lives outside the US I can say that miniconda is
my main option just for that reason. Not because I am a power user. In
fact I use it to teach beginner.

The "Anaconda Command Prompt" (AKA path ready python) would be very
helpful.

My work around is to tell student to download console_portable
http://portableapps.com/apps/utilities/console_portable and do that
themselves. But that is too much for some audiences.

—
Reply to this email directly or view it on GitHub
#352 (comment).

[ocefpaf]

Thanks @ccordoba12, but do we need another issue? I guess the title on this one is good enough to describe the problem. If not I can open a new one. (I just want to avoid cluttering the issue tracker.)

[ccordoba12]

Nop, so sorry about that! :-p

I was viewing this in my email client and thought it was reported in the Anaconda mailing list!

---

Pinging @msarahan about this one.

[georgedimitriadis]

Hi guys,

I faced the same problem.

With a bit of digging I found a .bat file that with a bit of modification I managed to make into a Miniconda ready cmd.

Here it is

---

@echo off
for %%i in ("%~dp0..\envs") do (
set ANACONDA_ENVS=%%~fi
)
if not "%1" == "" (
if not exist "%ANACONDA_ENVS%%1\python.exe" (
echo No environment named "%1" exists in %ANACONDA_ENVS%
goto :eof
)
set ANACONDA_ENV_NAME=%1
set ANACONDA="%ANACONDA_ENVS%%1"
title Anaconda (%ANACONDA_ENV_NAME%^)
) else (
set ANACONDA_ENV_NAME=
for %%i in ("%~dp0..") do (
set ANACONDA=%%~fi
)
title Anaconda
)

set %ANACONDA%="D:\Pythons\Miniconda3
set ANACONDA_SCRIPTS=%ANACONDA%\Scripts
set PATH=%ANACONDA%;%ANACONDA_SCRIPTS%;%PATH%
echo Added %ANACONDA% and %ANACONDA_SCRIPTS% to PATH.
if not "%ANACONDA_ENV_NAME%" == "" (
echo Activating environment %ANACONDA_ENV_NAME%...
set PROMPT=[%ANACONDA_ENV_NAME%] $P$G
)
rem vi:set ts=8 sw=4 sts=4 tw=0 expandtab:

cmd

The set %ANACONDA%="D:\Pythons\Miniconda3 is my dir for Miniconda. Use your own.

I hope this works

[msarahan]

Yikes, sorry I dropped the ball on this one.

This is very quick and easy. I believe the menuinst package comes with both Anaconda and Miniconda. There is another package, console_shortcut, that I think is what you want.

You can conda install this into any environment. You should get a shortcut into a prompt with that environment already activated. The shortcut name should have your environment name in it.

Please ping me if there are any issues. If availability of this package resolves this issue, please close this issue. If we need to include it in the miniconda installers as well by default, then let us know.

@rsignell-usgs we have also worked on your issue of the root env falling off of PATH for purposes of keeping activate.bat available. Please update conda and conda-env, and let us know how things work for you.

[rsignell-usgs]

I just downloaded 64 bit 2.7 miniconda for windows and installed without checking the boxes:

I did not get the Anaconda 64 prompt that is promised by the text on the installer screen above.

The only way I could think of to get miniconda going was to open a regular windows command prompt, navigate to the ..\Miniconda\Scripts directory, and run activate.

I then created a new conda environment (named "sscsw"), activated that environment, and ran:

conda install console_shortcut

as you suggested.

Indeed, I then see some Anaconda shortcuts in the start menu:

But when I select Launcher, I get:

And if I select Anaconda Prompt (sscsw), the environment it activated, but typing deactivate leaves me with no python environment instead of the base miniconda environment:

Luckily, typing launcher from the anaconda prompt after activating the (sscsw) environment does work.

But I'm reporting these other issues as users will likely get very confused (as I was).

`

[msarahan]

This is by design, I think. There is no activation "stack." Deactivation
takes you to your base environment variables, which for you should be no
python. It does, however, keep the scripts folder around, so you can
activate other envs.

If you want to get back to root environment, try:

activate

Or

activate root

The latter may not currently work right now, but should be fixed soon (PR
submitted)

On Tue, Jan 5, 2016, 11:19 Rich Signell notifications@github.com wrote:

I just downloaded 64 bit 2.7 miniconda for windows and installed without
checking the boxes:
[image: 2016-01-05_12-06-33]
https://cloud.githubusercontent.com/assets/1872600/12121764/11281fd0-b3a5-11e5-9e09-e24c681d4adf.png

I did not get the promised Anaconda 64 prompt.

I had to open a regular windows command prompt, navigate to the
..\Miniconda\Scripts directory, and run activate to get anaconda python.

I then created a new environment, activated that environment, and ran:

conda install console_shortcut

Indeed, I then see the shortcuts in the start menu:
[image: 2016-01-05_12-14-35]
https://cloud.githubusercontent.com/assets/1872600/12121914/053b197e-b3a6-11e5-965e-a7569e927131.png

But when I select Launcher, I get:
[image: 2016-01-05_11-55-10]
https://cloud.githubusercontent.com/assets/1872600/12121935/21020f14-b3a6-11e5-9683-8de3d299a828.png

If I select Anaconda Prompt (sscsw), the environment it activated, but
typing deactivate leaves me with no python environment instead of the
base miniconda environment:
[image: 2016-01-05_11-55-39]
https://cloud.githubusercontent.com/assets/1872600/12121996/7efb634a-b3a6-11e5-95b5-ef3875006a16.png

`

—
Reply to this email directly or view it on GitHub
#352 (comment)
.

[pbreach]

This would also be very useful for me in that I need to use multiple different python versions as well as 32bit and 64bit on Windows. Miniconda is a nice solution for this, but it would be nice to have an Anaconda Command Prompy to more easily install packages.

[alichaudry]

I agree. Is this issue under active development? I'm surprised Anaconda Command Prompt wasn't bundled in the Miniconda2/3 installer. It's a useful tool to have, and even here in the US, I don't want to have to download and install the whole Anaconda package when I use my own set of library/packages.

[jonathanlyonmoore]

I found on reddit how to use Python 2 and 3 on the same machine.

https://www.reddit.com/r/learnpython/comments/3l5pc9/using_python_3_and_python_2_on_the_same_machine/

Hope this helps,

[xtiansimon]

I've used the method suggested by cowboy Rsignell: "open a regular command prompt, figure out where miniconda got installed, cd to the miniconda\Scripts directory and type "activate".

After installing Miniconda 32-bit to use a package that didn't play with my 64-bit machine, I then had two installs of Miniconda. The command line is fine for me, but deploying Python CLI scripts at work this doesn't fly with my coworkers.

Here's a nice work-around
I added the shortcut, cmd /c start "" "C:\path\to\Miniconda3\Scripts\activate", with the name "Anaconda Prompt (32)". ('corse, you need to replace path\to with your actual path, and don't forget the empty quotes "" gotcha). And finally, this icon has the right-click contextual Pin to Start option. Now Cortana can find both 64 and 32 bit consoles.

[PunnyBoi]

Thank you @xtiansimon.

Also, if anybody else doesn't like the 'cmd without title' (congratulations you are as paranoid as me), then put the title that you want to appear on the cmd between the blank quotes that @xtiansimon mentioned. So, the complete path becomes cmd /c start "Title" "C:\path\to\Miniconda3\Scripts\activate".

[vpmapelli]

Found this issue when trying to install Miniconda 4.7.10 on Windows. My system is listed as 64-bit Operating system, x64-base processor, and that is why I tried 64-bit exe installer. However, it seems to me that there are a lot of missing files on Miniconda3 installed folder (as seen on attached image, Miniconda3/Scripts does not even exist, for example).

I also tried 32 bit exe installer and Anaconda prompt was automatically set up, and everything went fine. I may be missing something (not an expert), but I thought it could help someone reporting this.

[vhcandido]

@vpmapelli I'm also having the exact same issue. Tried installing miniconda3 x64 on different machines (both W10) without success, but installing the 32 bits version works fine.

[jayagami]

well, same problems,

I have solved it

I miniconda first, then installed anaconda, no prompt or navigator, in a word, can not create start menu.

1. uninstalled anaconda, reboot
2. deleted conda config file, then remove prefetch, you find it all anaconda file with everything.
3. reinstall miniconda, prompt appeared again

My guess, you should delete the config file while reinstalling conda

[laurafroelich]

I ran into the same issues. I tried both the 32- and 64-bit installer, with multiple uninstalls and reboots without any luck.

Finally, I thought to try to run the 64-bit installer with Admin privileges. I now have the Anaconda Prompt available in the start menu, and all the expected folders in C:\ProgramData\Miniconda3, including Scripts which was missing in all my previous installation attempts.

[CameronBodine]

I also had this issue after trying to reinstall miniconda after having both Anaconda and Miniconda previously installed. I noticed that my start menu had an Anaconda3 (64-bit) folder in the start menu with broken links. I went to C:\ProgramData\Microsoft\Windows\Start Menu\Programs, located the Anaconda3 folder, deleted it, then retried the install. Anaconda Prompt and Anaconda Powershell Prompt were both available in the start menu in a newly created Miniconda3 (64-bit) folder.

[pmunin]

Default "recommended" scenario of installing miniconda is still failing after 8 years since the bug was reported

[ParitoshSingh07]

Just got bit by this. Why is the installer lying to us? I'd prefer to have anaconda prompt installed with miniconda, but if not, at the very least that prompt message needs to change.

[ddileonardo]

@msarahan @ccordoba12

This is clearly still a problem. The miniconda install should not be misleading like this. People clearly still want Anaconda Prompt with miniconda.

The following answer seems to partially solve the issue (by installed the shortcut, but not fixing the misleading message), but could be better highlighted in the long chain of answers. @ParitoshSingh07 @pmunin

And it would be better still to just have the Anaconda Prompt install with miniconda. It is extremely useful, especially for beginners who can't or don't want to install the full Anaconda. Or even for users who become experienced and want to ditch the full Anaconda, but still routinely use the Anaconda Prompt to manage environments.

---

Yikes, sorry I dropped the ball on this one.

This is very quick and easy. I believe the menuinst package comes with both Anaconda and Miniconda. There is another package, console_shortcut, that I think is what you want.

You can conda install this into any environment. You should get a shortcut into a prompt with that environment already activated. The shortcut name should have your environment name in it.

Please ping me if there are any issues. If availability of this package resolves this issue, please close this issue. If we need to include it in the miniconda installers as well by default, then let us know.

[ddileonardo]

update: I was talking to a co-worker this morning who recently installed miniconda and it seems like Anaconda prompt DOES install with miniconda, but I don't know what settings he used at install. I suspect they were the default settings.

[SBS-BRhoades]

After encountering this issue on windows 10 with miniconda version 23.10.0, I uninstalled and reinstalled, but ensured that the shortcut creation checkbox was enabled this time through. I now have shortcuts for both the cmd and ps prompts.

[Be-Ko]

i just now had the same issue. first installation, where anaconda prompt was missing, i ticked the box to clear up the package cache.
i uninstalled and reinstalled with just the standard settings ticked and it worked.