Tales from a Trading Desk

Noise from an Investment Bank

Windows Update - 0x8024402C

Sometimes I hate Windows software....

I have this error on two machines when Windows Update is run - both machines are Windows XP with SP2, running behind an ISA 2000 server.

Windows Update has encountered an error and cannot display the requested page.  Error Number: 0x8024402C

Googling bring up a few items on the microsoft.public.windowsupdate newsgroup, but no real answer to the problem. Even this didn't appear to work

From the WindowsUpdate.log:

2004-09-07 22:24:43+0100  696 724 WU client executing call {161959AE-F9CA-417E-9F99-341DB905DCCA} of type Search Call
2004-09-07 22:24:43+0100  696 724 PT: Using serverID {9482F4B4-E343-43B6-B170-9A65BC822C77}
2004-09-07 22:24:43+0100  696 724 PT: Using server URL https://v5.windowsupdate.microsoft.com/ClientWebService/client.asmx
2004-09-07 22:24:43+0100  696 724 PT: Calling GetConfig on server
2004-09-07 22:24:43+0100  696 724 Add header for accept-encoding: xpress succeeded
2004-09-07 22:24:43+0100  696 724 Send failed with hr = 80072ee7.
2004-09-07 22:24:43+0100  696 724 SendRequest failed with hr = 80072ee7. Proxy List used: <(null)> Bypass List used : <(null)>
2004-09-07 22:24:43+0100  696 724 GetConfig: 0x8024402c
2004-09-07 22:24:43+0100  696 724 PT: Cannot recover from fault, origin=GetConfig, hr=0x8024402c
2004-09-07 22:24:43+0100  696 724 Sync of Updates: 0x8024402c
2004-09-07 22:24:43+0100  696 724 WU client failed Searching for update with error 0x8024402c
2004-09-07 22:24:43+0100  696 724 WU client calls back to search call WindowsUpdate with code Call failed and error 0x8024402c
2004-09-07 22:24:43+0100  696 724 WU client completed and deleted call {161959AE-F9CA-417E-9F99-341DB905DCCA}
2004-09-07 22:24:43+0100 2768 b54 Operation completed due to earlier error. (hr=8024402C)
2004-09-07 22:24:43+0100 2768 b54 Unable to complete asynchronous search successfully. (hr=8024402C)
2004-09-07 22:24:48+0100  696 bbc ISusInternal API failed CClientCallRecorder::DisconnectCall with error 0x8024000c
2004-09-07 22:24:48+0100 2768 b54 ISusInternal::DisconnectCall failed, hr=8024000C

Anyone had this problem and fixed it?

Posted: Sep 07 2004, 10:50 PM by mdavey | with 16 comment(s)

Comments

Mako said:

The same error occurred also on two machines of mine.
I asked Microsoft.
They said "Please update BITS".
Please apply the Windows XP hot fix KB842773.
I applied this to two machines and solved it.
# September 9, 2004 5:46 AM

Coach Rudy said:

I've tried to run this fix but it comes up with "Can not run this because a newer version is already installed.
# September 9, 2004 10:55 PM

Paul said:

The first error code is 0x80072EE7, Googling that implies that you have a name resolution problem.

I think proving you can resolve v5.windowsupdate.microsoft.com would be the place to start.

Paul
# September 10, 2004 6:13 PM

Matt said:

The name resolves fine in the browser and from the command line :(

Hotfix KB842773 gives the same result as per Coach Rudy
# September 13, 2004 3:08 AM

Scott said:

This may help. http://support.microsoft.com/default.aspx?scid=kb;en-us;883821

What I have generally seen is that you need to delete the ActiveX control and it be re-downloaded. The control is Wuaueng.dll and needs to be unregistered and removed from SYSTEM32 and DLLCACHE. Make a backup.

Good luck.

Scott
# September 13, 2004 8:11 PM

Matt said:

Tried both the unreg of wuaueng.dll and what was suggested in http://support.microsoft.com/default.aspx?scid=kb;en-us;883821 but nothing worked. Unregistering wuaueng.dll created error 0x800A01AD
# September 15, 2004 2:21 AM

Holbi said:

Hey
I have the same problem, and i think find solution.I change manualy in workstation IP for DNS (from IP Win2k with ISA (my Proxy) -> IP DNS internet provider).
I try change settings in ISA 2000 for DNS,but DNS doesnt work good.
After change DNS in workstation WindowsUpdate without problem download patches and install.

Now i will try settings WINS for propagations public DNS on my workstations automatic :)

good luck
# September 15, 2004 11:10 AM

mikewolf said:

http://support.microsoft.com/default.aspx?scid=kb;en-us;883821
# September 24, 2004 2:00 AM

Matt said:

Yep, I saw the above URL a few weeks ago, but the suggestions don't fix the problem
# September 24, 2004 2:23 AM

TrackBack said:

# September 27, 2004 12:09 AM

Karl Grant said:

Same problem. I ran proxycfg -P "proxy server" and that fixed the problem. After you install the new xp windows update it doesn't pick up your current proxy settings. This command forces it
# September 29, 2004 10:45 AM

Matt said:

Thanks Karl, however I now have error 0x80244008

Here is the log file for the error

2004-09-29 21:34:08+0100 2248 a0c Out of proc datastore is now active
2004-09-29 21:34:08+0100 696 390 PT: Using serverID {9482F4B4-E343-43B6-B170-9A65BC822C77}
2004-09-29 21:34:08+0100 696 390 PT: Using server URL https://v5.windowsupdate.microsoft.com/ClientWebService/client.asmx
2004-09-29 21:34:08+0100 696 390 PT: Calling GetConfig on server
2004-09-29 21:34:08+0100 696 390 Add header for accept-encoding: xpress succeeded
2004-09-29 21:34:08+0100 696 390 DetectCompressionType returning type 0, hr=0x1
2004-09-29 21:34:08+0100 696 390 GetConfig: 0x80244008
2004-09-29 21:34:08+0100 696 390 PT: Cannot recover from fault, origin=GetConfig, hr=0x80244008
2004-09-29 21:34:08+0100 696 390 Sync of Updates: 0x80244008
2004-09-29 21:34:08+0100 696 390 WU client failed Searching for update with error 0x80244008
2004-09-29 21:34:08+0100 696 390 WU client calls back to search call WindowsUpdate with code Call failed and error 0x80244008
# September 29, 2004 4:35 PM

wuaueng dll said:

Pingback from  wuaueng dll

# May 3, 2008 11:54 AM

Avandia. said:

Avandia side effects. Avandia and. Avandia and pregnancy risk. Avandia. Treating anemia caused by avandia. Avandia high dosing.

# July 30, 2008 7:38 AM

Error number: 0x8024402C | keyongtech said:

Pingback from  Error number: 0x8024402C | keyongtech

# January 22, 2009 3:55 AM

VISHWAMBER SHETTY said:

hey ppl in case u have any error with ur windows update den follow these simple steps

   1) On ur system tray click on the time being displayed

   2) Click on CHANGE DATE AND TIME SETTINGS

   3) Now click on INTERNET TIME

   4) If possible keep it same as the actual time

         else click on change settings

   5) Now tick SYNCHRONIZE WITH AN INTERNET

       TIME SERVER.

  6)   Now select server " time.windows.com"

  7)   Now click UPDATE NOW

  8) Once the update is successful try updating ur  

       windows

   9) I guess it should work

# June 16, 2009 11:57 AM
Leave a Comment

(required) 

(required) 

(optional)

(required)