Windows update failing due to missing timezone manifests

Mark56 · 23 Dec 2012

latest log attached

NoelDP · 23 Dec 2012

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 · 24 Dec 2012

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 · 24 Dec 2012

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 · 24 Dec 2012

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 · 24 Dec 2012

You were right - I was wrong!

Back in a minute with the repair protocol! :)

NoelDP · 24 Dec 2012

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 · 24 Dec 2012

Its looking good now
no errors, logs attached

thanks for all your help

Mark56 · 24 Dec 2012

the tutorial I used to do the registry trace Windows Update Manifests - Manually Trace Through Registry
this was very helpful

NoelDP · 24 Dec 2012

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.