Applies to: :heavy_check_mark: Windows VMs
Summary
Windows Update error 0x80244007 typically occurs when Windows clients or virtual machines (VMs) try to scan and download updates from Windows Server Update Services (WSUS) or Configuration Manager endpoints. This error is commonly linked to Simple Object Access Protocol (SOAP) faults that are returned by the server during the update process. This error indicates issues that affect communication or configuration between the client and the update service.
Prerequisites
For Microsoft Azure VMs that are running Windows, make sure that you back up the OS disk. For more information, see About Azure Virtual Machine restore.
How to identify the issue
Symptom 1
When a WSUS client computer scans for updates on the WSUS server, the following error entry is logged in the WindowsUpdate.log file on the client computer:
WS error: <detail><ErrorCode>InvalidParameters</ErrorCode><Message>parameters.InstalledNonLeafUpdateIDs</Message><ID>GUID</ID><Method> http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"</Method></detail>"
*FAILED* [80244007] SyncUpdates_WithRecovery failed
This issue occurs when the number of updates to be synchronized exceeds the maximum number of installed prerequisites that a WSUS client can pass to SyncUpdates.
Symptom 2
Updates don't install, and the scan itself fails because of an issue that affects the OtherCachedUpdateIDs parameter. You might see log entries in C:\Windows\Logs\WindowsUpdate.log that resemble the following example:
2015-10-30 17:12:53:980 880 1160 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 584; does use network; is at background priority
2015-10-30 17:12:54:073 880 1160 WS WARNING: Nws Failure: errorCode=0x803d0013
2015-10-30 17:12:54:073 880 1160 WS WARNING: The body of the received message contained a fault.
2015-10-30 17:12:54:073 880 1160 WS WARNING: Soap fault info:
2015-10-30 17:12:54:073 880 1160 WS WARNING: reason: Fault occurred
2015-10-30 17:12:54:073 880 1160 WS WARNING: code: Client
2015-10-30 17:12:54:073 880 1160 WS WARNING: detail: <detail><ErrorCode>InvalidParameters</ErrorCode><Message>parameters.OtherCachedUpdateIDs</Message><ID>8889e6f6-cc94-4b2b-9d0c-9818649a5dfc</ID><Method>"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"</Method></detail>
2015-10-30 17:12:54:073 880 1160 WS WARNING: Soap fault detail: errorCode='InvalidParameters', message='parameters.OtherCachedUpdateIDs', id='8889e6f6-cc94-4b2b-9d0c-9818649a5dfc', method='"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"'
2015-10-30 17:12:54:073 880 1160 WS FATAL: OnCallFailure failed with hr=0X80244007
2015-10-30 17:12:54:073 880 1160 PT WARNING: PTError: 0x80244007
2015-10-30 17:12:54:073 880 1160 PT WARNING: SyncUpdates_WithRecovery failed.: 0x80244007
2015-10-30 17:12:54:073 880 1160 IdleTmr WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 584) stopped; does use network; is at background priority
Symptom 3
The check for updates fails and generates internal server error code: 0x80244007 together with error code: 0x803d0013. These error codes are caused by a missing WSUS client entry that's used for authentication and authorization of client access. The Windows Update log shows:
2017-05-04 18:00:07:807 1676 117c PT +++++++++++ PT : Synchronizing server updates +++++++++++
2017-05-04 18:00:07:807 1676 117c PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = https://<wsusserver>/ClientWebService/client.asmx
2017-05-04 18:00:07:807 1676 117c EP Got WSUS SimpleTargeting URL: " https://<wsusserver> "
2017-05-04 18:00:07:807 1676 117c IdleTmr CIdleTimerHelper starting a WU operation (CAuthorizationCookieWrapper::InitializeSimpleTargetingCookie; does require network, is at background priority, will stop idle timer) from unspecified call
2017-05-04 18:00:07:807 1676 117c PT Initializing simple targeting cookie, clientId = , target group = special-01, DNS name = byolaq.bayer.cnb
2017-05-04 18:00:07:807 1676 117c PT Server URL = https://<wsusserver>/SimpleAuthWebService/SimpleAuth.asmx
2017-05-04 18:00:07:807 1676 117c WS Service URL='https://<wsusserver>/SimpleAuthWebService/SimpleAuth.asmx'.
2017-05-04 18:00:07:807 1676 117c WS Proxy List: '(null)', Bypass List: '(null)'.
2017-05-04 18:00:07:807 1676 117c WS Current service auth scheme='None'.
2017-05-04 18:00:07:807 1676 117c WS No proxy settings for this web service call.
2017-05-04 18:00:07:854 1676 1184 WS The SOAP message content is not xpress encoded.
2017-05-04 18:00:07:854 1676 117c WS WARNING: Nws Failure: errorCode=0x803d0013
2017-05-04 18:00:07:854 1676 117c WS WARNING: The body of the received message contained a fault .
2017-05-04 18:00:07:854 1676 117c WS WARNING: Soap fault info:
2017-05-04 18:00:07:854 1676 117c WS WARNING: reason: Fault occurred
2017-05-04 18:00:07:854 1676 117c WS WARNING: code: Server
2017-05-04 18:00:07:854 1676 117c WS WARNING: detail: <detail><ErrorCode> InternalServerError </ErrorCode><Message></Message><ID>9f8e13ac-3a64-41c6-a40b-cad7913fc1bb</ID><Method>" http://www.microsoft.com/SoftwareDistribution/Server/SimpleAuthWebService/GetAuthorizationCookie "</Method></detail>
2017-05-04 18:00:07:854 1676 117c WS FATAL: OnCallFailure failed with hr= 0X80244007
2017-05-04 18:00:07:854 1676 117c WS FATAL: NwsCallWithRetries<Functor>( Functor(_clientId, _targetGroupName, _dnsName, &_result)) failed with hr=0x80244007
Cause
This error is primarily caused by SOAP faults that are returned by the server during the update process. This issue can occur because of the following conditions:
- The client exceeded the maximum number of installed prerequisites that a WSUS client can pass to the
SyncUpdatesmethod. - Issues that affect
OtherCachedUpdateIDsduring the update scan. - A missing WSUS client entry that's used for authentication and authorization of client access.
Resolution or troubleshooting steps
Resolution 1: Increase maxInstalledPrerequisites in WSUS configuration
Edit the web.config file on the WSUS server. The file is located at %programfiles%\Update Services\WebServices\ClientWebService\web.config. Change the value for maxInstalledPrerequisites from 400 to 800.
For more information, see Error 80244007 when a WSUS client scans for updates.
Resolution 2: Decline superseded updates in WSUS
Decline all superseded updates on the WSUS server. For detailed instruction to do this procedure, see PowerShell script to decline superseded updates in WSUS.
For more information, see The complete guide to WSUS and Configuration Manager SUP maintenance.
Resolution 2.1: Increase maxCachedUpdate in WSUS configuration
Edit the web.config file on the WSUS server at C:\Program Files\Update Services\WebServices\ClientWebService\web.config. Increase the maxCachedUpdate value.
Resolution 3: Reset the WSUS client
Open an elevated Command Prompt window on the affected WSUS client, and run the following commands in the given order:
net stop wuauservreg Delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v PingID /freg Delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v AccountDomainSid /freg Delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v SusClientId /freg Delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v SusClientIDValidation /fnet start wuauservwuauclt.exe /resetauthorization /detectnow
You might receive messages such as the following message:
ERROR: The system was unable to find the specified registry key or value
These messages are expected and don't require mitigation.
After all the commands are run, wait 10-15 minutes, go to Control Panel > All Control Panel Items > Windows Update, check for updates, and monitor the status.
Source: Microsoft Learn / IT Pro troubleshooting by Microsoft and contributors. Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.
