Anaconda installer fails with OPENSSL_Uplink(00007FF89B2B9C88,08): no OPENSSL_Applink
#13408
Comments
8 tasks
|
@zhangzih4n can you tell me which installer you used exactly? This looks like Miniconda 24.5.0, but could you tell me if this was a specific python version? What's your Windows version and do you have any other python installations on your machine? |
Miniconda 24.5.0 (Python 3.12.4, x86_64)
Windows 11 x64, and the official Python 3.12.4 is installed When I tried 24.4.0, it installed successfully |
|
Thanks for trying 24.4.0, too! I am unable to reproduce your problem, even with the official python installed, so I'll spitball a little here. Could you try the Miniconda python 3.11 installer? https://repo.anaconda.com/miniconda/Miniconda3-py311_24.5.0-0-Windows-x86_64.exe Based on your install location, it looks like you installed Miniconda for all users? Did you do the same with the official Python installation? Do you happen to have any other OpenSSL installations on your PC? |
Same error:
Yes
Yes
No |
|
Thanks! I have a suspicion that it might be related to an update to our bootstrapper that somehow interferes with/is interfered by the existing python installation. Could you try the following:
I have seen another report that suggest that removing python gets the installer to work. An alternative is to just install Miniconda 24.4.0 and run |
Still got errors: PowerShell 7.4.4
PS D:\Downloads> .\conda-standalone-24.5.0-Windows-x86_64.exe create -p .\tmp conda
OPENSSL_Uplink(00007FFB01AE2FE8,08): no OPENSSL_Applink
PS D:\Downloads> |
2 tasks
|
Thank you! This looks like a problem with the To get this to work for you, you have two options:
If you want to help us debug this, I'd be curious if you see any references to Python or OpenSSL in your environment variables here: Get-ChildItem env: | fl |
Only in |
|
For what it's worth, I've been troubleshooting this error on my machine as well. I was using the standalone miniconda installer as well as one downloaded by the oobabooga scripts. I had various versions of official Python installed 3.11.2, 2.7.14, and some other versions that I forgot to document before I removed. Some were installed for all users, and others were just current user. Even after uninstalling them all,, cleaning up my environment variables and rebooting, I was still getting the error. I did find that if I run my command prompt as a different user, it works fine, so it appears to be something related to my Windows user profile. |
|
@guitarpicker Could you compare the environment variables of both user accounts to see if there is a difference (see the command above)? There must be something in the environment variables that is causing problems. |
|
OK, I did you one better. I copied the environment from working to mine, changing the usernames where appropriate. I don't have the final results, but there are two things to note. When I simply ran SET commands to pump the good user's environment variables in, it still didn't work, however, when I deleted all the existing variables in my CMD session and then imported the good ones, it did work, so one of the extra variables was causing conflict. I kept deleting the preexisting ones until it worked, and it appears to be my SSLKEYLOGFILE variable. SSLKEYLOGFILE=c:\users\me\SSLKeys\sslkeylog.log The file it points to is a forgotten 500 MB debugging file. This is a troubleshooting variable used to assist with decrypting SSL for programs like WireShark. I tried pointing it to a brand new file and also encountered the error, so it would appear that the existence of this variable is enough to break the installer. If you do test, I would setting the environment variable, logging out, logging in, running Chrome, visiting some SSL site (this should populate the file), and then launching the installer. |
|
Beautiful, that's what I was trying to get at in the end. I can reproduce this now! I can see that environment variable in OP's output. That at least gives me something to investigate now - thank you so much! |
3 tasks
|
To keep this thread up-to-date: the problem lies with |
Open
8 tasks
|
The new Miniconda is released, which should have that bug fixed. For those who encounter this error while still waiting for Anaconda Distribution, the workaround is to unset the Command line optionThis is the least intrusive way to do it.
Graphical installer
|
|
Thank you for the instructions! But I never have set SSLKEYLOGFILE variable in my pc, so there isn't in enviomental variables. |
|
That's strange. Can you open PowerShell and show me the output of the following command (make sure to anonymize your user name and any other secret/private output): Get-ChildItem env: | fl |
|
Name : ALLUSERSPROFILE Name : APPDATA Name : CommonProgramFiles Name : CommonProgramFiles(x86) Name : CommonProgramW6432 Name : COMPUTERNAME Name : ComSpec Name : DriverData Name : HOMEDRIVE Name : HOMEPATH Name : IGCCSVC_DB Name : JAVA_HOME Name : LOCALAPPDATA Name : LOGONSERVER Name : MAVEN_HOME Name : NUMBER_OF_PROCESSORS Name : OneDrive Name : OS Name : Path Name : PATHEXT Name : PROCESSOR_ARCHITECTURE Name : PROCESSOR_IDENTIFIER Name : PROCESSOR_LEVEL Name : PROCESSOR_REVISION Name : ProgramData Name : ProgramFiles Name : ProgramFiles(x86) Name : ProgramW6432 Name : PSModulePath Name : PUBLIC Name : SESSIONNAME Name : SystemDrive Name : SystemRoot Name : TEMP Name : TMP Name : USERDOMAIN Name : USERDOMAIN_ROAMINGPROFILE Name : USERNAME Name : USERPROFILE Name : windir Name : WSLENV Name : WT_PROFILE_ID Name : WT_SESSION Name : ZES_ENABLE_SYSMAN |
|
hey, i fixed the problem! I changed the tmp env variable and then try again the installation. I dont know if thats helpful for understanding the cause |
That's really odd. I wouldn't recommend changing that variable though, at least not permanently. What did you change it to? |
I have the same problem too.I try to update my Anaconda3 from 2024.02-1 to 2024.06-1 with official python 3.12.5 already in my laptop. After I uninstall 2024.02-1, I noticed that there was some errors when installing 2024.06-1. I retried for multiple times but it didn't solved. The code after "OPENSSL_Uplink" is different from issue title. (error details are at the end, inside Now it works!The details are the same until this line Thanks for your solutions! I can import my env now
Second installationFirst installationFirst installation |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I had the same problem. I only had Windows Defender on my computer, and it was turned off.
It doesn't seem to be an issue with the antivirus software.
Originally posted by @zhangzih4n in #13386 (comment)
The text was updated successfully, but these errors were encountered: