Windows 7 won't apply updates.

Here's the errors from the SFC scan...

Code:

	Line 5383: 2015-09-03 18:50:05, Info                  CSI    00000347 [SR] Repairing 2 components
	Line 5384: 2015-09-03 18:50:05, Info                  CSI    00000348 [SR] Beginning Verify and Repair transaction
	Line 5387: 2015-09-03 18:50:05, Info                  CSI    0000034a [SR] Cannot repair member file [l:22{11}]"xmllite.dll" of Microsoft-Windows-ServicingStack, Version = 6.1.7601.18766, 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 5390: 2015-09-03 18:50:05, Info                  CSI    0000034c [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, 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 5393: 2015-09-03 18:50:05, Info                  CSI    0000034e [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, 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

The last two aren't really errors - they are the result of having installed KB3022345 or KB 3068708 and can be ignored.
I'll post a fix protocol for the other error when I can get to it.

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

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

XCOPY <drive>:\ibtaa <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

Ooops! - seems I forgot to insert the necessary file!.
Try it again now.

Sorry about that!

Great - SFC is now clear of significant problems - the others are MS's fault
Now please try CheckSUR again - does it work now?

PLease post the resulting CheckSUR log - that is a fairly long scan time and could indicate some hefty problems.