locked
Windows Update Client failed to detect with error 0x8024400a RRS feed

  • Question

  • Hello. Thread name is the question. I have read, that's is the problem of Windows 2k3/IIS6, but I'm using 2012 server and IIS 8. I have this error only on part of clients, so it's not WSUS error (I think). We're also using proxy server (Ubuntu\Squid). Last lines of UpdateLog:

    2016-09-08 15:08:20:425 1044 c9c AU Successfully wrote event for AU health state:0
    2016-09-08 15:08:20:425 1044 c9c AU AU setting next detection timeout to 2016-09-08 17:08:20
    2016-09-08 15:08:20:440 1044 c9c AU Successfully wrote event for AU health state:0
    2016-09-08 15:08:20:440 1044 c9c AU Successfully wrote event for AU health state:0
    2016-09-08 15:08:25:427 1044 1b5c Report REPORT EVENT: {5FE3236C-2E99-4AAB-B90D-452188EBEB9D} 2016-09-08 15:08:20:425+0300 1 148 101 {00000000-0000-0000-0000-000000000000} 0 8024400a AutomaticUpdates Failure Software Synchronization Windows Update Client failed to detect with error 0x8024400a.
    2016-09-08 15:08:25:427 1044 1b5c Report CWERReporter::HandleEvents - WER report upload completed with status 0x8
    2016-09-08 15:08:25:427 1044 1b5c Report WER Report sent: 7.6.7601.18937 0x8024400a(0) 0000000-0000-0000-0000-000000000000 Scan 0 1 AutomaticUpdates {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} 0
    2016-09-08 15:10:19:385 1044 1b5c PT WARNING: GetConfig failure, error = 0x8024400A, soap client error = 10, soap error code = 0, HTTP status code = 200
    2016-09-08 15:10:19:385 1044 1b5c PT WARNING: PTError: 0x8024400a
    2016-09-08 15:10:19:385 1044 1b5c PT WARNING: GetConfig_WithRecovery failed: 0x8024400a
    2016-09-08 15:10:19:385 1044 1b5c PT WARNING: RefreshConfig failed: 0x8024400a
    2016-09-08 15:10:19:385 1044 1b5c PT WARNING: RefreshPTState failed: 0x8024400a
    2016-09-08 15:10:19:385 1044 1b5c PT WARNING: PTError: 0x8024400a
    2016-09-08 15:10:19:385 1044 1b5c Report WARNING: Reporter failed to upload events with hr = 8024400a.

    Windows is sh*t!

    Thursday, September 8, 2016 12:21 PM

Answers

  • Thanks for reply, Anne! But this article have helped me http://www.geek.giriblog.com/windows-error-80244022-solved.html.

    Windows make me mad!


    • Edited by Net Ranger Tuesday, September 13, 2016 10:09 AM
    • Marked as answer by Net Ranger Tuesday, September 13, 2016 10:09 AM
    Tuesday, September 13, 2016 10:09 AM

All replies

  • Hi Net Ranger

    "0x8024400A WU_E_PT_SOAPCLIENT_PARSE Same as SOAPCLIENT_PARSE_ERROR - SOAP client failed to parse the response from the server."

    1. Please try reset windows update components on the clients that have problems:

    https://support.microsoft.com/en-us/kb/971058

    2. Do the clients without issue use the same proxy with the clients having issues, if not, please check if the clients having issues can update from WSUS server directly without proxy, if yes, please check your proxy settings.

    3. On the WSUS server, also run server cleanup wizard and reindex WSUS database to do maintenance:

    https://gallery.technet.microsoft.com/scriptcenter/6f8cde49-5c52-4abd-9820-f1d270ddea61

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, September 9, 2016 7:04 AM
  • Thanks for reply, Anne! But this article have helped me http://www.geek.giriblog.com/windows-error-80244022-solved.html.

    Windows make me mad!


    • Edited by Net Ranger Tuesday, September 13, 2016 10:09 AM
    • Marked as answer by Net Ranger Tuesday, September 13, 2016 10:09 AM
    Tuesday, September 13, 2016 10:09 AM
  • Okay, it's didn't helped much. Some clients still occuring this issue. Including me. But once I have changing value of HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU\UseWUServer from 1 to 0 and restarting Update Center service - I'm getting updates from local WSUS (but clients still don't shows in WSUS console). With what such behaviour of updates are related? And yes, our company uses proxy-server and WSUS URL have been added to exceptions.

    Windows makes me mad!

    Wednesday, September 14, 2016 5:17 AM
  • Hi Net Ranger,

    Since it has been a period of time past when I see it, then what is your situation now? The register keys mentioned in your last reply is used to make clients not use WSUS server to update, it only indicates clients can update from MU.

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, September 20, 2016 8:57 AM
  • Hello. Yeah, now I know it too. Right now most clients perfom updating from MS servers, because right now I'm unable to resolve this issue due high load. All clients are using proxy, and http address of WSUS have been added to the exclusions. Cleaning of WSUS perfoming on daily basis. If the options you provided are only true slotuins, then I guess cleints shall updates thought MS servers further. Otherwise I'm ready to try another.

    Windows makes me mad!

    Wednesday, September 21, 2016 10:04 AM
  • Hi Net Ranger,

    > Cleaning of WSUS perfoming on daily basis. If the options you provided are only true slotuins, then I guess cleints shall updates thought MS servers further. Otherwise I'm ready to try another.

    If you don't want to troubleshoot the original WSUS server, then re-install a new WSUS server is also a good choose.

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, September 23, 2016 3:27 AM
  • Hi Net Ranger,

    > Cleaning of WSUS perfoming on daily basis. If the options you provided are only true slotuins, then I guess cleints shall updates thought MS servers further. Otherwise I'm ready to try another.

    If you don't want to troubleshoot the original WSUS server, then re-install a new WSUS server is also a good choose.

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Does reinstalling of WSUS is really need if only a part of clients have troubles with WSUS? I can include a content of iuident.txt, if it can helps. Need to note again, that's we're using proxy server and http url of local WSUS have been added to exceptions of proxy.

    iuident.txt

    I'm also have this errors (by Solarwinds tool):


    Windows makes me mad!



    • Edited by Net Ranger Tuesday, October 4, 2016 8:23 AM
    Monday, October 3, 2016 11:10 AM
  • I am getting these same two errors from our SolarWinds tool also. We have no proxy and we are not using SSL but there are 3 computers that are getting updates from WSUS, so it makes it hard to figure out where to troubleshoot. I think it's the server that is not responding to clients properly because when I enter http://<WSUSSERVER:port>/iuident.cab in my browser, I get a 404 error. 

    I have around 30 computers currently in my WSUS console and most of them say they have not yet reported status, two 2003 servers and one 2012 server are reporting every day and the 2012 server is getting updates. 


    Tuesday, October 4, 2016 7:48 PM
  • Usually the link should be http://<WSUSSERVER:port>/selfupdate/iuident.cab, because it's in the same place, as wuident.cab.


    Windows makes me mad!

    Wednesday, October 5, 2016 5:04 AM
  • Funny, all the articles I have been reading reference http://server:port/iuident.cab for testing in a browser, which is where I got it. Now when I try it with selfupdate I am prompted to download a file. 

    I guess this is good news. I just don't know what it means. I am still getting that error trying to check for updates. 


    Wednesday, October 5, 2016 7:35 PM