W2K looping update via WSUS

I have a Windows 2000 machine that is on a network which gets it's updates
from a server running WSUS.

This particular machine is stuck installing "Update Rollup 1 for Windows
2000 SP4 (KB891861)"

WSUS reports this as already installed on the client computer (It also lists
a load of successfull install events - one for each try - with a result code
of 0x00000000).

The event log on the client computer reports that the update was
successfully installed after each try.

After each install (except the very first attempt which required a re-start)
Windows Update on the client machine immediatley downloads the update again
and offers it for installation.

Does any one know why this may be looping and what the solution is?

Thanks,
Andrew

Hi,

Sometimes, if MDAC and/or MSXML 4 is not up to date, Windows Update/
Automatic Update doesn't see the Rollup 1 as installed:

From: "Dave Hawley" <>
Subject: Re: Windows 2000 SP4 Update Rollup "Sticking"
Date: Fri, 12 Aug 2005 16:21:01 -0700
Newsgroups: microsoft.public.windowsupdate
http://groups.google.co.uk/group/mic...e949fbb18d070a

In the thread in the link above Dave Hawley mentioned that the problem
seemed to be caused by

<quote>
....two components of Windows were out of date.
These were MS Data Access Components 2.8,
which needed to be upgraded to SP1, and MSXML 4.0,
which needed to be upgraded to SP2.
</quote>

He found this from running MBSA 1.2.1

There are specific version checker programs for both components:

How to check for MDAC version
http://support.microsoft.com/kb/301202/

Determine the Version of MSXML Parser Installed on a Computer
http://support.microsoft.com/kb/278674/


Regards,
Torgeir


Andrew Wright wrote:

> I have a Windows 2000 machine that is on a network which gets it's updates
> from a server running WSUS.
>
> This particular machine is stuck installing "Update Rollup 1 for Windows
> 2000 SP4 (KB891861)"
>
> WSUS reports this as already installed on the client computer (It also lists
> a load of successfull install events - one for each try - with a result code
> of 0x00000000).
>
> The event log on the client computer reports that the update was
> successfully installed after each try.
>
> After each install (except the very first attempt which required a re-start)
> Windows Update on the client machine immediatley downloads the update again
> and offers it for installation.
>
> Does any one know why this may be looping and what the solution is?
>
> Thanks,
> Andrew


--
torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway
Administration scripting examples and an ONLINE version of
the 1328 page Scripting Guide:
http://www.microsoft.com/technet/scr...r/default.mspx

Thanks for your help Torgeir - my problem is solved!

"Torgeir Bakken (MVP)" wrote:

> Hi,
>
> Sometimes, if MDAC and/or MSXML 4 is not up to date, Windows Update/
> Automatic Update doesn't see the Rollup 1 as installed:
>
> From: "Dave Hawley" <>
> Subject: Re: Windows 2000 SP4 Update Rollup "Sticking"
> Date: Fri, 12 Aug 2005 16:21:01 -0700
> Newsgroups: microsoft.public.windowsupdate
> http://groups.google.co.uk/group/mic...e949fbb18d070a
>
> In the thread in the link above Dave Hawley mentioned that the problem
> seemed to be caused by
>
> <quote>
> ....two components of Windows were out of date.
> These were MS Data Access Components 2.8,
> which needed to be upgraded to SP1, and MSXML 4.0,
> which needed to be upgraded to SP2.
> </quote>
>
> He found this from running MBSA 1.2.1
>
> There are specific version checker programs for both components:
>
> How to check for MDAC version
> http://support.microsoft.com/kb/301202/
>
> Determine the Version of MSXML Parser Installed on a Computer
> http://support.microsoft.com/kb/278674/
>
>
> Regards,
> Torgeir
>
>
> Andrew Wright wrote:
>
> > I have a Windows 2000 machine that is on a network which gets it's updates
> > from a server running WSUS.
> >
> > This particular machine is stuck installing "Update Rollup 1 for Windows
> > 2000 SP4 (KB891861)"
> >
> > WSUS reports this as already installed on the client computer (It also lists
> > a load of successfull install events - one for each try - with a result code
> > of 0x00000000).
> >
> > The event log on the client computer reports that the update was
> > successfully installed after each try.
> >
> > After each install (except the very first attempt which required a re-start)
> > Windows Update on the client machine immediatley downloads the update again
> > and offers it for installation.
> >
> > Does any one know why this may be looping and what the solution is?
> >
> > Thanks,
> > Andrew
>
>
> --
> torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway
> Administration scripting examples and an ONLINE version of
> the 1328 page Scripting Guide:
> http://www.microsoft.com/technet/scr...r/default.mspx
>