Solved Update KB2961072 failed error code 800B0100

[tonymaloney]

Hi guys.

Thanks in advance

Legit copy of windows.

Removed 4 .cab's to get under 8megs.

Scannow clean.

 

[NoelDP]

Here's the error-lit from the CheckSUR scan

Unavailable repair files:
 winsxs\manifests\amd64_microsoft-windows-winsock-core_31bf3856ad364e35_6.1.7601.18489_none_35c7815175410855.manifest
 winsxs\manifests\amd64_microsoft-windows-winsock-core_31bf3856ad364e35_6.1.7601.22705_none_36a3a0208e215d89.manifest
 servicing\packages\Package_2_for_KB2961072~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_2_for_KB2961072~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_for_KB2961072_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_for_KB2961072_SP1~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_for_KB2961072~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_for_KB2961072~31bf3856ad364e35~amd64~~6.1.1.1.mum
 servicing\packages\Package_2_for_KB2961072~31bf3856ad364e35~amd64~~6.1.1.1.cat
 servicing\packages\Package_2_for_KB2961072~31bf3856ad364e35~amd64~~6.1.1.1.cat
 servicing\packages\Package_for_KB2961072_SP1~31bf3856ad364e35~amd64~~6.1.1.1.cat
 servicing\packages\Package_for_KB2961072_SP1~31bf3856ad364e35~amd64~~6.1.1.1.cat
 servicing\packages\Package_for_KB2961072~31bf3856ad364e35~amd64~~6.1.1.1.cat
 servicing\packages\Package_for_KB2961072~31bf3856ad364e35~amd64~~6.1.1.1.cat

I'll post a fix protocol later.

 

[tonymaloney]

thankyou, sir.

what is the cause of this? or does it belong in the s**t happens file?

 

[NoelDP]

It looks as if something interrupted the installation of the one update - kb2961072 - possibly power failure? The folder entries are there - but the files are empty.


I've uploaded a file - tmyaa.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 tmyaa 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.

 

[tonymaloney]

there have been a couple of power failures in the last month so could be that.

 

[NoelDP]

Great! CheckSUR has fixed the problems it originally found.

If we're lucky, Windows Update should function properly now - first do a new Check for Updates and see what it finds, then attempt to install only the oldest update found
If it fails, post the KB number, and the error-code that it produced.

 

[tonymaloney]

unfortunately the exact same.

KB2961072 / 800B0100

 

[tonymaloney]

that is the only update pending. others since that one have gone through fine.

 

[NoelDP]

OK - please post the new CBS.log file, and also the C:\Windows\windowsupdate.log file

 

[tonymaloney]

that is the only update pending. others since that one have gone through fine.

 

[tonymaloney]

The CBS.log is over 7 megs and I cant attach it. Do you care where I upload it?

 

[NoelDP]

If you zip it, it should come down to reasonable size (90% compression isn't unusual)
If it's that size compressed, upload it preferably to Dropbox or OneDrive and post a link.

 

[tonymaloney]

forgot to unzip, ran out of ram in my head

thanks again

 

[NoelDP]

Looks like the problem file is this one...

Package_for_KB2961072

I'll post a fix protocol later to replace both the affected file and its companion file, and we'll see whether that works

 

[tonymaloney]

thanks again

 

[NoelDP]

I've uploaded a file - tymaa.zip - to my OneDrive at Noel's OneDrive
Please download and save it.

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

Now reboot to the Repair Environment - as soon as the machine restarts, start tapping F8 - this should bring up the Advanced Boot Menu, at the top of which should be the option 'Repair my Computer'
Pick that
You'll have to log in with your username and password.

Pick the option to use a Command Prompt
At the prompt type
DIR C:\tymaa
hit the enter key - if you get a 'Not Found' error try
DIR D:\tymaa
or
DIR E:\tymaa



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



XCOPY <drive>:\tymaa <drive>:\windows\servicing\Packages /y /i /s /v /h



(e.g. XCOPY P:\wfire P:\windows\servicing\Packages /y /i /s /v /h )



run the command (it should take almost no time) and when the prompt returns, type
EXIT
and hit the Enter key to exit Command Prompt - reboot to Normal Mode Windows.

Now run SFC /SCANNOW in an Elevated Command Prompt
then reboot and upload the new CBS.log file to your reply

 

[tonymaloney]

sfc was clear.

not sure if i was suppose to but i tried the update and it failed again.

cheers

 

[NoelDP]

That's sorta expected At least we've cleared the error I wanted to clear.

Now please open an Elevated Command Prompt and 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.

Your Update History will have cleared - but all updates are still installed, and listed in the Installed Updates listing.

 

[tonymaloney]

took a few minutes to check for update.

then a new fail.

8024200D

 

[NoelDP]

Which update was that for? - try downloading the update from the MS Download Centre - search on the KB number Microsoft Download Center