EAGLE not working on Windows 11

[arjen.lammerts]

Hi,

I am currently running Windows 11 with EAGLE and experiencing issues.

After a clean install of EAGLE(9.6.2) (and Windows11), it will not start up/get past the splash screen.

i've tried a workaround, which seemed to have a similar problem, linked in another forum post:

- Autodesk EAGLE hangs or crashes after the splash screen and doesn't start | EAGLE | Autodesk Knowled... 

Renaming the LIBEAY32.DLL to LIBEAY32.DLL.BAK (essentially turning the file off) causes EAGLE to start up properly but brings forward a different issue of not being able to login to the EAGLE Servers and not being able to use shared libraries from my work environment. 

After this I tried the next step listed, "replacing" the LIBEAY32.DLL and SSLEAY32.DLL with the ones downloaded from the Total Commander Win Tools this made it able for me to go online again, but I am still unable to use the shared libraries.

I'd like to hear how to fix this.

Best regards,

Arjen Lammerts

[jorge_garcia]

Hi @arjen.lammerts ,

I hope you're doing well. Could you be more specific? What do you mean you can't use the shared libraries? 

What type of computer are you using?

Any and all info you can provide can help figure out how we can help.

Best Regards,

[arjen.lammerts]

Hi Jorge,

I am using a Core i9-11900, Windows 11, desktop pc with EAGLE 9.6.2 installed.

Normally I'm using shared eagle libraries from library.io which our team is using/updating with specific devices and such, for our needs.

Because EAGLE does not want to go online, I am unable to sync/access those shared libraries due to some issue with Windows 11 compatibility it seems. The rest of the team running Windows 10 pc's are still able to connect to and use the shared library, showing the problem is not with library.io.

This is all after changing the LIBEAY32.DLL to LIBEAY32.DLL.BAK, because this was a solution given at another forum post about a similar looking problem.

If the LIBEAY32.DLL is in place, as it is after a clean install, EAGLE will only display the splash screen for a short while and not start.

The second step taken was to download the LIBEAY32.DLL and the SSLEAY32.DLL from the other link and place them in the EAGLE folder. This makes it able to go online in EAGLE but the shared libraries are still not able to be synced/accessed, yielding the attached screenshot taken from the library manager.

If there are more questions please let me know so the problem can be resolved.

Best regards,

Arjen Lammerts.

[jorge_garcia]

Hi @arjen.lammerts ,

I hope you're doing well. If you go into the Available tab, do you see the libraries your team members have made? If they are there then you can download them and use them in EAGLE.

I've reached out to our developers to share your image. Let me know if there's anything else I can do for you.

Best Regards,

[arjen.lammerts · Accepted solution]

Hi @jorge_garcia ,

My apologies for the late reaction,

I'll firstly say, The shared libraries are working again!

It seemed to be fixed after a restart of the pc, this was probably needed after installing Win64 openSSL 1.1.1Light (a simple restart of EAGLE is apperantly not enough).

I went over to the available libraries tab and the libraries were visible again, They were not before.

Currently all is working well again, I am able to use, adjust and update the shared libraries and also able to download the latest version(s).

Altough it is fixed for me after a few work arounds, The problem can still arise for new users running Windows 11. This has something to do with the compatibility of 32-bit files linked to account validation and sign in (or something in that area), not being properly supported by Windows 11 if you ask me, but I am no expert on this...

If there are more questions I'll happily answer them to try and solve this issue.

Also a 'quick' summary of the steps taken to solve this issue:

1 - Change the LIBEAY32.DLL to LIBEAY32.DLL.BAK

effect -> EAGLE got past splash screen but not able to go online.

2 - Change the original LIBEAY32.DLL and SSLEAY32.DLL to LIBEAY32.DLL.BAK and SSLEAY32.DLL.BAK and download and copy the new LIBEAY32.DLL and SSLEAY32.DLL  in the EAGLE directory. file was downloaded from:

Index of /win/tools (totalcommander.ch) The name of the file is: openssl-1.0.2u-x64_86-win64.zip.

effect -> EAGLE is able to go online, but cannot sync/open/use shared/managed libraries from library.io

3 - Downloaded the "Win64 OpenSSL v1.1.1L Light" from: Win32/Win64 OpenSSL Installer for Windows - Shining Light Productions (slproweb.com) Linked in the forum post, ran the .exe and restarted eagle.

effect -> Nothing new after a restart of EAGLE which was recommended in the forum post, but after a restart of the pc, the libraries appeared in the available tab in the library manager again and were able to be used as normal. 

P.S.

I linked a forum post in my initial question, but it seems I linked the wrong one, my apologies

The correct one is: EAGLE is stuck in offline mode after signing in | EAGLE | Autodesk Knowledge Network

This post also links to the first link but has the other steps listed aswell.

[csun8086]

Thanks, this solved my problem!

[simonmunyua6]

check on the updates on your Windows 11. Ensure that all the plugins and the drivers are up to date then try restarting your machine after the update.

[melaboudi]

Thanks a lot man. This solved my issue. 

[AMI8008]

Thanks a lot, this solved my problem.

[vaghasiyau70]

not open in my system, my system is window 11 ,64bit

[AMI8008]

I had the same problems.  The 'problem' seems to be that I am using two (2) screens.  I have to make sure that I NEVER open/move the EAGLE 360 screen to monitor nr 2.  Because when you close the application, you will get stuck  at the splash screen.  If I do make the mistake of closing the application (F360) and having a F360 'window' open on the 2nd screen , then I have to setup the computer (temporarily) to ONE(1) screen and make sure all my F360 screens are now on the main monitor.  After this (fix), I will enable the 2nd screen again and back in business.

Regards,

Arno

[aabmar]

This issue is quite serious:

Start with a completely new PC with Windows 11. Install Eagle, latest version. It will install, you will be asked to log in. After that, it will never come further than the splash screen.

A freshly installed Eagle on a brand new computer, will not work.

Marius

[marthinek]

Hej, autodesk, seriously. what is wrong with Eagle?

Fresh install on win 11 (MS surface) shows eagle logo and that's it. doesn't even go to login prompt.

/Marcin

[jorge_garcia]

Hi @marthinek,

I hope you're doing well. This is a known problem that we run into with surfaces predominantly. You have to replace the LIBEAY32.dll. It's been around for a while and hasn't been addressed, but at least there is a way around it.

https://knowledge.autodesk.com/support/eagle/learn-explore/caas/sfdcarticles/sfdcarticles/Autodesk-E...

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

Best Regards,

[marthinek]

Hi Jorge. it works now.. but if you know this issue, why Eagle is not delivered with these *.dll files in the first place?

Why Total Commander can make them right? 😉

BTW Total Commander is the best file manager ever, so who ever reads this, please check it out!

[jorge_garcia]

Hi @marthinek,

I report the issues and make tickets but I can't get things changed. With that said, the more these things come up the quicker they get addressed.

Thank you for your feedback.

Best Regards,

[cloudapps]

Who has time for this? 

[N1]

Hi 

I have made some changes as following Arjen.Lammers steps. I still can't let Eagle run at me pc . I have downloaded EAGLE 9.6.2. I m using windows 11 64-bit.

[peterjb]

Me too.  On Windows 11, Eagle 9.6.2, 64-bit CPU.  Same symptoms... splash screen for a few seconds, then nothing.

Examining the minidump with WinDbg doesn't really show anything other than Eagle is implemented with QT5.

Using WinDbg to run eagle.exe shows more detail:

ModLoad: 00007ff7`18d60000 00007ff7`1b071000   eagle.exe
ModLoad: 00007ffe`448d0000 00007ffe`44ae4000   ntdll.dll
ModLoad: 00007ffe`43190000 00007ffe`43252000   C:\WINDOWS\System32\KERNEL32.DLL
ModLoad: 00007ffe`42300000 00007ffe`426a3000   C:\WINDOWS\System32\KERNELBASE.dll

<<<snip>>>

ModLoad: 00007ffd`c2c00000 00007ffd`c2c41000   C:\EAGLE 9.6.2\imageformats\qjpeg.dll
ModLoad: 00007ffe`36c20000 00007ffe`36d4d000   C:\WINDOWS\SYSTEM32\textinputframework.dll
ModLoad: 00007ffe`38550000 00007ffe`3860c000   C:\WINDOWS\SYSTEM32\mscms.dll
ModLoad: 00000000`12000000 00000000`12061000   C:\EAGLE 9.6.2\ssleay32.dll
ModLoad: 00000000`11000000 00000000`1122d000   C:\EAGLE 9.6.2\LIBEAY32.dll
ModLoad: 00007ffe`33c00000 00007ffe`33c19000   C:\WINDOWS\SYSTEM32\NETAPI32.DLL
ModLoad: 00007ffe`3aef0000 00007ffe`3af0b000   C:\WINDOWS\SYSTEM32\wkscli.dll
(19d0.3d48): Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
LIBEAY32!SHA512+0x1503:
00000000`1100ca23 0f2870b8        movaps  xmm6,xmmword ptr [rax-48h] ds:0000022e`7fe09324=00000000000000000000000000000220

Thread info for first (failing) thread:

0x3d48 0x0 eagle!CZipCrc32Cryptograph::Decode+0xc3 (00007ff7`18e1a893) CrBrowserMain 

And finally, the failing thread's stack:

[0x0] LIBEAY32!SHA512+0x1503 0xd1491ae2f0 0x4046800000000000 
[0x1] 0x4046800000000000!+ 0xd1491ae2f8 0x0 

This is trivial to reproduce with this detail, which should make debugging trivial.  Seeing that Autodesk is charging for this product, and that this problem has been around for 5 years, it is really disappointing.

[warren_hawkins57R37]

I am currently stuck on this issue as well. I have Windows 11 and while some of this worked to be able to start Eagle, I still cannot load any libraries on library.io. The file version available for download of OpenSSL has changed. Not sure what to try next but I cannot do my work because of this. Not sure why it's not fixed officially in the installer by now?