Skip to main content
Participant
June 10, 2021
Answered

Adobe Reader June 2021 update unsigned dll libeay32.dll

  • June 10, 2021
  • 5 replies
  • 4021 views

Hi,

 

I would like to report a bug, the DLL libeay32.dll in x:\program files(86)\Adobe Reader DC\Reader is suddenly without digital signature after the update.
This is causing issues as we only allow digitally signed executables to run on our environments.

 

 

This topic is closed to new replies. Start a new post to keep the conversation going.
Correct answer Meenakshi_Negi

Hello,

 

Hope you are doing well and am sorry for the trouble.

 

We have released an update for Acrobat & Reader. Please install the latest update of Acrobat & Reader 21.007.20091 Planned update, Sept 14, 2021 application and see if you still experience this issue.

You may update the application from the help menu > check for updates in the application. Install the latest patch and reboot the machine.

 

To know more about the latest release, please see: Adobe Acrobat and Reader - September' 21 update is now available!

 

Let us know how it goes.

 

Thanks,

Meenakshi

5 replies

Meenakshi_Negi
Meenakshi_NegiCorrect answer
Legend
September 15, 2021

Hello,

 

Hope you are doing well and am sorry for the trouble.

 

We have released an update for Acrobat & Reader. Please install the latest update of Acrobat & Reader 21.007.20091 Planned update, Sept 14, 2021 application and see if you still experience this issue.

You may update the application from the help menu > check for updates in the application. Install the latest patch and reboot the machine.

 

To know more about the latest release, please see: Adobe Acrobat and Reader - September' 21 update is now available!

 

Let us know how it goes.

 

Thanks,

Meenakshi

Participant
June 11, 2021

we whitelisted the dll and it is working for now. 
As you understand we prefer to reduce expections. I'm glad to read it will be fixed in the next update.

Participant
June 11, 2021
  •  
subhadrav38507044
Participant
June 11, 2021

This issue has been acknowledged. It is planned to be fixed in our next update.
Could you please try whitelisting this dll in your protection software.

Participant
June 10, 2021

We experience the exact same thing.