"Only_Sometimes_Desperate_User" < ft.com> wrote in message
news:AD291701-5BCA-4054-ABE0-
....
> "Special_K" wrote:
>
>> This Error number: 0x8024402C I’m receiving while scanning for updates on
>> WU5 is driving me absolutely crazy!
....
>I tried ALL the stuff listed below, and it helped me to get it working again
> one time!
> Next time it didn´t work again. :-((
>
> Playing around then I just stopped the wuaserv and started the WinUpdate-
> and it worked !!!
What worked? Special_K was trying to scan for updates using WUv5.
I don't think that you can do that without the Automatic Updates service
(aka wuauserv) running.
> Rem: I´m using XP Pro SP1
Perhaps you are still using WUv4 then too and not WUv5?
I think that that could mean that you wouldn't have Special_K's
problem.
>
> I assume the running service (from startup) is causing a lot of trouble and
> headache.
If you tried using the proxycfg tool did you notice that the troubleshooting
article which Torgeir Bakken cited specifically tells you to stop and restart
the service?
http://v5.windowsupdate.microsoft.co...cleid=26&ln=en
If anything I would wonder about the order of the steps it gives:
<quote>
1.. Type proxycfg -d at the command prompt, and press Enter.
2.. Type net stop wuauserv at the command prompt, and press Enter.
3.. Type net start wuauserv at the command prompt, and press Enter.
4.. Now try the site again.
</quote>
E.g. my inclination would be to first stop service, then issue the
proxycfg command, and then restart the service.
However, it is also specified that way in the more general knowledge base
article which Patty MacLeod cites.
<title>You may receive an error message when you search for available updates on the Windows Update Web site</title>
http://support.microsoft.com/?kbid=883821
See also, for example:
http://groups-beta.google.com/groups...t=0&scoring=d&
(Google Groups search for
8024402C OR 0x8024402C MSFT OR MVP group:microsoft.public.windowsupdate
- sorted by date to try to capture current thinking about this symptom
)
Also, notice that others have made remarks which indicate
that the proxycfg tool may have some quirks you would need
to work around:
http://groups-beta.google.com/group/...1589b6962b003b
(Google Groups search for
proxycfg group:microsoft.public.windowsupdate
- first hit
)
HTH
Robert Aldwinckle
---
For thread context:
http://www.microsoft.com/windowsxp/e...0-defe7186c9b4