Eagle 9.1.x won't start on Windows 10

thomas_modliba
Contributor

Eagle 9.1.x won't start on Windows 10

thomas_modliba
Contributor
Contributor

I got a new notebook and tried to install Eagle, first 9.1.0, then 9.1.3.

On first start I need to enter account data and last verify with SMS code.

Then window disappears and nothing happens.

When I try to start Eagle, sometimes there's the splash-screen, but no program window opens. I can see in task manager that eagle .exe quits after some seconds.

Already deleted c:\Users\USER\AppData\Roaming\Eagle\subscription.v1 - start over wiith verification and same issue

So I am not able to use the program. Any ideas to fix it?

Reply
Accepted solutions (1)
43,157 Views
92 Replies
Replies (92)

Anonymous
Not applicable
I have found it again at that link. and I can use my eagle 9.6.2 again... thanks...
0 Likes

Anonymous
Not applicable

Need not to worry bro, I am just telling what to do now:-

1. Goto yo your eagle folder where program is installed (mostly in c drive) and look there for the file "libeay32.dll" in eagle installed directory.

2. If found goto the below link   https://indy.fulgan.com/SSL/Archive/Experimental/       

And select the version as per your requirement and download it and after unzipping the file, place it in the same directory of eagle after deleting the " libeay32.dll" file.

3. Now boom,  restart the program and do what you want.

Anonymous
Not applicable

How do I figure out which openssl file to download

 

0 Likes

camillo.swiss
Community Visitor
Community Visitor
Thank you so much
0 Likes

Anonymous
Not applicable

How do you install 9.0.1? I cant seem to find it on the Autodesk page....

 

PLEASE HELP!!

0 Likes

jorge_garcia
Autodesk
Autodesk

Hi @Anonymous ,

You can find it here http://eagle.autodesk.com/eagle/software-versions

 

Let me know if there's anything else I can do for you.

 

Best Regards,



Jorge Garcia
​Product Support Specialist for Fusion 360 and EAGLE

Kudos are much appreciated if the information I have shared is helpful to you and/or others.

Did this resolve your issue? Please accept it "As a Solution" so others may benefit from it.
0 Likes

Anonymous
Not applicable
Thanks so much! I did try it out, but it would not open. Like, at all.
would you be able to help me out with that?
0 Likes

Anonymous
Not applicable

thankss this helps faster and quicker!!!

0 Likes

Anonymous
Not applicable

Please, see MESSAGE 62 from sanjeev.kDZFVD

It worked for my case...

You can try to find file 

openssl-1.0.2p-x64_86-win64.zip

at https://indy.fulgan.com/SSL/Archive/

Good luck...

 

0 Likes

Anonymous
Not applicable

I had the same issue after installing Eagle version 9.6.2. I replaced the file "libeay32.dll" in the installed directory with the one from the zipped file "openssl-1.0.2u-x64_86-win64.zip" from the link: https://indy.fulgan.com/SSL/.
It ran successfully afterwards.

0 Likes

Anonymous
Not applicable

Ok

0 Likes

jemiaha
Participant
Participant

This thread goes back to 2018.  The issue has persisted for 15+ releases. In this and multiple other threads, @jorge.garcia has pointed users to a third party tool from Shining Light Productions to swap in a DLL to resolve the issue. Another popular solution is to use a DLL from https://www.dll-files.com. Another is from  https://indy.fulgan.com. Why does a tool that costs $495/year require hacking DLL files to work? Where is the explanation of why Eagle doesn't work as installed after so many versions with this issue?  I apologize for the rant but honestly when will the issue be resolved?

.

jakkennedy
Explorer
Explorer

Sadly, this ongoing problem clearly shows that Autodesk is not committed enough for maintaining their products or listening to feedback. Anyway, I switched to KiCad and have never looked back.

0 Likes

docmartin1014RF9P
Community Visitor
Community Visitor

Still an issue in July 2021. Deleted the libeay32.dll and it opened just fine.

0 Likes

jemiaha
Participant
Participant

I surprises me to see so many people saying things like "it opened just fine" after deleting libeay32.dll. I assume that all of them are working off-line. Working off-line cripples the SW into freeware mode. Why pay for the software if you have to cripple it into freeware mode?

.

 

0 Likes

jorge_garcia
Autodesk
Autodesk

Hi @jemiaha ,

 

I hope you're doing well. If they delete the libeay32.dll that we ship with EAGLE, then the system defaults to libeay32.dll that's already installed on the machine. So they don't cripple the software, they just have EAGLE use whatever libeay32.dll file is already in their system.

 

Let me know if there's anything else I can do for you.

 

Best Regards,



Jorge Garcia
​Product Support Specialist for Fusion 360 and EAGLE

Kudos are much appreciated if the information I have shared is helpful to you and/or others.

Did this resolve your issue? Please accept it "As a Solution" so others may benefit from it.
0 Likes

jemiaha
Participant
Participant

 @jorge.garcia

 Doing a survey of of my work PC I found 6 copies of libeay32.dll in three different versions.  Based on the programs that are using them I have my doubts that any of them actually register their copy with the OS so it could be used by another program. Windows 10 itself doesn't ship with its own copy. So can you elaborate on what you mean when you say the system will default to a copy already installed on the machine?  That question aside, I'm  much more interested in why Eagle doesn't ship with a functional library to begin with. Can you say anything about why this has been broken for so long?

 

PS Lucky for me, I copied the libeay32.dll file from my git install into my Eagle dir and now my Eagle install is back online. Still, for what people pay for this SW, there shouldn't need to be any DLL hacking to get it to work properly. 

0 Likes

one-of-the-robs
Advisor
Advisor

@jemiaha wrote:

 Doing a survey of of my work PC I found 6 copies of libeay32.dll in three different versions.

<snip>

That question aside, I'm  much more interested in why Eagle doesn't ship with a functional library to begin with. 


It does. The version it ships with works for many (most?) people. However, not for everyone.

I suspect what's going on is that all these different versions of libeay32.dll also rely on some other DLL, and some of the versions of libeay32.dll that some software installs depend specifically on a different (incompatible) version of one of those, which they install in a way that makes it the default. The version of libeay32.dll that ships with Eagle doesn't work on some systems that DO have a DIFFERENT version of libeay32.dll - which are the systems that will work without the version shipped.

Yes, it's a horrible mess, and yes, it would be nice if it wasn't like that. However, it may not be entirely Autodesk's fault - it's a consequence of the shocking lack of version control in system libraries that has plagued Windows since forever and led to the "DLL Hell" that is so familiar to software developers.

john.pollardDBLRP
Community Visitor
Community Visitor

Just confirming the same problem (and the same fix worked) on a freshly configured Surface Book 3 and Eagle 9.6.2...

...one would think that this problem should have been fixed in the shipping product after all this time

infoR3BS2
Participant
Participant

I had this issue on my new laptop with an 11th Gen Core i7 1165G. It works on all my other laptops and desktops (including Core i7 10980H and AMD Ryzen 9 5950X). I think it has to do with specific processors and their crypto instruction set. In my case, on the i7 1165G laptop (which runs on Linux), Eagle wouldn't run on either Wine or VMWare workstation (I don't use the native Linux version due to worse graphical performance issues, which Autodesk refuses to fix). Replacing the dll in both the Wine version and the VMWare version fixed the issue for me. Kudos to the person that found the fix.

0 Likes