OK, so half an hour when to pot, and turned into 12 hours.
Anyway, the overall reason is that a single file name can have multiple contents, and not all computers have every file.
Well, the correct way is to extract a replacement file from the actual install, which makes sense.
Right, there are two tutorials for System Update Readiness Tool logfiles, both of which are long, and both of which only brush the surface. If you are truly dedicated, read this!
http://www.sevenforums.com/tutorial...eadiness-tool-checksur-log-file-analyzis.html
It is not an easy read. The author's first language is not English, and it can be hard to follow at times.
However, it also teaches the basic, fundamental techniques. These are not longer used. Nowadays, we have automated tools (written by me ) to automate almost all scenarios, and tutorials for their use, usually reserved for apprentices in this field of study. If you are interested, send me a Private Message, and tell me which bits you are interested in. You are more than welcome to (and I am the author so I have the keys and rights)
Right, let's do things the semi-manual way.
Look again at your log. Take an example line.
"Package_for_KB2559049~31bf3856ad364e35~amd64~~6.1.1.2.cat"
Find which Knowledge Base (KB) article it belongs to, in this case KB2559049.
Check that there are no other KBs in the log. For you, there are not. If there are, repeat the below for each one.
Visit support.microsoft.com/kb/{number}, in this case support.microsoft.com/kb/2559049
(TIP: In actual fact, it is faster to Google KB2559049)
Select the download link for
IT Professionals (none of the others will bring you to the correct page)
Find the correct download link:
Download Details - Microsoft Download Center - Cumulative Security Update for Internet Explorer 8 in Windows 7 x64 Edition (KB2559049)
Understand now why I asked if you had IE8 or IE9?
Download it.
The above tutorial will show you how to extract it.
However, that is really slow. If you want to be an efficient pro, follow this tutorial instead:
http://www.sevenforums.com/tutorials/155584-windows-update-extract-update.html
Now use your extracted files to produce your fix. It will take ages!
But look, I have a tool to automate the whole thing!
Now that does save me a lot of time! It will analyse the log file, extract the update, create the fix, and .zip it up for me! I really no longer do any work at all! If you want a copy, please drop me a PM. And that goes for anybody reading this.
Very soon, there will be a version of that tool which inexperienced users can use. It features a nice wizard, analyses the log file, downloads the required files from Microsoft servers, creates the fix, and fixes the machine, all in a simple to use Next->Next->Finish format. Now that is cool
About 1 month away. Perfectly in time for any trends in Windows 8 update failures. I shall be hot off the mark for Windows 8!
There are so many more programs of mine, tricks, and so much more to learn. If you are interested, ask or PM me! Anyway, onto the fix (which you hopefully understand a little better now)
WARNING! This fix was created specifically for this user! If you are not this user, do not follow these instructions!
@
Crowface: Ignore the above
Download the attached .zip file. Inside it, will be two folders, Packages and Manifests.
Create these folders if they do not already exist:
C:\Windows\Temp\CheckSur\Servicing\Packages\ and
C:\Windows\Temp\CheckSur\winsxs\Manifests
Extract Packs.zip onto your Desktop. Please place the contents of my
Desktop\Packages in
C:\Windows\Temp\CheckSur\Servicing\Packages\ and my
Desktop\Manifests in
C:\Windows\Temp\CheckSur\winsxs\Manifests.
DO NOT place the .zip file in that folder, or the folders themselves. Make sure that a lot of files are in each of those Checksur folder. NOTE: For you there are no manifests. Just move on.
Re-run the System Update Readiness Tool, and get me another copy of
C:\Windows\Logs\CBS\CheckSUR.log.
Also, please retest Windows Updates (with fingers slightly crossed, no matter how much we both know that that won't help! lol.)
Thanks a lot!
Richard
