Windows Update Issues

Without the detail, what you've posted is all but useless.

Please follow the Windows Update Posting Instructions and post the requested data
If the file is too large (8MB compressed), remove the older CBSPersist cab files until the final file is below the limit - you can always post them separately after zipping them. (the forum doesn't allow the upload of bare CAB files, for a number of reasons)

Interesting.
There is a single bitflip in the registry which is causing all sorts of mayhem in your CBS.log file.

The error in the CBS log is this one...

Code:

2014-06-07 00:54:48, Error                 CSI    00000012 (F) STATUS_OBJECT_NAME_NOT_FOUND #272173# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = (AllowAccessDenied), key = {provider=NULL, handle=0}, da = (KEY_READ|DELETE|KEY_WOW64_64KEY), oa = @0xb2e7e0->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[217]"\Registry\Machine\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.17592 (win7sp1_gdr.110408-1631)\ComponentFamilies\amd64_microsoft-windows-d..gement-winproviders_31bf3856ad364e35_none_f21e73acf5c7442d\v!6n1.7600.q6385"; a:(OBJ_CASE_INSENSITIVE)}, disp = Unmapped disposition: 11724672 (0x00b2e780))[gle=0xd0000034]
2014-06-07 00:54:48, Error                 CSI    00000013@2014/6/6:23:54:48.046 (F) d:\win7sp1_gdr\base\wcp\sil\merged\ntu\ntsystem.cpp(3676): Error STATUS_OBJECT_NAME_NOT_FOUND originated in function Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey expression: (null)
[gle=0x80004005]

This is independent of the CheckSUR log - but correcting it may either correct some of the errors there, or create more that need correction (or both!)


Let's check what is actually there before we attempt to cure it...

Please open an Elevated Command Prompt and run the following commands

Code:

 
REG LOAD HKLM\COMPONENTS C:\Windows\System32\config\COMPONENTS
REG QUERY "HKLM\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.17592 (win7sp1_gdr.110408-1631)\ComponentFamilies\amd64_microsoft-windows-d..gement-winproviders_31bf3856ad364e35_none_f21e73acf5c7442d"
REG UNLOAD HKLM\COMPONENTS
 
.

Post the results.

Here are some instructions to make life easier :)
1) To open an Elevated Command Prompt Window (the ECP window), click on Start, All Programs, Accessories – then right-click on Command Prompt, and select Run as Administrator. Accept the UAC prompt.
2) To run the commands easier, highlight the block of commands, and right-click on the highlight – select Copy. In the CP Window, click on the black/white icon at top left – select Paste. The commands will run but may not complete the last command, so hit the Enter Key once.
3) To copy the results... click on the Black/White icon in the top left, and select Edit... 'Select All', and hit the Enter key - then use Ctrl+V or r-click+Paste to paste it into your response.

Hopefully, if we fix that one first, things will become a little easier to read!

Hmm - a very short listing (mine came to around 15 entries)
The one ending v!6n1.7600.q6385 is the problem - the question is how best to resolve it.

We can go the manual way (easiest for me, but potentially the hardest for you) or I can try and craft the proper patch to fix the bitflip, and hope everything goes according to plan.

Have you worked in Regedit before? How comfortable are you there?

Oh goody :) Makes my life a lot easier

Open an Elevated Command Prompt, and run the following commands

REG LOAD HKLM\COMPONENTS C:\Windows\System32\config\COMPONENTS
Regedit


Regedit will open once the hive has loaded
Navigate to
HKLM\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.17592 (win7sp1_gdr.110408-1631)\ComponentFamilies\amd64_microsoft-windows-d..gement-winproviders_31bf3856ad364e35_none_f21e73acf5c7442d

Export it for safety! (and please upload it so I can take a look - you'll have to zip it first)

and expand that branch so you can see the
v!6n1.7600.q6385
subfolder
right-click on it and select 'Rename' - edit it to read
v!6n1.7600.16385

Now close regedit and the CMD window, and reboot then run SFC and CheckSUR again - post the new CBS.log and CheckSUR.log files.