ACROBAT CANNOT LOAD IT'S CORE DLL - ACROBAT CANNOT LOAD IT'S CORE DLL

Please refer the Kb Doc :http://helpx.adobe.com/acrobat/kb/reader-core-dll-error.html

Kind of an old post but I've got a work-around for this issue.  I ran procmon to see what Adobe Reader was up to and for some reason it is trying to look at the root of C:\ for it's DLL files.  Copy C:\Program Files (x86)\Adobe\Reader X.X\reader\ all files, not the folders from here to C:\.  Adobe reader will work fine.  Still looking into why Reader is looking in C:\.

I am seeing this error going from 9.4.3 to 9.4.4.  We deploy via group policies on an internal network.

I've tried the following:

Ran Repair from add/remove programs

No change.  Same error.

Uninstall 9.4.4

This results in 9.4.4 being redeployed in a manor that creates the entry in Add/Remove Programs without actually installing anything.  Not very helpful.

Recreate the 9.4.4 install from 9.4.0 and applying the patches one by one deploying each step along the way...

... (1/2 a day later) and I'm no further along  than when I started.

9.4.3 works

9.4.4 doesn't work.

Reset all of the permissions for Adobe directory in Program Files giving Users Full Control access.

No change.

Disable Symantec and run repair again.

No change.

Might try recreating the transform file.  Any other ideas???

Well, solved problem by myself.  I've got the problem under a simple user, and it was not there under administrator users.  So, I first cleared the %appdata% in that user, then the registry keys pointed out here, and nothing helped.  Afterwards, I uninstalled and reinstalled the application and it didn't help exactly out.  But, I noticed that there was a little problem with securities in the C:\Program Files\Adobe folders and sub folders so I just re-applied the securities for "users" to be able to run and see content from that folder, and re-applied to all files and sub-folders.  That worked.

Cya

BTW - This error is still an issue and sporadically takes place in Adobe Acrobat AS WELL AS Acrobat READER so this is an appropriate forum regardless of what some “others” might think while trolling this forum. If you have any beneficial information regarding this error in ACROBAT & ACROBAT READER, please provide constructive responses.

Thank you,

It appears I've arrived to the party a bit late. Today, I responded to an Adobe Update window to update my Adobe 8 product contained in the CS3 that I own. I should preface I've never had an issue with the CS3 products other than a simple, quickly fixed glitch in Dreamweaver. However, after this "udpate" I continue to get, not only the "Acrobat cannot load it's core dll" message, but it's followed by this dilly.

"The instruction at "0x5a9288a4" referred to memory at "0x5a9288a4". The memory could not be "written". Click OK to terminate program.

Thinking that perhaps the update skunked something up, I got out my CS3 master disk and "repaired" the installation. That did nothing to solve the problem. Then I followed the instructions posted by UMC-1 as provided by Adobe. Still the problem persists. Given that it comes on the heels of the Adobe Update, I'm sure it is no coincidence. I use Acrobat every single day and have never had this issue.

Has anyone else had this same failure scenario immediately following the Update? And, (fingers crossed) has anyone discovered a solution to get back to happy Acrobatting?

Thanks.

Mark

im having the same problem. when ever i try to open my Adobe Reader 9 it says Acrobat failed to loads its Core DLL and when ever i try to open PDF files on the internet it doesent let me. Ive tried reinstalling Adobe Reader 9 but it doesn't let me reinstall it and it says Error. So can someone please tell me what is wrong with my Adobe Reader 9.

Here is the advice Adobe finally gave me:

Create a test PDF and attempt to reproduce the issue to verify that it

is not a file specific issue.

To create a test PDF file:

1. Open the Printers and Faxes Control Panel from the Start Menu.

2. Right-click on Adobe PDF and select Properties.

3. Select Print Test Page and save the PDF to the Desktop.

If the issue does not occur, then there is an issue with the original

file. You will either need to troubleshoot the content of the file or

try to recreate it.

If the issue persists with the test file, then it is possible that the

Acrobat preferences have become damaged. Reset the Acrobat

preferences and then attempt to reproduce the issue.

To reset the Acrobat preferences:

1. Exit all instances of Acrobat.

2. On the keyboard, hold down the Windows logo key and tap the #R#

key. This will open the Run dialog box.

3. Copy the following text into the Open field and press the OK

button:

%Appdata%\Adobe

4. Rename the #Acrobat# folder to #Acrobat old#.

5. On the keyboard, hold down the Windows logo key and tap the #R#

key.

6. Copy the following text into the Open field and press the OK

button:

regedit

7. Right-click on My Computer, select Export and then save the file

as #Registry Backup# to the Desktop. This creates a backup of the

registry.

8. Browse to: HKEY_CURRENT_USER\Software\Adobe\Adobe Acrobat.

9. Right-click on the 8.0 folder and select Rename.

10. Change the name from 8.0 to 8.0 old.

11. Close the Registry Editor.

12. Launch the Acrobat application and attempt to reproduce the

issue. Acrobat creates new preference directories.

I implemented their suggestions, however the registry key of HKEY_CURRENT_USER\Software\Adobe\Adobe Acrobat that they gave me was incorrect as ours is: HKEY_CURRENT_USER\Software\Adobe\Adobe Acrobat\PDFMaker\8.0

I went ahead and renamed it to 8.0.old as instructed so time will tell if the Acrobat Cannot Load It's Core Dll error message goes away.

Ummm...  if 500,000 Acrobat installations were falling dead with the same issue, then it might be Adobe's problem to "fix."  Otherwise, it is yours, and the question for you becomes, "how?"

The first place that I would look is in the Event Viewer, which is one of the Administrative Tools and which might require Administrator-level access.  When a Windows call fails in some unexpected way (such as one that might cause a message as cryptic as this one), Windows probably makes an entry in the error-log.

It would also be useful to know if any other applications have become similarly unstable at about the same time.

I do not generally find it useful to blame such things on the usual knee-jerk assumption, "it must be a virus."  Taking for granted that of course you are not running your Windows box as an Administrator ... ... that really won't be much of a likely possibility.  There is something that is causing a LoadLibrary() API call to fail, under conditions that ought never to occur.  The Event Viewer is your most likely source of useful, factual information about what might be going on in your system(s).

If you could be a little bit more specific about your error and environment, maybe somebody could help you.