Hi Robert,
Open your WindowsUpdate.log file, check the entries for the date and time
that you last failed to install updates and look for an error code that is
related to the failed install.........it may be similar to this one:
WU client failed installing updates with error 0x80240020
If the error code that you received is the same as the one I referenced
above, then please have a look at my somewhat lengthy <g> post in this
thread:
http://groups-beta.google.com/group/...a5fa82dfde3791
Although Nocturnal replied to say that he had already tried importing the
Senslogn subkey, and that it failed to solve the problem, I just noticed
that he has since started a new thread in this newgroup, Subject title
"0x80240020 FIX FOUND", where he states that he exported the Senslogn subkey
from a working 2K machine, imported it to the registry in his broken 2K
machine, and that the fix worked. Since I don't have immediate access to a
2K machine, to see if there is a difference in the Senslogn subkey for WIN2K
vs. WINXP, I don't know if his importing of the subkey originally failed due
to his having imported the values based on the information from a WINXP
machine, information that is in a reply post in a thread that I
referenced.....I must ask him that for future reference, as this install
failed error code on 2K machines seems to be becoming quite prevalent.
Regards,
--
Patti MacLeod
Microsoft MVP - Windows Shell/User
"Robert Towe" <> wrote in message
news:59E2F4F8-D479-4AA0-8C41-...
> When I update and run the troubleshoot, the updates fail and when I click
> the
> icon to find out why they fail, nothing happens...This has been happening
> when automatic updates and manual updates...It started after I downloaded
> the
> new update Windows Genuine Advantage Validation Tool (KB892130)...Can
> anyone
> help with this? Is this update only for WXP ?
> --
> rt