I have just used WSUS to update but it did not come up with the 8.1 Update 1 options so updated using the manual download of the six updates required and it worked a treat. However, it did not cure the update problem and now I have error 80240442 when I check for updates
Windows Update Error (80244FFF)
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.
137 answers
Sort by: Oldest
-
Anonymous
2014-04-12T18:44:23+00:00 -
Anonymous
2014-04-13T00:46:09+00:00 When Update was released on Tuesday, Microsoft immediately pulled some of the WSUS update versions because while it apparently updated machines, it then broke them so they could not update again (sounds like deja vu of the problems we've been suffering for months).
If you are running the most recent version on an Windows Server 2012, then it did send out the full updates, but the earlier version of the app and an older version of Server did not get the updates.
For more, see: http://windowsitpro.com/windows-81/microsoft-suspending-distribution-windows-81-update-wsus-servers-due-bug
-
Anonymous
2014-04-19T17:23:35+00:00 I was able to get around this error by unchecking "Automatically detect settings" under Intenet Options -> Connections -> LAN Settings
-
Anonymous
2014-04-19T19:50:46+00:00 Magically windows update has started working like its supposed to. Did not seem to work after the "spring update"--same issue as everyone else has been having--but today I noticed a pending update. And when I force a windows update check it also works. Not sure what happened, except that this is not the result of anything that I have done, or at least anything I have intentionally done.
-
Anonymous
2014-04-21T00:59:10+00:00 Magically windows update has started working like its supposed to. Did not seem to work after the "spring update"--same issue as everyone else has been having--but today I noticed a pending update. And when I force a windows update check it also works. Not sure what happened, except that this is not the result of anything that I have done, or at least anything I have intentionally done.
Count me in as bewildered, confused and cautiously delighted at the same time. The exact same thing happened to me. Appreciate the memo which had me check my system. It has been months if not close to a year that I haven't been receiving updates without the proxy trick. Tonight I checked my updates and there was one waiting for me. I installed it and it rebooted the computer and now I can check for updates without error. Oddly, the update that was supposedly installed was 2919355. Unless I am mistaken that is the big update to 8.1 that includes changes to Metro like being able to close programs easily, a power button on the Metro screen, etc. Strange thing is that update was installed and had made those changes a week or two ago the day it came out. It wasn't until receiving that update that the error message morphed to 80240442. This update took like 60 seconds to install and then maybe delayed my reboot by 60 seconds at most. It wasn't a huge update. Totally confused.