Clients can't update from WSUS server. Error 0x80244007 RRS feed

  • Question

  • Hi guys
    I have been wasting a lot of time struggling with WSUS error but no results
    Need your help

    We have one upstream WSUS server and 4 downstream (located in separate sites)

    All servers work without any issue (no errors in event logs, synchronization is ok etc.)
    But awhile ago we have faced with issue "There was a problem checking for updates. Code 80244007

    It happens on each client (who looks on different WSUS server), even on  WSUS server itself

    When I select Check online for updates from microsoft update everything works fine.

    Example of windowsupdate.log is below:
    2018-03-26 13:53:31:004  924 eb8 Setup FATAL: GetClientUpdateUrl failed, err = 0x8024D009
    2018-03-26 13:53:31:004  924 eb8 Setup Skipping SelfUpdate check based on the /SKIP directive in wuident
    2018-03-26 13:53:31:004  924 eb8 Setup SelfUpdate check completed.  SelfUpdate is NOT required.
    2018-03-26 13:53:31:160  924 eb8 PT +++++++++++  PT: Synchronizing server updates  +++++++++++
    2018-03-26 13:53:31:160  924 eb8 PT   + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = https://kiemsccmkie01.matone.materialise:8531/ClientWebService/client.asmx
    2018-03-26 13:53:31:176  924 eb8 Agent Reading cached app categories using lifetime 604800 seconds
    2018-03-26 13:53:31:176  924 eb8 Agent Read 0 cached app categories
    2018-03-26 13:53:31:176  924 eb8 Agent SyncUpdates adding 0 visited app categories
    2018-03-26 13:53:32:442  924 eb8 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 17; does use network; is at background priority
    2018-03-26 13:53:32:660  924 eb8 WS WARNING: Nws Failure: errorCode=0x803d0013
    2018-03-26 13:53:32:676  924 eb8 WS WARNING: The body of the received message contained a fault.
    2018-03-26 13:53:32:676  924 eb8 WS WARNING: Soap fault info:
    2018-03-26 13:53:32:676  924 eb8 WS WARNING: reason: Fault occurred
    2018-03-26 13:53:32:676  924 eb8 WS WARNING: code: Client
    2018-03-26 13:53:32:676  924 eb8 WS WARNING: detail: <detail><ErrorCode>InvalidParameters</ErrorCode><Message>parameters.InstalledNonLeafUpdateIDs</Message><ID>d4242c38-2f13-4234-be31-bd8dca62ab80</ID><Method>"</detail">http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"</Method></detail>
    2018-03-26 13:53:32:676  924 eb8 WS WARNING: Soap fault detail: errorCode='InvalidParameters', message='parameters.InstalledNonLeafUpdateIDs', id='d4242c38-2f13-4234-be31-bd8dca62ab80', method='"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"'
    2018-03-26 13:53:32:676  924 eb8 WS FATAL: OnCallFailure failed with hr=0X80244007
    2018-03-26 13:53:32:676  924 eb8 PT WARNING: PTError: 0x80244007
    2018-03-26 13:53:32:676  924 eb8 PT WARNING: SyncUpdates_WithRecovery failed.: 0x80244007
    2018-03-26 13:53:32:676  924 eb8 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 17) stopped; does use network; is at background priority
    2018-03-26 13:53:32:676  924 eb8 PT   + SyncUpdates round trips: 1
    2018-03-26 13:53:32:676  924 eb8 PT WARNING: Sync of Updates: 0x80244007
    2018-03-26 13:53:32:676  924 eb8 PT WARNING: SyncServerUpdatesInternal failed: 0x80244007
    2018-03-26 13:53:32:676  924 eb8 Agent   * WARNING: Failed to synchronize, error = 0x80244007
    2018-03-26 13:53:32:676  924 eb8 Agent   * WARNING: Exit code = 0x80244007
    2018-03-26 13:53:32:676  924 eb8 Agent *********
    2018-03-26 13:53:32:676  924 eb8 Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdatesWuApp  Id = 2]
    2018-03-26 13:53:32:676  924 eb8 Agent *************
    2018-03-26 13:53:32:676  924 eb8 Agent WARNING: WU client failed Searching for update with error 0x80244007
    2018-03-26 13:53:32:676  924 eb8 IdleTmr WU operation (CSearchCall::Init ID 2, operation # 16) stopped; does use network; is not at background priority
    2018-03-26 13:53:32:676  924 eb8 IdleTmr Decremented idle timer priority operation counter to 1
    2018-03-26 13:53:32:676  924 1f40 AU >>##  RESUMED  ## AU: Search for updates [CallId = {EB3674F4-88E7-4F1E-8ACA-38AE6ECC2727} ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}]
    2018-03-26 13:53:32:676  924 1f40 AU   # WARNING: Search callback failed, result = 0x80244007
    2018-03-26 13:53:32:692  924 1f40 AU #########
    2018-03-26 13:53:32:692  924 1f40 AU ##  END  ##  AU: Search for updates  [CallId = {EB3674F4-88E7-4F1E-8ACA-38AE6ECC2727} ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}]
    2018-03-26 13:53:32:692  924 1f40 AU #############
    2018-03-26 13:53:32:692  924 1f40 AU All AU searches complete.
    2018-03-26 13:53:32:692  924 1f40 AU   # WARNING: Failed to find updates with error code 80244007
    2018-03-26 13:53:32:692  924 1f40 AU AU setting next detection timeout to 2018-03-26 11:42:00
    2018-03-26 13:53:32:692  924 1f40 AU Adding timer:
    2018-03-26 13:53:32:692  924 1f40 AU     Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2018-03-26 11:42:00, not idle-only, not network-only
    2018-03-26 13:53:32:692  924 1f40 AU Currently AUX is enabled - so not show any WU Upgrade notifications.
    2018-03-26 13:53:32:692  924 1f40 AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
    2018-03-26 13:53:32:692  924 1f40 AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
    2018-03-26 13:53:37:682  924 180c Report REPORT EVENT: {4FF14C59-04F4-4AF2-AADD-4CD97CE678A1} 2018-03-26 13:53:32:676+0300 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 80244007 AutomaticUpdatesWuApp Failure Software Synchronization Windows Update Client failed to detect with error 0x80244007.
    2018-03-26 13:53:37:854  924 180c Report CWERReporter::HandleEvents - WER report upload completed with WER status 0x8 (hr=0)
    2018-03-26 13:53:37:854  924 180c Report WER Report sent: 7.9.9600.18838 0x80244007(0) 00000000-0000-0000-0000-000000000000 Scan 0 1 AutomaticUpdatesWuApp {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} 0
    2018-03-26 13:53:37:854  924 180c Report CWERReporter finished handling 1 events. (00000000)
    2018-03-26 14:19:49:318  924 b10 IdleTmr Decremented idle timer priority operation counter to 0

    I have found different solutions but nothing helped me
    1) removing SoftwareDistribution folder

    2) increasing maxCachedUpdartes parameter in C:\Program Files\Update Services\WebServices\ClientWebService\web.config

    3) resetup WSUS and recreate wsus DB

    and so on

    WSUS servers are Windows Server 2012R2
    Clients - Windows 7 - 10, Windows 2012r2, windows 2016

    Monday, March 26, 2018 11:26 AM

All replies

  • Hi
    thanks for your assistant but it didn't help me
    Monday, March 26, 2018 1:39 PM
  • WAM your servers!

    WAM fixes a boatload of issues and keeps them maintained so you don't have to.

    Please have a look at the WSUS Automated Maintenance (WAM) system. It is an automated maintenance system for WSUS, the last system you'll ever need to maintain WSUS!


    What it does:

    1. Add WSUS Index Optimization to the database to increase the speed of many database operations in WSUS by approximately 1000-1500 times faster.
    2. Remove all Drivers from the WSUS Database (Default; Optional).
    3. Shrink your WSUSContent folder's size by declining multiple types of updates including by default any superseded updates, preview updates, expired updates, Itanium updates, and beta updates. Optional extras: Language Packs, IE7, IE8, IE9, IE10, Embedded, NonEnglishUpdates, ComputerUpdates32bit, WinXP.
    4. Remove declined updates from the WSUS Database.
    5. Clean out all the synchronization logs that have built up over time (configurable, with the default keeping the last 14 days of logs).
    6. Compress Update Revisions.
    7. Remove Obsolete Updates.
    8. Computer Object Cleanup (configurable, with the default of deleting computer objects that have not synced within 30 days).
    9. Application Pool Memory Configuration to display the current private memory limit and easily set it to any configurable amount including 0 for unlimited. This is a manual execution only.
    10. Checks to see if you have a dirty database, and if you do, fixes it. This is primarily for Server 2012 WSUS, and is a manual execution only.
    11. Run the Recommended SQL database Maintenance script on the actual SQL database.
    12. Run the Server Cleanup Wizard.

    It will email the report out to you or save it to a file, or both.

    Although the script is lengthy, it has been made to be super easy to setup and use so don't over think it. There are some prerequisites and instructions at the top of the script. After installing the prerequisites and configuring the variables for your environment (email settings only if you are accepting all the defaults), simply run:

    .\Clean-WSUS.ps1 -FirstRun

    If you wish to view or increase the Application Pool Memory Configuration, or run the Dirty Database Check, you must run it with the required switch. See Get-Help .\Clean-WSUS.ps1 -Examples

    If you're having trouble, there's also a -HelpMe option that will create a log so you can send it to me for support.

    Adam Marshall, MCSE: Security
    Microsoft MVP - Windows and Devices for IT

    Tuesday, March 27, 2018 1:51 PM
  • Thanks adam
    I will try steps above

    Wednesday, March 28, 2018 1:25 PM
  • 0x80244007 = Same as SOAPCLIENT_SOAPFAULT - SOAP client failed because there was a SOAP fault for reasons of WU_E_PT_SOAP_* error codes.

    Please try to open the registry, and then go to : HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate

    And then look for Target Group key, export it first (just a backup) then delete it.

    Now, restart your computer and check Windows Updates.

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

    Thursday, March 29, 2018 8:34 AM
  • Please try to open the registry, and then go to : HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate

    And then look for Target Group key, export it first (just a backup) then delete it.

    Didn't help me. But in this thread:


    That WSUS admin was using a non alpha-numeric character in his computer group regkey/gpo.

    Tuesday, October 22, 2019 8:35 PM