Error number: 0x8024400A

[cdhitman]

Anyone know what this error code means and how to repair it? Thanks.
(Error number: 0x8024400A)

-Steve

[Bryan]

Just got the same error today.. Only found a German user group site
referring to the error - someone trying to get in behind a proxy.

My Windows Update worked great yesterday, today I get this error. I haven't
found a solution yet, but will keep looking.

[cdhitman]

Hey Bryan, I just solved the problem. First of all, turn off or disable all
anti-virus software. Secondly, click on Sart, then go to 'Run'. Type the
following in the run dialog and then click ok: regsvr32 MSXML3.DLL .For some
reason that file just doesn't want to register properly at times. Let me know
if this helps.

-Steve

[Joe]

got the same problem here
XP service pk2 +.net 1.1 +.net service pk1
someone said run regsvr32 MSXML3.DLL can solve the problem
It did work if you uninstall .net 1.1
But after reinstall .net 1.1 and service pk1 , this ox8024400A back again
And regsvr32.MSXML3.DLL trick no longer works
seems it's a bug cause by .net1.1+service pk1. :(

[Chris]

I have received same error but my error happened after install media player
10 and I do not have .net1.1 installed and none of the above fixes worked for
me

[Bryan]

Steve,

Yeah, saw that "fix" also, but I still get the error. :(

By coincidence, I did upload the latest .NET last night (with Windows
Update) and that seems to be when the problem started.

[cdhitman]

I just installed SP2 and now I'm back with the same stupid problem.....my
auto updates don't even seem to work now....ugh... gonna be a long night...

-Steve

[cdhitman]

More weird stuff....Windows Update via IE works on one user account on the
system but on the other I get the error code.

[DanK]

I am receiving the same error number 0x8024400A when running Express Update,
I started to receive it immediatly after I installed the GDI Detection Tool
and some office updates that according to I assume the detection tool I had
some security issues with. Was just reading everyones input so I thought I
would throw in how it appeared it started on my machine.

[Chris]

Try it again i have done nothing and I mean nothing at all and its working
again

[Bryan]

OK Steve,

More Info - though that tidbit about one user getting the error and another
one NOT getting the error was intreging...

My currect setup is:
Windows XP Pro with SP2. I have had SP2 for about 1 1/2 months with no
problems. My notebook and desktop are hooked to the same router. Desktop
Windows Update (WU) still works just fine. Desktop has same configuration as
notebook. Last WU was yesterday where I downloaded the GDI detection tool
and .Net 1.1. Today I ran WU and got this error.

I checked my Windowsupdate Log, and here is what I see:

2004-09-20 18:48:09-0700 1332 72c PT: Using serverID
{9482F4B4-E343-43B6-B170-9A65BC822C77}
2004-09-20 18:48:09-0700 1332 72c PT: Using server URL
https://v5.windowsupdate.microsoft.com/ClientWebService/client.asmx
2004-09-20 18:48:09-0700 1332 72c Add header for accept-encoding: xpress
succeeded
2004-09-20 18:48:09-0700 1332 72c DetectCompressionType returning type 1,
hr=0x0
2004-09-20 18:48:09-0700 1332 72c GetExtendedUpdateInfo: 0x8024400a
2004-09-20 18:48:09-0700 1332 72c PT: Cannot recover from fault,
origin=GetExtendedUpdateInfo, hr=0x8024400a
2004-09-20 18:48:09-0700 1332 72c Sync of Extended Info: 0x8024400a
2004-09-20 18:48:09-0700 1332 72c WU client failed Searching for update with
error 0x8024400a
2004-09-20 18:48:09-0700 1332 72c WU client calls back to search call
WindowsUpdate with code Call failed and error 0x8024400a
2004-09-20 18:48:09-0700 1332 72c WU client completed and deleted call
{761FA488-35F6-40F8-9804-CF08A0CCF250}
2004-09-20 18:48:09-0700 2372 4dc Operation completed due to earlier error.
(hr=8024400A)
2004-09-20 18:48:09-0700 2372 4dc Unable to complete asynchronous search
successfully. (hr=8024400A)

[Bryan]

opps, last line of that log:

2004-09-20 18:48:14-0700 1332 72c REPORT EVENT:
{96A05A26-7F9E-48A3-8725-A53B054B344E} 37 2004-09-20
18:48:09-0700 1 148 101 {00000000-0000-0000-0000-000000000000} 0 8024400a WindowsUpdate Failure Software
Synchronization Error: Agent failed detecting with reason: 0x8024400a

[jacob]

Hey guys,
I'm getting the same error too.
Just downloaded and installed SP2 via the MS update site. Have not dl'd
Net1.1 or Media Player 10 or the GDI update.

Has anyone checked their "windowsupdate.log" file located in the C:\winxp
(your windows system folder)?

Mine looks like this ::

2004-09-20 22:10:48-0500 2828 b10 Checking for different Redirector at:
http://download.windowsupdate.com/msdownload/update/v5/redir/wuredir.cab
2004-09-20 22:10:48-0500 2828 b10 WinInet: Server file is not newer.
Skipping download.
2004-09-20 22:10:48-0500 2828 b10 Successfully refreshed Redirector cab.
2004-09-20 22:10:48-0500 2828 b10 WinInet: Server file is not newer.
Skipping download.
2004-09-20 22:10:49-0500 2828 b10 WinInet: Download speed is 82018 bytes/sec
2004-09-20 22:10:49-0500 2828 b10 WinInet: Successfully downloaded
http://v5.windowsupdate.microsoft.com/SelfUpdate/AU/x86/XP/en/wusetup.cab to
file C:\WINXP\SoftwareDistribution\WebSetup\wusetup.cab
2004-09-20 22:10:49-0500 2828 b10 Loading inf file
C:\WINXP\SoftwareDistribution\WebSetup\wusetup.inf
2004-09-20 22:10:49-0500 2828 b10 Section name: cdm: Index: 0
2004-09-20 22:10:49-0500 2828 b10 Section name: iuengine: Index: 1
2004-09-20 22:10:49-0500 2828 b10 Section name: wuapi: Index: 2
2004-09-20 22:10:49-0500 2828 b10 Section name: wuauclt: Index: 3
2004-09-20 22:10:49-0500 2828 b10 Section name: wuauclt1: Index: 4
2004-09-20 22:10:49-0500 2828 b10 Section name: wuaucpl: Index: 5
2004-09-20 22:10:49-0500 2828 b10 Section name: wuaueng_WebSetup: Index: 6
2004-09-20 22:10:49-0500 2828 b10 Section name: wuaueng1: Index: 7
2004-09-20 22:10:49-0500 2828 b10 Section name: wuauserv_WebSetup: Index: 8
2004-09-20 22:10:49-0500 2828 b10 Section name: wucltui: Index: 9
2004-09-20 22:10:49-0500 2828 b10 Section name: wups: Index: 10
2004-09-20 22:10:49-0500 2828 b10 Section name: winhttp: Index: 11
2004-09-20 22:10:49-0500 2828 b10 Required Version for binary
C:\WINXP\system32\cdm.dll is: 5,5,3790,2182
2004-09-20 22:10:49-0500 2828 b10 Binary: C:\WINXP\system32\cdm.dll: Target
version: 5.5.3790.2182 Required: 5.5.3790.2182
2004-09-20 22:10:49-0500 2828 b10 Required Version for binary
C:\WINXP\system32\iuengine.dll is: 5,4,3790,2182
2004-09-20 22:10:49-0500 2828 b10 Binary: C:\WINXP\system32\iuengine.dll:
Target version: 5.4.3790.2182 Required: 5.4.3790.2182
2004-09-20 22:10:49-0500 2828 b10 Required Version for binary
C:\WINXP\system32\wuapi.dll is: 5,4,3790,2182
2004-09-20 22:10:49-0500 2828 b10 Binary: C:\WINXP\system32\wuapi.dll:
Target version: 5.4.3790.2182 Required: 5.4.3790.2182
2004-09-20 22:10:49-0500 2828 b10 Required Version for binary
C:\WINXP\system32\wuauclt.exe is: 5,4,3790,2182
2004-09-20 22:10:49-0500 2828 b10 Binary: C:\WINXP\system32\wuauclt.exe:
Target version: 5.4.3790.2182 Required: 5.4.3790.2182
2004-09-20 22:10:49-0500 2828 b10 Required Version for binary
C:\WINXP\system32\wuauclt1.exe is: 5,4,3790,2182
2004-09-20 22:10:49-0500 2828 b10 Binary: C:\WINXP\system32\wuauclt1.exe:
Target version: 5.4.3790.2182 Required: 5.4.3790.2182
2004-09-20 22:10:49-0500 2828 b10 Required Version for binary
C:\WINXP\system32\wuaucpl.cpl is: 5,4,3790,2182
2004-09-20 22:10:49-0500 2828 b10 Binary: C:\WINXP\system32\wuaucpl.cpl:
Target version: 5.4.3790.2182 Required: 5.4.3790.2182
2004-09-20 22:10:49-0500 2828 b10 Required Version for binary
C:\WINXP\system32\wuaueng.dll is: 5,4,3790,2182
2004-09-20 22:10:49-0500 2828 b10 Binary: C:\WINXP\system32\wuaueng.dll:
Target version: 5.4.3790.2182 Required: 5.4.3790.2182
2004-09-20 22:10:49-0500 2828 b10 Required Version for binary
C:\WINXP\system32\wuaueng1.dll is: 5,4,3790,2182
2004-09-20 22:10:49-0500 2828 b10 Binary: C:\WINXP\system32\wuaueng1.dll:
Target version: 5.4.3790.2182 Required: 5.4.3790.2182
2004-09-20 22:10:49-0500 2828 b10 Required Version for binary
C:\WINXP\system32\wucltui.dll is: 5,4,3790,2182
2004-09-20 22:10:49-0500 2828 b10 Binary: C:\WINXP\system32\wucltui.dll:
Target version: 5.4.3790.2182 Required: 5.4.3790.2182
2004-09-20 22:10:49-0500 2828 b10 Required Version for binary
C:\WINXP\system32\wups.dll is: 5,4,3790,2182
2004-09-20 22:10:49-0500 2828 b10 Binary: C:\WINXP\system32\wups.dll: Target
version: 5.4.3790.2182 Required: 5.4.3790.2182
2004-09-20 22:10:54-0500 972 534 WU client succeeds
CClientCallRecorder::BeginFindUpdates from WindowsUpdate with call id
{C31BF2FD-2D2D-4E05-A78E-65E03B740100}
2004-09-20 22:10:54-0500 972 4a0 WU client executing call
{C31BF2FD-2D2D-4E05-A78E-65E03B740100} of type Search Call
2004-09-20 22:10:54-0500 2840 b1c Trying to make out of proc datastore active
2004-09-20 22:10:55-0500 2840 b1c Out of proc datastore is now active
2004-09-20 22:10:57-0500 972 4a0 PT: Using serverID
{9482F4B4-E343-43B6-B170-9A65BC822C77}
2004-09-20 22:10:57-0500 972 4a0 PT: Using server URL
https://v5.windowsupdate.microsoft.com/ClientWebService/client.asmx
2004-09-20 22:10:58-0500 972 4a0 Add header for accept-encoding: xpress
succeeded
2004-09-20 22:10:58-0500 972 4a0 DetectCompressionType returning type 1,
hr=0x0
2004-09-20 22:10:59-0500 972 4a0 Add header for accept-encoding: xpress
succeeded
2004-09-20 22:11:00-0500 972 4a0 DetectCompressionType returning type 1,
hr=0x0
2004-09-20 22:11:01-0500 972 4a0 PT: Using serverID
{9482F4B4-E343-43B6-B170-9A65BC822C77}
2004-09-20 22:11:01-0500 972 4a0 PT: Using server URL
https://v5.windowsupdate.microsoft.com/ClientWebService/client.asmx
2004-09-20 22:11:01-0500 972 4a0 Add header for accept-encoding: xpress
succeeded
2004-09-20 22:11:02-0500 972 4a0 DetectCompressionType returning type 1,
hr=0x0
2004-09-20 22:11:02-0500 972 4a0 GetExtendedUpdateInfo: 0x8024400a
2004-09-20 22:11:02-0500 972 4a0 PT: Cannot recover from fault,
origin=GetExtendedUpdateInfo, hr=0x8024400a
2004-09-20 22:11:02-0500 972 4a0 Sync of Extended Info: 0x8024400a
2004-09-20 22:11:02-0500 972 4a0 WU client failed Searching for update with
error 0x8024400a
2004-09-20 22:11:02-0500 972 4a0 WU client calls back to search call

WindowsUpdate with code Call failed and error 0x8024400a

2004-09-20 22:11:02-0500 972 4a0 WU client completed and deleted call
{C31BF2FD-2D2D-4E05-A78E-65E03B740100}
2004-09-20 22:11:02-0500 2828 b10 Operation completed due to earlier error.
(hr=8024400A)
2004-09-20 22:11:02-0500 2828 b10 Unable to complete asynchronous search
successfully. (hr=8024400A)
2004-09-20 22:11:07-0500 972 4a0 REPORT EVENT:
{E5F666F0-13B5-49E3-8388-20472D0C03C3} 68 2004-09-20
22:11:02-0500 1 148 101 {00000000-0000-0000-0000-000000000000} 0 8024400a WindowsUpdate Failure Software

Synchronization Error: Agent failed detecting with reason: 0x8024400a

2004-09-20 22:16:02-0500 2840 b1c Out of proc datastore is shutting down
2004-09-20 22:16:03-0500 2840 b1c Out of proc datastore is now inactive

[Bryan]

HOLD THE PRESS FOLKS!! MY UPDATE STARTED WORKING AGAIN??!!! NO REASON - I
did nothing but look at WU log?! Go figure!! Now, as to how reliable WU
will be in the future - from reading these posts, I am pretty sure I'll see
it going in and out.. :(

I think that this may be (yet another) undocumented "feature"

[necroscope]

sp2 knocked me out completly. had to reload xp home. not using auto updates
at all had to use cdhitmans suggestion to get back in to WU and everything is
fine. am not at this point going to install sp2 again just yet. could not get
to any secure sites.

[jacob]

My WindowsUpdate.log file was super long. Copied it to
"WindowsUpdateOld.log", deleted all information out of "WindowsUpdate.log",
saved it (so it's basically blank), and re-ran windows update. Wallah.
Updates are processing fine. Don't know whether or not the log file got too
large or what.

Anyways, if all else failed, no need to reinstall everything - like I've
read others doing. Just use a system restore point and pick a spot prior to
SP2.

[Wesha]

> Anyone know what this error code means and how to repair it? Thanks.
> (Error number: 0x8024400A)

You're gonna be laughing hard, but this is how I solved it: I simply deleted
c:\windows\windowsupdate.log (seemingly windows gets crazy when it grows over
64K long). And after deleting it, everything worked!!!

P.S. If you cant dfelete it because it
s used by another process, go to sysinternals.com, download Process
Explorer, find all the handles that refer to that file, and forcefully close
them, that will release the file from the lock.

[Johnny Lange]

I had this same error when accessing Windows Updates. I belive it maybe
linked to the update KB883357...that's when the problem happened. I tried
performing a system restore but I had problems with that too. (don't know
that's linked to the same problem.) I ended up unstalling the update KB883357
from "add/remove" programs, restarted the computer, then the problem went
away, however Internet Explorer keep crashing/freezeing, so I went into
"add/remove" programs, performed a "repair/reinstall", restarted, and that
seemed to fix that issue, the error message 0x8024400A went away and "IE"
doesn't crash anymore. The only thing is I still can't get the system restore
to work...yet. Hope that helps.

[Pieter Erasmus]

Yep, I has the same problem but flloed the advice by turning off antivirus,
reregister the DLL "regsvr32 MSXML3.DLL" and it work fine now.

Pieter

[Jules@discussions.microsoft.com Crown Jules]

I haven't tried that yet, but I have the same problem, and Norton System
Doctor indicates the following error:

Microsoft Shared .DLL Error
The key, "SOFTWARE\Microsoft\Windows\Current Version\SharedDLLs," refers
to a missing file, "C:\WINDOWS\System32\iuctl.dll."

I'm guessing that's the root of the problem.

[Bieleke]

Hi,

> Anyone know what this error code means and how to repair it? Thanks.
> (Error number: 0x8024400A)

Indeed, problem was fixed by just deleting C:\windows\windowsupdate.log

Weird, cause on technet the error is not listed at all, even googling on
this error doesn't return usefull results beside a german listed proxy
problem.

Best Regards,

Patrick

[B@discussions.microsoft.com System B]

Thanks, that worked immediately!

Sys B

[Bieleke]

Hi Guys,

> Indeed, problem was fixed by just deleting C:\windows\windowsupdate.log

Another weird thing...

The original file was C:\windows\Windows Update.log (note the empty space)
After i deleted (or renamed) the file, i checked the dir again after the
windows
update that previous trapped the error...

Now the file is called... C:\windows\WindowsUpdate.log (note... no space !).

So now and then it's just voodoo :-)

Best Regards,

Patrick

[kimo]

Well, thanks to whoever came up with this fix if it wasn't jacob. It seems
to have done the trick for me.

[Marc]

I had the same error and it was resolved by Bieleke's fix. There were
actually two documents in my windows folder, the "windowsupdate" one and the
"windows update" one. I just deleted the "windows update" file and it worked
fine after that. Thanks.

[Janne]

I received the error 3 times, and started looking for help, found your
comment and tried a few times with "refresh" and it worked.

Thank You for the hint!

[eric]

ok, i fixed this problem. running the command "regsvr32 msxml3.dll" didn't
seem to work. And deleting the file "windowsupdate.log" didn't seem to work.
But after deleting "windows update.log" (with a space) seemed to fix the
problem. Hope this helps.

[Eunice]

Thank you,eric.
It was helpful after deleting "windows update.log" :). It seemed to fix the
problem.!

[Jeffrey Carlson]

This is interesting. Windows Update was working fine last night. At one
point, I had only 2 CU and 2 WU to perform, but was in a holding pattern and
was paused at the 'begin install/download' screen. That was last night
(9/20/04).

This morning, in my groggy pre-coffee state, I came in to my laptop and
pushed the power button -- forgetting that the system was in screen saver
mode. Long story short - the system powered down out of suspend.

Is this possibly the cause?

[SteveRam1]

I tried the solutions listed here and they worked but only until I rebooted
my computer but I did solve the problem doing the following. I put the
Windows Update log file back to its original state, I then turned off
automatic updates and rebooted and everything worked. I then turned on
automatic updates, rebooted and everything has been working since then. Hope
this solves the problem for everyone.

SteveRam1

"cdhitman" wrote:

> Hey Bryan, I just solved the problem. First of all, turn off or disable all
> anti-virus software. Secondly, click on Sart, then go to 'Run'. Type the
> following in the run dialog and then click ok: regsvr32 MSXML3.DLL .For some
> reason that file just doesn't want to register properly at times. Let me know
> if this helps.
>
> -Steve
>
>
>
> "Bryan" wrote:
>
> > Just got the same error today.. Only found a German user group site
> > referring to the error - someone trying to get in behind a proxy.
> >
> > My Windows Update worked great yesterday, today I get this error. I haven't
> > found a solution yet, but will keep looking.
> >

[stephen101]

i think it is server error because was working alright after installed

[unhappy xp user.@discussions.microsoft.com martin unhappy xp user.]

hello, running this regsvr32 msxml3.dll didnt work at my pc either, so eric
can u tell me where to find that windows update.log? all i find is a textdoc
called windows update. thx

[mase]

[SteveRam1]

I posted a fix here earlier and then suddenly I was getting the same error. I
have come to the conclusion that it is a server problem. After getting the
error several times it started working without me doing anything.

SteveRam1

[sythwraith]

That also worked for me. I just refreshed three times and it finally worked.

[Hoiberg]

I was having the same problem, did not install SP2 yet, had some
components that report SP2 in the install list, but I ran the
"regsvr32 msxml3.dll" command and immediately was able to run updates
again. I did not have .net frmework installed and make a point of not
installing it. I have also seen wierd issues with that new gdui
detection thing, that seems to have messed up a couple recen installs
I have done. And with the new WinUpdate interface, you have o be
careful not to choose the quick install which will shove that into
your system. Thanks for the "regsvr32 msxml3.dll" advice!

"jacob" <ja...@discussions.microsoft.com> wrote in message news:<DD164132-81B7-4E20...@microsoft.com>...

[Even Lo]

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

[Bieleke]

> Indeed, problem was fixed by just deleting "C:\windows\windows update.log"

Another weird thing...

The original file was C:\windows\Windows Update.log (note the empty space)
After i deleted (or renamed) the file, i checked the dir again after the
windows
update that previous trapped the error...

Now the file is called... C:\windows\WindowsUpdate.log (note... no space !).

So now and then it's just voodoo :-)

Best Regards,

Patrick

[DanK]

Guys I suppose I got lucky someone here said it was funny that they could
still run express install on microsoft update and no problems. I tried that
and it worked and when I went back to my regular account I have had no
further problems. Microsoft recommends setting your firewall up to accept
update from the microsoft site. But as soft ware goes my problem went away.

DanK

[Hahn@discussions.microsoft.com Markus Hahn]

I read most of the posts on this and noone of them helped me with my
WinServer 2003. Exept one which advised me to shutdown the Automatic Update
Service. This solved it for me immediately.

Greetings
Markus

[Robert Aldwinckle]

"Markus Hahn" <Markus Ha...@discussions.microsoft.com> wrote in message
news:F12E6BF9-41B9-44A0...@microsoft.com
...

> "cdhitman" wrote:
>
>> Anyone know what this error code means and how to repair it? Thanks.
>> (Error number: 0x8024400A)
>>
>> -Steve

>I read most of the posts on this and noone of them helped me with my

> WinServer 2003. Exept one which advised me to shutdown the Automatic Update
> Service. This solved it for me immediately.

Did you try a search too? <eg>

It looks as if you could be posting in the wrong newsgroup.
E.g. the code is seen mostly on SUS clients, so if you are using
a SUS client post in the SoftwareUpdateSVCs NG.

According to Chris Ard (and Wei Wu [MSFT]) the code means
<quote>
WU client get a response from server that client could not understand
</quote>

http://groups-beta.google.com/group/microsoft.public.softwareupdatesvcs/msg/dfbcac16ea4c53b5?hl=en&

(Google Groups search for
(0x8024400A OR 8024400A) (MSFT OR MVP) group:microsoft.*
)

HTH

Robert Aldwinckle
---

[Ed]

Ok guys, I think I got it! It is a bit of a bandage type of deal, but I am
pretty sure that it will work out. I am not saying that registering the dll
files will never work.. but a times it has been proven to fail. So, I would
try the following before registering the dll's:

So far I have seen 2 problems that report the same type of error code
0x8024400A.

1) A BLUE informational icon appears besides the host name that is listed in
the console with a report status of "Not yet reported":

Workaround - a) Remove the host from the console. b) run the "wuauclt
/resetauthorization /detectnow" command, and wait about 12 - 15 minutes for
WSUS server to report the client correctly. Keep in mind that as soon as you
run the wuauclt command, it appears at the console within minutes AND with
report status of UNKNOWN. (You need to wait about 15 minutes for this to
change).

2) Machines that it is known to have correct registry settings configured
for WSUS auto update functionality, BUT that DO NOT appear on the console:

Workaround: a) delete the following registry values from the following key
(DO NOT DELETE THE KEY - ONLY THE VALUES):
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate]

PingID (You might not always see this one)
AccountDomainSid
SusClientId

b) run the "wuauclt /resetauthorization /detectnow" command, and wait about
upto 15 minutes for WSUS server to report the client.
I would recommend to for this to be placed on an automated script UNTIL
Microsoft finds a permanent solution to this KAOS... Because if you do not
know how many machines there are on your network, you will really never know
if the WSUS server is really reporting all machines.

Hope this helps!

--
Ed

[Ricky]

Great find! Some problem, and your resolution worked! Thanks

[Phoenician]

I know what it means...it means that Microsoft screwed something up, and we
will get no updates until they unscrew it.

I have two near identical computers, both of which could get updates untill
recently. Now neither will update. Will try my laptop (computer #3) tomorrow.

I guess the way to fix it is to try to find someone at MS who gives a damn,
then beat on him/her till they do something about it.
--
PaulfromPhoenix

"cdhitman" wrote:

> Anyone know what this error code means and how to repair it? Thanks.
> (Error number: 0x8024400A)
>

> -Steve

[Solman]

Ok.... all this seems great.... but would have to say, it wasn't what was
causing the issue on my PC... turns out after much hassles and searching that
is was the "Nvidia Firewall" that was causing the problem... and that was
likely the cause of my last crash that forced me to reformat... steer clear
of the firewall.....

[Vasan@discussions.microsoft.com Narendra Vasan]

Hey,

This was a good solution to my problem. Once i went to run command &
typed "regsvr32 msxml3.dll" automatic updates started working. This was an
extremely good idea. This fixed my problem.

[Robin Walker [MVP]]

fahed <fa...@discussions.microsoft.com> wrote:

> Error number: 0x8024400A

Open a command-prompt window and type the command

regsvr32 msxml3.dll

Then restart Windows.

--
Robin Walker [MVP Networking]
rd...@cam.ac.uk

[Mark]

I've found this error to be rather puzzling until I found out it's the
Windows Update process itself that causes this problem, that's why it's so
random and with unrelated updates.

it seems to be a log file corruption issue and can be solved by doing the
following:

1) disable automatic updates in control panel
2) go into administrative tools -> services and stop the automatic updates
service there too
3) go to your windows dir (window or winnt or whatever) and -delete- both
"Windows Update.log" and "WindowsUpdate.log"
4) restart he Automatic Updates service

You should then be able to go to the windows update site and it should work
again.

HTH

[Kash]

I am also facing this problem and tried solution proposed by Pieter but
getting same problem. Is there any other solution?

"Pieter Erasmus" wrote:

> Yep, I has the same problem but flloed the advice by turning off antivirus,
> reregister the DLL "regsvr32 MSXML3.DLL" and it work fine now.
>
> Pieter

>
>
> "cdhitman" wrote:
>
> > Hey Bryan, I just solved the problem. First of all, turn off or disable all
> > anti-virus software. Secondly, click on Sart, then go to 'Run'. Type the
> > following in the run dialog and then click ok: regsvr32 MSXML3.DLL .For some
> > reason that file just doesn't want to register properly at times. Let me know
> > if this helps.
> >
> > -Steve
> >
> >
> >
> > "Bryan" wrote:
> >
> > > Just got the same error today.. Only found a German user group site
> > > referring to the error - someone trying to get in behind a proxy.
> > >
> > > My Windows Update worked great yesterday, today I get this error. I haven't
> > > found a solution yet, but will keep looking.
> > >

[AGoodwin]

yes, the simple step is to clear your proxy cache:

1. Click on Start, and then click Run.
2. Type cmd in the Open box to get a DOS prompt.
3. Type proxycfg -d at the command prompt, and press Enter.
4. Type net stop wuauserv at the command prompt, and press Enter.
5. Type net start wuauserv at the command prompt, and press Enter.
6. Now try the site again.

Bingo :)

(this also works for another common windows update error: 0x8024402c )

--- previous post ---

[Takis]

Hi,

Just run the update:
http://www.microsoft.com/downloads/details.aspx?FamilyID=C0B57F85-6C03-4D85-A845-92474BB8E53C&displaylang=en

"Bieleke" wrote:

> Hi,

>
> > Anyone know what this error code means and how to repair it? Thanks.
> > (Error number: 0x8024400A)
>

[mike]

Try to restart that computer first before trying the other ideas. That is all
I had to do.

[Cheef]

Hello there Steve,

To fix this problem permanently you will need to install kaspersky antivirus
for the 30 day trial period, at first you wont be able to install as trial so
choose to activate later, after you've succesfully installed kaspersky,
download malwarebytes and install it as well. After you do that, scan your
computer with malwarebytes he will find 4 viruses and a few bad registry
logs, try to fix them with your initial antivurus (symantec, microsoft
security essentials or even with the kaspersky you installed recently). Then
try to update your kaspersky, it should get stuck at 90% and he will find a
few viruses as well, delete or quarantine them and you shouldn't receive that
error anymore.

Enjoy.

Blue Air airlines - IT department.

"cdhitman" wrote:

> Anyone know what this error code means and how to repair it? Thanks.
> (Error number: 0x8024400A)
>

> -Steve

[Ekanim@discussions.microsoft.com Isreal Ekanim]

[villa...@gmail.com]

I had this problem with a clean install of XP SP2 ...I tried loads of the fixes suggested here and elsewhere ...like starting and stopping WU processes, stopping auto updates etc...

The thing that worked for me was downloading the Windows Update Agent:-

I found it on this page

http://www.pcworld.com/article/150734/when_windows_update_wont_update.html

You can download versions for the 32-bit version of XP, the 64-bit version, and the Itanium. Once you've downloaded the file, perform the following steps:

1. Click Start, Run, Browse.

2. Locate and double-click the file you just downloaded. Doing so will insert the path and the file name into the run box.

3. In the Run box, enter the text /wuforce after the Windows Update Agent file name.space before the slash) after the file name. Press ENTER and follow the wizard.

I rebooted and ran Windows Update and everything ran fine.

Hope this helps

[aylla....@gmail.com]

When I click delete the WindowsUpdate.log file shows: "It is being used by another person or program".
What can I do to delete it when you see this message?

[MowGreen]

aylla....@gmail.com wrote:
> When I click delete the WindowsUpdate.log file shows: "It is being used by another person or program".
> What can I do to delete it when you see this message?
>

You'll need to stop the Windows Update (Vista/Windows 7) or Automatic
Update (XP) service and/or the Background Intelligent Transfer Service (
BITS ) in order to delete the log.

Right click My Computer in XP, choose Manage to access Services and
Applications. Locate the above services and stop them.
For Vista/Win7, right click Computer, choose Manage, agree to the UAC
prompt to access Services and Applications. Locate the above services
and stop them.

If the services can not be accessed and/or stopping said services does
not allow you to delete the log then it's *highly* likely that the
system has been compromised by malware.


MowGreen
================
*-343-* FDNY
Never Forgotten
================