Skip navigation
finndesolace
Currently Being Moderated

Acrobat fatal error: failed to load core dll

Sep 21, 2010 3:08 AM

Hi,

 

I have a problem with acrobat reader on my laptop.

My OS is Vista Home Premium.

 

I had Master collection CS4 installed.

 

When starting up acrobat reader; i got following error:

failed to load core dll.

 

I went to the log and this is the explenatoin written in there: (i'm dutch speaking)

 

Kan activeringscontext voor 'C:\Program Files\Adobe\Reader  9.0\Reader\AcroRd32.dll' niet maken. Fout in manifest of beleidsbestand  '' op regel . Een onderdeelversie die nodig is voor de toepassing  conflicteert met een andere onderdeelversie die reeds actief is.  Conflicterende onderdelen zijn: Onderdeel 1:  C:\Windows\WinSxS\manifests\x86_microsoft.vc80.crt   _1fc8b3b9a1e18e3b_8.0.50727.42_none_db5f52fb98cb24  ad.manifest.  Onderdeel 2: C:\Windows\WinSxS\manifests\x86_microsoft.vc80.crt   _1fc8b3b9a1e18e3b_8.0.50727.762_none_10b2f55f9bffb  8f8.manifest.

Kan activeringscontext voor 'C:\Windows\system32\BHOManager.dll' niet  maken. Fout in manifest of beleidsbestand '' op regel . Een  onderdeelversie die nodig is voor de toepassing conflicteert met een  andere onderdeelversie die reeds actief is. Conflicterende onderdelen  zijn: Onderdeel 1: C:\Windows\WinSxS\manifests\x86_microsoft.vc80.crt   _1fc8b3b9a1e18e3b_8.0.50727.42_none_db5f52fb98cb24  ad.manifest.  Onderdeel 2: C:\Windows\WinSxS\manifests\x86_microsoft.vc80.crt   _1fc8b3b9a1e18e3b_8.0.50727.762_none_10b2f55f9bffb  8f8.manifest.

 

I simultaneously had a problem with Dreamweaver.

 

I think all this is caused by an Side By Side configuration issue.

 

I've tried to do following steps:

-

-redistibrutable 2008 c++ package geinstall
-system recoverage tool
-reinstall cs4 master collection
-uninstall master collection, clean up, install reeware acrobat reader
-uninstall acrobat reader, ccleaner register issues resolver , also older than 24 uur , reboot,  install acrobat reader freeware

-revo uninstall tool to remove acrobat

 

none of the above actions were successful.

 

What could u suggest or give as a solution.

 

Atm i'm using an altarnative pdf-reader.

But as i bought the master collection,

i'd rather have my adobe acrobat reader pro and dreamweaver working.

 

Thanks in advance,

 

With friendly regards

 

Anton

 
Replies
  • Currently Being Moderated
    Oct 29, 2010 5:37 PM   in reply to finndesolace

    Hi Anton

     

    I am sorry, I do not have an answer just a similar problem.

    I am no expert, but all these manifest files are to ensure that different developers can ensure that the appropriate versions of common libraries are used by particular versions of their software.

    Deatils are below. The original problem was a corrupted manifest file, probably due to a disk error. This resulted in several programs failing to run. In particular I was unable to access backup on my Windows Home Server. From the logs I was able to identify the manifest file in error and located a copy of a file with the same name on another of my computers. Using notepad I then changed the file causing the problem to match the file on the other computer.

    This appeared to resolve all my problems.

    When the Acrobat Reader updated itself, however, the"failed to load core DLL" message appeared. Simply uninstalling all adobe programs and re-installing makes no difference.

     

    If you have the solution please post.

     

    If not, I will continue to research this problem.

     

    Very best wishes

     

    Graham

     

    Details from error log and manifest files:

     

    Acrobat failed to load its core DLL

     


    Log Name:      Application
    Source:        SideBySide
    Date:          29/10/2010 23:30:07
    Event ID:      80
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      9GHASUSP5QSEx64
    Description:
    Activation context generation failed for "C:\Program Files (x86)\Adobe\Reader 9.0\Reader\AcroRd32.dll".
    Error in manifest or policy file "" on line .
    A component version required by the application conflicts with another component version already active.
    Conflicting components are:.
    Component 1: C:\Windows\WinSxS\manifests\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8 .0.50727.4927_none_d08a205e442db5b5.manifest.
    Component 2: C:\Windows\WinSxS\manifests\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8 .0.50727.762_none_10b2f55f9bffb8f8.manifest.

     


    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
        <noInheritable></noInheritable>
        <assemblyIdentity type="win32" name="Microsoft.VC80.CRT" version="8.0.50727.4927" processorArchitecture="x86" publicKeyToken="1fc8b3b9a1e18e3b"></assemblyIdentity>
        <file name="msvcr80.dll" hash="b2cd2205044f7cfd822da03b5f8d329ac5f4fcde" hashalg="SHA1"><asmv2:hash xmlns:asmv2="urn:schemas-microsoft-com:asm.v2" xmlns:dsig="http://www.w3.org/2000/09/xmldsig#"><dsig:Transforms><dsig:Transform Algorithm="urn:schemas-microsoft-com:HashTransforms.Identity"></dsig: Transform></dsig:Transforms><dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"></dsig:DigestMethod><dsig:DigestValue>niXcYiF5k0Z3fQ7PBFMJuaYHWTU=</ dsig:DigestValue></asmv2:hash></file>
        <file name="msvcp80.dll" hash="984100dac2591da1a03c5146fecc47eb5deabec7" hashalg="SHA1"><asmv2:hash xmlns:asmv2="urn:schemas-microsoft-com:asm.v2" xmlns:dsig="http://www.w3.org/2000/09/xmldsig#"><dsig:Transforms><dsig:Transform Algorithm="urn:schemas-microsoft-com:HashTransforms.Identity"></dsig: Transform></dsig:Transforms><dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"></dsig:DigestMethod><dsig:DigestValue>aW9cDm76mbaI14MUAAx8P0auVdE=</ dsig:DigestValue></asmv2:hash></file>
        <file name="msvcm80.dll" hash="34d9d81de781f7566e20e2bd33e410bc80837703" hashalg="SHA1"><asmv2:hash xmlns:asmv2="urn:schemas-microsoft-com:asm.v2" xmlns:dsig="http://www.w3.org/2000/09/xmldsig#"><dsig:Transforms><dsig:Transform Algorithm="urn:schemas-microsoft-com:HashTransforms.Identity"></dsig: Transform></dsig:Transforms><dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"></dsig:DigestMethod><dsig:DigestValue>pyazDrJIgYvW/Y3vCJt/9hpimHA=</ dsig:DigestValue></asmv2:hash></file>
    </assembly>

     

    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
        <noInheritable></noInheritable>
        <assemblyIdentity type="win32" name="Microsoft.VC80.CRT" version="8.0.50727.762" processorArchitecture="x86" publicKeyToken="1fc8b3b9a1e18e3b"></assemblyIdentity>
        <file name="msvcr80.dll" hash="10f4cb2831f1e9288a73387a8734a8b604e5beaa" hashalg="SHA1"><asmv2:hash xmlns:asmv2="urn:schemas-microsoft-com:asm.v2" xmlns:dsig="http://www.w3.org/2000/09/xmldsig#"><dsig:Transforms><dsig:Transform Algorithm="urn:schemas-microsoft-com:HashTransforms.Identity"></dsig: Transform></dsig:Transforms><dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"></dsig:DigestMethod><dsig:DigestValue>n9On8FItNsK/DmT8UQxu6jYDtWQ=</ dsig:DigestValue></asmv2:hash></file>
        <file name="msvcp80.dll" hash="b2082dfd3009365c5b287448dcb3b4e2158a6d26" hashalg="SHA1"><asmv2:hash xmlns:asmv2="urn:schemas-microsoft-com:asm.v2" xmlns:dsig="http://www.w3.org/2000/09/xmldsig#"><dsig:Transforms><dsig:Transform Algorithm="urn:schemas-microsoft-com:HashTransforms.Identity"></dsig: Transform></dsig:Transforms><dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"></dsig:DigestMethod><dsig:DigestValue>0KJ/VTwP4OUHx98HlIW2AdW1kuY=</ dsig:DigestValue></asmv2:hash></file>
        <file name="msvcm80.dll" hash="542490d0fcf8615c46d0ca487033ccaeb3941f0b" hashalg="SHA1"><asmv2:hash xmlns:asmv2="urn:schemas-microsoft-com:asm.v2" xmlns:dsig="http://www.w3.org/2000/09/xmldsig#"><dsig:Transforms><dsig:Transform Algorithm="urn:schemas-microsoft-com:HashTransforms.Identity"></dsig: Transform></dsig:Transforms><dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"></dsig:DigestMethod><dsig:DigestValue>YJuB+9Os2oxW4mY+2oC/r8lICZE=</ dsig:DigestValue></asmv2:hash></file>
    </assembly>

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 30, 2010 3:45 PM   in reply to jaygetee

    I have spent some time reading the forums without finding a solution.

    In  my case, and Anton's, there are two manifest files beginning  x86__microsoft.vc80.crt with the same public key _1fc8b3b9a1e18e3b.

    The version numbers are different, in my case 8.0.50727..4927 and 8.0.50727.762.

     

    The forums include a suggestion to delete one, but which?

    Also it is not clear that there are no other programs that might rely on the deleted version.

     

    Another consideration is that I have another computer also running 64 bit Windows 7 Ultimate; the manifest folder on that computer includes the identical two manifest files but is able to run Acrobat Reader without problem.

     

    The conclusion is that the existence of the two manifest files is not the issue, so what is?

     

    I suspect that unless an Adobe expert responds I need to repost this on a Microsoft manifest forum.

    Any Adobe experts monitoring this forum?

     

    Best wishes

     

    Graham

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 31, 2010 5:16 AM   in reply to jaygetee

    After further research I am inching towards a vague understanding.

    The Adobe Reader error is "Failed to load Core DLL", but the error leading to this is:

     

    A component version required by the application conflicts with another component version already active.

     

    This is the error description for System Error 14008 (0x36B8) ERROR_SXS_VERSION_CONFLICT

     

    Not being a developer I am not familiar with the use of manifest files, but bearing in mind that when the original manifest file was corrupted several programs failed including MS Office components and Kaspersky Internet Security, is it possible that one of these programs such as KIS which starts automatically has activated one version of vc80 and Adobe Reader version whatever reqests a different version.?

    Anyone from Adobe paying attention?

    Best wishes
    Graham
     
    |
    Mark as:
  • Currently Being Moderated
    Oct 31, 2010 5:55 AM   in reply to jaygetee

    I found this link which claims to have a solution is some cases:

     

    http://social.technet.microsoft.com/Forums/en-US/itprovistaapps/thread /a4c36078-6419-4424-8a43-ff3832786b59

     

    Some of these refer to 32 and 64 bit conflicts.

     

    One of these includes:

     

     Just spoke with Adobe tech support and the tech suggest I simply remove 
    one of the conflicting files. He "guessed" the first one would do it. I 
    did not follow that advice. It doesn't make sense, does it. One file is 
    for 64 the other for 32?

     

     

    Others to installing Adobe Reader version 9 after installing some Adobe software which installed Adobe Reader 8, which I guess is my situation. The proposed solution suggestes the use of software such as Resource Tuner to alter the Adobe Reader EXE. I do not like the idea of this and what happens when the next Adobe update comes along?

     

    Another relevant thread is http://forums.adobe.com/message/2805793. Most recent post os August 2010. Again no resolution.

     

    I keep up the research for a while, but I really have better things to do.

     

    Best wishes

     

    Graham

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 2, 2010 8:50 PM   in reply to finndesolace

    Anton

     

    I have finally cracked my problem!

     

    I do not know whether it will help you, but I will describe the thought process and the actions I took.

     

    Thinking back to the beginning of my problems, a number of programs were affected, including Kaspersky and MS Office programs such as Outlook. I do not recall that Adobe Acrobat Reader was affected because I do not use it much. It might have been due to a disk error, or some rogue program error, but the error logs indicated that a manifest file had invalid XML syntax on line 0. I use a Windows Home Server to back up my computers but I was unable to access the backup files.  I therefore found a copy of that file on my laptop and copied that to replace the corrupted file. I tested as many programs as I could think of and all seemed to work. My update policy is to update automatically, so my computers should keep in step, but it could be that different versions of Adobe Acrobat Reader were on the two computers. It was only when Adobe Acrobat Reader was updated to 9.4.0 that the fatal error: failed to load its core DLL appeared.

     

    The two manifest files listed in the error log are identical to the files of that name on the laptop, so it is not these files that cause the error. The problem must originate elsewhere. I looked up the notes I made when replacing the corrupt file and found that the file in question was:

    file:///C:/Windows/winsxs/Manifests/x86_policy.8.0.microsoft.vc80.crt_ 1fc8b3b9a1e18e3b_8.0.50727.4927_none_516ad11f0f4bdafe.manifest

    I then recovered a copy of this file from the WHS backup and found that there is an extra line compared with the laptop version. Having inserted this line Adobe Acrobat Reader version 9.4.0 now executes without that fatal error. Even more important, Kaspersky Internet Security, Outlook and other Office programs seem to be unaffected. I can only guess that these files vary with update history.

     

    I have seen these version control manifest files described as "DLL Hell". With over 27,000 of them on this computer I wonder how it all continues to function when one error causes a nightmare.

     

    Good luck with your problem Anton. My solution might give you a clue. If you want to compare manifest files, please let me know.

     

    Best wishes

     

    Graham

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 3, 2011 11:38 AM   in reply to finndesolace

    Did you try to do a selective startup?

     

    How about check Control Panel>Administrative Tools>Event Viewer

    Then click apllications, look for Error, double click it and look at the faulting module.

    There is supposed to be a destination/path of that faulting module.

    Locate it and remove the said faulting module.

    Restart the system then relaunch the software.

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 16, 2013 12:55 PM   in reply to finndesolace

    Please See the solution on below link : http://helpx.adobe.com/acrobat/kb/reader-core-dll-error.html

     
    |
    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points