Error 0x80070002 - Windows 7 cannot check for updates

Page 2 of 2 FirstFirst 12

  1. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #11

    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.
    Last edited by NoelDP; 20 Oct 2013 at 06:07. Reason: formatting
      My Computer


  2. Posts : 12
    Windows 7x64
    Thread Starter
       #12

    Thanks, this is very weird though as I have replaced drive P many months ago. Actually, it does not even exist anymore. I am a bit hesitant to run chkdsk on my system disk C - made some bad experiences before doing so, which led to drive failure or other things broken. I know that this is not supposed to happen, but seen many online posts that it is indeed an issue with chkdsk.

    Any other suggestion to troubleshoot?
      My Computer


  3. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #13

    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.
      My Computer


  4. Posts : 12
    Windows 7x64
    Thread Starter
       #14

    NoelDP said:
    PLease attempt validation at www.microsoft.com/genuine/validate - it may pass because of the hack, but the hack may also be discovered, and if so, you'll be offered the kit.
    I did another attempt when stopping some other things that I was running and also using a VPN. This time, I got a different error message: "This Update is not applicable to your computer".

    Other thoughts?
      My Computer


  5. Posts : 12
    Windows 7x64
    Thread Starter
       #15

    Thanks, here we go with the log file. Thanks in advance for any thoughts you may have.
      My Computer


  6. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #16

    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
      My Computer


  7. Posts : 12
    Windows 7x64
    Thread Starter
       #17

    Thanks for bringing the news - though it is bad news...

    Unfortunately, I am having the update issue since day-1, so I doubt rolling back to an earlier version will do any good.

    I can imagine that it will be painful to do a manual attempt to repair the registry. Is there any quick fix that I may at least try to see whether it repairs it.

    Is this a sign of malware, a broken disk, or others?
      My Computer


  8. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #18

    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).
      My Computer


  9. Posts : 12
    Windows 7x64
    Thread Starter
       #19

    It is not a ram issue. I have tested and all is great. Having said this, I have changed ram a few months back as it was faulty. Actually, when I had installed Win7 on this machine, it was installed with faulty ram. Can this error still be a legacy from this? HD is also ok. Any other ideas what to do to fix the registry corruption?
      My Computer


  10. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #20

    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
      My Computer


 
Page 2 of 2 FirstFirst 12

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 21:35.
Find Us