Solved Win7x64 Update Error 0x80073712 with KB 2844286

[monolake]

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!

 

[monolake]

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

 

[NoelDP]

The CheckSUR results show a fair number of problems...

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 -

 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.

 

[monolake]

@NoelDP

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

monolake

 

[monolake]

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

 

[NoelDP]

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.

 

[monolake]

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 :sarc:

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

 

[monolake]

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

 

[NoelDP]

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.

 

[monolake]

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

 

[monolake]

Maybe, you have to know some details of my system: It is windows 7, 64 bit, servicepack 1, language german (DE-DE).

I've tried to copy one of the wimgapi.dll files from a working computer to C:\windows\system32 (wimgapi 6.1.7601.17514 - 406528 Bytes, language deutsch, security: only read and execute).

In the windows\winsxs there are the following wimgapi.dll-files:
- in the amd64_microsoft-windows-wimgapi_31bf3856ad364e35_6.1.7600.16385_none_e4f094112e8f905d folder is a wimgapi.dll with 410176 Bytes, no specifications in the properties (!) (not yet exchanged)
- in the \x86_microsoft-windows-wimgapi_31bf3856ad364e35_6.1.7600.16385_none_88d1f88d76321f27 folder is a wimgapi.dll with 406016 Bytes, version 6.1.7600.16385, language English(USA)
- in the \x86_microsoft-windows-wimgapi_31bf3856ad364e35_6.1.7601.17514_none_8b030c557320a2c1 folder is a wimgapi.dll with 406528 Bytes, version 6.1.7601.17514, language English(USA)

The sfcdetails-log-file says that there is a hashmismatch with the wimgapi-file 6.1.7600.16385 which is refferenced to the "Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.WindowsFoundationDelivery".

When I properly understand this information, sfc compares the wimgapi.dll v 16385 with the wimgapi.dll v17514???

What can I do, to solve this sfc-error? I'm afraid to destry more things in my windows, when i begin to exchange files to my discretion/estimation.

Thank you for your help in advance!

monolake

 

[NoelDP]

2013-07-21 14:22:50, 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

I'll post a fix protocol for that later

 

[NoelDP]

I've uploaded a file - mlkaa.zip - to my SkyDrive at Noel's SkyDrive
Please download and save it.
Right-click on the saved file and select Extract all...
Change the target to C:\ and click on Extract
Close all windows (it would be a good idea to print these instructions!)
Now reboot to the Repair Environment - as soon as the machine restarts, start tapping F8 - this should bring up the Advanced Boot Menu, at the top of which should be the option 'Repair my Computer'
Pick that
You'll have to log in with your username and password.
Pick the option to use a Command Prompt
At the prompt type
DIR C:\mlkaa
hit the enter key - if you get a 'Not Found' error try
DIR D:\mlkaa
or
DIR E:\mlkaa

The drive letter in use when you find the folder will need to be substituted (for<drive>) into the following command...

XCOPY <drive>:\mlkaa <drive>:\windows\winsxs /y /i /s /v /h

(e.g. XCOPY P:\wfire P:\windows\winsxs /y /i /s /v /h )

run the command (it should take almost no time)and when the prompt returns, type
EXIT
and hit the Enter key to exit Command Prompt - reboot to Normal Mode Windows.
Now run SFC /SCANNOW in an Elevated Command Prompt
then reboot and upload the new CBS.log file to your SkyDrive Public folder, and post a new link
Also run a new MGADiag report, and post the result.

 

[monolake]

I didn't found mlkaa in your skydrive. Maybe its the ml7aa file?

Greetings!

monolake

 

[NoelDP]

Looks like I forgot to post it!!

It should be there now.

 

[monolake]

Seems to work!

I uploaded the log-files in my skydrive/public folder. I have never sharred the folder with other people, so I hope, you have an access with this link:

https://skydrive.live.com/?cid=82f537f5ed00ce8f&id=82F537F5ED00CE8F!102&action=Share

What have I done:

1. I xcopied your mlkaa content to my winsxs folder an made a restart.
2. Bluescreen after restart (no idea why, error F4(03), process or thread crusial to system operation has unexpectedly exited or been terminated) -> restart
3. sfc /scannow: found the wimgapi-error and repaired it. (see sfcdetails_130728.txt file in skydrive) -> restart
4. System hangs with the screen "windows starts" (no i dea why) -> restart
5. System says, I have to check a partition on a separate Harddisk, but now it boots my windows.
6. again a sfc-run: everything is alright.
7. PPF-Scan, CBS_130728.log in the skydrive.
8. MGADiag-run: 2 .cab-files in the skydrive.

So I will make soon the missing chkdsk-check, but it seems, my system is thanks to your help, now in a good condition.

Only thanks to your competent help I was able to avoid to format my Cartition and install a completely new win7!

monolake

 

[NoelDP]

Good - SFC is clear now.
The last error in the CBS.log file is timed prior to the last SFC scan.
Is Windows Update working?

 

[monolake]

Good - SFC is clear now.
The last error in the CBS.log file is timed prior to the last SFC scan.
Is Windows Update working?

Yes, it seems, Windows Updating is working. The critical update KB947821 is in the status "successfully" and when I'm looking for missing updates there isn't found any other update.

I wish you all the best!

monolake

 

[NoelDP]

Great

Good luck!