"istoba" <> wrote in message
news:5A76E90E-6735-4DCF-808B-
....
> Hi everyone,
> I just experienced this problem today. A lot of the feedback on this forum
> for this particular issue has been great, and thorough, but I still haven't
> been able to resolve this issue.
>
> Here's what I've tried:
> Tried to install MCE2005 Rollup 2, failed
> Uninstalled KB886904, tried to install MCE2005 Rollup 2, failed
> Installed KB886903, tried to install MCE2005 Rollup 2, failed
> Tried everything listed in http://support.microsoft.com/kb/822798, still the
> Rollup 2 install failed, with the same 0x643 error code.
>
>
> Someone else posted that they removed KB891781 and KB904706 and they were
> successful at getting MCE2005 Rollup 2 installed.
> I started to uninstall KB891781, but it gave a warning with a list of
> virtually every program I have installed, saying they may not work if I
> uninstall it.
When did you install it? If the list of programs is just stuff you installed
subsequently I suspect it could be just a warning that any dependencies
involved with the modules in that update are not known.
In this particular case there is only one module being replaced
so I can't imagine what kind of dependencies there would have
to be to allow one ActiveX control to make all subsequent application
installs invalid. <w>
http://www.microsoft.com/technet/sec.../ms05-013.mspx
<extract>Dhtmled.ocx
6.1.0.9232
11-Jan-2005
01:00
128,512
SP2GDR
</extract>
> KB904706 states that it can't be uninstalled.
Give more details? Perhaps it just means that there is a superseding
update already installed. E.g. in order to uninstall it you may also have
to back out something else first.
Was there an uninstall log? Perhaps a /verbose log is available too?
Look in them for clues.
Alternatively use the file manifest from the associated security bulletin
to try to see the list of modules involved and use that list to check your
actual current versions of them. If some have later version numbers
chances are that you have a superseding update applied which would
have to be backed off first.
Oh. (just looked at KB904706.) Have you checked that you are trying
to install the correct version of the update? (KB909596)
Is MUI involved? (KB910415) Looks as if your version of quartz.dll
may be a key determining factor. (It would probably be a good idea
to post it.)
However, note especially that the suggestion you are trying
is several months old so it is quite conceivable that
a superseding update could have come along in the meantime
which the other poster would not have had to refer to.
> I tried doing a system restore to an earlier date before those 2 KB updates
> were installed, and it failed, giving no reason.
Ooo. I suspect that is going to make diagnosis a lot harder.
E.g. what all did it back out? (Makes the question about superseding
updates possibly moot.)
Anyway, try finding out the current state of the modules involved.
You may still be able to puzzle out a way to use the other poster's
tip or try diagnosing what is wrong in your particular case.
Unfortunately as is often the case with rollups I can find no list
of modules involved. You may have to infer one from the update's
log or verbose log.
>
> Anyone else have any other ideas, suggestions, solutions?
In a thread last year I helped Dave Hawley discover that
the W2Ksp4 Rollup has some undocumented pre-reqs.
If the same condition is occurring in this rollup on your OS
you may have to do a similar diagnosis.
Unfortunately the thread was never marked as useful
and got aged off the Communities server.
I had to refind it for someone later on on Google.
Hopefully it is still there...
http://groups.google.com/group/micro...a15f60347e25e0
>
> Thanks!
> Paul
HTH
Robert Aldwinckle
---