New
#31
Sorry about that. .. been a very busy week.
Back when I can string two thoughts together.
No worries, mate! Just glad you are still on the case!
Cheers,
Lrw
I wonder if Noel or anyone else can take another shot at this problem? Still getting the same error 80070002 when trying to run windows search for updates.
Regards,
Lrw
I ran the Windows Update Readiness tool and see this in the CheckSUR.log:
Is there anywhere that I can get the needed file? Is it on the install disk for Windows 7 or downloadable from somewhere? Or is there something else I need to look at first?Code:================================= Checking System Update Readiness. Binary Version 6.1.7601.22471 Package Version 26.0 2015-01-05 10:48 Checking Windows Servicing Packages Checking Package Manifests and Catalogs Checking Package Watchlist Checking Component Watchlist Checking Packages Checking Component Store (f) CSI Payload File Missing 0x00000000 prnca00z.inf amd64_prnca00z.inf_31bf3856ad364e35_6.1.7600.16385_none_ea189c313845a10e Summary: Seconds executed: 646 Found 1 errors CSI Payload File Missing Total count: 1
Regards,
Lrw
Sorry about that - you seem to have fallen off my ToDo list
I think the best thing to do is probably start from scratch again - almost.
Please run another SFC /SCANNOW and post the new CBS.log file created - also post a new copy of the COMPONENTS file
Hi Noel, It turns out that I was away for most of the Holidays anyway but hopefully we can get to the bottom of this.
I'll get a new sfcscan done ASAP and post the results.
Best Regards,
Lrw
Sorry - here's the operative error from the CBS log...
Unfortunately, my limited repair skills within the registry aren't sufficient - I can clear the immediate error, but there's significant corruption at lower levels than I fell happy attempting.Code:2015-01-05 16:12:49, Error CSI 00000004 (F) STATUS_OBJECT_NAME_NOT_FOUND #63046# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = (AllowAccessDenied), key = {provider=NULL, handle=0}, da = (KEY_READ|DELETE|KEY_WOW64_64KEY), oa = @0xf8ea90->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[217]"\Registry\Machine\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.17592 (win7sp1_gdr.110408-1631)\ComponentFamilies\amd64_microsoft-windows-p..-localspl-licensing_31bf386ad364e5_none_05bb766c7c3a33fa\v!6.17600.1685"; a:(OBJ_CASE_INSENSITIVE)}, disp = Unmapped disposition: 16312880 (0x00f8ea30))[gle=0xd0000034]
This means that your only real recourse is to a repair install.