Solved Win 7 SP1 fails with 800B0100 error

[NoelDP]

Tosh L450D - Win 7 Home Premium

All other updates for Windows and Office install without problems.
SP1 fails with 800B0100 error
CheckSUR tool passes with no errors in log.
SFC - no problems found

Potential screwup factors
1) Machine is two years old - but still had the original trial of McAfee installed, which hadn't ever been activated! Ripped that out, ran MCPR, installed MSE. Surprisingly, no significant malware found.
2) no malware scans ever run on the machine - Malwarebytes installed, running full system scan as I write this.

otherwise, it seems like the machine just came out of the box!

Once the malware scan is finished, I intend to try a standalone SP1 install and see how that works.

Any suggestions gratefully received

 

[JMH]

Hello Noel,
Generic steps to take before installing Windows 7 Service Pack 1.

* How to increase your chances of installing Service Pack 1 successfully.
Steps to follow before you install Windows 7 Service Pack 1 from the Microsoft Download Center

* Update your device drivers to the most recent Windows 7 device drivers from your computer manufacture's support web site (for your specific make and model)

* Start by installing the chipset/motherboard driver followed by the remaining available drivers.

* Run the SFC /SCANNOW command. This will check and repair if necessary any critical Windows system files.
Click on Start/All programs/Accessories then
Right click on Command Prompt option and select 'Run as administrator'.
At the command prompt enter: SFC /SCANNOW

*AGAIN > Run the System Update Readiness Tool:
Description of the System Update Readiness Tool for Windows Vista, for Windows Server 2008, for Windows 7, and for Windows Server 2008 R2

* Windows 7 - Service Pack 1 – How to install Step by Step
Steps to follow before you install Windows 7 Service Pack 1 from the Microsoft Download Center

* Learn how to install Win 7 SP1
Learn how to install Windows 7 Service Pack 1 (SP1)

* Win7 SP1: Installation tips
Windows 7 SP1 Follow-up

* FYI -
Windows Update error 800B0100

Error code 0x800B0100 when using Windows Update or Microsoft Update to install updates

Clean Install Windows 7

Repair Install

Good luck & let us know how you go please.

 

[NoelDP]

Thanks, JMH - already covered most of that, and read a good few supposed solutions to the error message, none of which have yet worked.
I'm just going to finish installing all the other Important updates (Office mostly) before I attempt SP1 again from WU.
Then I'll get some sleep before trying to install SP1 from the standalone.

 

[JMH]

Fingers crossed.
Most of us don't have any issues...

 

[NoelDP]

Heh! - I know!
Funny thing is that this is the second machine in two days with an Updates issue - the other one is a 643 error with a .NET update (also with a clean SFC and CheckSur), that I've palmed off on MS WU Support , on the basis that they need a kicking to get the .NET thing right once and for all.

 

[NoelDP]

OK _ a little progress, perhaps.

1) I noticed that a VC++ 2005 install wasn't working either, so tried IE9 and got a 9c47 error
2) tried the WU reset fixit 50123 - no dice
3) tried the other relevant fixit (50202) in normal mode - no dice
4) used 50202 in Aggressive mode - the VC++ update installed
Now downloading the SP1 again - I'll leave that overnight (it's 2a.m. for the second time tonight )

 

[JMH]

Sleep well...

 

[Vandalus]

Having exactly the same issue as this guy. Currently trying out the Scannow method but tried most of the above bar the re-install. Not an option as I'm currently using this PC for Uni. Dpn't have the time to mess around and re-install on a whim like I used to.

Any other suggestions would be great.

Edit: also forgot to say I'm currently downloading the update to try manually installing it.

Scan didn't find anything, now to wait for the download to finish.

These are the four updates that keep failing on me.

 

[JMH]

http://www.sevenforums.com/member.php?u=182756Vandalus
You are best advised to start your own thread rather than tacking onto another.
That way you will get individual help.

Thank you.

 

[NoelDP]

Urrgghh!
Download of SP1 via WU bombed out at 63%, and refused to restart after a reboot or the usual Try Agains.

Now installing vias the standalone.
WIll report back with progess.

@Vandalus
Have you run CheckSUR yet? what errors are you getting with any other WU's?
Use Fixit 50123,reboot, then fixit 50202 in normal mode, reboot, and then 50202 again in Aggressive Mode - this will clear your Update History (but not the INstalled Updates listing). See if that helps.

 

[Vandalus]

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

 

[NoelDP]

Success!
SP1 is now installed
Hopefully the updates will follow OK.
(That was one of the longest install times I've seen for SP1 - 90 minutes!. TrustedInstaller peaked at 634MB, and the first reboot produced 115552 updates)

I'll get the rest of the updates in (please?), and then defrag the machine for the first time ever

 

[NoelDP]

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.

 

[JMH]

Well done to you!
Safe surfing.

 

[NoelDP]

Heh! - it's not even my PC
Any sensible person would have flattened and rebuilt it - but I haven't been called sensible for a loooong time!

 

[niemiro]

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]

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!

 

[niemiro]

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.