Tried many things, still error 800736B3

Some interesting errors there....
from the update log....

Code:

2013-04-08 04:24:56:762 1008 86c Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256"
2013-04-08 04:24:58:556 1008 86c Setup WARNING: Cbs StartSession, error = 0x8007370B
2013-04-08 04:24:58:556 1008 86c Setup FATAL: Applicability evaluation for setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256" failed, error = 0x8007370B
2013-04-08 04:24:58:556 1008 86c Setup FATAL: SelfUpdate check failed, err = 0x8007370B

2013-04-08 09:25:02:501 1008 77c Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80190194
2013-04-08 09:25:02:501 1008 77c Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80190194
2013-04-08 09:25:02:501 1008 77c Misc WARNING: DownloadFileInternal failed for http://download.windowsupdate.com/v9...uv4wuredir.cab: error 0x80190194

2013-04-08 09:25:14:451 1008 77c Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256"
2013-04-08 09:25:16:245 1008 77c Setup WARNING: Cbs StartSession, error = 0x8007370B
2013-04-08 09:25:16:245 1008 77c Setup FATAL: Applicability evaluation for setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256" failed, error = 0x8007370B
2013-04-08 09:25:16:245 1008 77c Setup FATAL: SelfUpdate check failed, err = 0x8007370B
2013-04-08 09:25:16:245 1008 77c Agent   * WARNING: Skipping scan, self-update check returned 0x8007370B
2013-04-08 09:25:16:245 1008 77c Agent   * WARNING: Exit code = 0x8007370B

So the root update problem appears to be that the system can't evaluate the install status for the Update Agent
This may be because of what we see in the CBS log...

Code:

2013-04-06 17:23:12, Error                 CSI    00000005 (F) Invalid attribute name found: [l:28{14}]"PublicKmyToken"[gle=0x80004005]
2013-04-06 17:23:12, Error                 CSI    00000006@2013/4/6:21:23:12.256 (F) d:\win7sp1_gdr\base\wcp\identity\id_baseidentity.cpp(1263): Error STATUS_SXS_INVALID_IDENTITY_ATTRIBUTE_NAME originated in function Windows::Identity::Rtl::Implementation::CRtlIdentityBase::CRtlIdentityBase_Initialize expression: pBAI != 0
[gle=0x80004005]
2013-04-06 17:23:12, Error                 CSI    00000007 (F) STATUS_SXS_INVALID_IDENTITY_ATTRIBUTE_NAME #99357# from Windows::Identity::Rtl::Implementation::CRtlIdentityAuthority::IRtlIdentityAuthority_Parse(flags = 0, string = [l:312{156}]"6b5819de600853a49507704bd68a01d1, Culture=neutral, Version=6.1.7600.21062, PublicKmyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS")
[gle=0xd0150017]
2013-04-06 17:23:12, Info                  CBS    NonStart: Failed to get store. [HRESULT = 0x8007370b - ERROR_SXS_INVALID_IDENTITY_ATTRIBUTE_NAME]
2013-04-06 17:23:12, Info                  CBS    Failed to ensure no startup processing was required. [HRESULT = 0x8007370b - ERROR_SXS_INVALID_IDENTITY_ATTRIBUTE_NAME]
2013-04-06 17:23:12, Info                  CBS    Failed during startup processing, continuing with Trusted Installer execution [HRESULT = 0x8007370b - ERROR_SXS_INVALID_IDENTITY_ATTRIBUTE_NAME]
2013-04-06 17:23:12, Info                  CBS    Startup processing thread terminated normally

That's actually not very difficult to fix - but it is fiddly without CheckSUR's aid
The error actually lies in the registry.

Please upload your C:\Windows\system32\config\components file (probably around 40MB) after compressing it - not that it's likely to be too big for the forum, so you'll have to upload it to a fileshare site such as SKydrive or DropBox and post a link.
Then I'll check through it as much as possible, and send it back - hopefully fixed :)

Ooops! fell off my radar!

I'll get back to you in an hour or so...

I've uploaded a file - test2kmy.zip - to my SkyDrive at Noel's SkyDrive
Please download and save it.
Right-click on the saved file and select Extract all....
This will place a new folder test2kmy in the same place - with one file inside it... test2kmy.reg

Open an Elevated Command Prompt, and run the following command

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

now right-click on the test2kmy.reg rile, and select Merge.

Accept the warnings - and you should get a 'success' message.

Now in the Command Prompt window, run the following command

REG UNLOAD HKLM\COMPONENTS

reboot

once rebooted, run the CheckSUR tool again, and post the new CheckSUR.log file.

Also - what happens if you now attempt to run SFC /SCANNOW from an Elevated Command Prompt?

Did you get 'success' messages from the two commands? (especially the first? (REG LOAD...))

This is how the Command prompt for the 'REG LOAD command should have processed....

Code:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.
C:\Windows\system32>reg load hklm\components c:\windows\system32\config\componen
ts
The operation completed successfully.
C:\Windows\system32>

Please try it again - do you get the same response or not?

If you do, try the Merge again.