New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

installation failure #1528

Closed
VeronicaBehrens opened this Issue Mar 17, 2017 · 9 comments

Comments

Projects
None yet
7 participants
@VeronicaBehrens

VeronicaBehrens commented Mar 17, 2017

Near the end of Anaconda 4.3.1 Python 2 Navigator installation on Windows (64 bit), get the error "Failed to create Anaconda menus." After "ignoring" get another error: "Failed to initialize Anaconda directories." And after ignoring that error: "Failed to add Anaconda to the system PATH." Note: I uninstalled a previous version of Anaconda about a year ago.

@goanpeca

This comment has been minimized.

Show comment
Hide comment
@goanpeca
Member

goanpeca commented Mar 17, 2017

@VeronicaBehrens

This comment has been minimized.

Show comment
Hide comment
@VeronicaBehrens

VeronicaBehrens Mar 22, 2017

@ilanschnell @goanpeca I get the same error messages when I try to install Anaconda 4.3.1 Python 3 Navigator on Windows (64 bit). Any ideas how to fix this?

VeronicaBehrens commented Mar 22, 2017

@ilanschnell @goanpeca I get the same error messages when I try to install Anaconda 4.3.1 Python 3 Navigator on Windows (64 bit). Any ideas how to fix this?

@ilanschnell

This comment has been minimized.

Show comment
Hide comment
@ilanschnell

ilanschnell Mar 22, 2017

Contributor

Which version of Windows are you using? CC @msarahan

Contributor

ilanschnell commented Mar 22, 2017

Which version of Windows are you using? CC @msarahan

@VeronicaBehrens

This comment has been minimized.

Show comment
Hide comment
@VeronicaBehrens

VeronicaBehrens commented Mar 22, 2017

Windows 10

@cecbur

This comment has been minimized.

Show comment
Hide comment
@cecbur

cecbur Mar 26, 2017

Me too. Same version.

cecbur commented Mar 26, 2017

Me too. Same version.

@shelbymustang

This comment has been minimized.

Show comment
Hide comment
@shelbymustang

shelbymustang Apr 14, 2017

Still happening. Had a similar issue with machine names that have a space in them for Vagrant. Could this be similar? Is there a manual way to fix (adding PATH or other ENV variables?) Its obviously at the end of the process and all files are in place successfully.

shelbymustang commented Apr 14, 2017

Still happening. Had a similar issue with machine names that have a space in them for Vagrant. Could this be similar? Is there a manual way to fix (adding PATH or other ENV variables?) Its obviously at the end of the process and all files are in place successfully.

@shelbymustang

This comment has been minimized.

Show comment
Hide comment
@shelbymustang

shelbymustang Apr 15, 2017

Updating my comment above. As mentioned above I had a similar issue with Vagrant. This time I went ahead and modified the user name on the Windows account to not have a space (or special character like Main-Computer) Seems to have solved this problem for me.

shelbymustang commented Apr 15, 2017

Updating my comment above. As mentioned above I had a similar issue with Vagrant. This time I went ahead and modified the user name on the Windows account to not have a space (or special character like Main-Computer) Seems to have solved this problem for me.

@y2kbugger

This comment has been minimized.

Show comment
Hide comment
@y2kbugger

y2kbugger Jun 22, 2017

See #732, #1775

Look like this is still a problem in 4.4.0 according to:
#2352

y2kbugger commented Jun 22, 2017

See #732, #1775

Look like this is still a problem in 4.4.0 according to:
#2352

@goanpeca

This comment has been minimized.

Show comment
Hide comment
@goanpeca

goanpeca Jul 12, 2017

Member

Tracking on #2352

Member

goanpeca commented Jul 12, 2017

Tracking on #2352

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment