Windows update failing error 80073712

please post its logs.
C:\Windows\Logs\CBS\CheckSUR.log and CheckSUR.Persist.log

here's one of the reasons we need it...

Code:

015-06-16 15:45:23, Info                  CSI    ouse, Version = 11.2.9600.17843, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral]) comp: (null) man: @0x22d2818
2015-06-16 15:45:23, Error                 CSI    00000082@2015/6/16:20:45:23.466 (F) d:\win7sp1_gdr\base\wcp\componentstore\storelayout.cpp(11690): Store corruption detected in function ComponentStore::CRawStoreLayout::CheckFamilyIndexForDeadWinnerComponent expression: (null)
  MissingWinningComponentKey on resource [100]"amd64_microsoft-windows-s..-downlevel.binaries_31bf3856ad364e35_6.3.9600.17207_none_5fc40d80ff2e33ea"[gle=0x80004005]
2015-06-16 15:45:23, Error                 CSI    00000083 (F) STATUS_SXS_COMPONENT_STORE_CORRUPT #81510# from CCSDirectTransaction::OperateEnding at index 0 of 102 (0x0000000000000066) operations, disposition 0[gle=0xd015001a]
2015-06-16 15:45:23, Error                 CSI    00000084 (F) HRESULT_FROM_WIN32(14098) #78743# from Windows::ServicingAPI::CCSITransaction::ICSITransaction2_AddComponents(Flags = 4, a = @0x182d8c0, mp = @0x182e0c0, disp = 0)[gle=0x80073712]
2015-06-16 15:45:23, Info                  CBS    Failed to add one or more component [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2015-06-16 15:45:23, Error                 CBS    Failed to complete component closure [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2015-06-16 15:45:23, Info                  CSI    00000085@2015/6/16:20:45:23.896 CSI Transaction @0x14e0070 destroyed
2015-06-16 15:45:23, Info                  CBS    Perf: Resolve chain complete.
2015-06-16 15:45:23, Info                  CBS    Failed to resolve execution chain. [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2015-06-16 15:45:23, Error                 CBS    Failed to process single phase execution. [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2015-06-16 15:45:23, Info                  CBS    WER: Generating failure report for package: Package_for_KB3058515~31bf3856ad364e35~amd64~~11.2.1.0, status: 0x80073712, failure source: Resolve, start state: Absent, target state: Staged, client id: WindowsUpdateAgent

Here's the summary from the log...

Code:

Summary:
Seconds executed: 800
 Found 890 errors
 Fixed 8 errors
  CSI Manifest Missing Total count: 45
  CSI Manifest and S256H Do Not Match Total count: 1
  CSI Located Replacement: Invalid (S256H) Total count: 102
  CSI Payload File Missing Total count: 836
  CSI F Mark Missing Total count: 8
  Fixed: CSI F Mark Missing.  Total count: 8

The type of errors I'm seeing imply possibly a hardware problem. - maybe RAM
I don't think there's any point in attempting to fix these errors (which may be a major project in themselves) untilwe've tested the hardware.

Please follow this tutorial to test the RAM first - RAM - Test with Memtest86+ - run at least 3 full passes. Even one discovered error is sufficient to call at least one of the involved pieces of hardware 'scrap'.

No problem - it's probably best to leave it to run overnight anyhow.
I'm not planning on leaving the country, so don't hurry on my account!

The original CBS.log showed only the following errors...

Code:

 Line 339062: 2015-06-16 15:57:26, Info                  CSI    00000538 [SR] Repairing 4 components
 Line 339063: 2015-06-16 15:57:26, Info                  CSI    00000539 [SR] Beginning Verify and Repair transaction
 Line 339064: 2015-06-16 15:57:26, Info                  CSI    0000053a [SR] Cannot verify component files for Microsoft.VC90.MFCLOC, Version = 9.0.30729.1, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:10{5}]"win32", TypeName neutral, PublicKey neutral, manifest is damaged (FALSE)
 Line 339065: 2015-06-16 15:57:26, Info                  CSI    0000053b [SR] Cannot verify component files for Microsoft.VC90.OpenMP, Version = 9.0.21022.8, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:10{5}]"win32", TypeName neutral, PublicKey neutral, manifest is damaged (FALSE)
 Line 339066: 2015-06-16 15:57:26, Info                  CSI    0000053c [SR] Cannot verify component files for Microsoft.VC80.ATL, Version = 8.0.50727.91, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:10{5}]"win32", TypeName neutral, PublicKey neutral, manifest is damaged (FALSE)
 Line 339067: 2015-06-16 15:57:26, Info                  CSI    0000053d [SR] Cannot verify component files for Microsoft.VC80.MFC, Version = 8.0.50727.91, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:10{5}]"win32", TypeName neutral, PublicKey neutral, manifest is damaged (FALSE)

- which generally indicate a minor problem with the VC++ install.
Your CheckSUR result shows a fairly massive corruption, which doesn't really fit with the SFC results (which is one reason why I asked for the MemTest86+ check).

Have you ever used any kind or registry 'optimiser' or 'cleaner'?? if so, which one?
It looks like most of the problem files relate to around three updates - it's possible that a power-out shutdown is the cause, where the system never got the change to properly save the files required by the update.

I could attempt to fix these errors manually - but to be honest, I don't have the time, and also, I feel that this could merely be the tip of the iceberg.

I think your best and quickest solution is going to be a repair install of Windows, so long as you have access to the proper SP1 media.