Anaconda 5.3.0 (and older versions) no longer working on Windows 10 #10236
Comments
|
@probit2011 By any chance, do you happen to have |
|
@nehaljwani Sure, here they are: So, I guess that if there was meant to be a PYTHONPATH set, the installer didn't take care of that? |
|
i have the same issue for weeks. i re-installed many times but same result. anaconda is a crap for windows 10 users |
|
Reinstalling can't help issues that originate in conflicts with the state of your system. Unfortunately, some software developers put qt software in very global locations. Because of the way that Windows works, it's pretty easy for the wrong thing to get found. You may also have existing configuration from a prior Python installation. That configuration may be incompatible with Anaconda as it comes by default. We test on clean VMs, and we can't possibly hope to test for every conceivable user configuration. If you help us understand what configuration is breaking your system, we can try to add tests for it. Calling anaconda crap is impolite. Please keep comments here technical, objective, and free of insults. |
|
@msarahan As an additional piece of information, Anaconda 4.4.0 was the very first Python installation on this laptop and worked without any problems for more than a year. That was until I tried to upgrade to 5.3.0. Hope it helps. |
|
That only means 4.4 was compatible with Easter broken DLLs you have in Windows\System32 while our newest software is not. |
|
@mingwandroid What would be your suggested solution? Wait for a new Anaconda release? Remove/modify some files? |
|
Please open a normal cmd.exe prompt (not Anaconda Prompt) and issue:
and also:
.. and paste the results. |
|
Not looking good... |
|
Please repeat the same from the |
|
Looks like Windows 10 is playing hide-and-seek with us... |
|
Oh no, this is all as it should be, but I'm still at a loss! Unfortunately further diagnosis requires using something like procmon to see what is going on at quite a low level. This tool isn't very user-friendly, but if you are willing to perservere with it (use filters to exclude executables other than python.exe) then try to launch |
|
If we want to get to the bottom of it (not just for me, but other users), I guess that's what I'll have to do. I'll download and get familiar with procmon, and will get back to you once I have some results. |
|
It wasn't too hard to use, your instructions were just what I needed (the help menu doesn't even work :) ). I have attached a xlsx file containing the >3000 entries I received after trying to launch anaconda-navigator. There are a fair few 'name not found' entries. |
|
Any chance of exporting as a csv? Preview on mac is having some difficultly with the xlsx for me. |
|
Doesn't look like csv is an acceptable format here, so I'll give .txt instead. |
|
Great, this is really useful for us so we can make our software more robust and isolated. Thank you for taking the time! I see: Can you show the contents of |
|
|
I believe that this is what's causing you these problems and to fix them you could just remove this site-packages folder, but I'd like to figure out what's causing python to look in this folder at all. Can you check for Python related registry keys? Perhaps search regedit for |
|
OK, I just plainly remove the site-packages folder? Couldn't find Python\Python36 in regedit, but found this: |
|
Yes, this a remnant from some old installation of Python I think. What's under InstallPath? |
|
Both of them have a InstallGroup folder with Data = Python 3.6. I removed the folder and was able to launch Anaconda Navigator and Spyder. Thanks for your help @mingwandroid ! |
|
OK I have tracked down exactly why this is happening, the code that determines the python search path is here: Hi @zooba, sorry to trouble you but I'd really appreciate if you could scan this bug report. I think for Anaconda Distro, we would like to have |
Great! And thank you for helping us to identify what's going on here. |
|
If your You're already patching CPython before you build, right? In If you update this to point at your key, then it won't pick up a regular install of Python. |
|
Thanks @zooba,
Yes, we have a few too many patches unfortunately! We could should/change the key here. The issue with using the registry for this for AD is that it doesn't fit in too well with conda's environments (and the python version in any env. including the base one can be changed even between Python 2 and 3). If we were to swap the order things would be better for most of our users, except those who have modules in that directory that they would prefer to be run instead of those from AD. If we change it we would break things for them. Do you think we should strive for isolation here, perhaps adding a custom env var to restore the old ordering (or select from various options around whether to use the registry and the ordering to use when we do use it). |
|
Given that each environment will need to be self-contained, I would argue that we should remove the registry stuff from our search path. Perhaps it's OK for the root env, but we do not want it to apply to any child envs. |
|
Thanks @msarahan, I guess we should have a discussion around this. I'm super keen to get our most painful WIndows problems fixed up. |
|
We definitely don't want the registry added during installation (which is handled by our Python interpreter for the most part), so we need some way to disable it dynamically I think (if we go for keeping it in the root env, I think the installing Python would probably consider itself in the root env?) |
|
Python since 3.5 or 3.6 should be finding |
|
New Python builds have been released. They do not perform the registry lookup. If you need this to happen still, then you can set |
|
@mingwandroid if I also provide you my procomon output, would you be able to help me identify my issue? Following the tips in this thread (admittedly a bit haphazardly) didn't resolve my issue. I am the person referenced above, #11424 |
|
I'm having the same problem as well. I've tried to follow through with this but unable to solve the problem on my own. Is anyone still monitoring this issue? |
I was trying to delete the wrong folder (from the image above). What worked for me is go to this path and delete the site-packages folder. C:\Users\langs\AppData\Roaming\Python\Python37 If you're using File Explorer to locate the site-packages folder, you may need to show hidden folders to find the AppData folder. |
Like many users have reported recently, I have tried to install Anaconda version 5.3.0 on my Windows 10 laptop. Previously, I was using Anaconda version 4.4.0 and it was working OK.
After installation of 5.3.0, all the icons (Anaconda Navigator, Spyder, Jupyter Notebook, Anaconda prompt) appear in the Windows Start menu, but only Anaconda Prompt is accessible. All the others do not execute anything.
I tried: 1- downgrading from Python 3.7 to Python 3.6; 2- uninstalling 5.3.0 and installing 5.2.0; 3- uninstalling 5.2.0 and re-installing my old 4.4.0. Every time, the same result: nothing executes, nothing opens.
I also tried dealing with the error message I obtained by launching anaconda-navigator manually in Anaconda Prompt (see below) by uploading PySide and resolve the Qt bindings problems, as suggested in another post, and nothing works.
Actual Behavior
Anaconda Navigator, Spyder, Jupyter Notebook refuse to execute/open in Windows 10 after installing/re-installing various versions of Anaconda.
Expected Behavior
It should be executing/opening.
Steps to Reproduce
I have described it above.
Anaconda or Miniconda version:
It didn't work for Anaconda 5.3.0, 5.2.0, 4.4.0, all for Windows 64-bit.
Operating System:
Windows 10 Home
conda infoCollected after installing 5.2.0
conda list --show-channel-urlsCollected after installing 5.2.0
anaconda-navigatorCollected after installing 5.2.0
The text was updated successfully, but these errors were encountered: