none
Latest version of Windows Update causing error 80244004

    Question

  • Dear Sir or Madam -

    In the past two days, we've run Windows Update on three different servers, all are running Win 2008 R2.   We are prompted to install a new version of Windows Update and proceed to do so.   After the update completes successfully, when we attempt to  "Check for updates" , it fails with error 0x80244004.

    In two of these cases, this occurred during the initial installation of Windows on the hardware.

    I've searched the Internet for these symptoms.  All the cases I've found that had a resolution pertained to some anti-virus product called "Eset" which we do not use.  I haven't found any resolved case citing other causes of this problem.

    Please adivse.  Thank you.

    Here are the relevant lines from "WindowsUpdate.log" -

    2012-06-28 15:23:46:515  928 170 AU Triggering AU detection through DetectNow API
    2012-06-28 15:23:46:515  928 170 AU Triggering Online detection (interactive)
    2012-06-28 15:23:46:515  928 ec8 AU #############
    2012-06-28 15:23:46:515  928 ec8 AU ## START ##  AU: Search for updates
    2012-06-28 15:23:46:515  928 ec8 AU #########
    2012-06-28 15:23:46:515  928 ec8 AU <<## SUBMITTED ## AU: Search for updates [CallId = {8EDDD883-C7CC-4084-B3C1-74EBDD9970F5}]
    2012-06-28 15:23:46:515  928 ddc Agent *************
    2012-06-28 15:23:46:515  928 ddc Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2012-06-28 15:23:46:515  928 ddc Agent *********
    2012-06-28 15:23:46:515  928 ddc Agent   * Online = Yes; Ignore download priority = No
    2012-06-28 15:23:46:515  928 ddc 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"
    2012-06-28 15:23:46:515  928 ddc Agent   * ServiceID = {9482F4B4-E343-43B6-B170-9A65BC822C77} Windows Update
    2012-06-28 15:23:46:515  928 ddc Agent   * Search Scope = {Machine}
    2012-06-28 15:23:46:515  928 ddc Setup Checking for agent SelfUpdate
    2012-06-28 15:23:46:515  928 ddc Setup Client version: Core: 7.6.7600.256  Aux: 7.6.7600.256
    2012-06-28 15:23:46:531  928 ddc Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\muv4wuredir.cab:
    2012-06-28 15:23:46:547  928 ddc Misc  Microsoft signed: Yes
    2012-06-28 15:23:46:656  928 ddc Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\muv4wuredir.cab:
    2012-06-28 15:23:46:656  928 ddc Misc  Microsoft signed: Yes
    2012-06-28 15:23:46:656  928 ddc Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
    2012-06-28 15:23:46:671  928 ddc Misc  Microsoft signed: Yes
    2012-06-28 15:23:46:734  928 ddc Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
    2012-06-28 15:23:46:734  928 ddc Misc  Microsoft signed: Yes
    2012-06-28 15:23:46:765  928 ddc Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
    2012-06-28 15:23:46:781  928 ddc Misc  Microsoft signed: Yes
    2012-06-28 15:23:46:874  928 ddc Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
    2012-06-28 15:23:46:874  928 ddc Misc  Microsoft signed: Yes
    2012-06-28 15:23:46:905  928 ddc Setup Determining whether a new setup handler needs to be downloaded
    2012-06-28 15:23:46:905  928 ddc Setup SelfUpdate handler is not found.  It will be downloaded
    2012-06-28 15:23:46:905  928 ddc Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256"
    2012-06-28 15:23:46:921  928 ddc Setup Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
    2012-06-28 15:23:46:921  928 ddc Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
    2012-06-28 15:23:47:030  928 ddc Setup Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
    2012-06-28 15:23:47:030  928 ddc Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
    2012-06-28 15:23:47:186  928 ddc Setup Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
    2012-06-28 15:23:47:186  928 ddc Setup SelfUpdate check completed.  SelfUpdate is NOT required.
    2012-06-28 15:23:47:327  928 ddc Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\muv4wuredir.cab:
    2012-06-28 15:23:47:327  928 ddc Misc  Microsoft signed: Yes
    2012-06-28 15:23:47:420  928 ddc Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\muv4wuredir.cab:
    2012-06-28 15:23:47:420  928 ddc Misc  Microsoft signed: Yes
    2012-06-28 15:23:47:420  928 ddc PT +++++++++++  PT: Synchronizing server updates  +++++++++++
    2012-06-28 15:23:47:420  928 ddc PT   + ServiceId = {9482F4B4-E343-43B6-B170-9A65BC822C77}, Server URL = https://www.update.microsoft.com/v6/ClientWebService/client.asmx
    2012-06-28 15:23:47:966  928 ddc PT WARNING: GetConfig failure, error = 0x80244004, soap client error = 4, soap error code = 0, HTTP status code = 200
    2012-06-28 15:23:47:966  928 ddc PT WARNING: PTError: 0x80244004
    2012-06-28 15:23:47:966  928 ddc PT WARNING: GetConfig_WithRecovery failed: 0x80244004
    2012-06-28 15:23:47:966  928 ddc PT WARNING: RefreshConfig failed: 0x80244004
    2012-06-28 15:23:47:966  928 ddc PT WARNING: RefreshPTState failed: 0x80244004
    2012-06-28 15:23:47:966  928 ddc PT WARNING: Sync of Updates: 0x80244004
    2012-06-28 15:23:47:966  928 ddc PT WARNING: SyncServerUpdatesInternal failed: 0x80244004
    2012-06-28 15:23:47:966  928 ddc Agent   * WARNING: Failed to synchronize, error = 0x80244004
    2012-06-28 15:23:47:966  928 ddc Agent   * WARNING: Exit code = 0x80244004
    2012-06-28 15:23:47:966  928 ddc Agent *********
    2012-06-28 15:23:47:966  928 ddc Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2012-06-28 15:23:47:966  928 ddc Agent *************
    2012-06-28 15:23:47:966  928 ddc Agent WARNING: WU client failed Searching for update with error 0x80244004
    2012-06-28 15:23:47:966  928 d10 AU >>##  RESUMED  ## AU: Search for updates [CallId = {8EDDD883-C7CC-4084-B3C1-74EBDD9970F5}]
    2012-06-28 15:23:47:966  928 d10 AU   # WARNING: Search callback failed, result = 0x80244004
    2012-06-28 15:23:47:966  928 d10 AU   # WARNING: Failed to find updates with error code 80244004
    2012-06-28 15:23:47:966  928 d10 AU #########
    2012-06-28 15:23:47:966  928 d10 AU ##  END  ##  AU: Search for updates [CallId = {8EDDD883-C7CC-4084-B3C1-74EBDD9970F5}]
    2012-06-28 15:23:47:966  928 d10 AU #############
    2012-06-28 15:23:47:966  928 d10 AU Successfully wrote event for AU health state:0
    2012-06-28 15:23:47:966  928 d10 AU Successfully wrote event for AU health state:0
    2012-06-28 15:23:52:974  928 ddc Report REPORT EVENT: {D4F6890B-DC12-4915-A0E6-9414793ECD7E} 2012-06-28 15:23:47:966-0400 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80244004 AutomaticUpdates Failure Software Synchronization Windows Update Client failed to detect with error 0x80244004.
    2012-06-28 15:23:52:989  928 ddc Report CWERReporter::HandleEvents - WER report upload completed with status 0x8
    2012-06-28 15:23:52:989  928 ddc Report WER Report sent: 7.6.7600.256 0x80244004 00000000-0000-0000-0000-000000000000 Scan 101 Unmanaged
    2012-06-28 15:23:52:989  928 ddc Report CWERReporter finishing event handling. (00000000)

    Thursday, June 28, 2012 7:43 PM

Answers

  • In our case, this problem was ultimately traced to the use of SSL bridging on outbound connections to the Windows Update site.  That is, the SSL tunnel was terminated at the firewall, decrypted, examined, then re-encrypted for transmission to the Microsoft host.  

    This worked fine until we installed the latest version of Windows Update.   It stopped working either because Microsoft changed an URL or the certificate they use on the SSL connection.  We didn't look closely enough to determine which of these was the cause.

    Our security people agreed that there is no need for SSL bridging on outbound connections to Windows Update.  After they removed it, there was no problem with WU.

    Regarding elshonno's suggestion to specify the WinHTTP proxy via netsh, we have never needed to do this.  In our experience, specifying the correct proxy in Internet Explorer has always been sufficient.  There may be cases where you must use netsh to specify the proxy, but we've never encountered one.

    Regarding the closed case referenced by Tracy Cai, that one was resolved by changing the settings of some anti-virus product called "Eset".  As I explained in my original note, we do not use "Eset".

    James Troy

    • Marked as answer by James W Troy Tuesday, July 03, 2012 4:01 PM
    Tuesday, July 03, 2012 4:00 PM

All replies

  • SAme problem. Mine looks like this

    2012-06-29 13:57:11:415  820 e28 AU Triggering AU detection through DetectNow API
    2012-06-29 13:57:11:415  820 e28 AU Triggering Online detection (interactive) non-default
    2012-06-29 13:57:11:415  820 3ac AU #############
    2012-06-29 13:57:11:415  820 3ac AU ## START ##  AU: Search for updates
    2012-06-29 13:57:11:415  820 3ac AU #########
    2012-06-29 13:57:11:415  820 3ac AU <<## SUBMITTED ## AU: Search for updates [CallId = {49A7E818-40A5-47D1-BD6B-2975FBF5D4C9}]
    2012-06-29 13:57:11:415  820 179c Agent *************
    2012-06-29 13:57:11:415  820 179c Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2012-06-29 13:57:11:415  820 179c Agent *********
    2012-06-29 13:57:11:415  820 179c Agent   * Online = Yes; Ignore download priority = No
    2012-06-29 13:57:11:415  820 179c 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"
    2012-06-29 13:57:11:415  820 179c Agent   * ServiceID = {7971F918-A847-4430-9279-4A52D1EFE18D} Third party service
    2012-06-29 13:57:11:415  820 179c Agent   * Search Scope = {Machine}
    2012-06-29 13:57:11:415  820 179c Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\muv4wuredir.cab:
    2012-06-29 13:57:11:430  820 179c Misc  Microsoft signed: Yes
    2012-06-29 13:57:11:477  820 179c Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\muv4wuredir.cab:
    2012-06-29 13:57:11:477  820 179c Misc  Microsoft signed: Yes
    2012-06-29 13:57:11:493  820 179c Agent Checking for updated auth cab for service 7971f918-a847-4430-9279-4a52d1efe18d at http://download.windowsupdate.com/v9/1/microsoftupdate/redir/muauth.cab
    2012-06-29 13:57:11:493  820 179c Misc Validating signature for C:\Windows\SoftwareDistribution\AuthCabs\authcab.cab:
    2012-06-29 13:57:11:508  820 179c Misc  Microsoft signed: Yes
    2012-06-29 13:57:11:539  820 179c Misc Validating signature for C:\Windows\SoftwareDistribution\AuthCabs\authcab.cab:
    2012-06-29 13:57:11:555  820 179c Misc  Microsoft signed: Yes
    2012-06-29 13:57:11:555  820 179c Setup Checking for agent SelfUpdate
    2012-06-29 13:57:11:555  820 179c Setup Already checked for selfupdate.  SelfUpdate is NOT required.
    2012-06-29 13:57:11:805  820 179c Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir\7971F918-A847-4430-9279-4A52D1EFE18D\muv4muredir.cab:
    2012-06-29 13:57:11:820  820 179c Misc  Microsoft signed: Yes
    2012-06-29 13:57:11:851  820 179c Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir\7971F918-A847-4430-9279-4A52D1EFE18D\muv4muredir.cab:
    2012-06-29 13:57:11:851  820 179c Misc  Microsoft signed: Yes
    2012-06-29 13:57:11:867  820 179c PT +++++++++++  PT: Synchronizing server updates  +++++++++++
    2012-06-29 13:57:11:867  820 179c PT   + ServiceId = {7971F918-A847-4430-9279-4A52D1EFE18D}, Server URL = https://www.update.microsoft.com/v6/ClientWebService/client.asmx
    2012-06-29 13:57:11:867  820 179c PT WARNING: Cached cookie has expired or new PID is available
    2012-06-29 13:57:12:148  820 179c PT WARNING: GetCookie failure, error = 0x80244004, soap client error = 4, soap error code = 0, HTTP status code = 200
    2012-06-29 13:57:12:148  820 179c PT WARNING: PTError: 0x80244004
    2012-06-29 13:57:12:148  820 179c PT WARNING: GetCookie_WithRecovery failed : 0x80244004
    2012-06-29 13:57:12:148  820 179c PT WARNING: RefreshCookie failed: 0x80244004
    2012-06-29 13:57:12:148  820 179c PT WARNING: RefreshPTState failed: 0x80244004
    2012-06-29 13:57:12:148  820 179c PT WARNING: Sync of Updates: 0x80244004
    2012-06-29 13:57:12:148  820 179c PT WARNING: SyncServerUpdatesInternal failed: 0x80244004
    2012-06-29 13:57:12:148  820 179c Agent   * WARNING: Failed to synchronize, error = 0x80244004
    2012-06-29 13:57:12:148  820 179c Agent   * WARNING: Exit code = 0x80244004
    2012-06-29 13:57:12:148  820 179c Agent *********
    2012-06-29 13:57:12:148  820 179c Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2012-06-29 13:57:12:148  820 179c Agent *************
    2012-06-29 13:57:12:148  820 179c Agent WARNING: WU client failed Searching for update with error 0x80244004
    2012-06-29 13:57:12:179  820 628 AU >>##  RESUMED  ## AU: Search for updates [CallId = {49A7E818-40A5-47D1-BD6B-2975FBF5D4C9}]
    2012-06-29 13:57:12:179  820 628 AU   # WARNING: Search callback failed, result = 0x80244004
    2012-06-29 13:57:12:179  820 628 AU   # WARNING: Failed to find updates with error code 80244004
    2012-06-29 13:57:12:179  820 628 AU #########
    2012-06-29 13:57:12:179  820 628 AU ##  END  ##  AU: Search for updates [CallId = {49A7E818-40A5-47D1-BD6B-2975FBF5D4C9}]
    2012-06-29 13:57:12:179  820 628 AU #############

    Friday, June 29, 2012 6:46 PM
  • proxy settings need to be reset

    • Click Start, and then type cmd in the Start programs and files box.
    • Right-click cmd.exe in the Programs list, and then click Run as administrator.

      Note If you are prompted for an administrator password or confirmation, type the password or click Continue.
    • Type the following command and then press Enter:
      netsh winhttp show proxy
      Note The proxy setting is listed next to Proxy Server. If there is no proxy server, Direct Access <no proxy server> is shown in  the Command Prompt window.
    • To remove the listed proxy setting, type the following command and then press Enter:
      netsh winhttp reset proxy - otherwise (if you have aproxy server)
    •  set your proxy server and add the windows update site in the bypass list.
    Saturday, June 30, 2012 3:51 PM
  • Hi ,

    There is a resolved thread for your reference:

    http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_update/windows-update-will-not-work-getting-error/d0ba46ff-64d7-402a-a9d8-82e03c84e4db

    Please kindly understand this is Windows 7 forum.  For Windows Server related issue, it is recommended to post your question on the Windows Server forum. Thank you for your understanding.

    Windows Server forum

    http://social.technet.microsoft.com/Forums/en-US/category/windowsserver


    Tracy Cai

    TechNet Community Support

    Monday, July 02, 2012 7:41 AM
    Moderator
  • Hello Tracy -

    It would help us if Microsoft would provide some guidance about which forum to use for a question.  There is one long list of forums, and they are not listed alphabetically (try looking for "Security" under  "Windows Server").  

    Also, Windows 7 and Windows 2008 R2 are the same thing from a code perspective, so if you want us to distinguish between workstations and servers, that should be made more clear.

    You should propose creating the  "Find the right Forum"  wizard.  They'll reward you with a big bonus.  (-:

    Thank you.

    James Troy

    Tuesday, July 03, 2012 3:47 PM
  • In our case, this problem was ultimately traced to the use of SSL bridging on outbound connections to the Windows Update site.  That is, the SSL tunnel was terminated at the firewall, decrypted, examined, then re-encrypted for transmission to the Microsoft host.  

    This worked fine until we installed the latest version of Windows Update.   It stopped working either because Microsoft changed an URL or the certificate they use on the SSL connection.  We didn't look closely enough to determine which of these was the cause.

    Our security people agreed that there is no need for SSL bridging on outbound connections to Windows Update.  After they removed it, there was no problem with WU.

    Regarding elshonno's suggestion to specify the WinHTTP proxy via netsh, we have never needed to do this.  In our experience, specifying the correct proxy in Internet Explorer has always been sufficient.  There may be cases where you must use netsh to specify the proxy, but we've never encountered one.

    Regarding the closed case referenced by Tracy Cai, that one was resolved by changing the settings of some anti-virus product called "Eset".  As I explained in my original note, we do not use "Eset".

    James Troy

    • Marked as answer by James W Troy Tuesday, July 03, 2012 4:01 PM
    Tuesday, July 03, 2012 4:00 PM
  • We, also, do not use ESET A/V but were having the same issues with Windows Update.

    We tracked the problem down to the new Windows Update certificate missing on our WatchGuard Firebox and causing HTTPS Deep Packet Inspection (DPI) to fail.  A quick workaround was to add the update server's network address range to a "DPI Bypass" rule on the firewall; but longer term we're waiting for WatchGuard to add the new certificate to the firewall's trusted root certificate store.

    Hope this saves someone else some time...

    --Scott

    Monday, July 09, 2012 6:49 PM