Can not update

Frondar · 15 Jan 2013

My Windows Updater has stopped working and I need your help, please.

I get the error code 80070002 - Unknown error.
My CBS folder is attached.

I have used the System Update Readiness Tool and done a SFC scan - no change.

Thank you.

NoelDP · 15 Jan 2013

You have some serious corruption problems in the reports - I'd normally hand these to Tom to solve, be it's his exam week.

Here's the details of the CheckSUR results...

Code:

Checking Component Store
(f) CSI C Mark Deployment Missing 0x00000000 c!a1b0¬961d1f.µ2516c49ÿ4e1_31bj3856ad3r4e35_6.ô.7601.21747_2781c161d72e01f1 amd64_microsoft-windows-m..cursor-library-ansi_31bf3856ad364e35_6.1.7601.21747_none_acdc7a2fd087986e 
(f) CSI C Mark Deployment Missing 0x00000000 c!0251d7be90b..34dd960851b_31bf3856ad364e35_6.ê.7601.1632_fe4t3bb890030e5 amd64_microsoft-windows-m..drivermanager-trace_31bf3856ad364e35_6.1.7601.17632_none_dd81f362582b9265 
(f) CSI C Mark Deployment Missing 0x00000000 c!9f5ef6d28c2..02f083e90ec_31bf3856ad3
4e35_6..7601.2¥747_9b3±3c4166e1e24 amd64_microsoft-windows-m..sor-library-unicode_31bf3856ad364e35_6.1.7601.21747_none_cf64bd82be6eec44 
(f) CSI C Mark Deployment Missing 0x00000000 c!eeb24a67e40.pe9d1dfahe9a_31bø3856ad3º4e35_6.‘.7601.2747_f94e0906c0631db5 x86_microsoft-windows-m..simple-provider-dll_31bf3856ad364e35_6.1.7601.21747_none_c204b9893c68027d 
(f) CSI C Mark Deployment Missing 0x00000000 c!3ed1(571a5d.µ9ea532fd73c_31bæ3856ad3¯4e35_6.«.7601.1w632_473N94496f911471 amd64_microsoft-windows-m..sor-library-unicode_31bf3856ad364e35_6.1.7601.17632_none_cee0ef31a54db1d6 
(f) CSI C Mark Deployment Missing 0x00000000 c!a1b0µ961d1f.ç2516c49¿4e1_31bë3856ad3(4e35_6.°.7601.21747_2781c161d72e01f1 amd64_a1b01961d1ffa7e5666cc2516c49f4e1_31bf3856ad364e35_6.1.7601.21747_none_2781c161d72e01f1

...and the SFC log shows no evidence that the SFC actually ran at all.
What it does show is....

Code:

Line 49467: 2013-01-15 16:59:41, Error                 CSI    00000004 (F) STATUS_OBJECT_NAME_NOT_FOUND #60540# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = (AllowAccessDenied), key = {provider=NULL, handle=0}, da = (KEY_READ|DELETE|KEY_WOW64_64KEY), oa = @0x17ee870->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[214]"\Registry\Machine\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.17592 (win7sp1_gdr.110408-1631)\ComponentFamilies\amd64_microsoft-windows-nfs-clientlocalui-d_31bf3856ad364e35_ngne_d491\u00eadfbfd3e=f6d\v!6.1.\u00f0601.1754"; a:(OBJ_CASE_INSENSITIVE)}, disp = Unmapped disposition: 25094160 (0x017ee810))[gle=0xd0000034]
 Line 49468: 2013-01-15 16:59:41, Error                 CSI    00000005@2013/1/15:15:59:41.759 (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)
 Line 49470: 2013-01-15 16:59:42, Error                 CSI    00000006 (F) STATUS_OBJECT_NAME_NOT_FOUND #60539# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = 0, key = {provider=NULL, handle=0}, da = (KEY_READ|DELETE|KEY_WOW64_64KEY), oa = @0x17ee870->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[214]"\Registry\Machine\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.17592 (win7sp1_gdr.110408-1631)\ComponentFamilies\amd64_microsoft-windows-nfs-clientlocalui-d_31bf3856ad364e35_ngne_d491\u00eadfbfd3e=f6d\v!6.1.\u00f0601.1754"; a:(OBJ_CASE_INSENSITIVE)}, disp = Unmapped disposition: 25095224 (0x017eec38))[gle=0xd0000034]
 Line 49471: 2013-01-15 16:59:42, Error                 CSI    00000007@2013/1/15:15:59:42.610 (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)
 Line 49473: 2013-01-15 16:59:42, Error                 CSI    00000008 (F) STATUS_OBJECT_NAME_NOT_FOUND #60538# from Windows::Rtl::SystemImplementation::CKey::OpenExistingKey(f = 2, da = (KEY_READ|DELETE), oa = @0x17eecd0, key = NULL, disp = (null))[gle=0xd0000034]
 Line 49474: 2013-01-15 16:59:42, Error                 CSI    00000009 (F) STATUS_OBJECT_NAME_NOT_FOUND #60533# from Windows::Rtl::SystemImplementation::CKey::DeleteRecursively(...)[gle=0xd0000034]
 Line 49475: 2013-01-15 16:59:42, Error                 CSI    0000000a (F) STATUS_OBJECT_NAME_NOT_FOUND #104# from Windows::Rtl::SystemImplementation::CKey::DeleteRecursively(...)[gle=0xd0000034]
 Line 49480: 2013-01-15 16:59:43, Error                 CSI    0000000b (F) STATUS_OBJECT_NAME_NOT_FOUND #129729# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = (AllowAccessDenied), key = {provider=NULL, handle=0}, da = (KEY_READ|DELETE|KEY_WOW64_64KEY), oa = @0xc9d1b0->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[214]"\Registry\Machine\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.17592 (win7sp1_gdr.110408-1631)\ComponentFamilies\amd64_microsoft-windows-nfs-clientlocalui-d_31bf3856ad364e35_ngne_d491\u00eadfbfd3e=f6d\v!6.1.\u00f0601.1754"; a:(OBJ_CASE_INSENSITIVE)}, disp = Unmapped disposition: 13226320 (0x00c9d150))[gle=0xd0000034]
 Line 49481: 2013-01-15 16:59:43, Error                 CSI    0000000c@2013/1/15:15:59:43.022 (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)
 Line 49483: 2013-01-15 16:59:43, Error                 CSI    0000000d (F) STATUS_OBJECT_NAME_NOT_FOUND #129728# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = 0, key = {provider=NULL, handle=0}, da = (KEY_READ|DELETE|KEY_WOW64_64KEY), oa = @0xc9d1b0->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[214]"\Registry\Machine\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.17592 (win7sp1_gdr.110408-1631)\ComponentFamilies\amd64_microsoft-windows-nfs-clientlocalui-d_31bf3856ad364e35_ngne_d491\u00eadfbfd3e=f6d\v!6.1.\u00f0601.1754"; a:(OBJ_CASE_INSENSITIVE)}, disp = Unmapped disposition: 13227384 (0x00c9d578))[gle=0xd0000034]
 Line 49484: 2013-01-15 16:59:43, Error                 CSI    0000000e@2013/1/15:15:59:43.044 (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)
 Line 49486: 2013-01-15 16:59:43, Error                 CSI    0000000f (F) STATUS_OBJECT_NAME_NOT_FOUND #129727# from Windows::Rtl::SystemImplementation::CKey::OpenExistingKey(f = 2, da = (KEY_READ|DELETE), oa = @0xc9d610, key = NULL, disp = (null))[gle=0xd0000034]
 Line 49487: 2013-01-15 16:59:43, Error                 CSI    00000010 (F) STATUS_OBJECT_NAME_NOT_FOUND #129722# from Windows::Rtl::SystemImplementation::CKey::DeleteRecursively(...)[gle=0xd0000034]
 Line 49488: 2013-01-15 16:59:43, Error                 CSI    00000011 (F) STATUS_OBJECT_NAME_NOT_FOUND #69293# from Windows::Rtl::SystemImplementation::CKey::DeleteRecursively(...)[gle=0xd0000034]
 Line 49490: 2013-01-15 16:59:43, Error                 CBS    Failed to initialize store parameters with boot drive:  and windows directory:  [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

I'll have to research the proper fix procedures for these errors - back later when I have some idea of what's needed, and what's possible.

Frondar · 15 Jan 2013

Well, that's unsettling...

I appreciate you taking the time to do this.

tom982 · 15 Jan 2013

I can do it on Thursday if you want? I have exams tomorrow and Thursday, then the following Tuesday and it's a really easy one on the Tuesday so I don't mind taking on some threads.

It's so strange how the bitflips have lined up like this:

Code:

(f) CSI C Mark Deployment Missing 0x00000000 c!eeb24a67e40.pe9d1dfahe9a_31bø3856ad3º4e35_6.‘.7601.2747_f94e0906c0631db5 x86_microsoft-windows-m..simple-provider-dll_31bf3856ad364e35_6.1.7601.21747_none_c204b9893c68027d  
(f) CSI C Mark Deployment Missing 0x00000000 c!3ed1(571a5d.µ9ea532fd73c_31bæ3856ad3¯4e35_6.«.7601.1w632_473N94496f911471   amd64_microsoft-windows-m..sor-library-unicode_31bf3856ad364e35_6.1.7601.17632_none_cee0ef31a54db1d6   
(f) CSI C Mark Deployment Missing 0x00000000 c!a1b0µ961d1f.ç2516c49¿4e1_31bë3856ad3(4e35_6.°.7601.21747_2781c161d72e01f1 amd64_a1b01961d1ffa7e5666cc2516c49f4e1_31bf3856ad364e35_6.1.7601.21747_none_2781c161d72e01f1

NoelDP · 15 Jan 2013

(I'd seen the correspondence - but it hadn't registered)

If the OP is happy to wait until then, I'm more than happy to leave it to you - at least he might end up with a working system then :)

I'm still very much in the learning phase with these errors.

tom982 · 15 Jan 2013

I'll try and explain everything on Thursday then :) It's no black magic!

Frondar · 16 Jan 2013

I can wait till Thursday. :)

tom982 · 17 Jan 2013

Hi Frondar,

Again, sorry for the delay. But I'm free to help now (apart from Monday and Tuesday).

I would like you to upload your COMPONENTS hive please, so I can find a little more information about your problem:

C:\Windows\system32\config\COMPONENTS (it has no file extension)

This file will be too big to upload as an attachment here. So I would recommend uploading it to your Dropbox, Skydrive or file-sharing website of your choice, of which I would recommend: Free large file hosting. Send big files the easy way!

Then send me the link please.

Tom

Frondar · 18 Jan 2013

Hi Tom

I hope I did this right.
Download COMPONENTS.zip from Sendspace.com - send big files the easy way

Thanks again for helping me. :)

tom982 · 18 Jan 2013

@Noel,

I'll talk you through what I did to fix the corruption here :) Looking at the errors in the CheckSUR log, it's quite easy to see there's a fair bit of corruption in a few C marks, so firstly we begin by loading the components hive that Frondar kindly uploaded. I'm not 100% sure on what C marks are actually for, but I know that they reference another part of the registry, which is why the SURT is reporting that the C Mark Deployment is missing. I'll take the first entry as an example:

(f) CSI C Mark Deployment Missing 0x00000000 c!a1b0¬961d1f.µ2516c49ÿ4e1_31bj3856ad3r4e35_6.ô.7601.21747_2781c161d72e01f1 amd64_microsoft-windows-m..cursor-library-ansi_31bf3856ad364e35_6.1.7601.21747_none_acdc7a2fd087986e

This points to the following location:

HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\key\\data

So a quick Ctrl+F of the key name finds it for us. For this example (it may differ in other scenarios), you will see two values - one intact and one corrupt:

c!a1b0¬961d1f.µ2516c49ÿ4e1_31bj3856ad3r4e35_6.ô.7601.21747_2781c161d72e01f1
c!a1b01961d1f..2516c49f4e1_31bf3856ad364e35_6.1.7601.21747_2781c161d72e01f1

So although somewhere along the line Windows Update has successfully rebuilt the C mark, the corrupt one still remains. This is pointing to a non-existent key and that's why the SURT is kicking up a fuss. Solution: delete the corrupt one.

I've listed the rest of the errors in the following format. First line: SURT log entry, second line: corrupt value under key, third line: intact value.

(f) CSI C Mark Deployment Missing 0x00000000 c!a1b0¬961d1f.µ2516c49ÿ4e1_31bj3856ad3r4e35_6.ô.7601.21747_2781c161d72e01f1 amd64_microsoft-windows-m..cursor-library-ansi_31bf3856ad364e35_6.1.7601.21747_none_acdc7a2fd087986e
c!a1b0¬961d1f.µ2516c49ÿ4e1_31bj3856ad3r4e35_6.ô.7601.21747_2781c161d72e01f1
c!a1b01961d1f..2516c49f4e1_31bf3856ad364e35_6.1.7601.21747_2781c161d72e01f1

(f) CSI C Mark Deployment Missing 0x00000000 c!0251d7be90b..34dd960851b_31bf3856ad364e35_6.ê.7601.1 632_fe4t3bb890030e5 amd64_microsoft-windows-m..drivermanager-trace_31bf3856ad364e35_6.1.7601.17632_none_dd81f362582b9265
c!0251d7be90b..34dd960851b_31bf3856ad364e35_6.ê.7601.1 632_fe4t3bb890030e5
c!0251d7be90b..34dd960851b_31bf3856ad364e35_6.1.7601.17632_fe493bb8900c30e5

(f) CSI C Mark Deployment Missing 0x00000000 c!9f5ef6d28c2..02f083e90ec_31bf3856ad34e35_6..7601.2¥747_9b3±3c4166e1e24 amd64_microsoft-windows-m..sor-library-unicode_31bf3856ad364e35_6.1.7601.21747_none_cf64bd82be6eec44
c!9f5ef6d28c2..02f083e90ec_31bf3856ad3
4e35_6..7601.2¥747_9b3±3c4166e1e24

This one was a little trickier as there was only the corrupt value under that key, so I had to get the name from elsewhere. I loaded my hive and cross referenced it with that, to find that the correct name should be:

c!9f5ef6d28c2..02f083e90ec_31bf3856ad364e35_6.1.7601.21747_9b313c4166e61e24

(f) CSI C Mark Deployment Missing 0x00000000 c!eeb24a67e40.pe9d1dfahe9a_31bø3856ad3º4e35_6.‘.7601.2747_f94e0906c0631db5 x86_microsoft-windows-m..simple-provider-dll_31bf3856ad364e35_6.1.7601.21747_none_c204b9893c68027d
c!eeb24a67e40.pe9d1dfahe9a_31bø3856ad3º4e35_6.‘.7601.2747_f94e0906c0631db5
c!eeb21a67e40..e9d1dfaee9a_31bf3856ad364e35_6.1.7601.21747_f94e0906c0631db5

(f) CSI C Mark Deployment Missing 0x00000000 c!3ed1(571a5d.µ9ea532fd73c_31bæ3856ad3¯4e35_6.«.7601.1w632_473N94496f911471 amd64_microsoft-windows-m..sor-library-unicode_31bf3856ad364e35_6.1.7601.17632_none_cee0ef31a54db1d6
c!3ed1(571a5d.µ9ea532fd73c_31bæ3856ad3¯4e35_6.«.7601.1w632_473N94496f911471
c!3ed19571a5d..9ea532f473c_31bf3856ad364e35_6.1.7601.17632_473994496f911471

(f) CSI C Mark Deployment Missing 0x00000000 c!a1b0µ961d1f.ç2516c49¿4e1_31bë3856ad3(4e35_6.°.7601.21747_2781c161d72e01f1 amd64_a1b01961d1ffa7e5666cc2516c49f4e1_31bf3856ad364e35_6.1.7601.21747_none_2781c161d72e01f1
c!a1b0µ961d1f.ç2516c49¿4e1_31bë3856ad3(4e35_6.°.7601.21747_2781c161d72e01f1
c!a1b01961d1f..2516c49f4e1_31bf3856ad364e35_6.1.7601.21747_2781c161d72e01f1

As long as the correct value exists, you are safe to delete a corrupt one :)

@Frondar, could you download this file:

https://dl.dropbox.com/u/16537616/COMPONENTS.zip

Extract it to your Desktop. There should be one file inside called COMPONENTS (no extension). Then navigate to:

C:\Windows\system32\config\

And rename the COMPONENTS file in there to COMPONENTS.old

Then copy and paste the COMPONENTS file on your Desktop to the config folder :)

Reboot, run the SURT and post the CheckSUR.persist.log please!

Tom