Windows Update Error 80070002 & Windows Update Diag Error 0x8007370B

Page 1 of 2 12 LastLast

  1. Posts : 11
    Indiana
       #1

    Windows Update Error 80070002 & Windows Update Diag Error 0x8007370B


    ASUS Desktop PC CM6850 Series
    Windows 7 Home Premium SP1
    64-bit
    Core i7
    4GB RAM
    500GB HDD


    Windows updates not working for a while. Initial was 8007370B appearing in the Windows Update window when searching for updates. Found bad memory using Memtest86+ and pulled the stick. Other stick no errors after 8 passes.

    Toshiba HDD installed. Ran two different HDD diagnostics test on it and it passed.

    No conflicts in device manager.

    Now, Windows Update window showing 80070002 error. Based upon instructions, ran System Update Readiness Tool (SURT) but that appears to have not made any resolution. Ran it twice to ensure it ran successfully.

    Then, ran the Windows Update Diagnostic.diagcab from go.microsoft.com/fwlink/?LinkID=231149 and it shows Windows Update error 0x8007370B(2014-09-18-T-06_58_30P) as NOT FIXED. All other items in list shows as FIXED.

    SFC /scannow will not run ... displaying the message "windows resource protection could not perform the requested operation". I tried the same in a elevated prompt in normal windows and in safe mode with the same result. No luck running Surface Scan.

    Ran chkdsk /r twice also.

    Screen captures of both errors and CBS log file attached. Any help is greatly appreciated. In the meantime, I will begin running some antimalware scans just in case.

    Thanks for any assistance.
    Last edited by woodcycl; 19 Sep 2014 at 21:15.
      My Computer


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

    Please follow the Windows Update Posting Instructions and post the requested data
    If the file is too large (8MB compressed), remove the older CBSPersist cab files until the final file is below the limit - you can always post them separately after zipping them. (the forum doesn't allow the upload of bare CAB files, for a number of reasons)

    We need that data whether or not either CheckSUR or SFC complete.
      My Computer


  3. Posts : 11
    Indiana
    Thread Starter
       #3

    Thanks for the response NoelDP. However, I did follow those specific instructions from the link you provided prior to posting my OP. If there is something else that needs included that is not mentioned in that link, please let me know. The CBS.zip file is attached also. Please advise.
      My Computer


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

    You didn't follow the instructions - as there are no data files in your post.
    Without the requested data, there is nothing we can do.
      My Computer


  5. Posts : 11
    Indiana
    Thread Starter
       #5

    Hello NoelDP. The OP includes a cbs.zip file and shows it as an "Attached file". I'll include again here if for some reason you aren't able to see an attached file.
      My Computer


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

    That file is just another picture - and no good for diagnostics.
      My Computer


  7. Posts : 11
    Indiana
    Thread Starter
       #7

    Okay, I zipped up the CBS log folder once again. And, tested it be extracting the files from it to ensure it is a valid .zip file. I've also included a .jpg showing the contest of the CBS folder just in case. If there is another compression you'd prefer other than .zip to see the contents, please let me know.

    Also, I noticed the size was 8.85MB ... so broke it down into to .zip files.
      My Computer


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

    That's more like it - unfortunately the news is not very good.
    You had massive corruption in the COMPONENT registry hive, most of which CheckSUR claims to have fixed
    Here's thefinal summary from that run...
    Code:
    Summary:
    Seconds executed: 1962
     Found 55832 errors
     Fixed 55786 errors
      CSI Manifest Missing Total count: 11
      CSI Missing Component Key Total count: 8105
      Fixed: CSI Missing Component Key.  Total count: 8105
      CSI Missing Pinned Component Key Total count: 3502
      Fixed: CSI Missing Pinned Component Key.  Total count: 3502
      CSI Missing Deployment Key Total count: 7
      CSI Corrupt Deployment Keyform Total count: 2
      CSI Corrupt Component Keyform Total count: 5
      CSI Missing Identity Total count: 11610
      Fixed: CSI Missing Identity.  Total count: 11610
      CSI Corrupt Identity Total count: 22
      Fixed: CSI Corrupt Identity.  Total count: 6
      CSI Missing C Mark Total count: 13851
      Fixed: CSI Missing C Mark.  Total count: 13851
      CSI Payload File Missing Total count: 6
      Fixed: CSI Payload File Missing.  Total count: 1
      CSI F Mark Missing Total count: 22212
      Fixed: CSI F Mark Missing.  Total count: 22212
      CSI Store Directory Missing Total count: 1
      Fixed: CSI Store Directory Missing.  Total count: 1
    Unavailable repair files:
     winsxs\manifests\x86_policy.6.0.microsoft.ink_31bf3856ad364e35_6.1.7600.16385_none_c7f11a6fdc17Šf5a.manifest
     winsxs\manifests\x86_microsoft.ink_31bf3856ad36Ée35_1.7.7600.16385_none_c87c51e0123d40da.manifest
     winsxs\manifests\x86_policy.1.0.microsoft.ink_31bf3856ad364e35_ .1.7600.16385_none_ac169bf8db6dc435.manifest
     winsxs\manifests\msil_microsoft.web.manag..iisclient.resources_31bf3856ad364e35Ì6.1.7600.16385_en-us_4a2dd1ed1a2ff335.manifest
     winsxs\manifests\x86_microsoft-windows-ú..diagnostic-settings_31bf3856ad364e35_6.1.7600.16385_none_62433344ed197c29.manifest
     winsxs\manifests\x86_microsoft-windows-m..ds-ce-rll.resources_3îbf3856ad364e35_6.1.7600.16385_en-us_0def3c4a82afa650.manifest
     winsxs\manifests\wow64_microsoft-windows-i..ttpredirectbinariesx31bf3856ad364e35_6.1.7600.16385_none_13c790eccc23afcd.manifest
     winsxs\manifests\wow64_microsoft-windows-i..stfilteringbinaries¦31bf3856ad364e35_6.1.7600.16385_none_38daa6d0fa5c3fac.manifest
     winsxs\manifests\amd64_Ùicrosoft-windows-azman.resources_31bf3856ad364e35_6.1.7600.16385_en-us_6daa7bd08415f83f.manifest
     winsxs\manifests\wow64_microsoft-windows-i..ellprovider-nonmsil'31bf3856ad364e35_6.1.7600.16385_none_e91133e4e5bac6bd.manifest
     winsxs\manifests\wow64_microsoft-windows-i..ext›nsibility-wowgc_31bf3856ad364e35_6.1.7600.16385_none_598a4032425b7fee.manifest
    The remaining errors are mostly the result of bitflips - which tends to indicate that the basic problem lies with RAM failures.

    Before doing anything more, you need to test the RAM using MemTest86++ RAM - Test with Memtest86+ for at least 3 passes (unless it fails earlier, which I suspect it will)
      My Computer


  9. Posts : 11
    Indiana
    Thread Starter
       #9

    Thanks NoelDP. As mentioned above, I replaced 1 of 2 sticks of memory after running Memtest86+. I ran it individually on each stick of RAM installed alone for 8 passes each. One passed and one failed. So, that portion should be addressed now.

    What do you think the next step may be?
      My Computer


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

    A lot of work - for me

    I need to have a look at your COMPONENTS registry hive

    Please copy the C:\Windows\System32\config\COMPONENTS file (no extension) to your desktop and then compress it - upload the compressed file to your favoured fileshare site (preferably Dropbox or OneDrive) and post a link.
      My Computer


 
Page 1 of 2 12 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 07:16.
Find Us