Hello!
Bit of a long post coming, I feel! lol. Hard problem = long post. Too hard a problem = short post! What shall it be!
We need to take a bit of inspiration from my tutor. He is a lot older, and a lot wiser than I, but you have me! However, he has trained me well!
He always said that when you fix a complicated issue like yours, the updates that failed in Windows Update often continue to fail, with strange and unpredictable errors. He has never found out why. No matter what he tried, on those systems, he never got those particular KBs to ever install through Windows Update. But try them through the Microsoft Download centre, and they went straight on.
People think that downloading a standalone Service Pack, and through Windows Update is basically the same, just how much media for other languages is available. This is not the case. We have never ever ever worked out why, but when trying to find replacement files from hotfixes before SP1 (notoriously difficult - those are the cases which usually fail) then we could never find them on systems installed from a standalone, but from Windows Update was fine.
Since Service Packs require prerequisites, but far fewer in standalone than Windows Update, our only guess was that there is some sort of corruption still on your system, undetectable to even the best tools. However, when you standalone, it flashes a huge number of files in one go, rather than staging them through CBS, and therefore fixes the corruption, and removes some of those pre-SP1 files.
I hope this has not gone completely over the top of your head. It was meant to explain our current best theory as to why we get you to download them, a boring procedure, as it may well work. It is not just "hope-work" - worse than "guess-work"!
My tutor also has some more pearls of wisdom.
The System Update Readiness Tool is imperfect. In fact, at times, it is downright wrong! One of the things is that a re-run sometimes show different results. It cannot guarantee that all errors will be shown in one run. Great! So I am going to ask for a rerun, when it is spending less time on fixing, and hopefully will do a better job at searching!
You may start to wonder why I am telling you my job, rather than providing you with fixes. We are delving into the unknown. You sound interested, so I am simply explaining why I am running each tool, in the hope that you will understand, learn, and have fewer issues with following such a long post - again. Also, quite a lot of it you have done before, and I am trying to explain the reasons for re-doing all of this work.
Right, your codes are actually quite intriguing:
Code:
C:\Users\Richard>err 800700C1
# as an HRESULT: Severity: FAILURE (1), Facility: 0x7, Code 0xc1
# for hex 0xc1 / decimal 193 :
SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION bugcodes.h
SQL_193_severity_15 sql_err
# The object or column name starting with '%.*ls' is too
# long. The maximum length is %d characters.
ERROR_BAD_EXE_FORMAT winerror.h
# %1 is not a valid Win32 application.
# 3 matches found for "800700C1"
C:\Users\Richard>err 80070643
# as an HRESULT: Severity: SUCCESS (0), Facility: 0x4c5, Code 0xc7f3
# as an HRESULT: Severity: FAILURE (1), Facility: 0x7, Code 0x643
# for hex 0x643 / decimal 1603 :
ecFavCreateMessage ec.h
ERROR_INSTALL_FAILURE winerror.h
# Fatal error during installation.
# 2 matches found for "80070643"
C:\Users\Richard>
We are only interested in the codes from winerror.h. ERROR_BAD_EXE_FORMAT, and ERROR_INSTALL_FAILURE
The second one really means very little, but the first one could indicate a corruption of an .exe file somewhere.
Now that we have filled the WinSxS folders, SURT is happy. But a file present doesn't mean a file copied correctly. Curiously, most were to do with IE. I don't know why that was.
What tool will pick up those corruptions? SFC? Correct! What tool will reset the registrations? WU Modules fix.
What if the corruptions are of downloaded files? WU Components fix!
So, finally, we are onto the fix. Did you read all of that? No. Don't blame you.
Please try a few from the Microsoft Download centre. If they work, do them all, if a few don't, then don't waste time with the rest:
If you can't find the link for one of them, try one of the others, with an easier link to find.
If they don't work, then I am really, really sorry, but we are back to this again. I know you are going to hate seeing this!
This applied the same to Vista and 7. Do not worry that it says Vista: Please run steps 1, 2A, 3 (about 15 minutes), 4, 5 from this tutorial
System Files - SFC Command Don't worry about the logs for the time being. I have a very good reason for not asking for them!
Download and run this tool:
Description of the System Update Readiness Tool for Windows Vista, for Windows Server 2008, for Windows 7, and for Windows Server 2008 R2 When it has finished installing the update, it is done!
Right, this has produces a log of logs for me. Please now upload them. To do this, create a new folder on your Desktop called LOGS. Navigate to C:\Windows\Logs and copy the entire CBS folder into your new LOGS folder.
Close the LOGS folder, and right click on it > Send to > Compressed (zipped) folder. Then upload that zip file here, to this forum.
I know you now hate me! For long posts! For time consuming instructions! After all, surely you are being dragged out to buy the Turkey!?
Take care!
Richard
EDIT: That is stupidly long! sz!
