Solved Windows Update Failing KB2937610 with Error Code 800B0100

[Kyle89]

I recently put together my first custom build and I am running into a very frustrating issue with the "Security Update for Microsoft .NET Framework 3.5.1 on Windows 7 and Windows Server 2008 R2 SP1 for x64-based Systems (KB2937610)".

Error Code: 800B0100

Normally I'm the kind of person that likes to figure things like this out on my own using Google and reading over old posts in forums like this, however I have exhausted my resources as well as my patience..

Here is what I've tried (in no specific order):

• Reformat SSD, reinstall Windows 7, installing updates immediately after.
• Ran sfc /scannow, it didn't find anything wrong.
• Ran MS Fixit, tried installing update with no luck, restarted, tried agian (did this twice)
• Ran Windows Update Readiness Tool, tried installing update with no luck, restarted, tried again (twice)
• Went to control panel > Programs and Features > Repaired .NET framework 4.5.1, didn't help
• Uninstalled .Net Framework 4.5.1 and let windows update reinstall it, didn't help
• Used the Microsoft .NET repair tool, didn't help
• Used d7 (tech tool, I work at a pc repair shop) to repair Windows Update
• Did a clean boot using msconfig method
• CHKDSK found no problems
• I even manually downloaded the update from MS and ran the installer. It ended with "Some updates were not installed", and listed the update as not installed.

Windows is installed on the Samsung EVO 840 SSD.
(I'm hoping my hardware shows up in my signature or something otherwise I'll edit/reply with a full list)

Since the list is so short, here is a list of my installed programs:

• Intel Network Connections 18.x.x.x
• Intel Graphics Driver
• Intel USB 3.0 eXtensible Host Controller Driver
• Java 8 Update 25
• marvell 91xx driver
• Microsoft .NET Framework 4.5.1
• Realtek High Definition Audio Driver

The CBS log file was too big to attach (28.5mb), so I uploaded it to my web server and you can access the zip file here: http://www.hujigy.com/log/CBS.zip

Also, I don't know if it is worth noting, or not, but every time I shut down it attempts to install the update and fails before shutting down.

To anyone willing to help, THANK YOU!!!! You have no idea (or maybe you do, if so I feel your pain) how crazy this problem is driving me. I just want to play with my new toy

 

[NoelDP]

Shouldn't be too difficult
Here's the errors from CheckSUR...

Unavailable repair files:
 servicing\packages\Package_10_for_KB2937610~31bf3856ad364e35~amd64~~6.1.1.3.mum
 servicing\packages\Package_10_for_KB2937610~31bf3856ad364e35~amd64~~6.1.1.3.mum
 servicing\packages\Package_1_for_KB2937610~31bf3856ad364e35~amd64~~6.1.1.3.mum
 servicing\packages\Package_1_for_KB2937610~31bf3856ad364e35~amd64~~6.1.1.3.mum
 servicing\packages\Package_2_for_KB2937610~31bf3856ad364e35~amd64~~6.1.1.3.mum
 servicing\packages\Package_2_for_KB2937610~31bf3856ad364e35~amd64~~6.1.1.3.mum
 servicing\packages\Package_3_for_KB2937610~31bf3856ad364e35~amd64~~6.1.1.3.mum
 servicing\packages\Package_3_for_KB2937610~31bf3856ad364e35~amd64~~6.1.1.3.mum
 servicing\packages\Package_4_for_KB2937610~31bf3856ad364e35~amd64~~6.1.1.3.mum
 servicing\packages\Package_4_for_KB2937610~31bf3856ad364e35~amd64~~6.1.1.3.mum
 servicing\packages\Package_56_for_KB2937610~31bf3856ad364e35~amd64~~6.1.1.3.mum
 servicing\packages\Package_56_for_KB2937610~31bf3856ad364e35~amd64~~6.1.1.3.mum
 servicing\packages\Package_5_for_KB2937610~31bf3856ad364e35~amd64~~6.1.1.3.mum
 servicing\packages\Package_5_for_KB2937610~31bf3856ad364e35~amd64~~6.1.1.3.mum
 servicing\packages\Package_9_for_KB2937610~31bf3856ad364e35~amd64~~6.1.1.3.mum
 servicing\packages\Package_9_for_KB2937610~31bf3856ad364e35~amd64~~6.1.1.3.mum
 servicing\packages\Package_for_KB2937610_SP1~31bf3856ad364e35~amd64~~6.1.1.3.mum
 servicing\packages\Package_for_KB2937610_SP1~31bf3856ad364e35~amd64~~6.1.1.3.mum
 servicing\packages\Package_for_KB2937610~31bf3856ad364e35~amd64~~6.1.1.3.mum
 servicing\packages\Package_for_KB2937610~31bf3856ad364e35~amd64~~6.1.1.3.mum

I'll post a fix protocol soon.

 

[NoelDP]

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

 

[Kyle89]

First off, thank you for your assistance Noel.

I followed your directions, and here are the log files requested!

( Smack me in the back of the head for this, but I cancelled the tool installation by mistake and had to restart it, so if anything funky is in the logs that's why )

CheckSUR.log

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2014-12-07 10:23

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store

Summary:
Seconds executed: 70
 No errors detected

CheckSUR.persist.log had to be attached due to size.

 

[Kyle89]

Okay, so for the heck of it I had Windows Update attempt to install the update again, and it appears to have been successful. The progress bar wasn't moving so I minimized assuming it would fail, but it popped up saying it was successfully installed! Restarted the PC and moved on to a new round of updates for .NET framework 4.5.1. After the PC restarted from these fresh updates I checked for more updates and it seems I am finally running an up-to-date version of Windows 7!

Thank you SO MUCH Noel! What a huge relief, some day I'll pay it forward.

Cheers!

 

[NoelDP]

Hehe... it's easy when you know how

Glad it worked for you.

Good luck.

 

[Kyle89]

What exactly happened that caused that?

It would be great to learn what I can in case this happens in the future or so I can help anyone I know that might encounter the problem

 

[NoelDP]

Difficult to be sure what causes it - but I suspect that in this case there was a power-loss partway through the install that led to the siles not being properly placed, and the backout safety procedures not working.