Windows Update Error (80244FFF)

Anonymous
2013-11-13T00:47:27+00:00

I've been having an issue updating my copy of Windows 8.1.  I went into Windows Update and noticed that it hadn't checked for updates since November 1st.  Every time I run Windows Update, either on the desktop or tiled interface, it gives a 80244FFF error.  It is able to download and install Windows Defender definition updates.  I've tried turning off Windows Defender and firewall, plugging my PC directly into the cable modem, trying Safe Mode (Which doesn't allow Windows Update to run), scanning all my drives for errors, and disconnecting all my hard drives except the boot drive but nothing has worked.  I don't want to "Refresh" my copy of Windows 8.1 given that I have many desktop applications and don't want to reinstall manually.

I did find a workaround, of sorts, using WSUS Offline, but I'm wanting the normal Windows Update process to work as intended.  Below is my log from the Windows directory showing what has been happening.  I'm surprised that there are no Action Center items saying Windows Update isn't working.  Is there a way to get Windows Update running as it should?

2013-11-12    19:33:46:852    1032    558    Misc    Validating signature for C:\WINDOWS\SoftwareDistribution\SelfUpdate\wuident.cab:

2013-11-12    19:33:46:859    1032    558    Misc     Microsoft signed: Yes

2013-11-12    19:33:46:859    1032    558    Misc     Infrastructure signed: Yes

2013-11-12    19:33:46:864    1032    558    Misc    Validating signature for C:\WINDOWS\SoftwareDistribution\SelfUpdate\TMP606C.tmp:

2013-11-12    19:33:46:870    1032    558    Misc     Microsoft signed: Yes

2013-11-12    19:33:46:870    1032    558    Misc     Infrastructure signed: Yes

2013-11-12    19:33:46:872    1032    558    Setup    Skipping SelfUpdate check based on the /SKIP directive in wuident

2013-11-12    19:33:46:872    1032    558    Setup    SelfUpdate check completed.  SelfUpdate is NOT required.

2013-11-12    19:33:57:001    1032    558    PT    +++++++++++  PT: Synchronizing server updates  +++++++++++

2013-11-12    19:33:57:001    1032    558    PT      + ServiceId = {7971F918-A847-4430-9279-4A52D1EFE18D}, Server URL = https://fe2.update.microsoft.com/v6/ClientWebService/client.asmx

2013-11-12    19:33:57:007    1032    558    Agent    Reading cached app categories using lifetime 604800 seconds

2013-11-12    19:33:57:007    1032    558    Agent    Read 1 cached app categories

2013-11-12    19:34:02:967    1032    558    WS    WARNING: Nws Failure: errorCode=0x803d0014

2013-11-12    19:34:02:967    1032    558    WS    WARNING: Original error code: 0x80072efe

2013-11-12    19:34:02:967    1032    558    WS    WARNING: There was an error communicating with the endpoint at 'https://fe2.update.microsoft.com/v6/ClientWebService/client.asmx'.

2013-11-12    19:34:02:967    1032    558    WS    WARNING: There was an error receiving the HTTP reply.

2013-11-12    19:34:02:967    1032    558    WS    WARNING: The connection with the remote endpoint was terminated.

2013-11-12    19:34:02:967    1032    558    WS    WARNING: The connection with the server was terminated abnormally

2013-11-12    19:34:02:967    1032    558    WS    WARNING: Web service call failed with hr = 80240440.

2013-11-12    19:34:02:967    1032    558    WS    WARNING: Current service auth scheme='None'.

2013-11-12    19:34:02:967    1032    558    WS    WARNING: Proxy List used: '(null)', Bypass List used: '(null)', Last Proxy used: '(null)', Last auth Schemes used: 'None'.

2013-11-12    19:34:02:967    1032    558    WS    FATAL: OnCallFailure(hrCall, m_error) failed with hr=0x80240440

2013-11-12    19:34:02:972    1032    558    PT    WARNING: PTError: 0x80240440

2013-11-12    19:34:02:972    1032    558    PT    WARNING: SyncUpdates_WithRecovery failed.: 0x80240440

2013-11-12    19:34:02:972    1032    558    PT    WARNING: Sync of Drivers failed (Software succeeded): 0x80240440

2013-11-12    19:34:08:878    1032    558    PT    +++++++++++  PT: Synchronizing extended update info  +++++++++++

2013-11-12    19:34:08:878    1032    558    PT      + ServiceId = {7971F918-A847-4430-9279-4A52D1EFE18D}, Server URL = https://fe2.update.microsoft.com/v6/ClientWebService/client.asmx

2013-11-12    19:34:08:883    1032    558    WS    WARNING: Nws Failure: errorCode=0x803d0001

2013-11-12    19:34:08:883    1032    558    WS    WARNING: Original error code: 0x80072efe

2013-11-12    19:34:08:883    1032    558    WS    WARNING: The operation could not be completed because the channel is in a faulted state.

2013-11-12    19:34:08:883    1032    558    WS    WARNING: There was an error communicating with the endpoint at 'https://fe2.update.microsoft.com/v6/ClientWebService/client.asmx'.

2013-11-12    19:34:08:883    1032    558    WS    WARNING: There was an error receiving the HTTP reply.

2013-11-12    19:34:08:883    1032    558    WS    WARNING: The connection with the remote endpoint was terminated.

2013-11-12    19:34:08:883    1032    558    WS    WARNING: The connection with the server was terminated abnormally

2013-11-12    19:34:08:883    1032    558    WS    WARNING: Web service call failed with hr = 80244fff.

2013-11-12    19:34:08:883    1032    558    WS    WARNING: Current service auth scheme='None'.

2013-11-12    19:34:08:883    1032    558    WS    WARNING: Proxy List used: '(null)', Bypass List used: '(null)', Last Proxy used: '(null)', Last auth Schemes used: 'None'.

2013-11-12    19:34:08:883    1032    558    WS    FATAL: OnCallFailure(hrCall, m_error) failed with hr=0x80244fff

2013-11-12    19:34:08:883    1032    558    PT    WARNING: PTError: 0x80244fff

2013-11-12    19:34:08:883    1032    558    PT    WARNING: GetExtendedUpdateInfo_WithRecovery: 0x80244fff

2013-11-12    19:34:08:883    1032    558    PT    WARNING: Sync of Extended Info: 0x80244fff

2013-11-12    19:34:08:883    1032    558    PT    WARNING: SyncExtendedUpdateInfoInternal failed : 0x80244fff

2013-11-12    19:34:08:886    1032    558    Agent      * WARNING: Exit code = 0x80244FFF

2013-11-12    19:34:08:886    1032    558    Agent    *********

2013-11-12    19:34:08:886    1032    558    Agent    **  END  **  Agent: Finding updates [CallerId = AutomaticUpdatesWuApp  Id = 1]

2013-11-12    19:34:08:886    1032    558    Agent    *************

2013-11-12    19:34:08:886    1032    558    Agent    WARNING: WU client failed Searching for update with error 0x80244fff

2013-11-12    19:34:08:887    1032    558    IdleTmr    WU operation (CSearchCall::Init ID 1, operation # 13) stopped; does use network; is not at background priority

2013-11-12    19:34:08:887    1032    558    IdleTmr    Decremented PDC RefCount for Network to 0

2013-11-12    19:34:08:887    1032    558    IdleTmr    Decremented idle timer priority operation counter to 1

2013-11-12    19:34:08:887    1032    a30    AU    >>##  RESUMED  ## AU: Search for updates [CallId = {768D461F-C399-446D-808C-97FBBA11CFE1} ServiceId = {7971F918-A847-4430-9279-4A52D1EFE18D}]

2013-11-12    19:34:08:887    1032    a30    AU      # WARNING: Search callback failed, result = 0x80244FFF

2013-11-12    19:34:08:887    1032    a30    AU    #########

2013-11-12    19:34:08:887    1032    a30    AU    ##  END  ##  AU: Search for updates  [CallId = {768D461F-C399-446D-808C-97FBBA11CFE1} ServiceId = {7971F918-A847-4430-9279-4A52D1EFE18D}]

2013-11-12    19:34:08:888    1032    a30    AU    #############

2013-11-12    19:34:08:888    1032    a30    AU    All AU searches complete.

2013-11-12    19:34:08:888    1032    a30    AU      # WARNING: Failed to find updates with error code 80244fff

2013-11-12    19:34:08:888    1032    a30    AU    AU was unable to detect updates for more than 48 hours

2013-11-12    19:34:08:888    1032    a30    AU    AU setting next detection timeout to 2013-11-13 05:34:08

2013-11-12    19:34:08:889    1032    a30    AU      # Publishing WNF Per user update count event Count: 0 SID {S-1-5-21-1016054517-69094927-1167762118-1000} Service {7971F918-A847-4430-9279-4A52D1EFE18D}

2013-11-12    19:34:08:889    1032    a30    AU      # Publishing WNF Per user update count event Count: 0 SID {S-1-5-21-1016054517-69094927-1167762118-1000} Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}

Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

137 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2014-05-06T15:03:46+00:00

    For best results you could run ProcMon to capture whatever diagnostics are being created when the update is redone.

    Has anyone tried doing this yet or found out the context of the 0x80240442?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2014-05-06T16:01:47+00:00

    Hi Mika,

    Thanks for posting the screenshot.

    Finnish does make it a little more difficult I must admit, but Google translate came to my aid and translated "Windows ei voinut hakea uusia päivityksiä" into "Windows could not search for new updates" which is rather what I expected to see.

    I'm wondering if the problem is related to a faulty hard drive because I note you already reinstalled Windows without fixing the problem.

    I suggest you run a diags check on the hard disk by doing the following.

    1. Right click the Start button and go to "Command Prompt (Admin)".
    2. Type (or copy/paste) CHKDSK /f /r and hit Enter.

    You'll get a message that a diags check can't be performed because the disk cannot be locked and whether you want to schedule a check on the next reboot. Click "Yes" and then either reboot immediately, or finish what you're doing and then restart.

    Chkdsk will check the drive for bad sectors and mark any found so that they can't be used. It will also check for file system errors and attempt to correct them.

    I should warn you that a diags check can take several hours depending on the hard drive capacity and how much corruption is found. If it appears to hang at a certain percentage for a long time i.e. 1-2 hours, then it's likely that your hard drive is defective and will need to be replaced.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2014-05-06T16:13:53+00:00

    I suggest you run a diags check on the hard disk by doing the following.

    1. Right click the Start button and go to "Command Prompt (Admin)".
    2. Type (or copy/paste) CHKDSK /f /r and hit Enter.

     

    @ Xircal

    Do we know if this is an SSD?  I think I read somewhere that you shouldn't do things like this to an SSD.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2014-05-06T16:26:43+00:00

    I suggest you run a diags check on the hard disk by doing the following.

    1. Right click the Start button and go to "Command Prompt (Admin)".
    2. Type (or copy/paste) CHKDSK /f /r and hit Enter.

    @ Xircal

    Do we know if this is an SSD?  I think I read somewhere that you shouldn't do things like this to an SSD.

    Hi Robert,

    That is indeed a noteworthy point, but the hard disk controller on an SSD would mark bad sectors automatically. Chkdisk /f is all that would be necessary in that particular case.

    But Mika mentioned reinstalling the OS on May 3, but still gets the error, so I'm assuming it's a standard rotary HD.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2014-05-06T16:41:01+00:00

    I suggest you run a diags check on the hard disk by doing the following.

    Right click the Start button and go to "Command Prompt (Admin)".

    Type (or copy/paste) CHKDSK /f /r and hit Enter.

    @ Xircal

    Do we know if this is an SSD?  I think I read somewhere that you shouldn't do things like this to an SSD.

    I am using an SSD, but chkdsk itself does not cause any harm to the drive. Defragging is counterproductive on an SSD, though. Because each cell can be read as quickly as the next one, there is no point in reorganizing data, so it would only add unnecessarily reduce the amount of times each cell could be written. Any modern Windows will flat-out refuse to defrag an SSD, though.

    I did not run a bad sector check, because the SMART information displayed by CrystalDiskInfo does not report any issues (including bad sectors).

    But chkdsk did not find any logical issues, either:

    C:\Windows\System32>chkdsk

    The type of the file system is NTFS.

    Volume label is System.

    WARNING!  F parameter not specified.

    Running CHKDSK in read-only mode.

    Stage 1: Examining basic file system structure ...

      895232 file records processed.

    File verification completed.

      5367 large file records processed.

      0 bad file records processed.

    Stage 2: Examining file name linkage ...

      1199678 index entries processed.

    Index verification completed.

      0 unindexed files scanned.

      0 unindexed files recovered.

    Stage 3: Examining security descriptors ...

    Security descriptor verification completed.

      152224 data files processed.

    CHKDSK is verifying Usn Journal...

      37065176 USN bytes processed.

    Usn Journal verification completed.

    Windows has scanned the file system and found no problems.

    No further action is required.

     156286975 KB total disk space.

     100209084 KB in 388362 files.

        247656 KB in 152225 indexes.

             0 KB in bad sectors.

       1177467 KB in use by the system.

         65536 KB occupied by the log file.

      54652768 KB available on disk.

          4096 bytes in each allocation unit.

      39071743 total allocation units on disk.

      13663192 allocation units available on disk.

    Nor did Repair-WindowsImage/DISM:

    PS C:\WINDOWS\system32> Repair-WindowsImage -Online -CheckHealth -Verbose

    VERBOSE: Dism PowerShell Cmdlets Version 6.3.0.0

    VERBOSE: Target Image Version 6.3.9600.17031

    Path               :

    Online             : False

    Image Health State : Healthy

    Restart Needed     : False

    Nor did sfc /scannow:

    C:\Windows\System32>sfc /scannow

    Beginning system scan.  This process will take some time.

    Beginning verification phase of system scan.

    Verification 100% complete.

    Windows Resource Protection did not find any integrity violations.

    Anyway.. the only three updates me and Robert had in common were:

    KB2919355 (Windows 8.1 Update 1)

    KB2962140 (Juniper Junos Pulse Client fix)

    KB2964358 (IE fix for security bulletin MS14-021)

    Was this answer helpful?

    0 comments