Solved Missing/corrupted manifests (Error 80073712)

[Fezzik]

Whenever I attempt to install KB2742599 (MS13-004: Description of the security update for the .NET Framework 3.5.1 on Windows 7 Service Pack 1 and Windows Server 2008 R2 Service Pack 1: January 8, 2013), I receive an error. I ran the system update readiness tool which identified the fact that there are corrupted files but was unable to fix them. Similarly, CheckSUR was largely unable to replace the missing manifests as they were not present in its directory. I appreciate help in correcting this problem.

 

[NoelDP]

I can find no evidence that you've run an SFC scan in the CBS.log file. There are however indications of some problems with the COMPONENTS registry hive.

Please run an SFC /SCANNOW and post another CBS.log

Most of the 100 errors in the CheckSUR log seem to relate to two updates - I'll have to research which two, though.
Back in a bit with what I can find

 

[NoelDP]

I've uploaded a file - fezaa.zip - to my SkyDrive at https://skydrive.live.com/#cid=936736BB8FCEB92F&id=936736BB8FCEB92F%21526
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 fezaa in the same place.
Open this folder - there should be one folder inside it (Manifests)

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

(I'm a few short - the eyes are crossing! - so we'll have to catch the rest next time around.)

 

[Fezzik]

Cheers!

 

[NoelDP]

91 posted, 91 fixed
9 to go.

Back soon with them.

Just one error in the CBS.log to contend with

 Line 7362: 2013-01-22 21:14:04, Info                  CSI    000002e8 [SR] Beginning Verify and Repair transaction
 Line 7366: 2013-01-22 21:14:04, Info                  CSI    000002ea [SR] Cannot repair member file [l:20{10}]"mfc90u.dll" of Microsoft.VC90.MFC, Version = 9.0.21022.8, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:10{5}]"win32", TypeName neutral, PublicKey neutral in the store, hash mismatch

I'll post that one later.

 

[NoelDP]

Here's the CheckSUR fix....


I've uploaded a file - fezab.zip - to my SkyDrive at https://skydrive.live.com/#cid=936736BB8FCEB92F&id=936736BB8FCEB92F%21526
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 fezab in the same place.
Open this folder - there should be one folder inside it (Manifests)

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

.... CBS fix next post

 

[NoelDP]

..and here's the CBS fix (I had a nightmare working out how to find the right file!)


I've uploaded a file - fezac.zip - to my SkyDrive at https://skydrive.live.com/#cid=936736BB8FCEB92F&id=936736BB8FCEB92F%21526
Please download and save it.
Right-click on the saved file and select Extract all...
Change the target to C:\ and click on Extract
This should create a folder C:\fezac
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:\fezac
hit the enter key - if you get a 'Not Found' error try
DIR D:\fezac
or
DIR E:\fezac

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

XCOPY <drive>:\fezac <drive>:\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 reply

 

[Fezzik]

I'm not sure why, but it's not letting me access your SkyDrive (it redirects me to a sign-in page; this wasn't an issue yesterday), so I can't get at what you uploaded right now. Any idea what happened? And thanks for helping me with this.

 

[NoelDP]

must be my fault - I can't use that link either.......
https://skydrive.live.com/#cid=936736BB8FCEB92F&id=936736BB8FCEB92F%21654 should work

 

[Fezzik]

Good news - check out the log! Thanks for helping with that. I'll do the CBS fix later today.

 

[NoelDP]

So far, so good

 

[Fezzik]

The Repair my Computer option is requiring my Win7 disk, which I haven't been able to find.

 

[NoelDP]

Oh heck!
You can download a Windows 7 SP1 disk from the links here.... Microsoft and create the DVD (you need to burn it, rather than copy it - you can use the Windows Disk Image Burner for that)

 

[Fezzik]

I don't have any handy writable DVD's, so I'm going to see if I can borrow a Win7 disk from IT tomorrow. I'm sorry for the hold up!

 

[NoelDP]

No problem - I'm not planning on going anywhere

 

[Fezzik]

No integrity violations found.

 

[Fezzik]

Is there anything else you wanted me to do, or are you ready to say case closed?

 

[NoelDP]

Sorry - I got cornered

Just test Windows updates, and see if everything happens as it should

 

[Fezzik]

No worries, I can see you're quite in demand. I successfully performed Windows Update and installed the one I mentioned in my OP with no trouble. Thanks a ton for all of your help, especially that nightmare you had fixing my CBS problem.

 

[NoelDP]

That was a relatively easy one - there are lots worse out there!