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

Failed to create Anaconda Menus #2395

Closed
danfp35 opened this Issue Jun 19, 2017 · 7 comments

Comments

Projects
None yet
8 participants
@danfp35

danfp35 commented Jun 19, 2017

Hi,

I've been working with anaconda 4.4.0 (python 2.7) for several months. However, one day my anti-virus (kaspersky) found that something in spyder folder was potentially dangerous and deleted it. After that it didn't work anymore. I tried to uninstall and reinstall. Nevertheless, at the end of the re-installation, appeared two warning issues: First, ''Failed to create Anaconda Menus" and ''Failed to initialize Anaconda Dirctories''. After that, it seems that the installation has ended correctly. But, there are no apps (so I cannot use spyder).

I think the problem comes because Ananconda uninstaller does leave something in my computer which interferes with the new installation, I have tried evertything I've thought, but problem persists.
Any help would be terrific! I'm desperate!

Thanks

2017-06-19 1
2017-06-19

@danfp35 danfp35 changed the title from Anaconda fails to create to Failed to create Anaconda Menus Jun 19, 2017

@y2kbugger

This comment has been minimized.

Show comment
Hide comment
@y2kbugger

y2kbugger Jun 22, 2017

This is a duplicate of #732

y2kbugger commented Jun 22, 2017

This is a duplicate of #732

@TutCanada

This comment has been minimized.

Show comment
Hide comment
@TutCanada

TutCanada Sep 6, 2017

I had this same problem on an initial installation in Windows 10, while installing from the executable Anaconda3-4.4.0-Windows-x86_64.exe. After trying several of the proposed solutions in these pages, the one that worked for me was to do a clean install with the Virus Checker in Windows Defender turned OFF.
I installed for current user only (no administrator priviledges). Before that, I uninstalled (from Control Panel > uninstall > Python 3.6.0 (Anaconda3 4.3.1 64-bit)), then check that my Anaconda3 directory was empty. The installer completed without complaining, and I can start Spyder from the Windows start button.

TutCanada commented Sep 6, 2017

I had this same problem on an initial installation in Windows 10, while installing from the executable Anaconda3-4.4.0-Windows-x86_64.exe. After trying several of the proposed solutions in these pages, the one that worked for me was to do a clean install with the Virus Checker in Windows Defender turned OFF.
I installed for current user only (no administrator priviledges). Before that, I uninstalled (from Control Panel > uninstall > Python 3.6.0 (Anaconda3 4.3.1 64-bit)), then check that my Anaconda3 directory was empty. The installer completed without complaining, and I can start Spyder from the Windows start button.

@AshutoshPhatak

This comment has been minimized.

Show comment
Hide comment
@AshutoshPhatak

AshutoshPhatak Oct 9, 2017

duplicate of #732 but would still answer because a lot many people are still facing the issue. I tried to fix the issue in isolation, wrt the solution provided in this(and other) thread.

  1. Copy the existing contents from PATH variable and keep it blank, Just enter <;> so as to save it.
  2. Retry the installation(latest 5.0.0) and select "All users option"
  3. After successful installation, put in the variables taken out from PATH.[had been using a lot of those for selenium, java etc]

AshutoshPhatak commented Oct 9, 2017

duplicate of #732 but would still answer because a lot many people are still facing the issue. I tried to fix the issue in isolation, wrt the solution provided in this(and other) thread.

  1. Copy the existing contents from PATH variable and keep it blank, Just enter <;> so as to save it.
  2. Retry the installation(latest 5.0.0) and select "All users option"
  3. After successful installation, put in the variables taken out from PATH.[had been using a lot of those for selenium, java etc]
@jhndrx

This comment has been minimized.

Show comment
Hide comment
@jhndrx

jhndrx Oct 17, 2017

Potential Workaround
I encountered this issue on several work computers but not my 2 home computers. I kept getting a popup with a 0xc0000022 error when the installer was running pythonw.exe from the temp folder. It appears this error occurs when files are corrupted or do not have proper permissions. It might explain why some are able to get past the error with admin rights (but not everyone?). Here's a link regarding it. I admit that I didn't thoroughly research this error. Just a precursory look. https://neosmart.net/wiki/0xc0000022/#About_the_82200xc00000228221_error

I noticed that it kept occurring at the same point in the Anaconda install. Line 56741 on the right shows the rest of the highlighted line on the Anaconda install to the left.
pythonw
After it failed, I did not click to continue (since it removes the temp files) and tried running the specified pythonw.exe in the temp folder and it kept giving me the 0xc000022 error. So, I finished out the Anaconda install, ignoring errors and saved a copy of the details as shown in the image. The Anaconda install folder was very bare, only a couple folders and definitely did not have the pythonw.exe file that was trying to be used in lines 56745-56749. So I simply installed python 3.6.3 somewhere not in my Anaconda install folder (just me, not modifying path) and I reran the command on line 56741 using the pythonw.exe included in the separate python install in place of the temporary folder one. Give it a couple of minutes and then run the 3 lines 56745-56748 (Anaconda install location of C:\Anaconda3). and it works fine. Probably best to reboot afterwards but doesn't appear necessary. This included the "add to path" selection from the install.

@msarahan I noticed from #732 that you were looking into this issue. Perhaps this will aide in determining the error. I would definitely look at the code that puts the pythonw.exe in the temporary folder as it might be corrupting it or doing incorrect permissions.

Extra information about previous possible workarounds. I did not have any Java stuff in my environment variables at home or at work. My home computers have less than 1024 characters in the path variable. Work computers have over 1024. I don't know if this affects the install at all but I will mention it for completeness.

Edit: You can uninstall the non-Anaconda python install I mention after finishing since its not necessary and to prevent any possible confusion about which python your using.

jhndrx commented Oct 17, 2017

Potential Workaround
I encountered this issue on several work computers but not my 2 home computers. I kept getting a popup with a 0xc0000022 error when the installer was running pythonw.exe from the temp folder. It appears this error occurs when files are corrupted or do not have proper permissions. It might explain why some are able to get past the error with admin rights (but not everyone?). Here's a link regarding it. I admit that I didn't thoroughly research this error. Just a precursory look. https://neosmart.net/wiki/0xc0000022/#About_the_82200xc00000228221_error

I noticed that it kept occurring at the same point in the Anaconda install. Line 56741 on the right shows the rest of the highlighted line on the Anaconda install to the left.
pythonw
After it failed, I did not click to continue (since it removes the temp files) and tried running the specified pythonw.exe in the temp folder and it kept giving me the 0xc000022 error. So, I finished out the Anaconda install, ignoring errors and saved a copy of the details as shown in the image. The Anaconda install folder was very bare, only a couple folders and definitely did not have the pythonw.exe file that was trying to be used in lines 56745-56749. So I simply installed python 3.6.3 somewhere not in my Anaconda install folder (just me, not modifying path) and I reran the command on line 56741 using the pythonw.exe included in the separate python install in place of the temporary folder one. Give it a couple of minutes and then run the 3 lines 56745-56748 (Anaconda install location of C:\Anaconda3). and it works fine. Probably best to reboot afterwards but doesn't appear necessary. This included the "add to path" selection from the install.

@msarahan I noticed from #732 that you were looking into this issue. Perhaps this will aide in determining the error. I would definitely look at the code that puts the pythonw.exe in the temporary folder as it might be corrupting it or doing incorrect permissions.

Extra information about previous possible workarounds. I did not have any Java stuff in my environment variables at home or at work. My home computers have less than 1024 characters in the path variable. Work computers have over 1024. I don't know if this affects the install at all but I will mention it for completeness.

Edit: You can uninstall the non-Anaconda python install I mention after finishing since its not necessary and to prevent any possible confusion about which python your using.

@danfp35 danfp35 closed this Oct 17, 2017

@Es-Sakhi

This comment has been minimized.

Show comment
Hide comment
@Es-Sakhi

Es-Sakhi Apr 29, 2018

After spending more than 2 days on this finally comes to an end. I considered as the most challenging task in 2018 so far. Here is the remedy: (some of this step my not be necessary, however this is the last process I followed in order to get it to work)

  1. Delete the variables form path all of them (remember to save them somewhere because you well have to put them back.
  2. Download and install Redistributable Package (link below)
    https://www.microsoft.com/en-us/download/confirmation.aspx?id=14632
  3. search your computer for any related previously installed python or anaconda and delete them
  4. reboot you PC
  5. go to https://www.anaconda.com/download/#windows download and install Anaconda.
  6. Put back all the variable were in the path previously
  7. Add the path to the newly installed anaconda
  8. Done

Es-Sakhi commented Apr 29, 2018

After spending more than 2 days on this finally comes to an end. I considered as the most challenging task in 2018 so far. Here is the remedy: (some of this step my not be necessary, however this is the last process I followed in order to get it to work)

  1. Delete the variables form path all of them (remember to save them somewhere because you well have to put them back.
  2. Download and install Redistributable Package (link below)
    https://www.microsoft.com/en-us/download/confirmation.aspx?id=14632
  3. search your computer for any related previously installed python or anaconda and delete them
  4. reboot you PC
  5. go to https://www.anaconda.com/download/#windows download and install Anaconda.
  6. Put back all the variable were in the path previously
  7. Add the path to the newly installed anaconda
  8. Done
@msarahan

This comment has been minimized.

Show comment
Hide comment
@msarahan

msarahan May 8, 2018

Member

@jhndrx thanks for the insight. Do you have any anti-virus running? We've seen that anti-virus can trigger this issue by delaying the files actually being present, which may explain your observations. It seems like we probably need a way to account for that, and build in delays rather than fall over.

@Es-Sakhi @AshutoshPhatak what were your PATH settings before you cleared them? We're having a hard time reproducing this. We've tried with long paths and with quotes in the path, but so far we haven't had any luck getting the problem to reliably show up.

Member

msarahan commented May 8, 2018

@jhndrx thanks for the insight. Do you have any anti-virus running? We've seen that anti-virus can trigger this issue by delaying the files actually being present, which may explain your observations. It seems like we probably need a way to account for that, and build in delays rather than fall over.

@Es-Sakhi @AshutoshPhatak what were your PATH settings before you cleared them? We're having a hard time reproducing this. We've tried with long paths and with quotes in the path, but so far we haven't had any luck getting the problem to reliably show up.

@Sleekery

This comment has been minimized.

Show comment
Hide comment
@Sleekery

Sleekery Jun 21, 2018

I'm getting the same menu error. I've already deleted my paths and tried deleting all folders with anything conda, anaconda, or python related. My only remaining paths are for variables TEMP and TMP.

I'm trying to install Anaconda 5.2.0 on Windows 10. I originally uninstalled Anaconda to reinstall it because I the program suddenly wouldn't work despite not having any updates overnight.

Sleekery commented Jun 21, 2018

I'm getting the same menu error. I've already deleted my paths and tried deleting all folders with anything conda, anaconda, or python related. My only remaining paths are for variables TEMP and TMP.

I'm trying to install Anaconda 5.2.0 on Windows 10. I originally uninstalled Anaconda to reinstall it because I the program suddenly wouldn't work despite not having any updates overnight.

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