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 No comments

137 answers

Sort by: Oldest
  1. Anonymous
    2014-05-06T20:53:10+00:00

    I'm currently taking a look at Process Monitor, but filtering the log to something browseable is going to take a while.

    What I do is just filter for  Operation Is Write  (or actually lately more generally,  Category Is Write).  Doing that shows you all the writes to all the logs correlated with accurate timestamps and lengths.  You can use ProcMon's Ctrl-J to open a file you are interested in.  So, if you are using Notepad to view it, it is useful to turn off Word Wrap and turn on the Status bar.  Then you can press End and see how long a line is.  Then you can try to match up with a trace record:  both the time in the log and the length and further try to confirm your assumption by doing the same thing with preceding or following records and trace entries.  (Note that the time in the log will be earlier than the trace entry's timestamp and the length of the write may be 1 or 2 bytes bigger.)  Then, once you are confident that the write you have selected is the one which output the log record you are interested in you can remove the filter and go back to find out what might have been happening to have caused it.

    Good luck

    Robert


    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2014-05-07T03:36:25+00:00

    Disk checks and log file parsing is what went on back in November when this first happened.  There are too many people with the same problem for this to require unqualified end users to debug.  Further, this is not an isolated issue, this is a Microsoft problem and we're on a Microsoft forum.  This error number didn't magically appear out of thin air and I'm getting kind of tired of Microsoft ignoring it.

    Here's an idea:  Someone drag a developer into the codebase and find out what piece of code generates that error.  Then ask them pretty please to find out what it means.

    After 6 months of farming this out to the MVP amateur sleauthing communitiy, it's about time Microsoft owned up to the problem and quit wasting all of our time.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2014-05-07T15:13:24+00:00

    Hard to dispute ScanIAm says in his 6 May post, especially given the looming deadline, as non-enterprise users at least are likely somewhat disappointed in the multiple problems in getting KB2919355 to install correctly (providing, of course they have prerequisite updates such as KB2919442 installed,

    and the steps outlined in the Microsoft Support articles Install the latest Windows 8.1 Update and Windows Update error 80070002 have proved of no avail).

          Nevertheless, users determined to eliminate this headache may wish to attempt the steps for installing KB2919355 on a clean-booted box running only Windows services as outlined by Thenrik in his May 7 2014 post to page 90 of the thread (yes, as Community Moderator, MVP and renowned patch expert Susan Bradley mentioned on an earlier page, that thread is approaching a "world record" for length) "Windows 8.1 Update 1 Failing to Install with errors 80070020, 80073712 and 0x800f081f".  Given that he reports having performed this successfully on three different builds, it would appear there may be more than mere anecdotal evidence that this approach works; one caution to bear in mind is the reported expenditure of time required, 6-8 hours per machine - which of course reinforces the position of ScanIAm and many other Community members that Microsoft needs to resolve this problem.  In their defense, the volume of notifications I've received about new revisions of KB2919355 would seem to imply that this is the current "hot topic" in the Halls of Redmond (the latest updated package released 5 May and the fact that the 7 May revision of the accompanying Knowledge base article is the 19th would surely confirm such).

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2014-05-07T17:21:14+00:00

    Mika,

    There's an article in the following link which has similarities to your own problem: http://www.kapilarya.com/fix-windows-8-1-unable-to-check-for-new-windows-updates

    Only the error code differs, but since it concerns Windows inability to search for new updates which is the same as your own error, it might be worth your while taking a look at it.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2014-05-08T04:56:06+00:00

    I gave up and did a full reinstall from a Windows 8.1 image. I'm still in the process of reinstalling.. well, everything, but at least Windows Update is working.

    Here's the list of updates that Windows Update gave me afterwards:

    HotFixID                                        Description     InstalledOn

    --------                                        -----------     -----------

    KB2899189_Microsoft-Windows-CameraCodec-Package Update          20140705

    KB2843630                                       Update          20140705

    KB2862152                                       Security Update 20140705

    KB2868626                                       Security Update 20140705

    KB2876331                                       Security Update 20140705

    KB2883200                                       Update          20140705

    KB2884846                                       Update          20140705

    KB2887595                                       Update          20140705

    KB2892074                                       Security Update 20140705

    KB2893294                                       Security Update 20140705

    KB2894029                                       Update          20140705

    KB2894179                                       Update          20140705

    KB2894853                                       Update          20140705

    KB2898514                                       Update          20140705

    KB2898742                                       Update          20140705

    KB2898871                                       Security Update 20140705

    KB2900986                                       Security Update 20140705

    KB2901101                                       Update          20140705

    KB2901128                                       Security Update 20140705

    KB2902892                                       Update          20140705

    KB2903939                                       Update          20140705

    KB2904266                                       Update          20140705

    KB2906956                                       Update          20140705

    KB2908174                                       Update          20140705

    KB2909210                                       Security Update 20140705

    KB2909569                                       Update          20140705

    KB2911106                                       Update          20140705

    KB2911134                                       Update          20140705

    KB2912390                                       Security Update 20140705

    KB2913152                                       Update          20140705

    KB2913270                                       Update          20140705

    KB2913760                                       Update          20140705

    KB2914218                                       Update          20140705

    KB2916036                                       Security Update 20140705

    KB2917929                                       Update          20140705

    KB2917993                                       Update          20140705

    KB2919355                                       Update          20140705

    KB2919394                                       Update          20140705

    KB2919442                                       Update          20140705

    KB2919907                                       Update          20140705

    KB2922229                                       Security Update 20140705

    KB2923300                                       Update          20140705

    KB2923528                                       Update          20140705

    KB2923768                                       Update          20140705

    KB2925418                                       Security Update 20140705

    KB2928680                                       Update          20140705

    KB2929961                                       Security Update 20140705

    KB2930275                                       Security Update 20140705

    KB2933809                                       Update          20140705

    KB2936068                                       Security Update 20140705

    KB2939087                                       Update          20140705

    KB2942844                                       Update          20140705

    KB2959977                                       Update          20140705

    KB2961887                                       Update          20140705

    KB2962140                                       Update          20140705

    KB2964358                                       Security Update 20140705

    KB2964444                                       Security Update 20140705

    KB2964757                                       Update          20140705

    KB976002                                        Update          20140705

    One thing that immediately grabs my attention is that the list is much, much longer than what WSUS Offline gave me, so it's not a comprehensive substitute for the real deal.

    Was this answer helpful?

    0 comments No comments