Solved Windows update failing due to missing timezone manifests

[Mark56]

Windows update errors are Code 80073712, 800B0100 and 8007065E

There are a number of manifests missing that the repair disk/original disk isn't fixing

I am running Windows 7 x64 Ultimate (upgrade online after originally installing Pro)
help fixing this much appreciated....

 

[NoelDP]

Ouch! 96 missing manifests is rather a lot - It'll take me a while to sort them out and craft a fix, so bear with me.

If you haven't heard in 24hrs, SHOUT!

 

[NoelDP]

I've managed to source all the files except one - which I can't find anywhere....
x86_microsoft-windows-minkernelapinamespace_31bf3856ad364e35_6.1.7601.17965_none_0c845227da39a5ef.manifest

I *think* it may come from Office 2013?? - would that make sense to you?

Here's the others, anyhow (I hope!)....

I've uploaded a file - mark56.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 mark56 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)

The reboot and run another SFC scan

Post the new CheckSUR.log and CBS.log file, and the CheckSUR.persist.log file.

 

[Mark56]

Hi Noel, thanks very much
it fixed 95 of them

you are right, I do have Office 2013 installed so the last one is probably from there
Any idea what i could do to fix the last one?

i've attached the logs and its looking much better

mark

 

[NoelDP]

I'm downloading it now - hopefully, I'll get it sometime today (300+MB over a 3G link is painfully slow!)
If I find it there, I'll get back to you, but at least I may have somewhere to start.

 

[NoelDP]

Not good - the 300MB language update I downloaded only contained a single manifest, and that was the wrong one.

Downloading the full 1.4GB package will not be possible until tomorrow, when I should be able to get to a landline.

If you have the media for Office 13 handy, you could try doing a Search for any of the more unique strings involved - e.g.

minkernelapinamespace
6.1.7601.17965_none
0c845227da39a5ef

but they are likely to be inside a .cab file which you would need to be able to extract, using WinRar or similar.

If you want to have a go, then feel free - if you find what you think is the right file, attach it to a replay, and I'll check it before we do anything rash

 

[Mark56]

OK, I'm doing a search now, I loaded office 2013 plus Visio 2013 and project 2013 but Ill check office first. May be a while, its 2AM here so I doubt I'll stay up to see the results. I'll post what I find

 

[Mark56]

I haven't had have any luck finding this on the iso's that I have for office, visio or project.
I did install the office 2013 beta but uninstalled that before I loaded the released version (from MSDN)

unfortunately this one is still screwing up the windows update and I still have the same error msg

 

[Mark56]

Update - the windows update now only returns a single error message 80073712 and from 1 failed update (KB2758857).

I have tried running the repair for Office 2013 and also a microsoft trouble shooter (logs attached)(http://go.microsoft.com/fwlink/?LinkId=231149) recommended by their update faq. It said it corrected a number of problems (see picture).
View attachment 246802

 

[NoelDP]

Some interesting logs there!
Please run CheckSUR again and see what it reports this time - I'm going out soon in a hunt for a landline I can use

 

[Mark56]

latest log attached

 

[NoelDP]

Still the same missing file - I'm downloading Office 2013 now, so it'll take me a few hours to find the right file (if it's there at all! - I may have to install it and try updating it before I can find it)

 

[Mark56]

I traced through the registry (instructions on this site by Tom982) and found the keys. It was pointing to kb2758857 (in the key CBS_package_37_for_kb2758857~31bf3856ad364e35~amd64~~6.1.1.0.275_09828e44b06653fd).

When i look it up on microsoft it doesn't find kb2758857
but it does list MS12-081: Vulnerability in Windows file handling component could allow remote code execution: December 11, 2012
it says "MS12-081: Vulnerability in Windows file handling component could allow remote code execution: December 11, 2012" but I'm not sure how to get the manifest from this.

 

[NoelDP]

Where are you getting KB2758857 from? It seems to me to have no bearing on the problem file?
I managed to get Office downloaded last night, so I'llstart playing in a minute and see if I can find the right file in it - do you have the 32-bit or the 64-bit version installed?

 

[Mark56]

hi Noel, I did a trace of the registry using the public key in teh manifest name (there is an article on this site explaining how to do it). It traced down to the deployment package which was KB2758857

I finally found it on the MS site and the manifest in the KB2758857 download at Download Security Update for Windows 7 for x64-based Systems (KB2758857) from Official Microsoft Download Center

I'm trying the fix now to load the manifest

 

[NoelDP]

You were right - I was wrong!

Back in a minute with the repair protocol!

 

[NoelDP]

Hi - here's teh protocol....#


I've uploaded a file - Mark562.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 mark562 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.

 

[Mark56]

Its looking good now
no errors, logs attached

thanks for all your help

 

[Mark56]

the tutorial I used to do the registry trace http://www.sevenforums.com/tutorial...anifests-manually-trace-through-registry.html
this was very helpful

 

[NoelDP]

Thanks for the link!

Now that CheckSUR is clear, please run an SFC /SCANNOW so we can see if anything else needs fixing.
If it comes back clear, see if Windows Updates now functions properly - you should do a manual check for updates first, as the detections will have changed.