Hi everybody,
I have tried installing the WU-Software-Update to V. 7.2.6001.788 now
several times (auto update and manual), still resulting in the same error
8007371C.
In microsoft error database, there is no such inquiery.
I have no clue, what to due.
Underneath is an excerpt from CBS.log after trying to update, I don't get
the context, perhaps you do.
Error CSI 00000036 (F) STATUS_OBJECT_NAME_NOT_FOUND
#43267# from
Windows::Rtl::SystemImplementation:
irectRegistryProvider::SysOpenKey(flg =
(AllowAccessDenied), key = {provider=NULL, handle=0}, da = (KEY_READ), oa =
@0x102e828->OBJECT_ATTRIBUTES {s:24; rd:NULL;
on:[24]"\Registry\machine\Schema"; a
OBJ_CASE_INSENSITIVE)}, disp = Unmapped
disposition: 16967612 (0x0102e7bc))[gle=0xd0000034]
Error CSI 00000037@2009/1/13:10:07:05.613 (F)
d:\rtm\base\wcp\sil\merged\ntu\ntsystem.cpp(3211): Error
STATUS_OBJECT_NAME_NOT_FOUND originated in function
Windows::Rtl::SystemImplementation:
irectRegistryProvider::SysOpenKey
expression: (null)
[gle=0x80004005]
THX for your help,
Maschdel
Machdel said:
Dear Darrell,
I now have run the Checksur program.
It took ages, but here is the result:
=================================
Checking System Update Readiness.
Version 6.0.6001.22275
2009-01-13 09:58
Checking Deployment Packages
Checking Package Manifests and catalogs.
Checking package watchlist.
Checking component watchlist.
Checking packages.
Checking component store
Checking SMI Store
Summary:
Milliseconds: 1838301
No errors detected
But my WU still refuses to function.
It still needs to update the Update Software itself, tries and fails giving
error 0x8007371C
Do you have another idea?
Great THX anyway,
Maschdel
"Darrell Gorter[MSFT]" said:
Hello Maschdel,
Did you run the checksur tool to check your system for corruption?
947821 Description of the System Update Readiness Tool for Windows Vista
and for Windows Server 2008
http://support.microsoft.com/default.aspx?scid=kb;EN-US;947821
Try running this tool and see if it helps, if it does not check it's log
file to see if it reports something else.
I suspect that some registry entries are not present or corrupted.
Thanks,
Darrell Gorter[MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights
--------------------