Update Rollup 1 Win 2000 SP4 not detected after install (KB891861)

Hi,

I have the following problem. (Win 2000 SP 4 German Language Version)

I have downloaded and installed the Win2000 SP4 update rollup 1 Version 2
via the Windowsupdate Website using the V6 update version.

The Update was downloaded and installed successfully (Windows Update shows
successful install on final screen).

After reboot and again detecting updates with windowsupdate.microsoft.com,
the detection still show that update KB891861 is not installed, although the
installation was successful.

How can I correct this and tell the system that the installation was
successful.

Thanks in advance,
Michael

"michaelf" <> wrote in message
news:3139FEDA-C29D-4C50-BE73-
> [Subject: Update Rollup 1 Win 2000 SP4 not detected after install (KB891861)]
....


Have you seen Dave Hawley's thread?

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

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

Tried using MBSA 1.2.1? Etc.

You're going to have to do something similar to provide some details
for us to work with. Others have reported your symptom even after
doing the things which worked for him but so far nobody else has
tried to continue the diagnosis. (At least I haven't noticed any reports
of such attempts).

Hmm... perhaps I should qualify that last statement with this example
of someone who might have thought about trying it. My reply in here
should give you some more ideas too.

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


Good luck

Robert Aldwinckle
---


> Hi,
>
> I have the following problem. (Win 2000 SP 4 German Language Version)
>
> I have downloaded and installed the Win2000 SP4 update rollup 1 Version 2
> via the Windowsupdate Website using the V6 update version.
>
> The Update was downloaded and installed successfully (Windows Update shows
> successful install on final screen).
>
> After reboot and again detecting updates with windowsupdate.microsoft.com,
> the detection still show that update KB891861 is not installed, although the
> installation was successful.
>
> How can I correct this and tell the system that the installation was
> successful.
>
> Thanks in advance,
> Michael

Dear Robert,

thank you for your detailed answer..

> Have you seen Dave Hawley's thread?
>
> <Title>Windows 2000 SP4 Update Rollup 'Sticking' in Windows Update</TITLE>
>
> http://www.microsoft.com/communities...=US&sloc=en-us


Unfortunately the thread given above does not longer exist (thread not
found). However, I reconstructed to install the newest MSXML 3.0 and MDAC
etc..

I have installed MSXML 3.0 SP 7, MSXML 4.0 SP 2, MSXML 6.0 and MDAC 2.8.

>
> Tried using MBSA 1.2.1? Etc.

I use MBSA 2.0 (which says also "Update Rollup not installed", however I can
try to scan again with MBSA 1.2.1.

> My reply in here should give you some more ideas too.
>
> http://www.microsoft.com/communities...dc3&sloc=en-us

I have read the thread and will do the things proposed here.

I will get back to you, with the newest results.

Thanks again,
Michael

"michaelf" <> wrote in message
news:F6BE3828-0DAB-4129-AFA5-...
> Dear Robert,
>
> thank you for your detailed answer..
>
>> Have you seen Dave Hawley's thread?
>>
>> <Title>Windows 2000 SP4 Update Rollup 'Sticking' in Windows Update</TITLE>
>>
>> http://www.microsoft.com/communities...=US&sloc=en-us
>
>
> Unfortunately the thread given above does not longer exist (thread not
> found).


Thanks for mentioning this. I guess we will have to resort to Google Groups
archive then. Let's see if this works:
1. The tid= is part of the original Message-ID.
2. The original Message-ID woulld have been in uppercase
and had @microsoft.com appended to it.
3. Go to Google Groups Advanced search and construct what would have
been the original Message-ID
4. Apparently Google Groups doesn't care about the uppercasing?
(serendipity).
5. Click on the Subject to find

http://groups.google.com/group/micro...a15f60347e25e0


> However, I reconstructed to install the newest MSXML 3.0 and MDAC
> etc..
>
> I have installed MSXML 3.0 SP 7, MSXML 4.0 SP 2, MSXML 6.0 and MDAC 2.8.
>
>>
>> Tried using MBSA 1.2.1? Etc.
>
> I use MBSA 2.0 (which says also "Update Rollup not installed", however I can
> try to scan again with MBSA 1.2.1.


Yes. Dave found that that one was better for finding some missing pre-reqs.


>
>> My reply in here should give you some more ideas too.
>>
>> http://www.microsoft.com/communities...dc3&sloc=en-us
>
> I have read the thread and will do the things proposed here.


Yikes. It's a good thing that that one is still around in the web interface
because Google Groups appears to have missed it.

Nope. It has some kind of copy of it; rather the link I gave is some
kind of copy of the one Google Groups has, since the References
in the response contain the one that Google Groups has. <sigh/>

FWIW here's the message I meant to cite (final reply to gwindor)

Subject: Re: W2K SP4 Update Rollup STILL sticks (after all the suggested st
Date: Wed, 7 Sep 2005 14:05:58 -0400

Message-ID: <>
(Google Groups isn't putting Message-IDs into URLs now either.)

http://groups.google.com/group/micro...1?dmode=source


>
> I will get back to you, with the newest results.
>
> Thanks again,
> Michael


You're welcome.


Good luck

Robert
---

Dear Robert,

I found the missing thread listed below and read everything carefully.

> Thanks for mentioning this. I guess we will have to resort to Google Groups
> archive then. Let's see if this works:
> http://groups.google.com/group/micro...a15f60347e25e0

I installed MBSA 1.2.1 and checked for MSXML, MDAC and other missing
updates. MBSA 1.2.1 results were that everything is installed properly and no
missing things were found. I also installed msjet 4.0 newest version.

Scanning again by Windows update says that Update rollup 1 is still missing.

...well I think, I do the same as other users where the problem still
persists. I ignore it until the update rollup is released and hope that then
the update is detected properly by windowsupdate.

Thanks again for your help!

Best regards,
Michael

"michaelf" <> wrote in message
news:60E432E7-14EB-410A-8CC7-
....
> I installed MBSA 1.2.1 and checked for MSXML, MDAC and other missing
> updates. MBSA 1.2.1 results were that everything is installed properly and no
> missing things were found. I also installed msjet 4.0 newest version.
>
> Scanning again by Windows update says that Update rollup 1 is still missing.
>
> ..well I think, I do the same as other users where the problem still
> persists. I ignore it until the update rollup is released and hope that then
> the update is detected properly by windowsupdate.


That's too bad. The problem is that the tools you have now are less useful
for providing the necessary diagnostics. It used to be that hfnetchk from
the command line could show you discrepancies only in module versions.
Later (in MBSA 1.x) mbsacli -hf -z -v was supposed to substitute
for this functionality (and at one time I thought it did) but no more apparently.

If the new mbsacli -xmlout -catalog alternative (in MBSA 2.0)
is capable of providing even the same information which was once
in mssecure.xml nobody so far has shown us how.
And that would only provide a base for starting a scripting solution which
would be able to list all of the modules involved, their expected versions
and then be able to iterate through that list checking the actual versions
installed, reporting differences, etc.

I think the most disappointing thing is that the provided verbose
options are apparently useless for allowing people to even get
a full list of modules and versions being installed. That at least
would allow sites which have multiple machines to do their own
differencing on the verbose logs from failed and successful
installs and thus allow them to focus on a reduced set of modules
for further analysis.

I think that in the same way that there are separate checkers
for MDAC and MSXML support there should be one for
your OS rollups. The number of changed modules is just too
great to expect anybody to be able to manage that degree of
complexity using manual methods.

Such a checker would still be only a crutch though IMO.
Other OS provide tools for assisting with comprehensive
version management. I don't see why Windows shouldn't too.


>
> Thanks again for your help!
>
> Best regards,
> Michael


You're welcome.


Robert
---