Windows Genuine Advantage Validation fails install - other updates

On a Windows XP SP2 machine I administer the April updates were successfully
downloaded and installed on April 17th. Today, April 24, Microsoft Update
showed a new update was available; it turned out to be a new WGAV
installation.

The WGAV tool downoad was successful. However the installation failed.

I believe that the general fixes for Windows Update install failures are
inapplicable in this case - Windows Install procedures worked fine for the
updates, including MS Office updates, 7 days ago.

Therefore it seems this install failure is specific to the new "Windows
Genuine Advantage Validation" tool package.

Can you provide me an explanation for this package specific failure, and a
work around to deal with it?
--
Sig under construction

Jim Pivonka wrote:
> On a Windows XP SP2 machine I administer the April updates were successfully
> downloaded and installed on April 17th. Today, April 24, Microsoft Update
> showed a new update was available; it turned out to be a new WGAV
> installation.
>
> The WGAV tool downoad was successful. However the installation failed.
>
> I believe that the general fixes for Windows Update install failures are
> inapplicable in this case - Windows Install procedures worked fine for the
> updates, including MS Office updates, 7 days ago.
>
> Therefore it seems this install failure is specific to the new "Windows
> Genuine Advantage Validation" tool package.
>
> Can you provide me an explanation for this package specific failure, and a
> work around to deal with it?

Why did you even allow that crap to be installed in the first place.
WGA/N is not only spyware, it does *nothing* to improve XP. SP3, which
you say is not installed, however, does improve XP.

Alias

Is this the same machine as in your later, "New behavior by machine at
shutdown after MS updates" thread in this newsgroup?

Are you referring to KB905474?
--
~Robear Dyer (PA Bear)
MS MVP-IE, Mail, Security, Windows Client - since 2002

Jim Pivonka wrote:
> On a Windows XP SP2 machine I administer the April updates were
> successfully
> downloaded and installed on April 17th. Today, April 24, Microsoft Update
> showed a new update was available; it turned out to be a new WGAV
> installation.
>
> The WGAV tool downoad was successful. However the installation failed.
>
> I believe that the general fixes for Windows Update install failures are
> inapplicable in this case - Windows Install procedures worked fine for the
> updates, including MS Office updates, 7 days ago.
>
> Therefore it seems this install failure is specific to the new "Windows
> Genuine Advantage Validation" tool package.
>
> Can you provide me an explanation for this package specific failure, and a
> work around to deal with it?

This thread is unique to machine "Grover". The later thread "New Behavior"
applies to both "Grover" and "Della". I will check the WGA update number
next time I am at the Grover site, probably later today.

Thanks, Jim P.
--
Sig under construction


"PA Bear [MS MVP]" wrote:

> Is this the same machine as in your later, "New behavior by machine at
> shutdown after MS updates" thread in this newsgroup?
>
> Are you referring to KB905474?
> --
> ~Robear Dyer (PA Bear)
> MS MVP-IE, Mail, Security, Windows Client - since 2002
>
> Jim Pivonka wrote:
> > On a Windows XP SP2 machine I administer the April updates were
> > successfully
> > downloaded and installed on April 17th. Today, April 24, Microsoft Update
> > showed a new update was available; it turned out to be a new WGAV
> > installation.
> >
> > The WGAV tool downoad was successful. However the installation failed.
> >
> > I believe that the general fixes for Windows Update install failures are
> > inapplicable in this case - Windows Install procedures worked fine for the
> > updates, including MS Office updates, 7 days ago.
> >
> > Therefore it seems this install failure is specific to the new "Windows
> > Genuine Advantage Validation" tool package.
> >
> > Can you provide me an explanation for this package specific failure, and a
> > work around to deal with it?
>
>