Windows Update Failure, Error Code 80070002

[richardchinnis]

I've exhausted my ability to try to solve this one on my own. I've run all of the automated fixes I can find from Microsoft, so I'm asking for some more targeted help.

I'm running Windows 7 Pro x64 SP1. I have run the System Update Readiness Tool (May '14). It completes successfully, but I don't know what it actually accomplishes because it doesn't make things better as far as I can tell.

Here is my windows update screenshot:
View attachment 330898

Here is what I see when I try to run SFC:
View attachment 330899

Here's my CBS zip file:
View attachment 330900

Thanks in advance for the help. Let me know if there is more info you guys need from me.

 

[archer]

Hi, Welcome to SF.

Try this,

Windows Update error 80070002 - Windows Help

 

[richardchinnis]

Thanks Archer.

I've gone through that process innumerable times, including after running SURT, after rebooting, etc. I've tried just about every permutation I can come up with.

 

[Gary]

I think what you have to do is to make sure that Windows Module in services is set to manual and that Automatic Updates are turned off. I set mine to notify and download but do not install. As I said it seems to be OK now as I can get to WU.

Sorry wrong thread.

 

[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)

 

[richardchinnis]

Hi Noel, I'm a bit confused. I honestly can't figure out what info my original post is lacking. Can you give me a bit more guidance?

Thanks for your patience.

 

[NoelDP]

Sorry - I missed your CBS zip yesterday!

Here's the errors from CheckSUR..

Checking Component Store
(f) CSI Missing Identity 0x00000000 appid wiahp001.inf_71bf3856ed364e35_6.1.7600.16385_Ebc6374fDcadec8c 
(f) CSI Corrupt Identity 0xC0150019 wiaky002.inf, Culpure=neupral, Type=driverUpdate, wiaky002.inf_31bf3856ad364e35_6.1.7600.16385_f9c4413b766f8371 Bad identity
(f) CSI Corrupt Identity 0xC0150019 wialx002.inf, Culpure=neuTral, TyPe=driverUpdate, wialx002.inf_31bf3856ad364e35_6.1.7600.16385_04a3e5f268636849 Bad identity
(f) CSI Corrupt Identity 0xC0150019 wIaep002.inf, Culture=neutral, Type=driverUpdate, Version96.1.7600.16385, PublicKEyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS wiaep002.inf_31bf3856ad364e35_6.1.7600.16385_507ad8fbb53e8f70 Bad identity
(f) CSI Missing Identity 0x00000000 appid b40d2f89c5d..b79d21fa43d_31bf3856ad364e35_6.1.7601.17577_62d5D3363648575f 
(f) CSI Missing Identity 0x00000000 appid wiaep003.inf_31bf3856ad364e35_6.1.7604.16385_1103eb30ge5ccbd9 
(f) CSI Corrupt Identity 0xC0150019 4807efaf1963263319edc02fec886cb7, Culture=neutral, Version=6.1.7601.17577, PublicOeyToken=31bf3856ad364e35, ProceSsorArchitectureamd64, versionSgope=NonSxS 4807efaf196..42fec886cb7_31bf7856ad364e35_6.17601.17577_9c58D3ecff419e9f Bad identity
(f) CSI Missing Deployment Key 0x00000000 e03064a16e8..4ef84fbcc59_31bf3856ad364e35_6.1.7601.21680_8beee53d1a9495e7 HKLM\Components\CanonicalData\Deployments 
(f) CSI Missing Deployment Key 0x00000000 4807efaf196..02fec886cb7_31bf3856ad364e35_6.1.7601.17577_9c58d3ecff419e9f HKLM\Components\CanonicalData\Deployments 
(f) CSI Missing Deployment Key 0x00000000 c4af0efa31c..aeae08d901a_31bf3856ad364e35_6.1.7601.21680_810e94de2e4f07ad HKLM\Components\CanonicalData\Deployments 
(f) CSI Missing Deployment Key 0x00000000 nvraid.inf_31bf3856ad364e35_6.1.7601.21680_983ab4c5eef82cad HKLM\Components\CanonicalData\Deployments 
(f) CSI Missing Deployment Key 0x00000000 wiacn001.inf_31bf3856ad364e35_6.1.7600.16385_95eb24d2d4a0a55b HKLM\Components\CanonicalData\Deployments 
(f) CSI Missing Deployment Key 0x00000000 b40d2b89c5d..f79d21fa03d_31bf3856ad364e35_6.1.7601.17577_62d5d3363648575f HKLM\Components\CanonicalData\Deployments 
(f) CSI Missing Deployment Key 0x00000000 74653de1029..1794f35f181_31bf3856ad364e35_6.1.7601.17577_5c75deb828587011 HKLM\Components\CanonicalData\Deployments 
(f) CSI C Mark Deployment Missing 0x00000000 c!wiaHp001.inF_31bf386ad364e35_6.1.7600.16385_ebc6374fdcadec8c amd64_wiahp001.inf_31bf3856ad364e35_6.1.7600.16385_none_ebc6374fdcadec8c 
(f) CSI C Mark Deployment Missing 0x00000000 c!wiaap003.inf_31bf3856ad364e35_6.1.7600.16385_5103eb30ce5ccbd9 amd64_wiaep003.inf_31bf3856ad364e35_6.1.7600.16385_none_5103eb30ce5ccbd9 
(f) CSI C Mark Deployment Not Marked 0x00000000 c!usbstor.inf_31bf3856ad364e35_6.1.7601.21680_a6e64054c7cca389 amd64_usbstor.inf_31bf3856ad364e35_6.1.7601.21680_none_a6e64054c7cca389 
(f) CSI C Mark Deployment Missing 0x00000000 c!wialx002.inF_31bf3856ad364e35_6.1.7600.16385_04a3e5f268636809 amd64_wialx002.inf_31bf3856ad364e35_6.1.7600.16385_none_04a3e5f268636849 
(f) CSI Missing Winning Component Key 0x00000000 amd64_usbstor.inf_31bf3856ad364e35_6.1.7601.17577_none_a66e757baea0992f

There's a fair number of bitflips there - which means that there's a possibility that either RAM or processor are failing.

Please follow the tutorial here - http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html to check out the RAM (run at least three full passes) and see what it says.

If it passes OK, then we can get working on a fix -

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.

 

[richardchinnis]

Yeah, I'm certain it was bad RAM that caused it. I was fighting all sorts of issues before I finally discovered two bad sticks and replaced them. The current RAM has passed a 24-hour Memtest86+ test.

Here's a link to the COMPONENTS zip file.

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

 

[NoelDP]

There are a LOT of bitflips there that CheckSUR didn't find. You may want to consider the possibility of a repair install before we go much further.

Here's a first-fix attempt, so we'll see how it looks after this.


I've uploaded a file - rchaa.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\rchaa\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.

 

[richardchinnis]

All commands completed successfully.

New CBS.zip
View attachment 331199

 

[NoelDP]

Here's the new list of errors...

Checking Component Store
(f) CSI Corrupt Identity 0xC0150019 wiaky002.inf, Culture=neutral, Type=driverUpdate, wiaky002.inf_31bf3856ad364e35_6.1.7600.16385_f9c4413b766f8371 Bad identity
(f) CSI Corrupt Identity 0xC0150019 wialx002.inf, Culpure=neutral, Type=driverUpdate, wialx002.inf_31bf3856ad364e35_6.1.7600.16385_04a3e5f268636849 Bad identity
(f) CSI Missing Identity 0x00000000 appid wiaep003.inf_31bf3856ad364e35_6.1.7604.16385_1103eb30ge5ccbd9 
(f) CSI Corrupt Identity 0xC0150017 4807efaf1963263319edc02fec886cb7, Culture=neutral, Version=6.1.7601.17577, PublicOeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS 4807efaf196..42fec886cb7_31bf7856ad364e35_6.1.7601.17577_9c58D3ecff419e9f Bad identity
(f) CSI Missing Identity 0x00000000 appid wiahp001.inf_71bf3856ed364e35_6.1.7600.16385_ebc6374fDcadec8c 
(f) CSI Missing Identity 0x00000000 appid b40d2f89c5d..b79d21fa43d_31bf3856ad364e35_6.1.7601.17577_62d5d3363648575f 
(f) CSI Missing Deployment Key 0x00000000 e03064a16e8..4ef84fbcc59_31bf3856ad364e35_6.1.7601.21680_8beee53d1a9495e7 HKLM\Components\CanonicalData\Deployments 
(f) CSI Missing Deployment Key 0x00000000 4807efaf196..02fec886cb7_31bf3856ad364e35_6.1.7601.17577_9c58d3ecff419e9f HKLM\Components\CanonicalData\Deployments 
(f) CSI Missing Deployment Key 0x00000000 c4af0efa31c..aeae08d901a_31bf3856ad364e35_6.1.7601.21680_810e94de2e4f07ad HKLM\Components\CanonicalData\Deployments 
(f) CSI Missing Deployment Key 0x00000000 nvraid.inf_31bf3856ad364e35_6.1.7601.21680_983ab4c5eef82cad HKLM\Components\CanonicalData\Deployments 
(f) CSI Missing Deployment Key 0x00000000 wiacn001.inf_31bf3856ad364e35_6.1.7600.16385_95eb24d2d4a0a55b HKLM\Components\CanonicalData\Deployments 
(f) CSI Missing Deployment Key 0x00000000 b40d2b89c5d..f79d21fa03d_31bf3856ad364e35_6.1.7601.17577_62d5d3363648575f HKLM\Components\CanonicalData\Deployments 
(f) CSI Missing Deployment Key 0x00000000 74653de1029..1794f35f181_31bf3856ad364e35_6.1.7601.17577_5c75deb828587011 HKLM\Components\CanonicalData\Deployments 
(f) CSI C Mark Deployment Missing 0x00000000 c!wiahp001.inf_31bf386ad364e35_6.1.7600.16385_ebc6374fdcadec8c amd64_wiahp001.inf_31bf3856ad364e35_6.1.7600.16385_none_ebc6374fdcadec8c 
(f) CSI C Mark Deployment Missing 0x00000000 c!wiaap003.inf_31bf3856ad364e35_6.1.7600.16385_5103eb30ce5ccbd9 amd64_wiaep003.inf_31bf3856ad364e35_6.1.7600.16385_none_5103eb30ce5ccbd9 
(f) CSI Missing C Mark 0x00000000 c!wiaep002.inf_31bf3856ad364e35_6.1.7600.16385_507ad8fbb53e8f70 amd64_wiaep002.inf_31bf3856ad364e35_6.1.7600.16385_none_507ad8fbb53e8f70 Missing c!
(fix) CSI Missing C Mark CSI Registry Item Repaired c!wiaep002.inf_31bf3856ad364e35_6.1.7600.16385_507ad8fbb53e8f70 successfully added to amd64_wiaep002.inf_31bf3856ad364e35_6.1.7600.16385_none_507ad8fbb53e8f70
(f) CSI C Mark Deployment Not Marked 0x00000000 c!usbstor.inf_31bf3856ad364e35_6.1.7601.21680_a6e64054c7cca389 amd64_usbstor.inf_31bf3856ad364e35_6.1.7601.21680_none_a6e64054c7cca389 
(f) CSI C Mark Deployment Missing 0x00000000 c!wialx002.inf_31bf3856ad364e35_6.1.7600.16385_04a3e5f268636809 amd64_wialx002.inf_31bf3856ad364e35_6.1.7600.16385_none_04a3e5f268636849 
(f) CSI Missing Winning Component Key 0x00000000 amd64_usbstor.inf_31bf3856ad364e35_6.1.7601.17577_none_a66e757baea0992f

I'll see what I can do with them...

 

[NoelDP]

Hokay...
Round 2...



I've uploaded a file - rchab.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\rchab\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.

 

[richardchinnis]

All commands completed successfully.

CBS.zip #3
View attachment 331250

 

[NoelDP]

Hmmm - not as successful as I'd hoped.

(f) CSI Corrupt Identity 0xC0150019 wiaky002.inf, Culture=neutral, Type=driverUpdate, wiaky002.inf_31bf3856ad364e35_6.1.7600.16385_f9c4413b766f8371 Bad identity
(f) CSI Missing Identity 0x00000000 appid wiahp001.inf_31bf3856ed364e35_6.1.7600.16385_ebc6374fDcadec8c 
(f) CSI Corrupt Identity 0xC0150019 wialx002.inf, Culture=neutral, Type=driverUpdate, wialx002.inf_31bf3856ad364e35_6.1.7600.16385_04a3e5f268636849 Bad identity
(f) CSI Missing Identity 0x00000000 appid wiaep003.inf_31bf3856ad364e35_6.1.7604.16385_1103eb30ge5ccbd9 
(f) CSI Missing Identity 0x00000000 appid b40d2f89c5d..b79d21fa43d_31bf3856ad364e35_6.1.7601.17577_62d5d3363648575f 
(f) CSI Corrupt Deployment Keyform 0x00000000 appid 4807efaf196..42fec886cb7_31bf7856ad364e35_6.1.7601.17577_9c58d3ecff419e9f appid and keyform do not match; keyform is wrong.
(f) CSI Missing Deployment Key 0x00000000 e03064a16e8..4ef84fbcc59_31bf3856ad364e35_6.1.7601.21680_8beee53d1a9495e7 HKLM\Components\CanonicalData\Deployments 
(f) CSI Missing Deployment Key 0x00000000 4807efaf196..02fec886cb7_31bf3856ad364e35_6.1.7601.17577_9c58d3ecff419e9f HKLM\Components\CanonicalData\Deployments 
(f) CSI Missing Deployment Key 0x00000000 wiahp001.inf_31bf3856ad364e35_6.1.7600.16385_ebc6374fdcadec8c HKLM\Components\CanonicalData\Deployments 
(f) CSI Missing Deployment Key 0x00000000 c4af0efa31c..aeae08d901a_31bf3856ad364e35_6.1.7601.21680_810e94de2e4f07ad HKLM\Components\CanonicalData\Deployments 
(f) CSI Missing Deployment Key 0x00000000 nvraid.inf_31bf3856ad364e35_6.1.7601.21680_983ab4c5eef82cad HKLM\Components\CanonicalData\Deployments 
(f) CSI Missing Deployment Key 0x00000000 wiacn001.inf_31bf3856ad364e35_6.1.7600.16385_95eb24d2d4a0a55b HKLM\Components\CanonicalData\Deployments 
(f) CSI Missing Deployment Key 0x00000000 b40d2b89c5d..f79d21fa03d_31bf3856ad364e35_6.1.7601.17577_62d5d3363648575f HKLM\Components\CanonicalData\Deployments 
(f) CSI Missing Deployment Key 0x00000000 74653de1029..1794f35f181_31bf3856ad364e35_6.1.7601.17577_5c75deb828587011 HKLM\Components\CanonicalData\Deployments 
(f) CSI C Mark Deployment Not Marked 0x00000000 c!usbstor.inf_31bf3856ad364e35_6.1.7601.21680_a6e64054c7cca389 amd64_usbstor.inf_31bf3856ad364e35_6.1.7601.21680_none_a6e64054c7cca389 
(f) CSI C Mark Deployment Missing 0x00000000 c!wiaep003.inf_31bf3856ad364e35_6.1.7600.16385_5103eb30ce5ccbd9 amd64_wiaep003.inf_31bf3856ad364e35_6.1.7600.16385_none_1103eb30ce5ccbd9 
(f) CSI Missing Winning Component Key 0x00000000 amd64_usbstor.inf_31bf3856ad364e35_6.1.7601.17577_none_a66e757baea0992f

Found 19 errors
Fixed 2 errors
CSI Missing Deployment Key Total count: 8
CSI Corrupt Deployment Keyform Total count: 1
CSI Corrupt Component Keyform Total count: 1
CSI Missing Identity Total count: 3
CSI Corrupt Identity Total count: 2
Fixed: CSI Corrupt Identity. Total count: 1
CSI Missing C Mark Total count: 1
Fixed: CSI Missing C Mark. Total count: 1
CSI C Mark Deployment Not Marked Total count: 1
CSI C Mark Deployment Missing Total count: 1
CSI Missing Winning Component Key Total count: 1

Let's see if I can do better this time...

 

[NoelDP]

OK - let's see how I did this time...

I've uploaded a file - rchac.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\rchac\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.

 

[richardchinnis]

#4

View attachment 331432

 

[NoelDP]

We're getting there (a bit like British Rail, but..)

(f) CSI Missing Identity 0x00000000 appid wiaep003.inf_31bf3856ad364e35_6.1.7604.16385_1103eb30ge5ccbd9 
(f) CSI Corrupt Deployment Keyform 0x00000000 appid 4807efaf196..02fec886cb7_31bf7856ad364e35_6.1.7601.17577_9c58d3ecff419e9f appid and keyform do not match; keyform is wrong.
(f) CSI Missing Deployment Key 0x00000000 4807efaf196..02fec886cb7_31bf3856ad364e35_6.1.7601.17577_9c58d3ecff419e9f HKLM\Components\CanonicalData\Deployments 
(f) CSI Corrupt Component Keyform 0x00000000 identity amd64_wiaep003.inf_31bf3856ad364e35_6.1.7600.16385_none_1103eb30ce5ccbd9 identity and keyform do not match; keyform is wrong.
(f) CSI Missing Winning Component Key 0x00000000 amd64_usbstor.inf_31bf3856ad364e35_6.1.7601.17577_none_a66e757baea0992f

are the remaining ones...
I'll see can do with them and post the new file when I can.

 

[NoelDP]

I think I've got them all now.

I've uploaded a file - rchad.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.

DEL C:\Windows\System32\config\COMPONENTS.OLD1
REN C:\Windows\System32\config\COMPONENTS COMPONENTS.OLD1
COPY %userprofile%\desktop\rchad\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.

 

[richardchinnis]

#5

View attachment 331496

And thanks for the persistence. I don't think I've received this much help from a complete stranger in any aspect of life.

 

[NoelDP]

Yay!
CheckSUR fixed the minor problems remaining, and is now happy
BUT...
There are a lot of errors remaining in the CBS data - so let's see what SFC /SCANNOW has to say...


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

post the new CBS.log file

IF the SFC /SCANNOW fails again '...could not perform...' then try running it 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)


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.

Then post the CBS.log file