Windows update issues, CBS.log attached

Windows 7 pro and it won't update. So I saw other threads about this on this forum and it seems to be a corruption but I am stumped on how to fix it.

I've tried system update readiness tool and re-running SP1 installation but no success.

You have a number of problems - not least some fairly widespread file corruption.
We really need the SFC scan, but I suspect that your best option is going to be a repair install.
I've never seen this type of error before, in a CheckSUR report...

Code:

(f) CBS Registry Error 0x800700EA   failed enumerating child package, index: 0
(f) CBS Registry Error 0x8007000D   failed enumerating child package, index: 1
(f) CBS Registry Error 0x800703E6   failed enumerating child package, index: 2
(f) CBS Registry Error 0x8007000D   failed enumerating child package, index: 3
(f) CBS Registry Error 0x800700EA   failed enumerating child package, index: 4
(f) CBS Registry Error 0x800705AA   failed enumerating child package, index: 5
(f) CBS Registry Error 0x800705AA   failed enumerating child package, index: 6
(f) CBS Registry Error 0x800700EA   failed enumerating child package, index: 7

I'm going to ask around to find out if anyone else knows anything about them -
please run SFC /SCANNOW and post the resulting CBS.log file (you'll have to copy it to the desktop first, and zip the copy for upload)

Issues installing Win 7 SP1, CSI payload files missing
[SOLVED] Windows update fails to install KB2809289 with error 80073712 - Sysnative Forums (user solves it in this post but not sure how to apply that to my log file readings)

I worked through methods 1-8 advised by MS here (method 5 didn't happen because I couldn't find HKEY_LOCAL_MACHINE\COMPONENTS). Now about to retry an install of SP1.

Your first link has very different errors to the ones you're experiencing, and although the SFCFix tool they may have used in the second has evolved a lot in the past year, I don't think it deals with this type of problem. I've brought the errors to the attention of the tool's team, so hopefully I'll get some good advice from them.

As for the Payload file error that you have, CheckSUR only does a partial scan of the system, and SFC often picks up more errors (and give more detail on them anyhow)

Oddly, in this case, it only picks up one error.

Code:

 Line 110088: 2014-09-07 18:49:39, Info                  CSI    000003df [SR] Repairing 1 components
 Line 110089: 2014-09-07 18:49:39, Info                  CSI    000003e0 [SR] Beginning Verify and Repair transaction
 Line 110092: 2014-09-07 18:49:39, Info                  CSI    000003e2 [SR] Cannot repair member file [l:24{12}]"usbvideo.inf" of usbvideo.inf, Version = 6.1.7600.16543, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 110095: 2014-09-07 18:49:39, Info                  CSI    000003e4 [SR] Cannot repair member file [l:24{12}]"usbvideo.inf" of usbvideo.inf, Version = 6.1.7600.16543, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 110096: 2014-09-07 18:49:39, Info                  CSI    000003e5 [SR] This component was referenced by [l:150{75}]"Package_2_for_KB979538~31bf3856ad364e35~amd64~~6.1.1.0.979538-4_neutral_GDR"
 Line 110101: 2014-09-07 18:49:39, Info                  CSI    000003e7 [SR] Repair complete

This makes me suspect that the CheckSUR Payload results are false-positives - possibly a result of the registry failures.

There is NO POINT in attempting SP1 again - it will continue to fail until we have corrected both CheckSUR and SFC errors, or done a repair install.

I need to have a look at your COMPONENTS registry hive

Please copy the C:\Windows\System32\config\COMPONENTS file (no extension) to your desktop and then compress it - upload the compressed file to your favoured fileshare site (preferably Dropbox or OneDrive) and post a link.

uploaded here

I asked for the COMPONENTS file (no extension) - you've uploaded a COMPONENTS.OLD2 file, which is no use to man or beast unless you renamed it specially for some reason.
How come you have such a file anyhow?
What happened to the original COMPONENTS file?

Ah - then the proper way to do it would have been to boot to Safe Mode and copy it there.
I can't see anything drastically wrong in it - but it's late now.
I'll have a closer look tomorrow.