"Mark Hazebroek" <> wrote in message
news:F7558E25-297A-41F7-92BB-...
> Cumulative Security Update for Outlook Express 6 Service Pack 1 (KB837009)
> Keeps on showing up on my 2000 DC.
> windowsupdate.log shows the following: WARNING: Failed to evaluate Installed
> rule, updateId = {ED300F67-421C-4C08-B3BA-F35C55F3B427}.100, error =
> 0x80041017. Every time after the update is completed (succesfully!), the
> machine starts the sequence again and again. what is wrong?
The usual problem is having other OE updates installed which have
superseding modules for *some* of the modules which 837009 updates.
Apparently some of the other updates are not "cumulative" or do not have
837009 indicated as a pre-req.
Depending on which set of modules would be restored if you uninstalled
837009 or 823353 or ...(something else) I think that that should be a way
of getting the module versions to be less than or equal to the ones that
837009 wants to provide and hence make it fully installable. BTW notice
that in spite of the numbers that 823353 supersedes 837009.
What I would do is find all instances of inetcomm.dll (since it is one of
the modules which has been updated the most) in order to find all the
uninstall directories. Then I would use filever (from the Support Tools)
to list the versions of all the *.dll in each of those uninstall directories.
That would let you figure out for sure which uninstall would do what
and which order they should be done in if it looked as if you would have
to uninstall more than one.
An alternative approach if you aren't interested in diagnosing the cause
of the symptom would be to download the 837009 update and use the
/N:V switch on it to force the regression of any superseding modules.
This should be safe because 837009 is a true cumulative update and
because so far there are no other updates which contain supersets of
the modules it installs (otherwise you might be risking creating a set of
incompatible modules with such an approach.)
BTW that error code is very unusual. Please look at the Q837009.log
to see if it gives any more context for it.
Hmm... the last time I saw one of these it looked as if the user might
not have all the necessary services running.
http://groups.google.com/group/micro...ac273bb590efa0
(Google Groups search for
0x80041017 MSFT group:microsoft.*
)
Also later on in another subthread of that discussion Grace reported
a solution which apparently helped others with the OP's symptom.
Good luck
Robert Aldwinckle
---
Similar Threads
Linear Mode
