4 Windows Update Failures error codes 8024200D and 8007371B

The last entry in the CBS.log file is from 18th Oct - and pretty useless to us, since it pre-dates the CheckSUR fixes.

Please copy the files from the c:\windows\logs\cbs folder again, and upload them

This error is still present...

Code:

2014-10-20 19:26:16, Error                 CSI    000002fc@2014/10/20:23:26:16.499 (F) d:\win7sp1_gdr\base\wcp\componentstore\storelayout.cpp(11690): Store corruption detected in function ComponentStore::CRawStoreLayout::CheckFamilyIndexForDeadWinnerComponent expression: (null)
  MissingWinningComponentKey on resource [75]"amd64_netfx-dfdll_dll_b03f5f7f11d50a3a_6.1.7601.18523_none_15007b59fcb45889"[gle=0x80004005]
2014-10-20 19:26:20, Error                 CSI    000002fd (F) STATUS_SXS_COMPONENT_STORE_CORRUPT #2404795# from CCSDirectTransaction::OperateEnding at index 0 of 10 (0x000000000000000a) operations, disposition 0[gle=0xd015001a]
2014-10-20 19:26:20, Error                 CSI    000002fe (F) HRESULT_FROM_WIN32(14098) #2404420# from Windows::ServicingAPI::CCSITransaction::ICSITransaction2_AddComponents(Flags = 4, a = @0x89a0eb0, mp = @0x89a16b0, disp = 0)[gle=0x80073712]
2014-10-20 19:26:20, Info                  CBS    Failed to add one or more component [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2014-10-20 19:26:20, Error                 CBS    Failed to complete component closure [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2014-10-20 19:26:20, Info                  CSI    000002ff@2014/10/20:23:26:20.358 CSI Transaction @0x78f4460 destroyed
2014-10-20 19:26:20, Info                  CBS    Perf: Resolve chain complete.

The CheckSUR result shows that you also have some serious file corruption.

Code:

(f) CSI Payload File Missing 0x00000000 KBDBASH.DLL amd64_microsoft-windows-i..l-keyboard-0000046d_31bf3856ad364e35_6.1.7601.18528_none_5bfea9a86c525f64 
(f) CSI Payload File Missing 0x00000000 KBDBASH.DLL wow64_microsoft-windows-i..l-keyboard-0000046d_31bf3856ad364e35_6.1.7601.18528_none_665353faa0b3215f 
(f) CSI Payload File Missing 0x00000000 KBDRU.DLL amd64_microsoft-windows-i..l-keyboard-00000419_31bf3856ad364e35_6.1.7601.18528_none_48ed66d678941c92 
(f) CSI Payload File Missing 0x00000000 KBDRU.DLL wow64_microsoft-windows-i..l-keyboard-00000419_31bf3856ad364e35_6.1.7601.18528_none_53421128acf4de8d 
(f) CSI Payload File Missing 0x00000000 KBDRU1.DLL amd64_microsoft-windows-i..l-keyboard-00010419_31bf3856ad364e35_6.1.7601.18528_none_ec0baadf6b2539cb 
(f) CSI Payload File Missing 0x00000000 KBDRU1.DLL wow64_microsoft-windows-i..l-keyboard-00010419_31bf3856ad364e35_6.1.7601.18528_none_f66055319f85fbc6 
(f) CSI Payload File Missing 0x00000000 KBDTAT.DLL amd64_microsoft-windows-i..l-keyboard-00000444_31bf3856ad364e35_6.1.7601.18528_none_46b57e987a0152d2 
(f) CSI Payload File Missing 0x00000000 KBDTAT.DLL wow64_microsoft-windows-i..l-keyboard-00000444_31bf3856ad364e35_6.1.7601.18528_none_510a28eaae6214cd 
(f) CSI Payload File Missing 0x00000000 KBDYAK.DLL amd64_microsoft-windows-i..l-keyboard-00000485_31bf3856ad364e35_6.1.7601.18528_none_4726aaa679b8bddd 
(f) CSI Payload File Missing 0x00000000 KBDYAK.DLL wow64_microsoft-windows-i..l-keyboard-00000485_31bf3856ad364e35_6.1.7601.18528_none_517b54f8ae197fd8 
(f) CSI Payload File Missing 0x00000000 gdi32.dll amd64_microsoft-windows-gdi32_31bf3856ad364e35_6.1.7601.18539_none_b793fa3d5ffce5e2 
(f) CSI Payload File Missing 0x00000000 gdi32.dll wow64_microsoft-windows-gdi32_31bf3856ad364e35_6.1.7601.18539_none_c1e8a48f945da7dd 
(f) CSI Payload File Missing 0x00000000 locale.nls amd64_microsoft-windows-i..nal-core-locale-nls_31bf3856ad364e35_6.1.7601.18528_none_c8d750bcbfe9e700 
(f) CSI Payload File Missing 0x00000000 locale.nls x86_microsoft-windows-i..nal-core-locale-nls_31bf3856ad364e35_6.1.7601.18528_none_6cb8b539078c75ca 
(f) CSI Payload File Missing 0x00000000 micross.ttf amd64_microsoft-windows-f..-microsoftsansserif_31bf3856ad364e35_6.1.7601.18528_none_873924b85eaecc3e 
(f) CSI Payload File Missing 0x00000000 segoeui.ttf amd64_microsoft-windows-font-truetype-segoeui_31bf3856ad364e35_6.1.7601.18528_none_2edb239c28e0d397 
(f) CSI Payload File Missing 0x00000000 segoeuib.ttf amd64_microsoft-windows-font-truetype-segoeui_31bf3856ad364e35_6.1.7601.18528_none_2edb239c28e0d397 
(f) CSI Payload File Missing 0x00000000 segoeuii.ttf amd64_microsoft-windows-font-truetype-segoeui_31bf3856ad364e35_6.1.7601.18528_none_2edb239c28e0d397 
(f) CSI Payload File Missing 0x00000000 segoeuiz.ttf amd64_microsoft-windows-font-truetype-segoeui_31bf3856ad364e35_6.1.7601.18528_none_2edb239c28e0d397 
(f) CSI Payload File Missing 0x00000000 tahoma.ttf amd64_microsoft-windows-font-truetype-tahoma_31bf3856ad364e35_6.1.7601.18528_none_8deb8a8f8b479ca8 
(f) CSI Payload File Missing 0x00000000 tahomabd.ttf amd64_microsoft-windows-font-truetype-tahoma_31bf3856ad364e35_6.1.7601.18528_none_8deb8a8f8b479ca8 
(f) CSI Payload File Missing 0x00000000 tzres.dll amd64_microsoft-windows-i..rnational-timezones_31bf3856ad364e35_6.1.7601.18539_none_735ca6b7203d6b5a 
(f) CSI Payload File Missing 0x00000000 tzres.dll wow64_microsoft-windows-i..rnational-timezones_31bf3856ad364e35_6.1.7601.18539_none_7db15109549e2d55 
(f) CSI Payload File Missing 0x00000000 tzres.dll.mui amd64_microsoft-windows-i..timezones.resources_31bf3856ad364e35_6.1.7601.18539_en-us_e18aa24b9871e017 
(f) CSI Payload File Missing 0x00000000 tzres.dll.mui x86_microsoft-windows-i..timezones.resources_31bf3856ad364e35_6.1.7601.18539_en-us_856c06c7e0146ee1 
(f) CSI Payload File Missing 0x00000000 tzupd.exe amd64_microsoft-windows-i..rnational-timezones_31bf3856ad364e35_6.1.7601.18539_none_735ca6b7203d6b5a 
(f) CSI Payload File Missing 0x00000000 win32k.sys amd64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.18528_none_1712999db12aeeef 
(f) CSI Payload File Missing 0x00000000 win32k.sys amd64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.18539_none_1708c9fbb1322437

I think in view of this combination of errors, the best option for you is going to be a repair install of the OS - it will almost certainly be quicker than attempting manual repair of the known (and unknown) errors.##See the tutorial here... Repair Install

Frequently the root problem predates available System Restore points - but yes, it's worth trying. go back a week before you first noticed the problem.