Ordinal 535 could not be located #224
Comments
Am I having the similar problem? Googling it revealed that this file is a part of Microsoft Visual C++ 2015, but downloading and installing both x64 and x86 versions did not help. |
I'm not sure what the issue is here. Both api-ms-win-core-localization-l1-2-0.dll and ssleay32.dll are distributed with the release binary. Which version(s) are you having issues with? |
I am only able to run Version 1.3.11.1 |
The latest, 1.3.15. |
Can you try installing this and see if it fixes this issue? https://aka.ms/vs/15/release/VC_redist.x86.exe |
I've done that and i still get the same error. via installing https://aka.ms/vs/15/release/VC_redist.x86.exe. |
I tired as well with a reboot after I installed it. So did you intentionally disable updating cdda with the older versions? |
Same with me. I also tried installing an x64 version of Visual C++ 2017. |
I get the message variant with "The ordinal 354 could not be located in the dynamic link library ssleay32.dll", but that's no wonder since that dll doesn't actually exist in system32. What should I do? I run Windows 10 Pro 64-bit. |
It seems like there might be multiple version of those libraries and some of them might be older causing this problem. This is what I could find out by doing a quick google search. There might be a way to fix this by modifying the way the binary is bundled. I'll see what I can do. |
Can you test this new bundle? https://www.dropbox.com/s/8e7cl0d8j9rmt5u/test-launcher.zip?dl=1 |
Thanks. Tried, but getting the same error. |
This is likely to need some more investigation maybe with some virtual machines so I can reproduce the issue on my side. |
Let me know if I can help with anything.
…On Mon, 22 Oct 2018 at 19:22, Rémy Roy ***@***.***> wrote:
This is likely to need some more investigation maybe with some virtual
machines so I can reproduce the issue on my side.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#224 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AF7mrzlinfOCdYFUhuDVeQRU0tssiXqWks5ungzPgaJpZM4XvqQJ>
.
--
*"Isn't it pretty to think so?" **― Ernest Hemingway*
|
I tried the test launcher as well just in case. |
I tried a few things i'm not sure which one worked but i think it was deleting the LIBEAY32.dll dll inside the win 32 folder (Win 7 64bit) that acutally worked in the end for me but i also downloaded https://slproweb.com/products/Win32OpenSSL.html before (I installed both 32bit/64bit) I was just trying everything under the sun to get it to work it struck me as something was wrong with my end rather than the launcher since it was only a handful of people who had this problem But yeah, i'm able to run 1.3.15 now perfectly fine |
Tried installing win32openSSL. Same error. What else did you do @zakhad? |
I think i installed Visual C++ 2017.as well, both 32 and 64bit, as well as the 2015 variants, pretty much tried everyone to see if it'd help, but i'm fairly certain it wasn't them, it was quite literally the last thing i did was delete that LIBEAY32 file i,e to see if i got a corrupted file and reinstall the previously mentioned in here things. I did notice that there is a similar issue with another program and some found a workaround/hack but I've no idea if'it'd work. |
Still getting the error too, but it says ordinal 354 instead or something. |
Still having this issue in the latest update with ordinal 354 |
Just ran into the same issue but with ordinal 353, and thought I could provide some insight on it with how I fixed it. I did some digging and found I had a copy of the openssl libraries from 2003 installed in C:\Windows\System (not System32). I replaced those with modern versions and the launcher worked. Given how... dodgy fiddling with system directories is, I didn't test if it would work if I deleted them, but I bet that has something to do with the intermittency of this issue. |
@Saint-of-Grey I was suspecting something similar. Thanks for the information. |
May I ask how you replaced it with a modern version? Where did you get it from? Tried to look in C\Windows\System but it's empty, too. EDIT: Did a search in my C: Drive for LIBEAY32. It's everywhere. What the hell? Which one do I delete so I can finally stop getting this stupid "Ordinal could not be located" error? Getting a new OpenSSL from https://slproweb.com/products/Win32OpenSSL.html didn't work, either. |
I recall reading somewhere you want the libraries from 1.0.2, not 1.1.0. But honestly, I have no idea which libraries it's trying to use on your setup, maybe the ones in SysWOW64? Those look like they're a decade old. |
@Saint-of-Grey Thank you! Installing 1.0.2 libraries and replacing the ones that exist in SysWOW64 worked. |
All right, so I'm back and the problem is still with me. The latest release of the launcher just won't start, because 'api-ms-win-core-localization-l1-2-0.dll is missing from your computer'. Then the brightest idea to actually check the system folders came to my mind and, as expected, there was no such file as api-ms-win-core-localization-l1-2-0.dll in neither system32 nor syswow64. I really do not want to download this file alone from some shady sites. If this file is included into the Visual C++ package, it should get installed from the package, right? Okay, so here is this file where it is present. Should I just copy one of the versions into the system folders? Seems obvious for me that those guys have been installed by other apps. The VC2015/2017 packages fail to install it. |
Returns the error "The ordinal 535 could not be located in the dynamic link library C:\Windows\system32\ssleay32.dll." upon launch of current version of launcher, then crashes upon pressing OK.
Version 1.3.11.1 is the last version I can run without this error. Am running Windows 8.1 and have reinstalled Microsoft Visual C++ 2015 in an attempt to trouble shoot.
The text was updated successfully, but these errors were encountered: