Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Win7x64 Update Error 0x80073712 with KB 2844286


11 Jul 2013   #1

W7 Prof 64 bit
 
 
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 System SpecsSystem Spec
.

11 Jul 2013   #2

W7 Prof 64 bit
 
 

Quote   Quote: Originally Posted by monolake View Post

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...


Attached Files
File Type: zip sfcdetails130711.zip (5.3 KB, 3 views)
File Type: zip cbs-logs.zip (111.4 KB, 2 views)
My System SpecsSystem Spec
13 Jul 2013   #3

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)
 
 

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 System SpecsSystem Spec
.


14 Jul 2013   #4

W7 Prof 64 bit
 
 

@NoelDP

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

monolake
My System SpecsSystem Spec
16 Jul 2013   #5

W7 Prof 64 bit
 
 

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 System SpecsSystem Spec
16 Jul 2013   #6

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)
 
 

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 System SpecsSystem Spec
16 Jul 2013   #7

W7 Prof 64 bit
 
 


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




Attached Files
File Type: zip checksur_130717.zip (4.2 KB, 5 views)
My System SpecsSystem Spec
20 Jul 2013   #8

W7 Prof 64 bit
 
 

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 System SpecsSystem Spec
21 Jul 2013   #9

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)
 
 

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 System SpecsSystem Spec
21 Jul 2013   #10

W7 Prof 64 bit
 
 

Quote   Quote: Originally Posted by NoelDP View Post
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


Attached Files
File Type: txt sfcdetails_130721.txt (87.5 KB, 2 views)
My System SpecsSystem Spec
Reply

 Win7x64 Update Error 0x80073712 with KB 2844286




Thread Tools



Similar help and support threads for2: Win7x64 Update Error 0x80073712 with KB 2844286
Thread Forum
Solved Win7x64 Update Error 57A with KB2687276 Windows Updates & Activation
Solved Winows Update errors 0x80073712 & 0x80070002 Windows Updates & Activation
Solved 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT General Discussion
Windows 7 x64 Professional SP1 Fails 0X80073712 Windows Updates & Activation
Error code 0x80073712 Windows Updates & Activation
(SP1) Installation was not successful: 0x80073712 Windows Updates & Activation
win7x64 adobe x ms visual c++ runtime error BSOD Help and Support

Our Sites

Site Links

About Us

Find 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 04:49 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33