Windows Update Error 0x8024400A

Discussion in 'Windows Update' started by Hector, Aug 23, 2006.

  1. Hector

    Hector Guest

    Im trying to update my windows xp professional. I have installed on the pc
    the Micrsoft Update too.

    When i get to the point to choose between Express or Custom, i press any of
    the buttons and i get the erro 0x8024400A.

    I cant update my windows.
     
    Hector, Aug 23, 2006
    #1
    1. Advertisements

  2. 0x8024400A SUS_E_PT_SOAPCLIENT_PARSE - failed in parsing response

    Two things you can try :

    1) Go to Start > Run > type in cmd
    Click OK
    At the Command Prompt, type in

    regsvr32 msxml3.dll

    Press Enter
    Restart the system. Revisit MS update.
    If no joy -

    2) Navigate to the WINDOWS directory (folder)
    Locate the Windows Update.log (note the space between Windows and
    Update) Move this log to the Desktop or delete it.
    Revisit MS Update.
    If that doesn't resolve the error message, close Internet Explorer.
    Go to Start > Run type in services.msc
    Click OK
    Scroll down to Automatic Updates. Click the " Stop the service " link
    LEAVE the Service console open.

    Navigate to the WindowsUpdate.log located in the WINDOWS directory
    (NOTE there is NO space between Windows and Update)
    COPY the log to the Desktop by right clicking on it, drag it to the
    Desktop without letting go of the right click, and then choose Copy.

    Open the WindowsUpdate.log located in the WINDOWS directory.
    Click Edit > Select All.
    When all of the text is highlighted, press the Delete key.
    ALL entries should now be removed.
    Click File > Save.
    Close the WindowsUpdate.log.
    Restart the Automatics Update service from the Services console by
    clicking on the " Restart the service " link.
    Close the Services console.
    Restart the system and then revisit MS Update.

    IF the issue is resolved, you can safely delete the WindowsUpdate.log
    that you copied to the Desktop.
    IF IT IS NOT, then please copy&paste the contents of the newly created
    WindowsUpdate.log into your next post, please.

    Please, DO NOT delete the copy of the log located on the Desktop yet.

    MowGreen [MVP 2003-2006]
    ===============
    *-343-* FDNY
    Never Forgotten
    ===============
     
    MowGreen [MVP], Aug 23, 2006
    #2
    1. Advertisements

  3. I have same issue (Error: Agent failed detecting with reason: 0x8024400a)
    with Windows Server 2003 x64 Edition. Only difference is that I’m using WSUS
    with sp1.

    Can I try using same steps you described on Win2003 x64?

    Milutin

     
    Milutin Stanković, Oct 12, 2006
    #3
  4. Hector

    lewynz

    Joined:
    Jul 25, 2012
    Messages:
    1
    Likes Received:
    0
    Hi there. I have tried all that has been suggested on this page however I still cannot get the updates to install. I have just tried to copy and paste the windows update log in here but it says I cannot post links....... I'm not sure where the links are in the 16000 character textfile. Is someone able to help me and if so tell me which part of the text file you need or provide an email address or something I can send it to. Thanks heaps.

    Lewis
     
    lewynz, Jul 25, 2012
    #4
  5. Hector

    Noodle

    Joined:
    Jul 29, 2012
    Messages:
    1
    Likes Received:
    0
    Same problem xp pro 32

    I followed the instructions, problem remains.
    Here is the text from the windowsupdate.log
    2012-07-29 00:41:19-0700 840 c10 Service Main starts
    2012-07-29 00:41:19-0700 840 c10 Using BatchFlushAge = 11491.
    2012-07-29 00:41:19-0700 840 c10 Using SamplingValue = 141.
    2012-07-29 00:41:19-0700 840 c10 Successfully loaded event namespace dictionary.
    2012-07-29 00:41:19-0700 840 c10 Successfully loaded client event namespace descriptor.
    2012-07-29 00:41:19-0700 840 c10 Successfully initialized local event logger. Events will be logged at C:\WINDOWS\SoftwareDistribution\ReportingEvents.log.
    2012-07-29 00:41:19-0700 840 c10 Successfully initialized NT event logger.
    2012-07-29 00:41:20-0700 840 c10 Successfully initialized event uploader 0.
    2012-07-29 00:41:20-0700 840 c10 Reopened existing event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{9CBC31FE-6B66-4A38-9CD2-13FA2D93CCCD}.bin for writing.
    2012-07-29 00:41:20-0700 840 c10 Successfully initialized event uploader 1.
    2012-07-29 00:41:20-0700 840 c10 WU client with version 5.4.3790.2180 successfully initialized
    2012-07-29 00:41:20-0700 840 c10 Service status is now SERVICE_RUNNING
    2012-07-29 00:42:05-0700 840 c10 start delayed initialization of WU client
    2012-07-29 00:42:05-0700 2304 904 Trying to make out of proc datastore active
    2012-07-29 00:42:05-0700 2304 904 Out of proc datastore is now active
    2012-07-29 00:42:05-0700 840 c10 Client Call Recorder finished delayed initialization
    2012-07-29 00:42:05-0700 840 c10 Setting AU scheduled install time to 2012-07-29 10:00:00
    2012-07-29 00:42:05-0700 840 c10 AU finished delayed initialization
    2012-07-29 00:42:05-0700 840 c10 AU received event of 1
    2012-07-29 00:42:05-0700 840 c10 WU client succeeds CClientCallRecorder::BeginFindUpdates from AutomaticUpdates with call id {D53C10D4-1E3E-46D7-BA8D-235005EADC7F}
    2012-07-29 00:42:05-0700 840 aec WU client executing call {D53C10D4-1E3E-46D7-BA8D-235005EADC7F} of type Search Call
    2012-07-29 00:42:05-0700 840 aec WU client found 0 updates and 0 categories in search
    2012-07-29 00:42:05-0700 840 aec WU client finished Searching for update
    2012-07-29 00:42:05-0700 840 aec AU Detection callback: 0 updates detected
    2012-07-29 00:42:05-0700 840 aec Setting AU scheduled install time to 2012-07-29 10:00:00
    2012-07-29 00:42:05-0700 840 aec WU client calls back to search call AutomaticUpdates with code Call complete and error 0
    2012-07-29 00:42:05-0700 840 aec WU client completed and deleted call {D53C10D4-1E3E-46D7-BA8D-235005EADC7F}
    2012-07-29 00:42:16-0700 1216 5e0 0 updates are ready to be installed at shutdown.
    2012-07-29 00:42:18-0700 840 34c Service received logoff notification
    2012-07-29 00:42:18-0700 840 c10 AU received event of 3
    2012-07-29 00:42:19-0700 840 3cc AU Restart required....
    2012-07-29 00:42:19-0700 840 c10 AU received event of 1
    2012-07-29 00:42:19-0700 840 c10 AU is paused, not initializing any handlers
    2012-07-29 00:42:20-0700 840 34c Service received SERVICE_CONTROL_SHUTDOWN control
    2012-07-29 00:42:20-0700 840 c10 Exiting Service Main
    2012-07-29 00:42:20-0700 2304 904 Out of proc datastore is shutting down
    2012-07-29 00:42:20-0700 840 c10 WUAUENG ServiceMain exits. Exit code is 0x240001
    2012-07-29 00:42:21-0700 2304 904 Out of proc datastore is now inactive
    2012-07-29 00:42:55-0700 980 6d4 Service Main starts
    2012-07-29 00:42:55-0700 980 6d4 Using BatchFlushAge = 11491.
    2012-07-29 00:42:55-0700 980 6d4 Using SamplingValue = 141.
    2012-07-29 00:42:55-0700 980 6d4 Successfully loaded event namespace dictionary.
    2012-07-29 00:42:55-0700 980 6d4 Successfully loaded client event namespace descriptor.
    2012-07-29 00:42:55-0700 980 6d4 Successfully initialized local event logger. Events will be logged at C:\WINDOWS\SoftwareDistribution\ReportingEvents.log.
    2012-07-29 00:42:55-0700 980 6d4 Successfully initialized NT event logger.
    2012-07-29 00:42:55-0700 980 6d4 Successfully initialized event uploader 0.
    2012-07-29 00:42:55-0700 980 6d4 Reopened existing event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{9CBC31FE-6B66-4A38-9CD2-13FA2D93CCCD}.bin for writing.
    2012-07-29 00:42:55-0700 980 6d4 Successfully initialized event uploader 1.
    2012-07-29 00:42:55-0700 980 6d4 WU client with version 5.4.3790.2180 successfully initialized
    2012-07-29 00:42:55-0700 980 6d4 Service status is now SERVICE_RUNNING
    2012-07-29 00:42:55-0700 980 3d8 Service received connect notification
    2012-07-29 00:43:40-0700 980 6d4 start delayed initialization of WU client
    2012-07-29 00:43:41-0700 2060 6bc Trying to make out of proc datastore active
    2012-07-29 00:43:41-0700 2060 6bc Out of proc datastore is now active
    2012-07-29 00:43:41-0700 980 6d4 Client Call Recorder finished delayed initialization
     
    Noodle, Jul 29, 2012
    #5
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.