locked
Windows Updates on WSUS RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Guys, I have a problem in my environment, computers suddenly stopped reporting back to WSUS, previously they had SCCM and now we moved to WSUS. I am recieving the below error on the old machines, while servers and freshly formatted devices are updating.

    Does any one know what is going on?

    I tried to reset WU on clients, tried to reset WMI still nothing.

    WSUS is on server 2012 r2

    this is the error generated

    2018-04-18    12:13:59:356     108    fd0    AU    ## START ##  AU: Search for updates
    2018-04-18    12:13:59:356     108    fd0    AU    #########
    2018-04-18    12:13:59:356     108    fd0    AU    <<## SUBMITTED ## AU: Search for updates [CallId = {18CB4A84-C3E1-44FF-9E59-22CB6CEBBD9D}]
    2018-04-18    12:13:59:356     108    694    Agent    *************
    2018-04-18    12:13:59:356     108    694    Agent    ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2018-04-18    12:13:59:356     108    694    Agent    *********
    2018-04-18    12:13:59:357     108    694    Agent      * Online = Yes; Ignore download priority = No
    2018-04-18    12:13:59:357     108    694    Agent      * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
    2018-04-18    12:13:59:357     108    694    Agent      * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2018-04-18    12:13:59:357     108    694    Agent      * Search Scope = {Machine}
    2018-04-18    12:13:59:357     108    694    Setup    Checking for agent SelfUpdate
    2018-04-18    12:13:59:357     108    694    Setup    Client version: Core: 7.6.7601.23806  Aux: 7.6.7601.23806
    2018-04-18    12:13:59:397     108    694    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab with dwProvFlags 0x00000080:
    2018-04-18    12:13:59:403     108    694    Misc     Microsoft signed: NA
    2018-04-18    12:13:59:407     108    694    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\TMPEFAC.tmp with dwProvFlags 0x00000080:
    2018-04-18    12:13:59:417     108    694    Misc     Microsoft signed: NA
    2018-04-18    12:13:59:422     108    694    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab with dwProvFlags 0x00000080:
    2018-04-18    12:13:59:430     108    694    Misc     Microsoft signed: NA
    2018-04-18    12:13:59:450     108    694    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab with dwProvFlags 0x00000080:
    2018-04-18    12:13:59:456     108    694    Misc     Microsoft signed: NA
    2018-04-18    12:13:59:503     108    694    Setup    Determining whether a new setup handler needs to be downloaded
    2018-04-18    12:13:59:503     108    694    Setup    SelfUpdate handler is not found.  It will be downloaded
    2018-04-18    12:13:59:503     108    694    Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.320"
    2018-04-18    12:13:59:504     108    694    Setup    Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.320" is already installed.
    2018-04-18    12:13:59:504     108    694    Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320"
    2018-04-18    12:13:59:520     108    694    Setup    Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320" is already installed.
    2018-04-18    12:13:59:520     108    694    Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320"
    2018-04-18    12:13:59:544     108    694    Setup    Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320" is already installed.
    2018-04-18    12:13:59:544     108    694    Setup    SelfUpdate check completed.  SelfUpdate is NOT required.
    2018-04-18    12:13:59:616     108    694    PT    +++++++++++  PT: Synchronizing server updates  +++++++++++
    2018-04-18    12:13:59:616     108    694    PT      + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://10.4.151.7:8530/ClientWebService/client.asmx
    2018-04-18    12:13:59:640     108    694    PT    WARNING: Cached cookie has expired or new PID is available
    2018-04-18    12:13:59:640     108    694    PT    Initializing simple targeting cookie, clientId = 639e97bb-2fdc-4e88-be36-9d5600eb5831, target group = , DNS name = xxxx
    2018-04-18    12:13:59:640     108    694    PT      Server URL = http://xxxx:8530/SimpleAuthWebService/SimpleAuth.asmx
    2018-04-18    12:15:48:501     108    694    PT    WARNING: Exceeded max server round trips: 0x80244010
    2018-04-18    12:15:48:501     108    694    PT    WARNING: Sync of Updates: 0x80244010
    2018-04-18    12:15:48:501     108    694    PT    WARNING: SyncServerUpdatesInternal failed: 0x80244010
    2018-04-18    12:15:48:501     108    694    Agent      * WARNING: Failed to synchronize, error = 0x80244010
    2018-04-18    12:15:48:502     108    694    Agent      * WARNING: Exit code = 0x80244010
    2018-04-18    12:15:48:502     108    694    Agent    *********
    2018-04-18    12:15:48:502     108    694    Agent    **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2018-04-18    12:15:48:502     108    694    Agent    *************
    2018-04-18    12:15:48:502     108    694    Agent    WARNING: WU client failed Searching for update with error 0x80244010
    2018-04-18    12:15:48:505     108    544    AU    >>##  RESUMED  ## AU: Search for updates [CallId = {18CB4A84-C3E1-44FF-9E59-22CB6CEBBD9D}]
    2018-04-18    12:15:48:505     108    544    AU      # WARNING: Search callback failed, result = 0x80244010
    2018-04-18    12:15:48:505     108    544    AU      # WARNING: Failed to find updates with error code 80244010
    2018-04-18    12:15:48:505     108    544    AU    #########
    2018-04-18    12:15:48:505     108    544    AU    ##  END  ##  AU: Search for updates [CallId = {18CB4A84-C3E1-44FF-9E59-22CB6CEBBD9D}]
    2018-04-18    12:15:48:505     108    544    AU    #############
    2018-04-18    12:15:48:506     108    544    AU    Successfully wrote event for AU health state:0
    2018-04-18    12:15:48:506     108    544    AU    AU setting next detection timeout to 2018-04-18 13:15:48
    2018-04-18    12:15:48:507     108    544    AU    Setting AU scheduled install time to 2018-04-18 23:00:00
    2018-04-18    12:15:48:507     108    544    AU    Successfully wrote event for AU health state:0
    2018-04-18    12:15:48:508     108    544    AU    Successfully wrote event for AU health state:0
    2018-04-18    12:15:53:504     108    694    Report    REPORT EVENT: {6B890B7C-F983-4E31-8A4A-18B67933F4AE}    2018-04-18 12:15:48:502+0400    1    148    101    {00000000-0000-0000-0000-000000000000}    0    80244010    AutomaticUpdates    Failure    Software Synchronization    Windows Update Client failed to detect with error 0x80244010.

    Alexei Kanbar


    Wednesday, April 18, 2018 8:27 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Follow up Steps on this document and try to find the cause and the solution.

    https://gallery.technet.microsoft.com/office/Troubleshooting-WSUS-d63da113

    Wednesday, April 18, 2018 8:45 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Check your WSUS related Group policies, Communication to WSUS from Client PCs.
    Wednesday, April 18, 2018 8:46 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    allready all this was done but no result

    Alexei Kanbar

    Wednesday, April 18, 2018 8:51 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    GPO wise ok, it was all working properly then suddenly stopped, tried to remove some kbs no result also.

    so in a dead loop here

    Alexei Kanbar

    Wednesday, April 18, 2018 10:41 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    On an affected client, run from an Administrative command prompt:

    net stop bits
net stop wuauserv
reg delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v AccountDomainSid /f
reg delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v PingID /f
reg delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v SusClientId /f
reg delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v SusClientIDValidation /f
rd /s /q "C:\WINDOWS\SoftwareDistribution"
net start bits
net start wuauserv
wuauclt /resetauthorization /detectnow
PowerShell.exe (New-Object -ComObject Microsoft.Update.AutoUpdate).DetectNow()
    If that doesn't work, run a gpresult /h gpo.htm from the Admin command prompt and pastebin it so that we can see it.

    Adam Marshall, MCSE: Security
    http://www.adamj.org
    Microsoft MVP - Windows and Devices for IT

    Friday, April 20, 2018 2:07 AM