*** SOLUTION *** to Windows Update's error number: 0x8024400A

Hello to the whole community here.

About the problem in subject, the only solution that worked for me,
apart all the suggestions I've seen here, was to completely delete the
IE's cache, history, et. (cookies included).

Hope this will help all of U 2.

Credits go to "" who originally wrote this
solution in an Italian newsgroup dedicated to Windows XP.

Thanks to MS for the usual totally unexpected gifts in crucial
functions which make the OEM SysAdmin's spend hours to find a solution
to such a silly problem, trying to imagine whatever sort of HW/SW
conflicts especially after the installation of the (in)famous SP2.

And real thanks to all the real world users out there who are always
the only resource to help their similars survive in this modern times
jungle.

Regards,

E=MC^2 (Erio "U2?!" Michelangelo C.)

You do uninstall winxp hotfix 833978 and try to windows update again.

"E=MC^2" wrote:

> Hello to the whole community here.
>
> About the problem in subject, the only solution that worked for me,
> apart all the suggestions I've seen here, was to completely delete the
> IE's cache, history, et. (cookies included).
>
> Hope this will help all of U 2.
>
> Credits go to "" who originally wrote this
> solution in an Italian newsgroup dedicated to Windows XP.
>
> Thanks to MS for the usual totally unexpected gifts in crucial
> functions which make the OEM SysAdmin's spend hours to find a solution
> to such a silly problem, trying to imagine whatever sort of HW/SW
> conflicts especially after the installation of the (in)famous SP2.
>
> And real thanks to all the real world users out there who are always
> the only resource to help their similars survive in this modern times
> jungle.
>
> Regards,
>
> E=MC^2 (Erio "U2?!" Michelangelo C.)
>

Sorry!!!
You do uninstall winxp hotfix 833987 and try to windows update again.

"E=MC^2" wrote:

> Hello to the whole community here.
>
> About the problem in subject, the only solution that worked for me,
> apart all the suggestions I've seen here, was to completely delete the
> IE's cache, history, et. (cookies included).
>
> Hope this will help all of U 2.
>
> Credits go to "" who originally wrote this
> solution in an Italian newsgroup dedicated to Windows XP.
>
> Thanks to MS for the usual totally unexpected gifts in crucial
> functions which make the OEM SysAdmin's spend hours to find a solution
> to such a silly problem, trying to imagine whatever sort of HW/SW
> conflicts especially after the installation of the (in)famous SP2.
>
> And real thanks to all the real world users out there who are always
> the only resource to help their similars survive in this modern times
> jungle.
>
> Regards,
>
> E=MC^2 (Erio "U2?!" Michelangelo C.)
>

Do NOT uninstall anything. It's a server problem and will go away.

--
Peter.
Toronto, Canada.
Windows XP Home SP2.
P4 Dual HT @ 3.0ghz, 160gb HD, 1.0gb DDR.
"Even Lo" <> wrote in message
news:5AC857D5-DBA3-43A4-9D1C-...
> You do uninstall winxp hotfix 833978 and try to windows update again.
>
> "E=MC^2" wrote:
>
>> Hello to the whole community here.
>>
>> About the problem in subject, the only solution that worked for me,
>> apart all the suggestions I've seen here, was to completely delete the
>> IE's cache, history, et. (cookies included).
>>
>> Hope this will help all of U 2.
>>
>> Credits go to "" who originally wrote this
>> solution in an Italian newsgroup dedicated to Windows XP.
>>
>> Thanks to MS for the usual totally unexpected gifts in crucial
>> functions which make the OEM SysAdmin's spend hours to find a solution
>> to such a silly problem, trying to imagine whatever sort of HW/SW
>> conflicts especially after the installation of the (in)famous SP2.
>>
>> And real thanks to all the real world users out there who are always
>> the only resource to help their similars survive in this modern times
>> jungle.
>>
>> Regards,
>>
>> E=MC^2 (Erio "U2?!" Michelangelo C.)
>>

If it is a server problem... why is the error I am receiving (0x80244010)
limited to just one machine in my network?


"Peter" wrote:

> Do NOT uninstall anything. It's a server problem and will go away.
>
> --
> Peter.
> Toronto, Canada.
> Windows XP Home SP2.
> P4 Dual HT @ 3.0ghz, 160gb HD, 1.0gb DDR.
> "Even Lo" <> wrote in message
> news:5AC857D5-DBA3-43A4-9D1C-...
> > You do uninstall winxp hotfix 833978 and try to windows update again.
> >
> > "E=MC^2" wrote:
> >
> >> Hello to the whole community here.
> >>
> >> About the problem in subject, the only solution that worked for me,
> >> apart all the suggestions I've seen here, was to completely delete the
> >> IE's cache, history, et. (cookies included).
> >>
> >> Hope this will help all of U 2.
> >>
> >> Credits go to "" who originally wrote this
> >> solution in an Italian newsgroup dedicated to Windows XP.
> >>
> >> Thanks to MS for the usual totally unexpected gifts in crucial
> >> functions which make the OEM SysAdmin's spend hours to find a solution
> >> to such a silly problem, trying to imagine whatever sort of HW/SW
> >> conflicts especially after the installation of the (in)famous SP2.
> >>
> >> And real thanks to all the real world users out there who are always
> >> the only resource to help their similars survive in this modern times
> >> jungle.
> >>
> >> Regards,
> >>
> >> E=MC^2 (Erio "U2?!" Michelangelo C.)
> >>
>
>
>

I have the problem too. and i can not uninstal the hotfix because the only
patch i have is SP2, i have tried all the tips in this topic and nothing helps
Copy of my windows update log:
2004-09-22 11:02:22+0200 1180 71c WU client succeeds
CClientCallRecorder::BeginFindUpdates from WindowsUpdate with call id
{2CF56AA8-5412-49A9-B7A1-44476F9D281D}
2004-09-22 11:02:22+0200 1180 430 ISusInternal API failed
CClientCallRecorder:isconnectCall with error 0x8024000c
2004-09-22 11:02:22+0200 1768 6ec ISusInternal:isconnectCall failed,
hr=8024000C
2004-09-22 11:02:22+0200 1180 640 WU client executing call
{2CF56AA8-5412-49A9-B7A1-44476F9D281D} of type Search Call
2004-09-22 11:02:22+0200 1604 1a4 Trying to make out of proc datastore active
2004-09-22 11:02:23+0200 1604 1a4 Out of proc datastore is now active
2004-09-22 11:02:24+0200 1180 640 PT: Using serverID
{9482F4B4-E343-43B6-B170-9A65BC822C77}
2004-09-22 11:02:24+0200 1180 640 PT: Using server URL
https://v5.windowsupdate.microsoft.c...ce/client.asmx
2004-09-22 11:02:24+0200 1180 640 PT: Calling GetConfig on server
2004-09-22 11:02:24+0200 1180 640 Add header for accept-encoding: xpress
succeeded
2004-09-22 11:02:25+0200 1180 640 DetectCompressionType returning type 1,
hr=0x0
2004-09-22 11:02:25+0200 1180 640 Add header for accept-encoding: xpress
succeeded
2004-09-22 11:02:25+0200 1180 640 DetectCompressionType returning type 1,
hr=0x0
2004-09-22 11:02:25+0200 1180 640 Add header for accept-encoding: xpress
succeeded
2004-09-22 11:02:26+0200 1180 640 DetectCompressionType returning type 1,
hr=0x0
2004-09-22 11:02:26+0200 1180 640 Add header for accept-encoding: xpress
succeeded
2004-09-22 11:02:26+0200 1180 640 DetectCompressionType returning type 1,
hr=0x0
2004-09-22 11:02:26+0200 1180 640 Add header for accept-encoding: xpress
succeeded
2004-09-22 11:02:27+0200 1180 640 DetectCompressionType returning type 1,
hr=0x0
2004-09-22 11:02:27+0200 1180 640 Add header for accept-encoding: xpress
succeeded
2004-09-22 11:02:27+0200 1180 640 DetectCompressionType returning type 1,
hr=0x0
2004-09-22 11:02:27+0200 1180 640 Add header for accept-encoding: xpress
succeeded
2004-09-22 11:02:28+0200 1180 640 DetectCompressionType returning type 1,
hr=0x0
2004-09-22 11:02:28+0200 1180 640 Add header for accept-encoding: xpress
succeeded
2004-09-22 11:02:28+0200 1180 640 DetectCompressionType returning type 1,
hr=0x0
2004-09-22 11:02:29+0200 1180 640 Add header for accept-encoding: xpress
succeeded
2004-09-22 11:02:29+0200 1180 640 DetectCompressionType returning type 1,
hr=0x0
2004-09-22 11:02:30+0200 1180 640 Add header for accept-encoding: xpress
succeeded
2004-09-22 11:02:31+0200 1180 640 DetectCompressionType returning type 1,
hr=0x0
2004-09-22 11:02:31+0200 1180 640 Add header for accept-encoding: xpress
succeeded
2004-09-22 11:02:31+0200 1180 640 DetectCompressionType returning type 1,
hr=0x0
2004-09-22 11:02:31+0200 1180 640 Add header for accept-encoding: xpress
succeeded
2004-09-22 11:02:32+0200 1180 640 DetectCompressionType returning type 1,
hr=0x0
2004-09-22 11:02:32+0200 1180 640 Add header for accept-encoding: xpress
succeeded
2004-09-22 11:02:33+0200 1180 640 DetectCompressionType returning type 1,
hr=0x0
2004-09-22 11:02:33+0200 1180 640 Add header for accept-encoding: xpress
succeeded
2004-09-22 11:02:33+0200 1180 640 DetectCompressionType returning type 1,
hr=0x0
2004-09-22 11:02:33+0200 1180 640 Add header for accept-encoding: xpress
succeeded
2004-09-22 11:02:34+0200 1180 640 DetectCompressionType returning type 1,
hr=0x0
2004-09-22 11:02:35+0200 1180 640 Add header for accept-encoding: xpress
succeeded
2004-09-22 11:02:35+0200 1180 640 DetectCompressionType returning type 1,
hr=0x0
2004-09-22 11:02:36+0200 1180 640 Add header for accept-encoding: xpress
succeeded
2004-09-22 11:02:36+0200 1180 640 DetectCompressionType returning type 1,
hr=0x0
2004-09-22 11:02:36+0200 1180 640 Add header for accept-encoding: xpress
succeeded
2004-09-22 11:02:37+0200 1180 640 DetectCompressionType returning type 1,
hr=0x0
2004-09-22 11:02:37+0200 1180 640 Add header for accept-encoding: xpress
succeeded
2004-09-22 11:02:39+0200 1180 640 DetectCompressionType returning type 1,
hr=0x0
2004-09-22 11:02:39+0200 1180 640 Add header for accept-encoding: xpress
succeeded
2004-09-22 11:02:40+0200 1180 640 DetectCompressionType returning type 1,
hr=0x0
2004-09-22 11:02:40+0200 1180 640 Add header for accept-encoding: xpress
succeeded
2004-09-22 11:02:40+0200 1180 640 DetectCompressionType returning type 1,
hr=0x0
2004-09-22 11:02:40+0200 1180 640 Add header for accept-encoding: xpress
succeeded
2004-09-22 11:02:41+0200 1180 640 DetectCompressionType returning type 1,
hr=0x0
2004-09-22 11:02:42+0200 1180 640 Add header for accept-encoding: xpress
succeeded
2004-09-22 11:02:42+0200 1180 640 DetectCompressionType returning type 1,
hr=0x0
2004-09-22 11:02:43+0200 1180 640 Add header for accept-encoding: xpress
succeeded
2004-09-22 11:02:43+0200 1180 640 DetectCompressionType returning type 1,
hr=0x0
2004-09-22 11:02:43+0200 1180 640 Add header for accept-encoding: xpress
succeeded
2004-09-22 11:02:44+0200 1180 640 DetectCompressionType returning type 1,
hr=0x0
2004-09-22 11:02:44+0200 1180 640 Add header for accept-encoding: xpress
succeeded
2004-09-22 11:02:44+0200 1180 640 DetectCompressionType returning type 1,
hr=0x0
2004-09-22 11:02:44+0200 1180 640 Add header for accept-encoding: xpress
succeeded
2004-09-22 11:02:44+0200 1180 640 DetectCompressionType returning type 1,
hr=0x0
2004-09-22 11:02:44+0200 1180 640 Add header for accept-encoding: xpress
succeeded
2004-09-22 11:02:44+0200 1180 640 DetectCompressionType returning type 1,
hr=0x0
2004-09-22 11:02:45+0200 1180 640 Add header for accept-encoding: xpress
succeeded
2004-09-22 11:02:45+0200 1180 640 DetectCompressionType returning type 1,
hr=0x0
2004-09-22 11:02:45+0200 1180 640 Add header for accept-encoding: xpress
succeeded
2004-09-22 11:02:45+0200 1180 640 DetectCompressionType returning type 1,
hr=0x0
2004-09-22 11:02:46+0200 1180 640 Add header for accept-encoding: xpress
succeeded
2004-09-22 11:02:46+0200 1180 640 DetectCompressionType returning type 1,
hr=0x0
2004-09-22 11:02:46+0200 1180 640 Add header for accept-encoding: xpress
succeeded
2004-09-22 11:02:47+0200 1180 640 DetectCompressionType returning type 1,
hr=0x0
2004-09-22 11:02:47+0200 1180 640 Add header for accept-encoding: xpress
succeeded
2004-09-22 11:02:47+0200 1180 640 DetectCompressionType returning type 1,
hr=0x0
2004-09-22 11:02:47+0200 1180 640 Add header for accept-encoding: xpress
succeeded
2004-09-22 11:02:47+0200 1180 640 DetectCompressionType returning type 1,
hr=0x0
2004-09-22 11:02:47+0200 1180 640 Add header for accept-encoding: xpress
succeeded
2004-09-22 11:02:47+0200 1180 640 DetectCompressionType returning type 1,
hr=0x0
2004-09-22 11:02:48+0200 1180 640 Add header for accept-encoding: xpress
succeeded
2004-09-22 11:02:48+0200 1180 640 DetectCompressionType returning type 1,
hr=0x0
2004-09-22 11:02:48+0200 1180 640 Add header for accept-encoding: xpress
succeeded
2004-09-22 11:02:48+0200 1180 640 DetectCompressionType returning type 1,
hr=0x0
2004-09-22 11:02:49+0200 1180 640 Add header for accept-encoding: xpress
succeeded
2004-09-22 11:02:49+0200 1180 640 DetectCompressionType returning type 1,
hr=0x0
2004-09-22 11:02:49+0200 1180 640 Add header for accept-encoding: xpress
succeeded
2004-09-22 11:02:50+0200 1180 640 DetectCompressionType returning type 1,
hr=0x0
2004-09-22 11:02:50+0200 1180 640 Add header for accept-encoding: xpress
succeeded
2004-09-22 11:02:50+0200 1180 640 DetectCompressionType returning type 1,
hr=0x0
2004-09-22 11:02:50+0200 1180 640 Add header for accept-encoding: xpress
succeeded
2004-09-22 11:02:50+0200 1180 640 DetectCompressionType returning type 1,
hr=0x0
2004-09-22 11:02:50+0200 1180 640 Add header for accept-encoding: xpress
succeeded
2004-09-22 11:02:50+0200 1180 640 DetectCompressionType returning type 1,
hr=0x0
2004-09-22 11:02:51+0200 1180 640 Add header for accept-encoding: xpress
succeeded
2004-09-22 11:02:51+0200 1180 640 DetectCompressionType returning type 1,
hr=0x0
2004-09-22 11:02:51+0200 1180 640 Add header for accept-encoding: xpress
succeeded
2004-09-22 11:02:52+0200 1180 640 DetectCompressionType returning type 1,
hr=0x0
2004-09-22 11:02:52+0200 1180 640 Add header for accept-encoding: xpress
succeeded
2004-09-22 11:02:52+0200 1180 640 DetectCompressionType returning type 1,
hr=0x0
2004-09-22 11:02:53+0200 1180 640 Add header for accept-encoding: xpress
succeeded
2004-09-22 11:02:53+0200 1180 640 DetectCompressionType returning type 1,
hr=0x0
2004-09-22 11:02:53+0200 1180 640 Add header for accept-encoding: xpress
succeeded
2004-09-22 11:02:53+0200 1180 640 DetectCompressionType returning type 1,
hr=0x0
2004-09-22 11:02:53+0200 1180 640 Add header for accept-encoding: xpress
succeeded
2004-09-22 11:02:54+0200 1180 640 DetectCompressionType returning type 1,
hr=0x0
2004-09-22 11:02:54+0200 1180 640 Add header for accept-encoding: xpress
succeeded
2004-09-22 11:02:54+0200 1180 640 DetectCompressionType returning type 1,
hr=0x0
2004-09-22 11:02:54+0200 1180 640 Add header for accept-encoding: xpress
succeeded
2004-09-22 11:02:55+0200 1180 640 DetectCompressionType returning type 1,
hr=0x0
2004-09-22 11:02:55+0200 1180 640 Add header for accept-encoding: xpress
succeeded
2004-09-22 11:02:56+0200 1180 640 DetectCompressionType returning type 1,
hr=0x0
2004-09-22 11:02:56+0200 1180 640 Add header for accept-encoding: xpress
succeeded
2004-09-22 11:02:57+0200 1180 640 DetectCompressionType returning type 1,
hr=0x0
2004-09-22 11:02:57+0200 1180 640 Add header for accept-encoding: xpress
succeeded
2004-09-22 11:02:57+0200 1180 640 DetectCompressionType returning type 1,
hr=0x0
2004-09-22 11:02:57+0200 1180 640 Sync of Updates: 0x80244010
2004-09-22 11:02:57+0200 1180 640 Agent state changed, signalling AU to
redetect with NO delay
2004-09-22 11:02:57+0200 1180 640 WU client failed Searching for update with
error 0x80244010
2004-09-22 11:02:57+0200 1180 640 WU client calls back to search call
WindowsUpdate with code Call failed and error 0x80244010
2004-09-22 11:02:57+0200 1180 640 WU client completed and deleted call
{2CF56AA8-5412-49A9-B7A1-44476F9D281D}
2004-09-22 11:02:57+0200 1768 6ec Operation completed due to earlier error.
(hr=80244010)
2004-09-22 11:02:57+0200 1768 6ec Unable to complete asynchronous search
successfully. (hr=80244010)
2004-09-22 11:03:02+0200 1180 640 REPORT EVENT:
{34C54D0A-7998-40D9-9E17-7239751D6BEF} 15 2004-09-22
11:02:57+0200 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80244010 WindowsUpdate Failure Software
Synchronization Error: Agent failed detecting with reason: 0x80244010
2004-09-22 11:07:57+0200 1604 1a4 Out of proc datastore is shutting down
2004-09-22 11:08:01+0200 1604 1a4 Out of proc datastore is now inactive


"Even Lo" wrote:

> Sorry!!!
> You do uninstall winxp hotfix 833987 and try to windows update again.
>
> "E=MC^2" wrote:
>
> > Hello to the whole community here.
> >
> > About the problem in subject, the only solution that worked for me,
> > apart all the suggestions I've seen here, was to completely delete the
> > IE's cache, history, et. (cookies included).
> >
> > Hope this will help all of U 2.
> >
> > Credits go to "" who originally wrote this
> > solution in an Italian newsgroup dedicated to Windows XP.
> >
> > Thanks to MS for the usual totally unexpected gifts in crucial
> > functions which make the OEM SysAdmin's spend hours to find a solution
> > to such a silly problem, trying to imagine whatever sort of HW/SW
> > conflicts especially after the installation of the (in)famous SP2.
> >
> > And real thanks to all the real world users out there who are always
> > the only resource to help their similars survive in this modern times
> > jungle.
> >
> > Regards,
> >
> > E=MC^2 (Erio "U2?!" Michelangelo C.)
> >

"CallandServe" <> wrote in message
news:CB813A93-41ED-435C-AA5F-...
>I have the problem too. and i can not uninstal the hotfix because the only
> patch i have is SP2, i have tried all the tips in this topic and nothing helps

Did you try cleaning out the SoftwareDistribution directory
using Torgeir's instructions?


> Copy of my windows update log:

(loop snipped)


The unusual loop evident in your log could be caused by corruption.
Apparently wuauclt.exe reads binary data out of it (e.g. .edb files)
so if they were old or corrupt and not identified as such I can imagine
any number of bizarre things could happen.


HTH

Robert Aldwinckle
---

Hello to all,
I tried a lot of recommended things, but E=MC^2 s tip was the only thing
that helped: Deleting IE-cache, cookies, history corrected the problem.

What I also did, but without success (But it's not senseless to have a
current system):
Installing .Net Framework 1.1
Installing MDAC 2.8 (Microsoft Data Access Components)
Updating MS Parser to SP 4
Installing MS-Patch KB842773


"E=MC^2" wrote:

> Hello to the whole community here.
>
> About the problem in subject, the only solution that worked for me,
> apart all the suggestions I've seen here, was to completely delete the
> IE's cache, history, et. (cookies included).
>
> Hope this will help all of U 2.
>
> Credits go to "" who originally wrote this
> solution in an Italian newsgroup dedicated to Windows XP.
>
> Thanks to MS for the usual totally unexpected gifts in crucial
> functions which make the OEM SysAdmin's spend hours to find a solution
> to such a silly problem, trying to imagine whatever sort of HW/SW
> conflicts especially after the installation of the (in)famous SP2.
>
> And real thanks to all the real world users out there who are always
> the only resource to help their similars survive in this modern times
> jungle.
>
> Regards,
>
> E=MC^2 (Erio "U2?!" Michelangelo C.)
>

Fine, that it helped you.
But it's not a solution to me.
Any other indeas out there?
I already started the background transfer service with no success afterwards.
Come on .. somebody must have choosen this error no. for some reason ...

Thomas

"E=MC^2" wrote:

> Hello to the whole community here.
>
> About the problem in subject, the only solution that worked for me,
> apart all the suggestions I've seen here, was to completely delete the
> IE's cache, history, et. (cookies included).
>
> Hope this will help all of U 2.
>
> Credits go to "" who originally wrote this
> solution in an Italian newsgroup dedicated to Windows XP.
>
> Thanks to MS for the usual totally unexpected gifts in crucial
> functions which make the OEM SysAdmin's spend hours to find a solution
> to such a silly problem, trying to imagine whatever sort of HW/SW
> conflicts especially after the installation of the (in)famous SP2.
>
> And real thanks to all the real world users out there who are always
> the only resource to help their similars survive in this modern times
> jungle.
>
> Regards,
>
> E=MC^2 (Erio "U2?!" Michelangelo C.)
>

Well, Thomas... you're dealing with "doctors" at MS, never forget.

Another terms exists which is "workaround" to patch some problems
until they're fixed in an "official" way... as far as I know, it
didn't happend to any of my customers anymore since when I made them
and I did myself erase the darn temproary files in the IE's disk
cache.

So... call it a solution or not, but it works as a workaround... and
considered MS doesn't pay me for the time I invest correcting their
troubles, I feel perfectly find with any WORKING workaround anybody
would give me to go ahead and don't have headaches doing my job.

Regards,

E=MC^2 (Erio "U2?!" Michelangelo C.)

p.s.: despite that, I too am always interested knowing what caused
what... has anyone discovered the real cause of such "feature"? Was it
a server problem at MS's side for real? Or is there any "tech inside"
we SysAdmins should know and that MS didn't share (yet)? TIA w y'all

DontSendMeMails <> wrote in message news:<057003F3-1929-4D85-B55C->...
> Fine, that it helped you.
> But it's not a solution to me.
> Any other indeas out there?
> I already started the background transfer service with no success afterwards.
> Come on .. somebody must have choosen this error no. for some reason ...
>
> Thomas
>
> "E=MC^2" wrote:
>
> > Hello to the whole community here.
> >
> > About the problem in subject, the only solution that worked for me,
> > apart all the suggestions I've seen here, was to completely delete the
> > IE's cache, history, et. (cookies included).
> >
> > Hope this will help all of U 2.
> >
> > Credits go to "" who originally wrote this
> > solution in an Italian newsgroup dedicated to Windows XP.
> >
> > Thanks to MS for the usual totally unexpected gifts in crucial
> > functions which make the OEM SysAdmin's spend hours to find a solution
> > to such a silly problem, trying to imagine whatever sort of HW/SW
> > conflicts especially after the installation of the (in)famous SP2.
> >
> > And real thanks to all the real world users out there who are always
> > the only resource to help their similars survive in this modern times
> > jungle.
> >
> > Regards,
> >
> > E=MC^2 (Erio "U2?!" Michelangelo C.)
> >