Share via

How can I fix crashing libeay32.dll?

Anonymous
2023-10-31T03:05:46+00:00

Hi,

I have an application which was last released for Windows 10. I have run it on Dell laptop with Windows 11 without a problem.

I just got a Surface Pro 9 which came with Windows 10. Once I booted up for the first time, I upgraded it to Windows 11 as soon as the initial updates are done. Then I installed this application. However, it failed to start.

In Event Viewer -> Windows Logs -> Application, I can see an error for this application

Event 1000, Application Error

Faulting module name: LIBEAY32.dll, version:1.0.2.5, time stamp: 0x56a8b383

I've tried to uninstall and reinstall but it did not help. Also check md5sum against the Dell laptop and they are the same.

What could be done to fix the issue?

Thanks

*** moved from Windows / Windows 11 / Apps / Windows apps***

Windows for home | Windows 11 | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2023-11-03T01:33:34+00:00

    The issue was the library was old and needs update for the new CPU. I was able to copy from another application that worked fine.

    Thanks

    8 people found this answer helpful.
    0 comments
  2. Anonymous
    2023-11-06T16:01:24+00:00

    Hi redhonker,

    Thank you for the response and for sharing the fix you found. Glad to know that it now works fine. Thank you also for spending time here with us in the Community.

    Kind regards,

    Marrion

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2023-11-01T18:49:07+00:00

    Hi redhonker,

    Thank you for reaching Microsoft Community. I understand that you are experiencing issues with an application crashing due to the libeay32.dll file.

    May I know which Surface Pro 9 configuration do you have? Intel or 5G?

    Also, may I know the exact name of the program or software that you are using?

    Based on the error message you provided, it seems that the libeay32.dll file is causing the application to crash. This file is a part of the OpenSSL library, which is used by many applications to provide secure communication over the internet.

    Here are some possible causes and solutions for this issue:

    1. Compatibility issues: The application may not be fully compatible with Windows 11 or the Surface Pro 9. You can try running the application in compatibility mode for Windows 10 to see if it resolves the issue. To do this, right-click on the application's executable file, select Properties, go to the Compatibility tab, and select "Run this program in compatibility mode for" and choose Windows 10.
    2. Corrupted libeay32.dll file: The libeay32.dll file may be corrupted or missing. You can try replacing the file with a fresh copy. You can download the latest version of OpenSSL from the official website and replace the libeay32.dll file in the application's directory with the new one.
    3. Antivirus software: Your antivirus software may be blocking the application from running properly. You can try disabling your antivirus temporarily and see if it resolves the issue.
    4. System file corruption: There may be some corruption in the system files that is causing the issue. You can try running the System File Checker (SFC) tool to scan and repair any corrupted system files. To do this, open Command Prompt as an administrator and type "sfc /scannow" and press Enter.

    Additionally, run also the Surface Diagnostic Toolkit on the device to run some system checks and repairs. See: Fix common Surface problems using the Surface app and Surface Diagnostic Toolkit - Microsoft Support

    I hope these solutions help resolve the issue. If you need further assistance, please let me know. Here are some articles that may be helpful:

    Let me know how it goes.

    Kind regards,
    Marrion

    1 person found this answer helpful.
    0 comments