Error 0x80070002 - Windows 7 cannot check for updates

There are a lot of errors in the System event log saying that the drive P: is corrupted - you should run CHKDSK P: /R to fix that.
Oddly, the last event logged in that is dated 26th August - which possibly indicates some form of corruption in either the file itself, or the service.
The Application event log is OK - but shows a number of errors....
Open an Elevated Command Prompt and run the following command
fsutil resource setautoreset true c:\

wait for it to complete, and then reboot


Please run a full CHKDSK and SFC scan....

Click on Start > All Programs > Accessories

Right-click on the Command Prompt entry

Select Run as Administrator and accept the UAC prompt - the ElevatedCommand Prompt window should pop up.

At the Command prompt, type

CHKDSK C: /R

and hit the Enter key.

You will be told that the drive is locked,

and the CHKDSK will run at he next boot - hit the Y key, press Enter, and then reboot.



The CHKDSK will take a few hours depending on the size of the drive,so be patient!

After the CHKDSK has run, Windows should boot normally (possibly after a second auto-reboot) -

then run the SFC.



SFC -System File Checker -Instructions

Click on Start > All Programs > Accessories

Right-click on the Command Prompt entry

Select Run as Administrator and accept the UAC prompt - the ElevatedCommand Prompt window should pop up.

At the Command prompt, type

SFC /SCANNOW

and hit the Enter key

Wait for the scan to finish - make a note of any error messages -and then reboot.

Copy the CBS.log file created(C:\Windows\Logs\CBS\CBS.log) to your desktop (you can't manipulate itdirectly) and then compress the copy and attach it to your reply.

Post a new MGADiag report with details of any error messagesencountered.

You can ignore the P: drive CHKDSK then :)

CHKDSK will only cause problems where the disk is already failing badly, as it does stress it a little. Assuming the drive is in a reasonable state, then it can do no harm, and may do a lot of good.

SFC is essential - it may tell us which of the many Loaders has been used, which may then allow us to uninstall it properly, and check for remaining nasties.

(Are there any strange folders in the C: drive root? - another possible clue to the loader)

I have to go out now - back later.

Ouch - this isn't good

Code:

2013-10-20 19:59:31, Info                  CSI    00000004@2013/10/20:11:59:31.666 PopulateComponentFamiliesKey - Begin
2013-10-20 19:59:41, Error                 CSI    00000005 (F) STATUS_OBJECT_NAME_NOT_FOUND #1278636# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = 0, key = {provider=NULL, handle=0}, da = (KEY_READ|KEY_WOW64_64KEY), oa = @0xc0e210->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[164]"\Registry\Machine\Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_Microsoft-windows-a..es-interface-router_31bf3856ad364e35_none_f2dccc14f607b91"; a:(OBJ_CASE_INSENSITIVE)}, disp = Unmapped disposition: 12641752 (0x00c0e5d8))[gle=0xd0000034]
2013-10-20 19:59:41, Error                 CSI    00000006@2013/10/20:11:59:41.476 (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]
2013-10-20 19:59:41, Error                 CSI    00000007 (F) STATUS_OBJECT_NAME_NOT_FOUND #1278635# from Windows::Rtl::SystemImplementation::CKey::OpenExistingKey(f = 0, da = (KEY_READ), oa = @0xc0e6d0, key = NULL, disp = (null))[gle=0xd0000034]
2013-10-20 19:59:41, Info                  CBS    NonStart: Failed to get store. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2013-10-20 19:59:41, Info                  CBS    Failed to ensure no startup processing was required. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2013-10-20 19:59:41, Info                  CBS    Failed during startup processing, continuing with Trusted Installer execution [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2013-10-20 19:59:41, Info                  CBS    Startup processing thread terminated normally
2013-10-20 19:59:44, Info                  CSI    00000008@2013/10/20:11:59:44.369 PopulateComponentFamiliesKey - Begin
2013-10-20 19:59:54, Error                 CSI    00000009 (F) STATUS_OBJECT_NAME_NOT_FOUND #2557289# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = 0, key = {provider=NULL, handle=0}, da = (KEY_READ|KEY_WOW64_64KEY), oa = @0xdecb00->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[164]"\Registry\Machine\Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_Microsoft-windows-a..es-interface-router_31bf3856ad364e35_none_f2dccc14f607b91"; a:(OBJ_CASE_INSENSITIVE)}, disp = Unmapped disposition: 14601928 (0x00decec8))[gle=0xd0000034]
2013-10-20 19:59:54, Error                 CSI    0000000a@2013/10/20:11:59:54.253 (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]
2013-10-20 19:59:54, Error                 CSI    0000000b (F) STATUS_OBJECT_NAME_NOT_FOUND #2557288# from Windows::Rtl::SystemImplementation::CKey::OpenExistingKey(f = 0, da = (KEY_READ), oa = @0xdecfc0, key = NULL, disp = (null))[gle=0xd0000034]

You have some registry corruption present.
Your best bet is to attempt a System Restore back to a time before the system started misbehaving - assuming it's not much more than a couple of weeks ago.

other than that, we'll have to start playing in the registry, which is not much fun

It could be damaged media or perhaps faulty RAM.
Test the hard drive with the (HD) manufacturer's test utility and the RAM with MemTest86+ (www.memtest.org).

Certainly, installing an OS when you have faulty RAM could cause this type of problem.

You may find it better to do a repair install - or even a clean install, if you don't have much else on the system yet.
See here for the instructions for a repair.... Repair Install