update error 8007370A (can't run SFC Scan )

Page 1 of 5 123 ... LastLast

  1. Posts : 37
    Windows 7 Home Premium 64bit.
       #1

    update error 8007370A (can't run SFC Scan )


    I haven't been able to update windows (7x64) for past week ,i have CheckSUR log but i can't run SFC Scan
    I've followed all of the online Microsoft recommendations here;
    Unable to install updates in Windows Vista, Windows 7, Windows Server 2008 and Windows Server 2008 R2
    Method 3 is where i hit the wall ,Any help would be appreciated.
    Thank you
    here is screenshot before hot fix


    and today (same error)-still can't update
      My Computer


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

    Try running the SFC scan from the Repair Environment....


    Reboot the computer, and tap the F8 key until you get the advanced boot menu up - one option should be 'Repair your computer'. Pick that one.

    Log into your normal account.
    You'll get a set of options - pick the Command Prompt one.
    At the command prompt, type DIR C:\
    - if we're lucky this will bring up a listing of your normal C: drive contents, including the Program Files folder(s) and the Windows folder.
    If not, try D:\ or E:\ (etc. until you get the right letter)
    then type the following command


    sfc /scannow /OFFBOOTDIR=<drive>:\ /OFFWINDIR=<drive>:\Windows

    where <drive> is the letter you found above.
    (example - sfc /scannow /OFFBOOTDIR=P:\ /OFFWINDIR=P:\Windows)

    Wait for the command to complete. (make a note of the response!).

    Once it has, type EXIT and the pick the option to reboot.


    The post the new CBS.log file (we don't need the rest this time - but you'll have to copy the file to the desktop before uploading it)
      My Computer


  3. Posts : 37
    Windows 7 Home Premium 64bit.
    Thread Starter
       #3

    i don't exactly fallow " normal account" (i'm the only user/administrator) can i just bring up the CMD from search box ?

    "Then post the new CBS.log file "- so the old CBS.log file will be replaced correct ?

    Thank you for quick response

    EDIT; when you mention trying different drives ( D:\ or E:\ ..,) i just realized that i have another SSD (with striped XP for benching ) that i should mention (maybe that's the problem .)

    EDIT 2;
    i think i got it (i try DIR C:\ in CMD before going in to safe mode )


    see attachment
    Last edited by coolhand411; 24 Feb 2013 at 07:11.
      My Computer


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

    Ah - I don't *think* the XP install would cause a problem - certainly not for a normal mode SFC scan, anyhow.

    Typing the command into the Search box will only run it in a normal User mode - it must be run as an Administrator (perhaps that is why it didn't work before?? - no- from your second picture, it looks like it ran in Admin mode but failed. ) Booting to the Repair Environment automatically elevates your logon and takes UAC out of the equation, and reduces the potential interferences to the minimum. 'normal account' simply means for you to use the normal username and password that you log into the PC with (which is almost certainly an Admin account).

    Looking in the CheckSUR log, there is a registry entry that is causing problems, as well as a few missing files

    The missing files are interesting - They would tend to indicate that you should be seeing non-genuine notifications, but I can see no signs of that in your screenshots.

    Please run an MGADiag report so we can check this...
    we need to see a full copy of the report produced by the MGADiag tool
    (download and save to desktop - http://go.microsoft.com/fwlink/?linkid=52012 )
    Once saved, run the tool.
    Click on the Continue button, which will produce the report.
    To copy the report to your response, click on the Copy button in the tool (ignore any error messages at this point), and then paste (using either r-click/Paste, or Ctrl+V ) into your response.
      My Computer


  5. Posts : 37
    Windows 7 Home Premium 64bit.
    Thread Starter
       #5

    sorry i just edited again,missed your post (i think it worked this time )
      My Computer


  6. Posts : 37
    Windows 7 Home Premium 64bit.
    Thread Starter
       #6

    here is MGADiag (if it matters this is clone copy from my smaller SSD )

    Code:
    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->
    
    Validation Code: 0
    Cached Online Validation Code: N/A, hr = 0xc004f012
    Windows Product Key: *****-*****-VJDGY-JVQJR-Q2RFR
    Windows Product Key Hash: o1EQlR+scTldhTQCff7vX6DSTH0=
    Windows Product ID: 00359-OEM-8702191-06805
    Windows Product ID Type: 3
    Windows License Type: OEM System Builder
    Windows OS version: 6.1.7601.2.00010300.1.0.003
    ID: {8F2D0527-4506-40AF-9255-1A6C9370374F}(1)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: N/A, hr = 0x80070002
    Signed By: N/A, hr = 0x80070002
    Product Name: Windows 7 Home Premium
    Architecture: 0x00000009
    Build lab: 7601.win7sp1_gdr.120830-0333
    TTS Error: 
    Validation Diagnostic: 
    Resolution Status: N/A
    
    Vista WgaER Data-->
    ThreatID(s): N/A, hr = 0x80070002
    Version: N/A, hr = 0x80070002
    
    Windows XP Notifications Data-->
    Cached Result: N/A, hr = 0x80070002
    File Exists: No
    Version: N/A, hr = 0x80070002
    WgaTray.exe Signed By: N/A, hr = 0x80070002
    WgaLogon.dll Signed By: N/A, hr = 0x80070002
    
    OGA Notifications Data-->
    Cached Result: N/A, hr = 0x80070002
    Version: N/A, hr = 0x80070002
    OGAExec.exe Signed By: N/A, hr = 0x80070002
    OGAAddin.dll Signed By: N/A, hr = 0x80070002
    
    OGA Data-->
    Office Status: 109 N/A
    OGA Version: N/A, 0x80070002
    Signed By: N/A, hr = 0x80070002
    Office Diagnostics: 025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3
    
    Browser Data-->
    Proxy settings: N/A
    User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
    Default Browser: C:\Users\coolhand\AppData\Local\Google\Chrome\Application\chrome.exe
    Download signed ActiveX controls: Prompt
    Download unsigned ActiveX controls: Disabled
    Run ActiveX controls and plug-ins: Allowed
    Initialize and script ActiveX controls not marked as safe: Disabled
    Allow scripting of Internet Explorer Webbrowser control: Disabled
    Active scripting: Allowed
    Script ActiveX controls marked as safe for scripting: Allowed
    
    File Scan Data-->
    File Mismatch: C:\Windows\system32\wat\watadminsvc.exe[Hr = 0x80070003]
    File Mismatch: C:\Windows\system32\wat\npwatweb.dll[Hr = 0x80070003]
    File Mismatch: C:\Windows\system32\wat\watux.exe[Hr = 0x80070003]
    File Mismatch: C:\Windows\system32\wat\watweb.dll[Hr = 0x80070003]
    
    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{8F2D0527-4506-40AF-9255-1A6C9370374F}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010300.1.0.003</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-Q2RFR</PKey><PID>00359-OEM-8702191-06805</PID><PIDType>3</PIDType><SID>S-1-5-21-196860974-1216559597-1948589503</SID><SYSTEM><Manufacturer>Gigabyte Technology Co., Ltd.</Manufacturer><Model>To be filled by O.E.M.</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>F14</Version><SMBIOSVersion major="2" minor="7"/><Date>20120822000000.000000+000</Date></BIOS><HWID>246D3407018400FE</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Central Standard Time(GMT-06:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults>  
    
    Spsys.log Content: 0x80070002
    
    Licensing Data-->
    Software licensing service version: 6.1.7601.17514
    
    Name: Windows(R) 7, HomePremium edition
    Description: Windows Operating System - Windows(R) 7, OEM_COA_NSLP channel
    Activation ID: 586bc076-c93d-429a-afe5-a69fbc644e88
    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
    Extended PID: 00359-00174-021-906805-02-1033-7600.0000-1972012
    Installation ID: 015380690645832505012362457573754963886735083192161321
    Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88338
    Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88339
    Use License URL: http://go.microsoft.com/fwlink/?LinkID=88341
    Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88340
    Partial Product Key: Q2RFR
    License Status: Licensed
    Remaining Windows rearm count: 4
    Trusted time: 2/24/2013 6:19:01 AM
    
    Windows Activation Technologies-->
    HrOffline: 0x00000000
    HrOnline: N/A
    HealthStatus: 0x0000000000000000
    Event Time Stamp: N/A
    ActiveX: Not Registered - 0x80040154
    Admin Service: Not Registered - 0x80040154
    HealthStatus Bitmask Output:
    
    
    HWID Data-->
    HWID Hash Current: MgAAAAEAAAABAAEAAgADAAAAAgABAAEAln32rtoPdlCol+4W/qdOkfaolnYStFbFlmM=
    
    OEM Activation 1.0 Data-->
    N/A
    
    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: yes, but no SLIC table
    Windows marker version: N/A
    OEMID and OEMTableID Consistent: N/A
    BIOS Information: 
      ACPI Table Name    OEMID Value    OEMTableID Value
      APIC            ALASKA        A M I
      FACP            ALASKA        A M I
      HPET            ALASKA        A M I
      MCFG                    
      SSDT            SataRe        SataTabl
      SSDT            SataRe        SataTabl
      SSDT            SataRe        SataTabl
      MATS            ALASKA        A M I
      My Computer


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

    Odd - although since the WAT update is installed, it may not be checking the relevant files.
    The report looks fine :) -

    There's no sign of any SFC results in your CBS log, but that may be because of the registry error.
    I've uploaded a small file ch4aa.zip to my SkyDrive at Noel's SkyDrive
    Please download and save it - extract the contained wow64.reg file to your desktop

    Now open an Elevated Command Prompt window, and run the following commands

    Code:
     
     
    REG LOAD HKLM\COMPONENTS C:\Windows\System32\config\COMPONENTS
    REG QUERY HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\wow64_microsoft-windows-f..client-applications_31bf3856ad364e35_6.1.7600.16759_none_df67c0e4765c33a8
    REG IMPORT %userprofile%\desktop\wow64.reg
    REG QUERY HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\wow64_microsoft-windows-f..client-applications_31bf3856ad364e35_6.1.7600.16759_none_df67c0e4765c33a8
    REG UNLOAD HKLM\COMPONENTS

    Post the results, then reboot and run another CheckSUR scan and then try another SFC scan and post the new CBS logs.


    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.
    Last edited by NoelDP; 24 Feb 2013 at 07:50. Reason: mismatched key!
      My Computer


  8. Posts : 37
    Windows 7 Home Premium 64bit.
    Thread Starter
       #8

    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>REG QUERY HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Componen
    ts\wow64_microsoft-windows-f..client-applications_31bf3856ad364e35_6.1.7600.1675
    9_none_df67c0e4765c33a8
    
    HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\wow64_microsoft-windows-f..
    client-applications_31bf3856ad364e35_6.1.7600.16759_none_df67c0e4765c33a8
        identity    REG_BINARY    4D6963726F736F66742D57696E646F77732D4661782D436C69
    656E742D4170706C69636174696F6E732C2043756C747572653D6E65757472616C2C205665727369
    6F6E3D362E312E373630302E31363735392C205075626C69634B6579546F6B656E3D333162663338
    353661643336346533352C2050726F636573736F724172636869746563747572653D776F7736342C
    2076657273696F6E53636F70653D4E6F6E537853
        f!wfs.mof    REG_BINARY    7700660073002E006D006F006600
        c!42c1639ef2f..b1ab137e0a2_31bf3856ad364e35_6.1.7600.16759_9875cb54fd424176
       REG_BINARY
    
    
    C:\Windows\system32>REG IMPORT %userprofile%\desktop\wow64.reg
    ERROR: Error accessing the registry.
    
    C:\Windows\system32>REG QUERY HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Componen
    ts\wow64_microsoft-windows-f..client-applications_31bf3856ad364e35_6.1.7600.1675
    9_none_df67c0e4765c33a8
    
    HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\wow64_microsoft-windows-f..
    client-applications_31bf3856ad364e35_6.1.7600.16759_none_df67c0e4765c33a8
        identity    REG_BINARY    4D6963726F736F66742D57696E646F77732D4661782D436C69
    656E742D4170706C69636174696F6E732C2043756C747572653D6E65757472616C2C205665727369
    6F6E3D362E312E373630302E31363735392C205075626C69634B6579546F6B656E3D333162663338
    353661643336346533352C2050726F636573736F724172636869746563747572653D776F7736342C
    2076657273696F6E53636F70653D4E6F6E537853
        f!wfs.mof    REG_BINARY    7700660073002E006D006F006600
        c!42c1639ef2f..b1ab137e0a2_31bf3856ad364e35_6.1.7600.16759_9875cb54fd424176
       REG_BINARY
    
    
    C:\Windows\system32>REG UNLOAD HKLM\COMPONENTS
    The operation completed successfully.
    
    C:\Windows\system32>
      My Computer


  9. Posts : 37
    Windows 7 Home Premium 64bit.
    Thread Starter
       #9

    here is CBS file
      My Computer


  10. Posts : 37
    Windows 7 Home Premium 64bit.
    Thread Starter
       #10

    i ran command again right after:

    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>REG QUERY HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Componen
    ts\wow64_microsoft-windows-f..client-applications_31bf3856ad364e35_6.1.7600.1675
    9_none_df67c0e4765c33a8
    
    HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\wow64_microsoft-windows-f..
    client-applications_31bf3856ad364e35_6.1.7600.16759_none_df67c0e4765c33a8
        identity    REG_BINARY    4D6963726F736F66742D57696E646F77732D4661782D436C69
    656E742D4170706C69636174696F6E732C2043756C747572653D6E65757472616C2C205665727369
    6F6E3D362E312E373630302E31363735392C205075626C69634B6579546F6B656E3D333162663338
    353661643336346533352C2050726F636573736F724172636869746563747572653D776F7736342C
    2076657273696F6E53636F70653D4E6F6E537853
        f!wfs.mof    REG_BINARY    7700660073002E006D006F006600
        c!42c1639ef2f..b1ab137e0a2_31bf3856ad364e35_6.1.7600.16759_9875cb54fd424176
       REG_BINARY
    
    
    C:\Windows\system32>REG IMPORT %userprofile%\desktop\wow64.reg
    ERROR: Error accessing the registry.
    
    C:\Windows\system32>REG QUERY HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Componen
    ts\wow64_microsoft-windows-f..client-applications_31bf3856ad364e35_6.1.7600.1675
    9_none_df67c0e4765c33a8
    
    HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\wow64_microsoft-windows-f..
    client-applications_31bf3856ad364e35_6.1.7600.16759_none_df67c0e4765c33a8
        identity    REG_BINARY    4D6963726F736F66742D57696E646F77732D4661782D436C69
    656E742D4170706C69636174696F6E732C2043756C747572653D6E65757472616C2C205665727369
    6F6E3D362E312E373630302E31363735392C205075626C69634B6579546F6B656E3D333162663338
    353661643336346533352C2050726F636573736F724172636869746563747572653D776F7736342C
    2076657273696F6E53636F70653D4E6F6E537853
        f!wfs.mof    REG_BINARY    7700660073002E006D006F006600
        c!42c1639ef2f..b1ab137e0a2_31bf3856ad364e35_6.1.7600.16759_9875cb54fd424176
       REG_BINARY
    
    
    C:\Windows\system32>REG UNLOAD HKLM\COMPONENTS
    ERROR: Access is denied.
    
    C:\Windows\system32>
      My Computer


 
Page 1 of 5 123 ... LastLast

  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 18:14.
Find Us