win 7 64 bit error code 800b0100

[marcencar]

i have been getting this error consistently. There was another error i was getting but it seemed to not show up. But the error code 800b0100 has never gone away and it is really annoying. I am a noob at this stuff so bear with me through the process.

I also have gone through alot of the steps others on forums suggested, with negative results. Help would be appreciated.

Thank you for the assistance.

 

[Anak]

Hi marcencar, welcome to 7F!

The error points to running the System Update Readiness Tool (SURT):
Windows Update error 800B0100

That would of been step #1 here: http://www.sevenforums.com/windows-...4840-windows-update-posting-instructions.html we will need to see a log of that also.

If you've already ran it just find it and upload it like you did with the CBS file

The System Update Readiness Tool creates a log file that captures any issues that the tool found or fixed. The log file is located here:

• %SYSTEMROOT%\Logs\CBS\CheckSUR.log
• %SYSTEMROOT%\Logs\CBS\CheckSUR.persist.log

Source: System Update Readiness Tool fixes Windows Update errors in Windows 7, Windows Vista, Windows Server 2008 R2, and Windows Server 2008

 

[marcencar]

sorry, I thought i had it in the original attachment. Guess it was one of the things i deleted since i was going over the allotted mb for upload. Hope this is everything. thanks again for the assistance.

 

[Anak]

Not a problem it happens, it shows some unrepairable files, but that doesn't mean they can't be. I'm going to call in for help.

 

[marcencar]

Great thank you!

 

[Anak]

Hang in there, I've asked NoelDP if he could take a look at your logs.

Have you tried running: http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html? Use Option Two.

This Note box is after step4 Option Two

   Note

• If SFC could not fix something, then run the command again to see if it may be able to the next time. Sometimes it may take running the sfc /scannow command 3 or more times to completely fix everything that it's able to.
• If not, then download and run the 32-bit (x86) or 64-bit (x64) System Update Readiness Tool for your same installed 32-bit or 64-bit Windows 7, restart the PC afterwards, and try the sfc /scannow command again.
• If still not, then you can attempt to run a System Restore using a restore point dated before the bad file occured to fix it. You may need to repeat doing a System Restore until you find a older restore point that may work.
• If still not, then you can use the steps in the TIP box in the OPTION THREE section below to manually replace the files that SFC could not fix.

You've already done the SURT tool so try the SFC scan and run it at least twice with reboots in between, hopefully we don't have to do steps 3 & 4.

 

[marcencar]

ok tried sfc/scannow still did not work. will try the other steps after i grab some sleep. just got back from work. thanks again for the help

 

[Anak]

Noel and the other members must be busy elsewhere it usually doesn't take this long to receive a response from them, could be the holiday too.

One question I forgot to ask, Do you get the 800B0100 error when you install all updates or is it peculiar to just one or several?

Before you go on to the next two steps in the Note Box you may want to try these if you haven't already.

There was this Automatic Troubleshooter | Diagnostics Troubleshooting Wizard on the SURT page at my first link. It is a direct download so you may want to save it to your Desktop and then run it.

http://www.sevenforums.com/tutorials/91738-windows-update-reset.html

Fix the problem with Microsoft Windows Update that is not working

 

[NoelDP]

's OK - I'm back online now (My ICS Machine's PSU died )

Here's the error list from the CheckSUR log...

Unavailable repair files:
 winsxs\manifests\msil_system.security.resources_b03f5f7f11d50a3a_6.1.7601.22250_en-us_3d79652f40f525e9.manifest
 winsxs\manifests\msil_system.security.resources_b03f5f7f11d50a3a_6.1.7601.18077_en-us_54486d2f274caba7.manifest
 servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum
 servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum
 servicing\packages\Package_1_for_KB2804579~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_1_for_KB2804579~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_1_for_KB2839894~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_1_for_KB2839894~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_2_for_KB2804579~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_2_for_KB2804579~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_2_for_KB2839894~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_2_for_KB2839894~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_4_for_KB2804579~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_4_for_KB2804579~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2804579_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2804579_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2804579~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2804579~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2839894_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2839894_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2839894~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2839894~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.cat
 servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.cat
 servicing\packages\Package_1_for_KB2804579~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_1_for_KB2804579~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_1_for_KB2839894~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_1_for_KB2839894~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_2_for_KB2804579~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_2_for_KB2804579~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_2_for_KB2839894~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_2_for_KB2839894~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_4_for_KB2804579~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_4_for_KB2804579~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2804579_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2804579_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2804579~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2804579~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2839894_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2839894_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2839894~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2839894~31bf3856ad364e35~amd64~~6.1.1.0.cat

(it's not as bad as it looks!)
I'll post a fix protocol for it a little later.

 

[Anak]

Thank you Noel,

If I'm reading it right there's two KB's that are having problems on two levels, one before and one after the win 7 SP1 install. Would that be caused by a difficult SP1 install, for whatever reason?

marcencar; I should have asked you earlier about your System Specs , Do you have SP1 installed?

 

[NoelDP]

I've uploaded a file - mccaa.zip - to my SkyDrive at Noel's SkyDrive
Please download and save it.
Right-click on the downloaded file, and select Extract all…
Extract to the default location - which will create a new folder mccaa in the same place.
Open this folder - there should be two folders inside it (Manifests, and Packages)

Copy the content of the Packages folder to the folder
C:\Windows\Temp\CheckSur\Servicing\Packages

And the content of the manifests folder (.manifest files) into this folder:

C:\Windows\Temp\CheckSur\Winsxs\Manifests

Now run the CheckSUR tool again (it may take a while)

Post the new CheckSUR.log file, and the CheckSUR.persist.log file.

Anak
All Windows patches include data for all SP levels below their design install, as well, so that they can cope with system down-dates if necessary - That's why you see cat/mum files with SP1 and possibly RTM as well as the default. (If the RTM entry is missing, I believe the update is uninstalled as well, if you uninstall SP1). This avoids the dll-hell that we used to get with updates in Win9x and early NT/XP

 

[Anak]

Noel,

In case marcencar has any questions:

• marcencar can save the mccaa.zip file to his Desktop, and that becomes his default location. Correct?
• Then he extracts to the desktop/default location.
• Then copies the two files to their respective locations.

Thank you for the clarification on avoiding .dll-hell. I'm having a bit of trouble with my updates, but that's for another time, and a new thread.

Now its up to marcencar.

   Warning

Never, under any circumstances, follow the instructions posted to another user who appears to be having the same problem as you (unless specifically instructed to). Windows Update problems are very computer specific and following instructions made to another user will probably do more harm than good.

Source: http://www.sevenforums.com/windows-...4840-windows-update-posting-instructions.html

 

[marcencar]

sorry work has been crazy. i will be working on the fix.

 

[Anak]

All good things take time....

 

[marcencar]

ok here are the logs.

 

[marcencar]

looks like it worked. thanks guys for the help!!!

 

[NoelDP]

Great - the remaining errors in the CheckSUR log are normal for a system with IE10 installed, and can be ignored.

Good luck!

 

[Anak]

Give it a little time, your SUR log still shows a couple of errors, hopefully Noel will see this and know if they can be ignored or not?

Summary:
Seconds executed: 478
 Found 13 errors
 Fixed 11 errors
  CSI Manifest All Zeros Total count: 2
  Fixed: CSI Manifest All Zeros.  Total count: 2
  CBS MUM Corrupt Total count: 11
  Fixed: CBS MUM Corrupt.  Total count: 9
  Fixed: CBS Paired File.  Total count: 9

Unavailable repair files:
    servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum
    servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.mum
    servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.cat
    servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~10.2.9200.16437.cat

Did you run at least one SFC scan after you ran the SURT tool? See note in my #6 post.
I've gotten in the habit of running at least two SFC scans with re-starts after each when I'm doing machine maintenance, even if the first one showed no integrity violations.

When you're sure the SFC's are good, try checking for Updates, any errors? Errors or not, we'll need to see a new set of CBS and CheckSUR logs.


EDIT:

I see you beat me to it, Thanks Noel!