Windows Update Error 80070002 & Windows Update Diag Error 0x8007370B

[woodcycl]

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.

 

[NoelDP]

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.

 

[woodcycl]

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.

 

[NoelDP]

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.

 

[woodcycl]

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.

 

[NoelDP]

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

 

[woodcycl]

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.

 

[NoelDP]

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

Summary:
Seconds executed: 1962
 [B]Found 55832 errors
 Fixed 55786 errors
[/B]  CSI Manifest Missing Total count: 11
[B]  CSI Missing Component Key Total count: 8105
[/B]  Fixed: CSI Missing Component Key.  Total count: 8105
[B]  CSI Missing Pinned Component Key Total count: 3502
[/B]  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
[B]  CSI Missing Identity Total count: 11610
[/B]  Fixed: CSI Missing Identity.  Total count: 11610
  CSI Corrupt Identity Total count: 22
  Fixed: CSI Corrupt Identity.  Total count: 6
  [B]CSI Missing C Mark Total count: 13851[/B]
  Fixed: CSI Missing C Mark.  Total count: 13851
  CSI Payload File Missing Total count: 6
  Fixed: CSI Payload File Missing.  Total count: 1
[B]  CSI F Mark Missing Total count: 22212
[/B]  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++ http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html for at least 3 passes (unless it fails earlier, which I suspect it will)

 

[woodcycl]

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?

 

[NoelDP]

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.

 

[NoelDP]

please run memtest again - with both sticks installed - for at least the three passes to check that their timings aren't still causing problems. Sometimes, even bath/batch variation on the same production line can cause matching-problems for the end-user. That's one reason why it's generally better to replace RAM in matched pairs rather than one at a time.

 

[woodcycl]

Again, thanks a ton! Here's the Component file as requested ...

https://dl.dropboxusercontent.com/u/19473469/COMPONENTS.zip

 

[woodcycl]

please run memtest again - with both sticks installed - for at least the three passes to check that their timings aren't still causing problems. Sometimes, even bath/batch variation on the same production line can cause matching-problems for the end-user. That's one reason why it's generally better to replace RAM in matched pairs rather than one at a time.

Will start another memtest now ...

 

[NoelDP]

I've managed to eliminate the obvious remaining errors, I think...


I've uploaded a file - wdcaa.zip - to my OneDrive at Noel's OneDrive
Please download and save it to your desktop.
Right-click on the file and select Extract All, and save to the default destination (which should be a folder on the desktop)

Create a new System Restore point

Open an Elevated Command Prompt, and run the following commands.

REN C:\Windows\System32\config\COMPONENTS COMPONENTS.OLD1
COPY %userprofile%\desktop\wdcaa\COMPONENTS C:\Windows\System32\config

If you get an error with either command, STOP THERE - do not reboot! - post for instructions.

Assuming both commands go OK, reboot, and run another CheckSUR scan - post the new CheckSUR.log file.

 

[woodcycl]

When attempting to rename ... it states that it is in use by another process. Safe mode possibly?

 

[NoelDP]

Yep - that doesn't surprise me too much.

 

[woodcycl]

Thoughts on next step?

 

[woodcycl]

Would it be best to rebuild with a fresh copy of windows at this point? Or, do you believe the issue can be resolved? Thank you again for all the help.

 

[woodcycl]

Haven't heard back ... so I'm performing a system recovery. Many thanks for the assistance ... appreciated.

 

[NoelDP]

Sorry about that - been too busy in resl life
Good luck with the recovery. Don't forget to backup your data to external storage first!