"sd" <> wrote in message
news:ddiqdt$o9j$
....
> here's the KB893756.log (for one of the updates that fails)
There are clues in your log worth further diagnosis IMO
but it would be even more useful to you if you had another log
of a successful install to compare with. E.g. I suspect that
you would find at least one difference here:
> 2.719: GetGenericPathNameWithRoot: Unable to open HKLM,
> SOFTWARE\Microsoft\ResKit\NameSpace\Windows 2000 Resource Kit, 0x2.
> 2.719: SetDynamicDirectoryId: Failure while generating dynamic path, 0xf111
BTW that code should be converted to decimal before searching
for clues about its meaning:
http://www.microsoft.com/technet/pro.../winupdte.mspx
(MSN search for
61713 site:microsoft.com
)
<quote>
61713
STATUS_INVALID_DIRID_SECTION
</quote>
Uh huh. That tells us a lot... ;]
As PA Bear indicated all signs are pointing to a permissions problem
either for the registry or for the file system.
If you don't get anywhere trying to change permissions (e.g. the way that
others have done successfully) I would try adding /verbose to the
command line options of a manual install and see if that gives you any
clearer picture of what's wrong. Note: so far people who have tried this
suggestion with me haven't had much luck finding where the /verbose
log is going. In that case I have suggested that they do a file find
(e.g. Win-F) for all files which were changed on the day of the update
and sort that result by Date Modified (thus sorting the list by timestamp
and allowing you to see files listed within the minutes that the install
was active.) Alternatively or in addition, I would run FileMon filtering on
SoftwareDistribution;Update;CatRoot to supplement (and identify) any
logs which the install produces. There is also a verbose option for the
download and install (if done by WU) documented in KB902093.
HTH
Robert Aldwinckle
---
Similar Threads
Linear Mode
