Windows 7 update error 80070002

[TjaMat]

Windows 7 is not updating any more.
Did step one didn't change anything.
My cbs.zip file is more than 8 mb (its 20mb) what should I do?
It gives this error code 80070002.
It says most recent check for updates: never
Updates were installed: never

I can't start a sfc/scannow with command promt. This is also not possible in safemode.

Can anyone help to get windows to update?

 

[TjaMat]

Part of the cbs.zip file

 

[NoelDP]

Pleasefollow the WindowsUpdate Posting Instructions and postthe requested data



If thefile is too large (8MB compressed), remove the older CBSPersist cab files untilthe final file is below the limit - you can always post them separately afterzipping them. (the forum doesn't allow the upload of bare CAB files, for anumber of reasons)



Pleasealso post the C:\Windows\windowsudpate.log file

 

[TjaMat]

Thank you.

 

[NoelDP]

The CheckSUR log shows the following summary

Summary:
Seconds executed: 403
 Found 1 errors
  CSI Manifest Missing Total count: 1
Unavailable repair files:
 winsxs\manifests\x86_microsoft-windows-i..rendering.resources_31bf3856ad364e35_11.2.9600.17280_en-us_933d3ccb600776ac.manifest

I'll post a fix for that later, but I suspect that it's not related to your WU problem.

The WU log shows this errorsequence...

2015-07-03 09:23:26:334 1052 16c0 Setup SelfUpdate handler is not found.  It will be downloaded
2015-07-03 09:23:26:335 1052 16c0 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.320"
2015-07-03 09:23:29:602 1052 16c0 Setup WARNING: Cbs StartSession, error = 0x80070002
2015-07-03 09:23:29:625 1052 16c0 Setup FATAL: Applicability evaluation for setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.320" failed, error = 0x80070002
2015-07-03 09:23:29:625 1052 16c0 Setup FATAL: SelfUpdate check failed, err = 0x80070002

- which is a change on the earlier errors...

2015-06-23 14:50:52:793  912 181c Setup SelfUpdate handler is not found.  It will be downloaded
2015-06-23 14:50:52:793  912 181c Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.320"
2015-06-23 14:51:33:414  912 181c Setup WARNING: Cbs StartSession, error = 0x8007370A
2015-06-23 14:51:33:414  912 181c Setup FATAL: Applicability evaluation for setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.320" failed, error = 0x8007370A
2015-06-23 14:51:33:414  912 181c Setup FATAL: SelfUpdate check failed, err = 0x8007370A

I need to do some research on those before attempting to fix it

 

[NoelDP]

I've uploaded a file - tjmaa.zip - to my OneDrive at Noel's OneDrive

Please download and save it.
Right-click onthe downloaded file, and select Extract all…
Extract to thedefault location - which will create a new folder tjmaa in the same place.
Open this folder- there should be one folder inside it (Manifests)

Copy the content of the manifestsfolder (.manifest files) into this folder:

C:\Windows\Temp\CheckSur\Winsxs\Manifests

Now run the CheckSUR tool again (it may take a while)

Post the new CheckSUR.log file, and the CheckSUR.persist.log file.

 

[TjaMat]

Thank you.
These are the new CheckSUR.log and CheckSUR.persist.log

 

[NoelDP]

Good - CheckSUR is clear now.

Please attempt Windows Update again, and then post the C:\Windows\windowsupdate.log and C:\Windows\Logs\CBS\CBS.log files so I can see if anything has changed.

 

[TjaMat]

Still god the same error code for windows update
Here are these files

 

[NoelDP]

Here's the end of the CBS data...

2015-07-07 19:36:54, Info                  CBS    Startup processing thread terminated normally
2015-07-07 19:36:54, Error                 CSI    0000000b (F) STATUS_OBJECT_NAME_NOT_FOUND #65319# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = (AllowAccessDenied), key = {provider=NULL, handle=0}, da = (KEY_READ|DELETE|KEY_WOW64_64KEY), oa = @0xdcd4a0->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[217]"\Registry\Machine\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.18766 (win7sp1_gdr.150217-1551)\ComponentFamilies\amd64_microsoft-windows-ie-iexpress.resources_31bf3856ad364e35_fr-fr_daaed94793ae5ce4\v!9.4.8112.16421"; a:(OBJ_CASE_INSENSITIVE)}, disp = Unmapped disposition: 14472256 (0x00dcd440))[gle=0xd0000034]
2015-07-07 19:36:54, Error                 CSI    [EMAIL="0000000c@2015/7/7:17:36:54.292"]0000000c@2015/7/7:17:36:54.292[/EMAIL] (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]
2015-07-07 19:36:54, Error                 CSI    0000000d (F) STATUS_OBJECT_NAME_NOT_FOUND #65318# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = 0, key = {provider=NULL, handle=0}, da = (KEY_READ|DELETE|KEY_WOW64_64KEY), oa = @0xdcd4a0->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[217]"\Registry\Machine\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.18766 (win7sp1_gdr.150217-1551)\ComponentFamilies\amd64_microsoft-windows-ie-iexpress.resources_31bf3856ad364e35_fr-fr_daaed94793ae5ce4\v!9.4.8112.16421"; a:(OBJ_CASE_INSENSITIVE)}, disp = Unmapped disposition: 14473320 (0x00dcd868))[gle=0xd0000034]
2015-07-07 19:36:54, Error                 CSI    [EMAIL="0000000e@2015/7/7:17:36:54.323"]0000000e@2015/7/7:17:36:54.323[/EMAIL] (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]
2015-07-07 19:36:54, Error                 CSI    0000000f (F) STATUS_OBJECT_NAME_NOT_FOUND #65317# from Windows::Rtl::SystemImplementation::CKey::OpenExistingKey(f = 2, da = (KEY_READ|DELETE), oa = @0xdcd900, key = NULL, disp = (null))[gle=0xd0000034]
2015-07-07 19:36:54, Error                 CSI    00000010 (F) STATUS_OBJECT_NAME_NOT_FOUND #65312# from Windows::Rtl::SystemImplementation::CKey::DeleteRecursively(...)[gle=0xd0000034]
2015-07-07 19:36:54, Error                 CSI    00000011 (F) STATUS_OBJECT_NAME_NOT_FOUND #34941# from Windows::Rtl::SystemImplementation::CKey::DeleteRecursively(...)[gle=0xd0000034]
2015-07-07 19:36:54, Info                  CBS    Failed to get CSI store. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2015-07-07 19:36:54, Error                 CBS    Failed to initialize store parameters with boot drive:  and windows directory:  [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

I need to do some research on this - back when I find something (shout if you haven't heard in 48 hours!)

 

[TjaMat]

Shout, it has been 48 hours

 

[NoelDP]

Sorry about that - 11-hour work days are taking their toll
I'll get back to you tomorrow (promise!)

 

[TjaMat]

Just wondering if you had time to have a look in to it

 

[NoelDP]

Sorry about the delay...

Can you zip up and attach this file to your next post please?

C:\Windows\winsxs\Pending.xml

 

[TjaMat]

This is the only pending.xml I was able to find.

 

[NoelDP]

OK - I think we'll try a pending revert...

Reboot to the Repair Environment
as soon as the machine restarts, start tapping F8 - this should bring up the Advanced Boot Menu, at the top of which should be the option 'Repair my Computer'
Pick that
You'll have to log in with your username and password.

Pick the option to use a Command Prompt

At the command prompt, type

dism.exe /image:C:\ /cleanup-image /revertpendingactions

This is supposed to revert all pended updates, (If it fails the first time change the C:\ to D:\ and try again)

 

[TjaMat]

Alright I followed your instructions and got this back.

Deployment Image Servicing and Management tool
version:6.1.7600.16385

Error: 1639

The command-line is missing a required servicing command
for more info.....
The Dism lof file can be found at
X:\Windows\Logs\DISM\dism.log

What to do next?

 

[NoelDP]

That sounds like there's a missing space in your command -

dism.exe<space>/image:C:\<space>/cleanup-image<space>/revertpendingactions
or
dism.exe<space>/image:\<space>/cleanup-image<space>/revertpendingactions

 

[TjaMat]

Alright I followed your instructions and got this back. :C:

Deployment Image Servicing and Management tool
version:6.1.7600.16385

Error: 2

Unable to access the image
Make sure that the path and the Windows directory for the image exist and you have read permissions on the folderX:\Windows\Logs\DISM\dism.log


I got this back on : D :

Deployment Image Servicing and Management tool
version:6.1.7601.18489

Error: 87

The cleanup-image option is unknown
For more information, refer to the help by running DISM.exe /?.
The Dism lof file can be found at
X:\Windows\Logs\DISM\dism.log

What to do next?

 

[NoelDP]

Did you boot to the Repair Environment? - or just to Safe Mode?

The command will ONLY work in the repair environment.