Win 7 SP1 fails with 800B0100 error

Right, will try that. Thanks. Shan't interfere with your thread from here on out.

Well done to you!
Safe surfing.

NoelDP said:

I think we can close this thread out now - the recommended updates for Windows installed without problems, and the only major Important one remaining is the Office 2007 SP2 (IE9 installed happily).

Just to round it up a little, the cure for this appears to be

1) run Fixit 50123 followed by Fixit 50202 in both normal and aggressive modes

and/or

2) install SP1 from the standalone, if the WU fails for any reason.

Hello!

Really sorry that I was so late to the party. On every case of the 0x800B0100 error code I have ever worked on, if no errors were detected, it was running the Fix-It in Aggressive Mode which fixed it. The reason lies in the CBS.log. Corrupt .mum or .cat files in winsxs caused errors in CheckSUR. If this was not the case, CBS.log always pointed to corrupt .cat/.mum files in the SoftwareDistribution folder, fixed by running Aggressive Mode of the aformentioned fix, which cleans out this temporary folder.

Sorry I was late,

Richard

NoelDP said:

niemiro said:

On every case of the 0x800B0100 error code I have ever worked on, if no errors were detected, it was running the Fix-It in Aggressive Mode which fixed it. The reason lies in the CBS.log. Corrupt .mum or .cat files in winsxs caused errors in CheckSUR. If this was not the case, CBS.log always pointed to corrupt .cat/.mum files in the SoftwareDistribution folder, fixed by running Aggressive Mode of the aformentioned fix, which cleans out this temporary folder.

Sorry I was late,

Richard

Thanks for the come-back!

In this case, neither SFC nor CheckSUR reported problems, so I was a little at a loss as to how best to approach it - and I really wanted to avoid the inevitable history loss involved in running 50202 in aggressive mode.
Beggars can't be choosers, though. I'm just happy I had a full set of SP1 standalones already on disk - downloading that amount on a dongle can get expensive, especially when the darn thing decides to change IP half-way through!

I also try to avoid deleting the history, one of the reasons why I have abandoned that Fix-It as a first post solution, and moved entirely to running it only when evidence points to a fix (e.g. from a CBS.log). I have tried deleting just portions of the SoftwareDistribution folder to preserve the history, and although I have had some success, it has not yet proven to be reliable. However, I have had more success in attempting to fix corruptions inside the SoftwareDistribution folder, but due to time commitments, and lack of availablilty of scanning tools for that folder, I have not yet made that a service, although I do intend to one day.