You have a rather nasty error set in the CBS log....
Code:
2013-01-18 00:00:19, Error CSI 00000005 (F) Invalid attribute name found: [l:42{21}]"ProcessorA3chitecture"[gle=0x80004005]
2013-01-18 00:00:19, Error CSI 00000006@2013/1/18:06:00:19.640 (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-01-18 00:00:19, Error CSI 00000007 (F) STATUS_SXS_INVALID_IDENTITY_ATTRIBUTE_NAME #387366# from Windows::Identity::Rtl::Implementation::CRtlIdentityAuthority::IRtlIdentityAuthority_Parse(flags = 0, string = [l:304{152}]"Microsoft-Windows-RasRTUtils, Culture=neutral, Version=6.1.7601.17514, PublicKeyToken=31bf3856ad364e35, ProcessorA3chitecture=amd64, versionScope=NonSxS")
[gle=0xd0150017]
2013-01-18 00:00:19, Info CBS NonStart: Failed to get store. [HRESULT = 0x8007370b - ERROR_SXS_INVALID_IDENTITY_ATTRIBUTE_NAME]
2013-01-18 00:00:19, Info CBS Failed to ensure no startup processing was required. [HRESULT = 0x8007370b - ERROR_SXS_INVALID_IDENTITY_ATTRIBUTE_NAME]
2013-01-18 00:00:19, Info CBS Failed during startup processing, continuing with Trusted Installer execution [HRESULT = 0x8007370b - ERROR_SXS_INVALID_IDENTITY_ATTRIBUTE_NAME]
The errors in the CheckSUR log are of the same type (bit-flips)
Code:
(f) CSI Corrupt Identity 0xC0150017 Microsoft-Windows-RasRTUtils, Culture=neutral, Version=6.1.7601.17514, PublicKeyToken=31bf3856ad364e35, ProcessorA3chitecture=amd64, versionScope=NonSxS amd64_microsoft-windows-rasrtu,ils_31bf3856ad364e35_6.1.7601.17514_none_6b3b9980011a19de Bad identity
(f) CSI Manifest Missing 0x00000002 amd64_microsoft-windows-rasrtu,ils_31bf3856ad364e35_6.1.7601.17514_none_6b3b9980011a19de.manifest amd64_microsoft-windows-rasrtu,ils_31bf3856ad364e35_6.1.7601.17514_none_6b3b9980011a19de
These both relate, I suspect to the same fault.
I think I'd better call in the cavalry on this one - I'm not competent on this type of error in this area
Please wait for Tom to respond.