Windows Update failures

Hi

I am running Win 7 Pro x64 on an HP Elite 7100 and have been having persistent issues with update failures - most updates fail and a few succeed but with no apparent pattern.

Running the System Update Readiness tool produced the attached log file. From what I glean it suggests that some elements of an earlier update (KB2443685) are corrupt.

I would be grateful for any help/suggestions to fix this issue.

Thanks
Nick

Hello Nick, and welcome to the Seven Forums!

Well done on uploading that log file.

I am sorry to hear that you are having problems. If all goes well, then this *shouldn't* be too hard to fix. I shall create a special fix, just for your computer (to repair just those corrupt files) and show you how to use it.

Unfortunately, I am currently at work, and I can't create this fix while at work, but it is nearly the end of the day :)

Please give me just a few more hours, and I will be back with further instructions.

Please just hang on for a little while longer for me!

Richard

niemiro - Thanks for your welcome and quick response.

I really appreciate your offer of help; will await your instructions. Cheers.

niemiro - An update. By the way thanks again for your custom help!

Followed your instructions to the letter and ran SUR again - log file (checkSUR_fix1.log) showed that six errors had been found and repaired.

Then tried to install Windows Updates and ran into issues again.

Here is a summary of steps:
1. Tried to install KB2443685 individually. Better progress than before - completed download section and then install progress bar stepped up to 70% mark and the install failed. Error code: 8024200D

2. Ran SUR again and checked log file (checkSUR_recheck1.log) - shows no errors.

3. Tried to install all 14 "important" updates. Failed with three reported errors: 8E5E03FB / 800B0100 / 8007065E.

4. Performed a system reboot.

5. Tried to install KB976932 (SP1) standalone. Install progress bar stepped to around 50% mark then install failed with "unknown" error 0x8e5e03fb.

6. Ran SUR again. Log file still reports no errors.

So -many thanks for getting me over the initial hurdle. Anyone have suggestions about a sensible next step to take?

Cheers - Nick

Hello again!

For a simple 0x800B0100 error code, what you have done would be enough to fix it. There is something else at work here (but an important first section, some corrupt files, have now been fixed)

Firstly, please create a new folder on your Desktop called LOGS. Copy into that folder the C:\Windows\Logs\CBS\ folder, and the C:\Windows\WindowsUpdate.log file.

Right click on your new LOGS folder > Send to > Compressed (zipped) folder, and upload that here.

Thanks a lot!

Richard

Hi. Thanks for your continuing assistance!

I have uploaded the requested files - including just the latest version of CbsPersist_xxxx.cab.

Cheers - Nick

Nick,

Thanks for the logs :)

That is quite a mess! Anyhow, I feel that quite a bit of it is just caused by corrupt files in your Windows Update Download directory. This is fixable, and we shall do this now.

Please run this tool in Aggressive Mode: How do I reset Windows Update components?

It is a waste of time to do it manually (just run the Fix-It) and you MUST run it in Aggressive Mode to achieve what I wish it to.

Now please re-boot your computer, and retry Windows Update. If the situation changes not at all, please tell me, otherwise, what has changed!?

Have you been battling with this for months? I see System Update Readiness Tool runs dating back to "2011-03-15 18:25", and back then you had some serious corruptions (numerically low, sometimes people have hundreds of errors, and I have a colleague who saw someone with 5000+ errors, but I have only ever dealt with 700+.) More important are the type of errors, and they weren't good! More on that later!

Richard

Richard

Thanks for the response. I will run the Fixit program but need first to back up some important work! The Fixit page in the link reports to me that it applies to a different version of Windows - I assume it does apply to Win 7?

You asked have I been battling with this for months. The PC was new at the end of February - so the Update issues have effectively been present from the start. Since the PC itself has been absolutely sound and I have been busy working intensively on a critical project I treated the Update issue as a frustrating annoyance but not a show-stopper. It's only now that I have found time to look into it a little deeper.

Cheers - Nick

Hello again!

Sorry I forgot to mention that message! It is incredibly annoying! Yes, it is perfectly compatible with Windows 7. That message is old (the tool was written for Vista, when 7 was not around. Therefore Vista is in the compatible list, but 7 isn't, generating that message.) However, it is COMPLETELY compatible with 7, and Microsoft and everyone uses it on 7 (it is fine to do so)

Sorry that I forgot to mention this, and I wish Microsoft would just update that page

Richard