I was received this error, and I tried all the MS KB articles, and read
through every single thread in this newsgroup related to Error: 0x8024402C
and was unable to fix it. If you read very carefully in Windows Update,
besides the 8024402C error, there is an error that says "You didn't accept
the EULA". Go back and check! I was unsure what was going on, but I never
saw an EULA (End User License Agreement) Dialogue Pop-up. Until I made the
3 changes below.
This works for sure:
1) BITS (Background Intelligent Transfer Agent); Automatic Updates and
Cryptographic Services *MUST* be enabled (Control Panel, Administrative
Tools, Services). **You can turn them OFF and disable later if you so
desire.
2) Go to "Tools, Interent Options, Privacy, Pop-Up Blocker, Settings...and
made sure
the following are added:
*.microsoft.com
*.download.microsoft.com
*.windowsupdate.com
*.windowsupdate.microsoft.com
v5.windowsupdate.microsoft.com
windowsupdate.microsoft.com
2) Go to TCP-IP Properties, Advanced, DNS, and made sure all defaults are
chosen. (Append Primary & Suffix radio button is checked, everything else is
blank)
This assumes you are receiving a DHCP address. Unplug & Plug your Network
cable back out & in, so it gets a new DNS suffix with the DHCP address.
No more Windows Update Errors!
Please post if this worked for you.
cheers
-karim
"iratespamhater" wrote:
> Tried running WU on this XP Home SP2 rig, but instead of working correctly it
> returns the error code in the subject header above. Reseaching in the
> Knowledge Base, this code states that I'm having problems in the proxy
> exceptions list of my internet connection. The fix is to clean out
> characters from this list and flush the proxy cache.
>
> Funny thing is, I'm not running with any sort of proxy server at all. At
> least that I KNOW OF.
>
> Over the past weekend, WU ran fine (even though I had no updates to add).
> Today, it's a NoGo. Why? Now, I can see my installation history fine when
> requested, but whenever WU tries to find new updates, the stupid IE/Windows
> flag waves for what seems forever, only to return the bloody 0x8024402C error
> code.
>
> So now what?
>
|