Win7x64 Update Error 0x80073712 with KB 2844286

Page 1 of 2 12 LastLast

  1. Posts : 11
    W7 Prof 64 bit
       #1

    Win7x64 Update Error 0x80073712 with KB 2844286


    Hi!
    First of all, please forgive my real clumsy English - I hope it's at least understandable.

    I have difficulties with the last MS patch (July 9), the KB 2844286 (something with .NET Framework 3.5.1) doesn't install. I tried first to delete the accompanying Files KB 2832414, 283946 and 2840631 and then a re-updating, but again for the KB 2844286 fails with the

    error 0x80073712 (error_sys_component_store_corrupt)

    The checksur.log shows several errors (cbs.zip)

    sfc /scannow shows one error with wimgapi.dll (hashmismatch) which cannot repaired, because source file is also corrupted (sfcdetails.txt).

    lossless repairing with the Win repair system isn't possible, because user-, program- and windows-folders are not in the same partition.

    In other threads, I saw very profund and competent answers, so I hope someone can help me too!

    Appreciating your help very much!
      My Computer


  2. Posts : 11
    W7 Prof 64 bit
    Thread Starter
       #2

    monolake said:

    The checksur.log shows several errors (cbs.zip)

    sfc /scannow shows one error with wimgapi.dll (hashmismatch) which cannot repaired, because source file is also corrupted (sfcdetails.txt).
    Sorry, seems the attachment hasn't been uploaded...
      My Computer


  3. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #3

    The CheckSUR results show a fair number of problems...
    Code:
    Unavailable repair files:
     winsxs\manifests\msil_system.configuration.resources_b03f5f7f11d50a3a_6.1.7601.18156_de-de_005d254fc5b281e6.manifest
     winsxs\manifests\msil_system.data.sqlxml.resources_b77a5c561934e089_6.1.7601.22326_de-de_c32719cd2f498855.manifest
     winsxs\manifests\msil_system.configuration_b03f5f7f11d50a3a_6.1.7601.22326_none_e8b3f52f0d05b71e.manifest
     winsxs\manifests\amd64_netfx-system.configuration_b03f5f7f11d50a3a_6.1.7601.18156_none_353dc22bc8a66817.manifest
     winsxs\manifests\msil_system.data.sqlxml.resources_b77a5c561934e089_6.1.7601.18156_de-de_d9f7c18f159f7403.manifest
     winsxs\manifests\msil_system.xml.resources_b77a5c561934e089_6.1.7601.22326_de-de_07f9a482d806f6b3.manifest
     winsxs\manifests\msil_system.configuration.resources_b03f5f7f11d50a3a_6.1.7601.22326_de-de_e98c7d8ddf5c9638.manifest
     winsxs\manifests\msil_system.configuration_b03f5f7f11d50a3a_6.1.7601.18156_none_ff849cf0f35ba2cc.manifest
     winsxs\manifests\amd64_netfx-system.configuration_b03f5f7f11d50a3a_6.1.7601.22326_none_1e6d1a69e2507c69.manifest
     winsxs\manifests\amd64_netfx-system.data.sqlxml_b03f5f7f11d50a3a_6.1.7601.18156_none_141ef12023ae4228.manifest
     winsxs\manifests\amd64_netfx-system.xml_b03f5f7f11d50a3a_6.1.7601.18156_none_6155a31a3c26f410.manifest
     winsxs\manifests\msil_system.xml_b77a5c561934e089_6.1.7601.22326_none_3f2fb06c1f9ce455.manifest
     winsxs\manifests\msil_system.xml_b77a5c561934e089_6.1.7601.18156_none_5600582e05f2d003.manifest
     winsxs\manifests\msil_system.data.sqlxml_b77a5c561934e089_6.1.7601.18156_none_05d86c68619fbb7b.manifest
     winsxs\manifests\amd64_netfx-system.data.sqlxml_b03f5f7f11d50a3a_6.1.7601.22326_none_fd4e495e3d58567a.manifest
     winsxs\manifests\msil_system.data.sqlxml_b77a5c561934e089_6.1.7601.22326_none_ef07c4a67b49cfcd.manifest
     winsxs\manifests\amd64_netfx-system.xml_b03f5f7f11d50a3a_6.1.7601.22326_none_4a84fb5855d10862.manifest
     winsxs\manifests\msil_system.xml.resources_b77a5c561934e089_6.1.7601.18156_de-de_1eca4c44be5ce261.manifest
     servicing\packages\Package_1_for_KB2844286~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_1_for_KB2844286~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_2_for_KB2844286~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_2_for_KB2844286~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_7_for_KB2844286~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_7_for_KB2844286~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_for_KB2844286_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_for_KB2844286_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_for_KB2844286~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_for_KB2844286~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_1_for_KB2844286~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_1_for_KB2844286~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_2_for_KB2844286~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_2_for_KB2844286~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_7_for_KB2844286~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_7_for_KB2844286~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_for_KB2844286_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_for_KB2844286_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_for_KB2844286~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_for_KB2844286~31bf3856ad364e35~amd64~~6.1.1.0.cat


    I'll post a fix protocol later which should fix them.

    There's also a single error in the SFC log -
    Code:
     Line 5293: 2013-07-11 02:04:07, Info                  CSI    0000033b [SR] Repairing 1 components
     Line 5294: 2013-07-11 02:04:07, Info                  CSI    0000033c [SR] Beginning Verify and Repair transaction
     Line 5297: 2013-07-11 02:04:07, Info                  CSI    0000033e [SR] Cannot repair member file [l:22{11}]"wimgapi.dll" of Microsoft-Windows-Wimgapi, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch


    ...but we'll leave that until we've fixed the CheckSUR errors, as they may bring other errors to light when fixed.
      My Computer


  4. Posts : 11
    W7 Prof 64 bit
    Thread Starter
       #4

    @NoelDP

    I'm sure, I am in good hands! (I read some of your hints & responses)

    monolake
      My Computer


  5. Posts : 11
    W7 Prof 64 bit
    Thread Starter
       #5

    I found another strange behavior of my system: Programs, which are located in drive E: suddenly changed to C: without any intervention on my part. From partition C: they work properly, only the link on the Desktop shows the wrong location.

    Has this behavior possibly a connection with the above shown errors? Hoping (and thanking!) for a fix protocoll...

    monolake
      My Computer


  6. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #6

    Sorry about the delay - trying to fit real life into my computing is getting difficult


    I've uploaded a file - mnlaa.zip - to my SkyDrive at Noel's SkyDrive
    Please download and save it.
    Right-click on the downloaded file, and select Extract all…
    Extract to the default location - which will create a new folder mnlaa in the same place.
    Open this folder - there should be two folders inside it (Manifests, and Packages)

    Copy the content of the Packages folder to the folder
    C:\Windows\Temp\CheckSur\Servicing\Packages

    And the content of the manifests folder (.manifest files) into this folder:

    C:\Windows\Temp\CheckSur\Winsxs\Manifests

    Now run the CheckSUR tool again (it may take a while)

    Post the new CheckSUR.log file, and the CheckSUR.persist.log file.
      My Computer


  7. Posts : 11
    W7 Prof 64 bit
    Thread Starter
       #7


    Sorry about the delay - trying to fit real life into my computing is getting difficult

    You are talking to the real problem in Life... Fortunately, every day has 24 h and a night

    I downloaded the mnlaa-file, put the contents in the appropriate folders and ran checksur. In the attachment are the new CheckSUR.log and CheckSUR.persist.log file.

    Hopefully, you can see solutions in the new log-files! Thank you indeed for your help!!

    monolake


      My Computer


  8. Posts : 11
    W7 Prof 64 bit
    Thread Starter
       #8

    Dear NoelDP

    So far, my computer is running quiet stable! If I interpret the checksur-log from July 17 correct, thanks to your help, all the files are corrected and 41 errors are destroyed!

    There remains the problem with sfc /scannow error on the wimgapi.dll File. Is there a possibilty to correct also this error thanks to your magic forces?

    I don't want to hurry you, it would be very nice, if you find some time to answer me.

    monolake
      My Computer


  9. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #9

    Great!
    We managed to fix all the CheckSUR errors in one go :)


    Now please run a new SFC /SCANNOW and post the new CBS.log, and we'll see if there's more to do.
      My Computer


  10. Posts : 11
    W7 Prof 64 bit
    Thread Starter
       #10

    NoelDP said:
    Great!
    We managed to fix all the CheckSUR errors in one go :)


    Now please run a new SFC /SCANNOW and post the new CBS.log, and we'll see if there's more to do.

    sfc /scannow remains unchanged. The CBS.log-File says at the end, the error is repaired, but a new sfc /scannow shows the same error with the wimgapi.dll... Hope you can find a solution.

    monolake
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 03:56.
Find Us