KB905474 (Windows Genuine Advantage Notifications) Will Not Instal

A problem with registry key permissions may cause the installation of
KB905474 to fail.

These permissions can be repaired using Registry Editor as follows:

1. Click Start, and then click Run
2. In the Open box, type regedit, and then click OK
3. Expand HKEY_CLASSES_ROOT
4. Locate the subkey HKEY_CLASSES_ROOT\LegitCheckControl.LegitCheck
5. Right-click the subkey and select Permissions….
6. Ensure that Administrators allowed Full Control permission
7. Repeat steps 3-6 for the subkey
HKEY_CLASSES_ROOT\LegitCheckControl.LegitCheck.1

(Hat tip to Robin Walker who orginally posted this fix.)

This fix is presently being incorporated into an update of the WGADiag2.exe
utility, which will be made available in a few days. Those interested in
testing this utility should contact me directly.

Ken: KB905474 has been VERY frustrating! I have gone ahead and ran Mr.
Walker's fix and I was able to complete the WGA Notification with no further
issues.

I'm not sure if there would be any value to me testing the new WGADiag2 file
since I am now doing ok. But it would be nice to have the file hanging around
;-)
(I already have last months version but as you already know, it didn't fix
this months issue.)

I do have a followup question. Could the permission issue that Robin
discovered this time be the same reason that March's WGA validation
(distributed via Win Update) failed to install? (In March, WGADiag2 got me
going again so that I could get to and use Win Update. But I was never
convinced I was still "ok". And as it turns out, I wasn't!)


"Ken Bauernfreund MSFT" wrote:

> A problem with registry key permissions may cause the installation of
> KB905474 to fail.
>
> These permissions can be repaired using Registry Editor as follows:
>
> 1. Click Start, and then click Run
> 2. In the Open box, type regedit, and then click OK
> 3. Expand HKEY_CLASSES_ROOT
> 4. Locate the subkey HKEY_CLASSES_ROOT\LegitCheckControl.LegitCheck
> 5. Right-click the subkey and select Permissions….
> 6. Ensure that Administrators allowed Full Control permission
> 7. Repeat steps 3-6 for the subkey
> HKEY_CLASSES_ROOT\LegitCheckControl.LegitCheck.1
>
> (Hat tip to Robin Walker who orginally posted this fix.)
>
> This fix is presently being incorporated into an update of the WGADiag2.exe
> utility, which will be made available in a few days. Those interested in
> testing this utility should contact me directly.
>
>

"HAN" wrote:

> Ken: KB905474 has been VERY frustrating! I have gone ahead and ran Mr.
> Walker's fix and I was able to complete the WGA Notification with no further
> issues.
>
> I'm not sure if there would be any value to me testing the new WGADiag2 file
> since I am now doing ok. But it would be nice to have the file hanging around
> ;-)
> (I already have last months version but as you already know, it didn't fix
> this months issue.)
>
> I do have a followup question. Could the permission issue that Robin
> discovered this time be the same reason that March's WGA validation
> (distributed via Win Update) failed to install? (In March, WGADiag2 got me
> going again so that I could get to and use Win Update. But I was never
> convinced I was still "ok". And as it turns out, I wasn't!)
>
>
> "Ken Bauernfreund MSFT" wrote:
>
> > A problem with registry key permissions may cause the installation of
> > KB905474 to fail.
> >
> > These permissions can be repaired using Registry Editor as follows:
> >
> > 1. Click Start, and then click Run
> > 2. In the Open box, type regedit, and then click OK
> > 3. Expand HKEY_CLASSES_ROOT
> > 4. Locate the subkey HKEY_CLASSES_ROOT\LegitCheckControl.LegitCheck
> > 5. Right-click the subkey and select Permissions….
> > 6. Ensure that Administrators allowed Full Control permission
> > 7. Repeat steps 3-6 for the subkey
> > HKEY_CLASSES_ROOT\LegitCheckControl.LegitCheck.1
> >
> > (Hat tip to Robin Walker who orginally posted this fix.)
> >
> > This fix is presently being incorporated into an update of the WGADiag2.exe
> > utility, which will be made available in a few days. Those interested in
> > testing this utility should contact me directly.
> >
> > I tried this fix last night and still didn't work

Here's another one. You could try this one:

start > search > type " wgatray.exe " (no quotes) in the search box >
highlight the found file > click Search's File menu > select
Open Containing Folder > double click the "update" folder >
double click "update.exe" in that update folder.

workaround provided by Peter, worked for Randy.

"grays" <> wrote in message news:3DF34BF1-F680-4291-A6B0-...

I tried this fix last night and still didn't work

Thanks Mike,

I also tried that one and an error message came up saying access denied.

Grays

"Michael Jennings" wrote:

> Here's another one. You could try this one:
>
> start > search > type " wgatray.exe " (no quotes) in the search box >
> highlight the found file > click Search's File menu > select
> Open Containing Folder > double click the "update" folder >
> double click "update.exe" in that update folder.
>
> workaround provided by Peter, worked for Randy.
>
> "grays" <> wrote in message news:3DF34BF1-F680-4291-A6B0-...
>
> I tried this fix last night and still didn't work
>
>
>

Then don't worry about it - when WU asks if you want it hidden,
answer yes. It's some banners that display if Windows isn't
genuine. Critical for Microsoft maybe, but probably not for you.

"grays" <> wrote in message news:391A666D-B016-45BE-9FA1-...
> Thanks Mike,
>
> I also tried that one and an error message came up saying access denied.
>
> Grays
>
> "Michael Jennings" wrote:
>
>> Here's another one. You could try this one:
>>
>> start > search > type " wgatray.exe " (no quotes) in the search box >
>> highlight the found file > click Search's File menu > select
>> Open Containing Folder > double click the "update" folder >
>> double click "update.exe" in that update folder.
>>
>> workaround provided by Peter, worked for Randy.
>>
>> "grays" <> wrote in message news:3DF34BF1-F680-4291-A6B0-...
>>
>> I tried this fix last night and still didn't work
>>

To clarify below the installation got about halfway and then said access denied

Grays

"grays" wrote:

> Thanks Mike,
>
> I also tried that one and an error message came up saying access denied.
>
> Grays
>
> "Michael Jennings" wrote:
>
> > Here's another one. You could try this one:
> >
> > start > search > type " wgatray.exe " (no quotes) in the search box >
> > highlight the found file > click Search's File menu > select
> > Open Containing Folder > double click the "update" folder >
> > double click "update.exe" in that update folder.
> >
> > workaround provided by Peter, worked for Randy.
> >
> > "grays" <> wrote in message news:3DF34BF1-F680-4291-A6B0-...
> >
> > I tried this fix last night and still didn't work
> >
> >
> >

Michael,

I'm not sure what you mean by this. I have a Genuine copy of XP. When I run
the procedure listed below the installation fails but also says that XP is
only partly updated and may not work properly.

Thats not the kind of thing I'm comfortable to ignore.

Grays

"Michael Jennings" wrote:

> Then don't worry about it - when WU asks if you want it hidden,
> answer yes. It's some banners that display if Windows isn't
> genuine. Critical for Microsoft maybe, but probably not for you.
>
> "grays" <> wrote in message news:391A666D-B016-45BE-9FA1-...
> > Thanks Mike,
> >
> > I also tried that one and an error message came up saying access denied.
> >
> > Grays
> >
> > "Michael Jennings" wrote:
> >
> >> Here's another one. You could try this one:
> >>
> >> start > search > type " wgatray.exe " (no quotes) in the search box >
> >> highlight the found file > click Search's File menu > select
> >> Open Containing Folder > double click the "update" folder >
> >> double click "update.exe" in that update folder.
> >>
> >> workaround provided by Peter, worked for Randy.
> >>
> >> "grays" <> wrote in message news:3DF34BF1-F680-4291-A6B0-...
> >>
> >> I tried this fix last night and still didn't work
> >>
>
>
>

I'm comfortable living *without* this update, however I posted
information for others who want to install it, which often worked.

What I meant was that critical update KB905474 does nothing
if your Windows is legitimate. If your Windows isn't, then KB905474
asks you to fix that. If you select "Resolve Later," it puts a banner
on your desktop saying that your Windows is not genuine:

http://labnol.blogspot.com/2006/04/w...f-windows.html

My way to deal with KB905474 was to do a System Restore
which left it downloaded but not installed. You could do that.

If you don't want to do that, check to make sure that you are
logged in as an administrator before you try to install it. Also
disable your antivirus and other such programs. If it still
doesn't work, ask for free support from Windows Update:

http://support.microsoft.com/oas/def...spx?gprid=6527

"grays" <> wrote in message news:57CAA61F-F031-4FED-82FE-...
> Michael,
>
> I'm not sure what you mean by this. I have a Genuine copy of XP. When I run
> the procedure listed below the installation fails but also says that XP is
> only partly updated and may not work properly.
>
> That's not the kind of thing I'm comfortable to ignore.
>
> Grays
>
> "Michael Jennings" wrote:
>
>> Then don't worry about it - when WU asks if you want it hidden,
>> answer yes. It's some banners that display if Windows isn't
>> genuine. Critical for Microsoft maybe, but probably not for you.
>>
>> "grays" <> wrote in message news:391A666D-B016-45BE-9FA1-...
>> > Thanks Mike,
>> >
>> > I also tried that one and an error message came up saying access denied.
>> >
>> > Grays
>> >
>> > "Michael Jennings" wrote:
>> >
>> >> Here's another one. You could try this one:
>> >>
>> >> start > search > type " wgatray.exe " (no quotes) in the search box >
>> >> highlight the found file > click Search's File menu > select
>> >> Open Containing Folder > double click the "update" folder >
>> >> double click "update.exe" in that update folder.
>> >>
>> >> workaround provided by Peter, worked for Randy.
>> >>
>> >> "grays" <> wrote in message news:3DF34BF1-F680-4291-A6B0-...
>> >>
>> >> I tried this fix last night and still didn't work
>> >>
>>
>>
>>

Yes, i did the suggested fix and was now able to install the
"Windows Genuine Advantage Validation Tool (KB892130)" update.
thomas



"HAN" wrote:

> Ken: KB905474 has been VERY frustrating! I have gone ahead and ran Mr.
> Walker's fix and I was able to complete the WGA Notification with no further
> issues.
>
> I'm not sure if there would be any value to me testing the new WGADiag2 file
> since I am now doing ok. But it would be nice to have the file hanging around
> ;-)
> (I already have last months version but as you already know, it didn't fix
> this months issue.)
>
> I do have a followup question. Could the permission issue that Robin
> discovered this time be the same reason that March's WGA validation
> (distributed via Win Update) failed to install? (In March, WGADiag2 got me
> going again so that I could get to and use Win Update. But I was never
> convinced I was still "ok". And as it turns out, I wasn't!)
>
>
> "Ken Bauernfreund MSFT" wrote:
>
> > A problem with registry key permissions may cause the installation of
> > KB905474 to fail.
> >
> > These permissions can be repaired using Registry Editor as follows:
> >
> > 1. Click Start, and then click Run
> > 2. In the Open box, type regedit, and then click OK
> > 3. Expand HKEY_CLASSES_ROOT
> > 4. Locate the subkey HKEY_CLASSES_ROOT\LegitCheckControl.LegitCheck
> > 5. Right-click the subkey and select Permissions….
> > 6. Ensure that Administrators allowed Full Control permission
> > 7. Repeat steps 3-6 for the subkey
> > HKEY_CLASSES_ROOT\LegitCheckControl.LegitCheck.1
> >
> > (Hat tip to Robin Walker who orginally posted this fix.)
> >
> > This fix is presently being incorporated into an update of the WGADiag2.exe
> > utility, which will be made available in a few days. Those interested in
> > testing this utility should contact me directly.
> >
> >