Solved Windows Update Error 800B0100

[JoshuaW]

Hello!
I've had this problem for a while and since I've misplaced my Windows install disk, I've put off reinstalling Windows, since I've tried every other suggestion I could find so far.

When I try to run Windows Update, I receive the error code 800B0100 - "An error occurred while checking for new updates for your computer". It doesn't seem as though its actually installing anything, but rather that it cannot check for any updates anymore?

I installed SURT and have done a SFC /scannow (it did not find any integrity violations), but neither of these have fixed the issue. The issue seems really similar to the one below, so I am really hopeful that you can help.
http://www.sevenforums.com/windows-...4-installing-sp1-kb976932-error-800b0100.html

Let me know if there is any information you need not provided here.

 

[NoelDP]

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

Unavailable repair files:
 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

I'll post a fix protocol later.

 

[NoelDP]

I've uploaded afile - jawaa.zip - to my OneDrive at Noel's OneDrive

Please downloadand save it.

Right-click onthe downloaded file, and select Extract all…

Extract to thedefault location - which will create a new folder jawaain the same place.

Open this folder- there should be one folder inside it (Packages)



Copy the content of the Packages folder to thefolder

C:\Windows\Temp\CheckSur\Servicing\Packages

Nowrun the CheckSUR tool again (it may take a while)



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

 

[JoshuaW]

Thank so much for your quick response!

It looks like there are still some unavailable repair files?

 

[NoelDP]

You're right -- that's what comes of trying to sneak in a couple of responses while I'm at work!

I'll post a revised protocol soon.

 

[NoelDP]

I've uploaded a file - jawab.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 jawab in the same place.

Open this folder- there should be one folder inside it (Packages)



Copy the content of the Packages folder to the folder

C:\Windows\Temp\CheckSur\Servicing\Packages

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



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

 

[JoshuaW]

Hmm, now it seems that the SURT tool wont run...

I get the error message from the Windows Update Standalone Installer:
"Installer encountered an error: 0x80080005
Server execution failed"

I tried running sfc /scannow again (last time it didn't find any integrity violations) and this time it said

Windows Resource Protection found corrupt files but was unable to fix some of them.
Details are included in the CBS.log.

I've included this log.

 

[NoelDP]

Here's the error list from SFC...

 Line 73286: 2015-06-15 19:39:47, Info                  CSI    0000067b [SR] Beginning Verify and Repair transaction
 Line 73289: 2015-06-15 19:39:47, Info                  CSI    0000067d [SR] Cannot repair member file [l:22{11}]"wuaueng.dll" of Microsoft-Windows-WindowsUpdateClient-Core, Version = 7.6.7600.320, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 73292: 2015-06-15 19:39:47, Info                  CSI    0000067f [SR] Cannot repair member file [l:22{11}]"wuauclt.exe" of Microsoft-Windows-WindowsUpdateClient-Core, Version = 7.6.7600.320, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 73295: 2015-06-15 19:39:47, Info                  CSI    00000681 [SR] Cannot repair member file [l:18{9}]"wups2.dll" of Microsoft-Windows-WindowsUpdateClient-Core, Version = 7.6.7600.320, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 73298: 2015-06-15 19:39:47, Info                  CSI    00000683 [SR] Cannot repair member file [l:22{11}]"wucltux.dll" of Microsoft-Windows-WindowsUpdateClient-UI, Version = 7.6.7600.320, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

- it's no wonder that the WU system is borked!

I'll post another fix protocol later.

 

[JoshuaW]

Yea, it's weird since I ran that just yesterday and it was fine! No integrity violations

 

[NoelDP]

I've uploaded afile - jawac.zip - to my OneDrive at Noel'sOneDrive
Please downloadand save it.

Right-click onthe saved file and select Extract all...
Change the targetto C:\ and click on Extract
Close all windows(it would be a good idea to print these instructions!)

Now reboot to theRepair Environment - as soon as the machine restarts, start tapping F8 - this should bring up the Advanced BootMenu, at the top of which should be the option'Repair my Computer'
Pick that

You'll have tolog in with your username and password.

Pick the optionto use a Command Prompt

At the prompttype

DIR C:\jawac

hit the enter key- if you get a 'Not Found' error try

DIR D:\jawac

or

DIR E:\jawac

The drive letterin use when you find the folder will need to be substituted (for<drive>)into the following command...

XCOPY <drive>:\jawac <drive>:\windows\winsxs /y /i /s /v /h

(e.g. XCOPYP:\wfire P:\windows\winsxs /y /i /s /v /h )

run the command(it should take almost no time) and when the prompt returns, type

EXIT

and hit the Enterkey to exit Command Prompt - reboot to Normal Mode Windows.

Now run SFC /SCANNOW in an Elevated Command Prompt

then reboot andupload the new CBS.log file to your reply

 

[NoelDP]

(the reason it didn't find anything yesterday was because it wasn't looking for those files )

 

[JoshuaW]

Ooook. No integrity violations once again!

 

[NoelDP]

Geat!
Does Windows Update work now? - start with a fresh Check for Updates.

 

[JoshuaW]

Ok it looks... good!

OK Installing update 1 of 120! Woohoo!

I'll let this run today and probably get back to you tonight, but that's awesome! Thank you!

If this works it will have saved me so much time and likely money; thank you, thank you.

Just out of curiosity, was this just a case of corrupt files that you overwrote from some pristine source of yours or did we do something additional? And do you have any idea how these files got that way in the first place?

 

[NoelDP]

The work with CheckSUR was to correct registry errors, and replace missing files with ones from my stock. These files essentially tell Windows what other files should be present, and some of the reelted registry entries required
The SFC work was to replace missing files identified by either CheckSUR or SFC with 'proper' copies, again from my store - I have around 60GB of Windows 7 update files stored away here

 

[JoshuaW]

Awesome. Thanks again for your help.

So, I was able to install most of the updates, but one "Important" update is being stubborn and is still throwing an error.

KB982670 - Microsoft .NET Framework 4 Client Profile for Windows 7 x64-based Systems (41 MB)
This one fails to install and throws a code 643.

I looked around online and tried a few suggestions, uninstalling .NET and trying to reinstall it etc. but without any success with this update. Can you help with this as well or should I start a new thread?

 

[NoelDP]

643 errors in .NET (or anything else, for that matter!) are a pain.
For your case, there may be a simple solution.

Run the .NET cleanup tool from here .NET Framework Cleanup Tool User's Guide - Aaron Stebner's WebLog - Site Home - MSDN Blogs (read the instructions first)
then install the latest version offered by Windows Update after a couple of reboots, and a new Check for updates.

 

[JoshuaW]

After some time looking at the logs I discovered the following error:
"Crypt Provider not initialized."

This led me to the following thread where others are having the same issue:
https://social.msdn.microsoft.com/F...ies-to-40-45-and-all-updates?forum=netfxsetup

Turns out that the solution is to uninstall KB2918614, KB3000988 and KB3008627 first. THEN install everything to do with .NET (security updates etc.), and THEN reinstall those three updates. I'm not sure why this works, but it worked for me, and hopefully it will work for others

So happy with my Windows Update now! :-D

Thanks again for all your help!

 

[NoelDP]

Well done! - nice find, especially as it's not one I'd probably have found easily.
Thanks for posting your solution - and good luck!