Windows 7 update error code 800B0100

Good - the errors which CheckSUR can fix are now gone.
We need to address the others at this point.
Please run another SFC /SCANNOW, and post the new CBS.log file.

I get 'invalid attachment'?

Great - the SFC scan shows these errors...

Code:

 Line 3555: 2015-03-25 06:53:58, Info                  CSI    00000325 [SR] Repairing 1 components
 Line 3556: 2015-03-25 06:53:58, Info                  CSI    00000326 [SR] Beginning Verify and Repair transaction
 Line 3557: 2015-03-25 06:53:58, Info                  CSI    00000327 [SR] Cannot repair member file [l:104{52}]"_DataOracleClientPerfCounters_shared12_neutral_D.ini" of Microsoft-Windows-NETFXCoreComp.Resources, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-us", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
 Line 3558: 2015-03-25 06:53:58, Info                  CSI    00000328 [SR] Cannot repair member file [l:80{40}]"_dataperfcounters_shared12_neutral_D.ini" of Microsoft-Windows-NETFXCoreComp.Resources, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-us", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing
 Line 3559: 2015-03-25 06:53:58, Info                  CSI    00000329 [SR] Cannot repair member file [l:58{29}]"_Networkingperfcounters_D.ini" of Microsoft-Windows-NETFXCoreComp.Resources, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-us", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file is missing

This correlates nicely with the ones found by CheckSUR...

Code:

Checking Component Store
(f) CSI Payload File Missing 0x00000000 _DataOracleClientPerfCounters_shared12_neutral_D.ini amd64_microsoft-windows-n..xcorecomp.resources_31bf3856ad364e35_6.1.7601.17514_en-us_61a8bbbea8eff9bd 
(f) CSI Payload File Missing 0x00000000 _dataperfcounters_shared12_neutral_D.ini amd64_microsoft-windows-n..xcorecomp.resources_31bf3856ad364e35_6.1.7601.17514_en-us_61a8bbbea8eff9bd 
(f) CSI Payload File Missing 0x00000000 _Networkingperfcounters_D.ini amd64_microsoft-windows-n..xcorecomp.resources_31bf3856ad364e35_6.1.7601.17514_en-us_61a8bbbea8eff9bd 
(f) CSI Payload File Missing 0x00000000 _DataOracleClientPerfCounters_shared12_neutral_D.ini amd64_microsoft-windows-n..xcorecomp.resources_31bf3856ad364e35_6.1.7600.16385_en-us_5f77a7f6ac017623 
(f) CSI Payload File Missing 0x00000000 _dataperfcounters_shared12_neutral_D.ini amd64_microsoft-windows-n..xcorecomp.resources_31bf3856ad364e35_6.1.7600.16385_en-us_5f77a7f6ac017623 
(f) CSI Payload File Missing 0x00000000 _Networkingperfcounters_D.ini amd64_microsoft-windows-n..xcorecomp.resources_31bf3856ad364e35_6.1.7600.16385_en-us_5f77a7f6ac017623

I'll post a fix protocol later.

I've uploaded a file - tnoab.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:\tnoab
hit the enter key - if you get a 'Not Found' error try
DIR D:\tnoab
or
DIR E:\tnoab



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



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



(e.g. XCOPY P:\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 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