W2K SP4 Update Rollup STILL sticks (after all the suggested stuff)

I've got the same problem discussed in other posts, but while the others seem
to have solved it by upgrading msxml 3.0 and MDAC, I didn't.

Here's what I've done:
Run MBSA old version. It detected what the other posts had said
Upgraded msxml 3.0 to the last version
Upgraded another couple of things i don't remember
Run MBSA new (2.0) version. Nothing detected
Upgraded MDAC to the last version (as suggested in the newsgroup)
Checked MDAC with component checker (OK).

After all that and a last reboot (you never know...) I checked again the
windows update site, but the update rollup was still there.

Any further suggestions?

Thanks in advance

Gwindor/Giampaolo

"Gwindor" <> wrote in message
news:4C93C911-6305-45C9-B537-...
> I've got the same problem discussed in other posts, but while the others seem
> to have solved it by upgrading msxml 3.0 and MDAC, I didn't.
>
> Here's what I've done:
> Run MBSA old version. It detected what the other posts had said
> Upgraded msxml 3.0 to the last version
> Upgraded another couple of things i don't remember
> Run MBSA new (2.0) version. Nothing detected
> Upgraded MDAC to the last version (as suggested in the newsgroup)
> Checked MDAC with component checker (OK).
>
> After all that and a last reboot (you never know...) I checked again the
> windows update site, but the update rollup was still there.
>
> Any further suggestions?
>
> Thanks in advance
>
> Gwindor/Giampaolo


Gwindor,


I assume you have read Dave Hawley's diagnostic session with me?


<Title>Windows 2000 SP4 Update Rollup 'Sticking' in Windows Update</TITLE>

http://www.microsoft.com/communities...=US&sloc=en-us


You're going to have to do something similar to provide some details
for us to work with.

BTW "Upgraded another couple of things i don't remember"
is an example of where we need more precision. <EG>


HTH

Robert Aldwinckle
---

Hi Robert, and thanks for answering.

> I assume you have read Dave Hawley's diagnostic session with me?

Of course I did. Where else do you think I could've got information about
all that MBSA and MDAC stuff?

> You're going to have to do something similar to provide some details
> for us to work with.

I really don't know what I can provide, since I basically did the same
things that where suggested in the other thread. Anyway, not to waste time,
can you please be more explicit as to what can be really useful? Windows
Update log? MBSA Log? Anything else?

> BTW "Upgraded another couple of things i don't remember"
> is an example of where we need more precision. <EG>

Indeed it was one and I remembered it, but I didn't mention it because
nobody else did and so it didn't seem important. I upgraded to the last SP of
Microsoft Jet, just to see it had some effects (needless to say it didn't).

Here's again what I've done, with a couple of integrations:
Run MBSA old version. It detected what the other posts had said
Upgraded msxml 3.0 to the last version
Upgraded Microsoft Jet
Run MBSA new (2.0) version. Nothing detected
Upgraded MDAC to the last version (this also upgraded again MSXML3.0 to
SP7)
Checked MDAC with component checker (OK)
Run all the Enterprise Update Scan Tools i could find (all OK).

Thank again

Gwindor

"Gwindor" <> wrote in message news:44C39019-3DE6-4385-9D64-...
> Hi Robert, and thanks for answering.
>
>> I assume you have read Dave Hawley's diagnostic session with me?
>
> Of course I did. Where else do you think I could've got information about
> all that MBSA and MDAC stuff?

Newer threads which refer to it?


>
>> You're going to have to do something similar to provide some details
>> for us to work with.
>
> I really don't know what I can provide, since I basically did the same
> things that where suggested in the other thread. Anyway, not to waste time,
> can you please be more explicit as to what can be really useful? Windows
> Update log? MBSA Log? Anything else?


Details. ;}

There is a lot of implicit feedback you could provide using that thread.
Did you try using the /v or /verbose options? Did you try looking for
other logs or diagnostics using the techniques I mentioned? Etc.


>
>> BTW "Upgraded another couple of things i don't remember"
>> is an example of where we need more precision. <EG>
>
> Indeed it was one and I remembered it, but I didn't mention it because
> nobody else did and so it didn't seem important. I upgraded to the last SP of
> Microsoft Jet, just to see it had some effects (needless to say it didn't).
>
> Here's again what I've done, with a couple of integrations:
> Run MBSA old version. It detected what the other posts had said
> Upgraded msxml 3.0 to the last version
> Upgraded Microsoft Jet
> Run MBSA new (2.0) version. Nothing detected
> Upgraded MDAC to the last version (this also upgraded again MSXML3.0 to
> SP7)
> Checked MDAC with component checker (OK)
> Run all the Enterprise Update Scan Tools i could find (all OK).


Were all of those additions done with the Rollup still installed
or did you uninstall it each time? You shouldn't try to install pre-reqs
after the update that requires them is installed. That's how regressions
can occur. BTW I don't know if those other components were pre-reqs
or co-reqs. If the update doesn't touch the modules of other needed
updates those updates would be called co-reqs. It is regressions or more
missing pre-reqs or co-reqs that we are trying to find. Unfortunately
Microsoft doesn't think about its updating as precisely as this and that's
why we have this much trouble occasionally, especially with mass updates
such as this one (IMO).

I would uninstall it, then reinstall it, then use the mbsacli /hf -v -z
command and see what it says. I know that it is not as comprehensive
an exception report as it once gave but I'm still hoping that we can find
something to reduce the complexity of this analysis.
Similarly, Dave reported that the Belarc Advisor missed some details. Perhaps it has been updated since then?

Could you please check Dave's assertion that the spuninst.exe
does not support either the /v or /verbose switch? The uninstall
and install logs really were not detailed enough to understand which
versions were being copied by them and equally importantly why.
It's not clear if he tried to use those options on the update.exe command
or not but knowing whether they are available would be helpful too.

Also, can you get the Rollup via AU? If so,have you tried letting AU
install it instead? A related question would be which agent(s) have you
used to install this update: WU, AU or MU?

Do you have access to another machine on which the Rollup has been
successfully installed? If so, I suspect it may be useful to compare its
Uninstall directory with yours (e.g. looking for version differences.)
Similarly, as I mentioned to Dave, depending on how the Uninstall
is constructed it may also be useful to use that list of modules as a way
to construct a script which would show you the list of versions that each
machine is now operating with. E.g., I suspect that finding differences
there would explain your symptom. Etc.

There are still more ideas left in my discussion with Dave
which I believe could be relevant in your case too
but I won't bother trying to restate them all here.


HTH

Robert
---

"Robert Aldwinckle" wrote:

<cut>

Hello Robert.

This is just to thank you again for your incredible kindness, but I think
I'll give up with this thing. I've already wasted a couple of days trying to
fix it and I think it's enough. After all everything seems to work fine and
there's definitely a bunch of things which are worse than just seeing an
entry sticking in the updates list.

Thanks again and let's hope in Update Rollup #2 :-)

Good Bye

Gwindor