Windows Update Team-Please don't distribute KB905474 until it is f

For the second month in a row, installation of a WGA tool has failed for me
and others. In my case, and I'm sure many others, we are using genuine copies
of XP. And yet the Update-distributed patches fail and cause us to go through
unneeded and unnecessary time and effort to make things right again. Clearly,
something is seriously wrong with patches themselves or the quality testing
on them.

While I am no programmer, I can suggest a simple fix. Distribute an existing
program you already have called WGADiag2.exe. It works. No glitches, no
failed install, no issues. After failing installation of KB905474, I ran
WGADiag2.exe and again (just as last month) verified that I indeed have a
genuine copy of XP Home.

I understand the desire (and need) for Microsoft to protect it's code and
intellectual property. But using flawed programs to do it serves no one...
Yourself or your customers.

Subject should read "until it is fixed".



"HAN" wrote:

> For the second month in a row, installation of a WGA tool has failed for me
> and others. In my case, and I'm sure many others, we are using genuine copies
> of XP. And yet the Update-distributed patches fail and cause us to go through
> unneeded and unnecessary time and effort to make things right again. Clearly,
> something is seriously wrong with patches themselves or the quality testing
> on them.
>
> While I am no programmer, I can suggest a simple fix. Distribute an existing
> program you already have called WGADiag2.exe. It works. No glitches, no
> failed install, no issues. After failing installation of KB905474, I ran
> WGADiag2.exe and again (just as last month) verified that I indeed have a
> genuine copy of XP Home.
>
> I understand the desire (and need) for Microsoft to protect it's code and
> intellectual property. But using flawed programs to do it serves no one...
> Yourself or your customers.

wgdiag2 verified that I am genuine too but it still wouldnt let me down the
update without a failure unlike last month. maybe we should just all install
the dll fix when it comes out instead - ha ha

"HAN" wrote:

> Subject should read "until it is fixed".
>
>
>
> "HAN" wrote:
>
> > For the second month in a row, installation of a WGA tool has failed for me
> > and others. In my case, and I'm sure many others, we are using genuine copies
> > of XP. And yet the Update-distributed patches fail and cause us to go through
> > unneeded and unnecessary time and effort to make things right again. Clearly,
> > something is seriously wrong with patches themselves or the quality testing
> > on them.
> >
> > While I am no programmer, I can suggest a simple fix. Distribute an existing
> > program you already have called WGADiag2.exe. It works. No glitches, no
> > failed install, no issues. After failing installation of KB905474, I ran
> > WGADiag2.exe and again (just as last month) verified that I indeed have a
> > genuine copy of XP Home.
> >
> > I understand the desire (and need) for Microsoft to protect it's code and
> > intellectual property. But using flawed programs to do it serves no one...
> > Yourself or your customers.

HAN wrote:
> For the second month in a row, installation of a WGA tool has failed
> for me and others. In my case, and I'm sure many others, we are using
> genuine copies of XP. And yet the Update-distributed patches fail and
> cause us to go through unneeded and unnecessary time and effort to
> make things right again. Clearly, something is seriously wrong with
> patches themselves or the quality testing on them.
>
> While I am no programmer, I can suggest a simple fix. Distribute an
> existing program you already have called WGADiag2.exe. It works. No
> glitches, no failed install, no issues. After failing installation of
> KB905474, I ran WGADiag2.exe and again (just as last month) verified
> that I indeed have a genuine copy of XP Home.
>
> I understand the desire (and need) for Microsoft to protect it's code
> and intellectual property. But using flawed programs to do it serves
> no one... Yourself or your customers.

You might find this interesting?
http://arstechnica.com/journals/micr...2006/4/25/3740

--
Mike Pawlak