Windows can not check for updates error code 800B0100

[Funda]

Installed Win7 yesterday and installed some drivers for it, when I went to look for updates for win7 it came up with that error code, Ive also tried doing what Microsofts website advices to do and that did not help. I also called Microsofts technicians and they weren't able to solve the problem. Im hoping you guys are able to give me a solution.

 

[NoelDP]

Please follow the Windows Update Posting Instructions and post the requested data
If the file is too large (8MB compressed), remove the older CBSPersist cab files until the final file is below the limit - you can always post them separately after zipping them. (the forum doesn't allow the upload of bare CAB files, for a number of reasons)

 

[Funda]

Just did it now, sorry, when I posted it I wasn't home.

 

[NoelDP]

That makes more sense now
CheckSUR shows the following problems...

Unavailable repair files:
 winsxs\manifests\amd64_microsoft-windows-w..lient-aux.resources_31bf3856ad364e35_7.6.7600.320_en-us_d5981a6600d138cc.manifest
 winsxs\manifests\wow64_microsoft-windows-w..lient-aux.resources_31bf3856ad364e35_7.6.7600.320_en-us_dfecc4b83531fac7.manifest
 winsxs\manifests\amd64_microsoft-windows-w..owsupdateclient-aux_31bf3856ad364e35_7.6.7600.320_none_bc07877c65502903.manifest
 winsxs\manifests\wow64_microsoft-windows-w..owsupdateclient-aux_31bf3856ad364e35_7.6.7600.320_none_c65c31ce99b0eafe.manifest
 servicing\packages\WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~amd64~en-US~7.6.7600.320.mum
 servicing\packages\WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~amd64~en-US~7.6.7600.320.mum
 servicing\packages\WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~amd64~~7.6.7600.320.mum
 servicing\packages\WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~amd64~~7.6.7600.320.mum
 servicing\packages\WUClient-SelfUpdate-Aux-MiniLP~31bf3856ad364e35~amd64~en-US~7.6.7600.320.mum
 servicing\packages\WUClient-SelfUpdate-Aux-MiniLP~31bf3856ad364e35~amd64~en-US~7.6.7600.320.mum
 servicing\packages\WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320.mum
 servicing\packages\WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320.mum
 servicing\packages\WUClient-SelfUpdate-Aux~31bf3856ad364e35~amd64~en-US~7.6.7600.320.mum
 servicing\packages\WUClient-SelfUpdate-Aux~31bf3856ad364e35~amd64~en-US~7.6.7600.320.mum
 servicing\packages\WUClient-SelfUpdate-Aux~31bf3856ad364e35~amd64~~7.6.7600.320.mum
 servicing\packages\WUClient-SelfUpdate-Aux~31bf3856ad364e35~amd64~~7.6.7600.320.mum
 servicing\packages\WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~amd64~en-US~7.6.7600.320.cat
 servicing\packages\WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~amd64~en-US~7.6.7600.320.cat
 servicing\packages\WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~amd64~~7.6.7600.320.cat
 servicing\packages\WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~amd64~~7.6.7600.320.cat
 servicing\packages\WUClient-SelfUpdate-Aux-MiniLP~31bf3856ad364e35~amd64~en-US~7.6.7600.320.cat
 servicing\packages\WUClient-SelfUpdate-Aux-MiniLP~31bf3856ad364e35~amd64~en-US~7.6.7600.320.cat
 servicing\packages\WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320.cat
 servicing\packages\WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320.cat
 servicing\packages\WUClient-SelfUpdate-Aux~31bf3856ad364e35~amd64~en-US~7.6.7600.320.cat
 servicing\packages\WUClient-SelfUpdate-Aux~31bf3856ad364e35~amd64~en-US~7.6.7600.320.cat
 servicing\packages\WUClient-SelfUpdate-Aux~31bf3856ad364e35~amd64~~7.6.7600.320.cat
 servicing\packages\WUClient-SelfUpdate-Aux~31bf3856ad364e35~amd64~~7.6.7600.320.cat

These are all from the update for the Windows Update Agent - and could well explain your problems.

Having said that, your SFC results are a little unusual. Most results have at least 126 'POQ's - your first run only have 115, whicle the second doesn't appear to have completed before you made the copy. Neither run found any significant problems, although there are a lot of problems from the same errors that CheckSUR found.

I'll post a fix protocol for the CheckSUR errors shortly

 

[Funda]

Well the first run may have been from last night, did it today but i got a bsod while it was scanning. been having bsod a lot as well I can run it again for you if you wish.

 

[NoelDP]

I've uploaded a file - fdaaa.zip - to my OneDrive at Noel's OneDrive
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 fdaaa 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.

 

[Funda]

I tried doing it and got a bsod, so i went in safe mode with command promt and did it then. I hope that works as well.

 

[Funda]

Sorry did the wrong thing, ignore the above

 

[Funda]

Ok Noel, Look at this one.

 

[NoelDP]

Great - CheckSUR is happy now.
Do a new Check for UPdates, and attempt to install ONLY the oldest update found. If it fails, post the KB number and errorcode.
Of it goes OK, install remaining updates in batches of 5 or so (expect a couple of failures as the order in the list isn't the same as the needed install order)

 

[Funda]

Great - CheckSUR is happy now.
Do a new Check for UPdates, and attempt to install ONLY the oldest update found. If it fails, post the KB number and errorcode.
Of it goes OK, install remaining updates in batches of 5 or so (expect a couple of failures as the order in the list isn't the same as the needed install order)

Noel, I'm not sure which updates to download, here's a picture, you tell me.

 

[Funda]

Another fail

 

[NoelDP]

That surprises me - the indication is that there are still problems that CheckSUR should be seeing.

I think resetting the SoftwareDownload folder should fix that...


Open an Elevated Command Prompt
Run the following commands

NET STOP WUAUSERV
REN C:\WINDOWS\SoftwareDistribution SDOLD
NET START WUAUSERV

reboot
then wait 10 minutes, and open Windows Updates, and run a Check for Updates.

Install only the oldest update found - and reboot once installed
then go back to Windows updates and install the others.

 

[Funda]

Ok so, I went into the 100+ updates and only checked the 2013 ones, which were 35 of them. Its currently doing that with no problem, taking forever but its going. Im at update 11. Should I stop and do what you just said or do it after?

 

[NoelDP]

No - wait until it's finished, and then try the others.
Once all the updates that can be installed have gone in, post the list of failing updates, and the error code associated with the oldest.

Reboot after each batch of updates and run another Check for Updates before attempting the new installs

 

[Funda]

Noel, Just finished downloading the 35 updates I told you about and it successfully installed 32 and failed 6. Have a look.

 

[Funda]

I input the commands you told me to and still no luck

 

[NoelDP]

OK - run SFC and CheckSUR again, and post the new CBS folder.

 

[Funda]

Noel, I'm doing that now. By the way, I installed the other updates and they're just 16 failed updates left to download and install.

 

[Funda]

It's been like an hour and CheckSUR has not finished, shall I retry?