Australian cloud for business software — built and run in Sydney since 2002

NetLeverage
NetLeverage

Windows Update error 0x80244007 against WSUS: "SyncUpdates_WithRecovery failed" and the SOAP fault

Technical article
Troubleshooting

About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.

When a WSUS client scan fails with 0x80244007, the WindowsUpdate.log on the client shows *FAILED* [80244007] SyncUpdates_WithRecovery failed, and the server has answered with a SOAP fault. Microsoft's troubleshooting page says the error "is primarily caused by SOAP faults that are returned by the server during the update process" and names three conditions, each with its own log text.

Read the fault text in the client log before changing anything. The two fixes given here change WSUS server configuration or the client's identity at WSUS, so the fix follows the text, not the code.

What the error means

Microsoft's page "Troubleshoot Windows Update error 0x80244007" says the error "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", and that it "indicates issues that affect communication or configuration between the client and the update service." The three conditions it lists, with the log text that tells them apart, are:

  • Symptom 1: the client log shows WS error: <detail><ErrorCode>InvalidParameters</ErrorCode><Message>parameters.InstalledNonLeafUpdateIDs</Message> and then *FAILED* [80244007] SyncUpdates_WithRecovery failed. Microsoft says this happens "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 do not install, and the scan fails with the fault message parameters.OtherCachedUpdateIDs in C:\Windows\Logs\WindowsUpdate.log. Microsoft's cause is "Issues that affect OtherCachedUpdateIDs during the update scan."
  • Symptom 3: the check for updates fails with 0x80244007 together with 0x803d0013, and the fault detail reads InternalServerError, from the GetAuthorizationCookie call. Microsoft says these codes "are caused by a missing WSUS client entry that's used for authentication and authorization of client access."

The matching server-side entry for symptom 1 is in the SoftwareDistribution.log file on the WSUS server: an exception that includes "ErrorCode=InvalidParameters, Message=parameters.InstalledNonLeafUpdateIDs", according to Microsoft's web.config page.

An older Microsoft Support page for Windows RT, Windows 8 and Windows Server 2012 gives a fourth cause for the same code: "Windows cannot renew the cookies for Windows Update", fixed on those systems by update rollup 2883201.

Likely causes

Cause What you see How to confirm
Too many updates for the client's installed-prerequisites limit Client log: parameters.InstalledNonLeafUpdateIDs The same text appears in SoftwareDistribution.log on the WSUS server
A fault on the OtherCachedUpdateIDs parameter Client log: parameters.OtherCachedUpdateIDs; updates do not install Fault text in C:\Windows\Logs\WindowsUpdate.log
Missing WSUS client entry 0x80244007 with 0x803d0013 and InternalServerError on GetAuthorizationCookie Fault text in the log, from the GetAuthorizationCookie call to the SimpleAuth web service
Cookie not renewed (older systems) 0x80244007 on Windows RT, Windows 8 or Server 2012 Microsoft's page names rollup 2883201 as the fix

Prove the cause before changing anything

All of these only read.

  1. On a failing client, open C:\Windows\Logs\WindowsUpdate.log and find the lines around [80244007]. Note the Message in the SOAP fault detail: parameters.InstalledNonLeafUpdateIDs, parameters.OtherCachedUpdateIDs, or an InternalServerError with 0x803d0013.
  2. On the WSUS server, open the SoftwareDistribution.log file and look for the InvalidParameters exception with the same message. Microsoft's pages do not give its folder.
  3. On the WSUS server, open %programfiles%\Update Services\WebServices\ClientWebService\web.config in a text editor without saving, and read the two values maxInstalledPrerequisites and maxCachedUpdates. Write them down.

Example (illustrative): at contoso.com.au the WSUS server wsus01 serves about 150 servers and PCs. Several clients log [80244007] SyncUpdates_WithRecovery failed, and each fault detail reads parameters.InstalledNonLeafUpdateIDs. SoftwareDistribution.log on wsus01 shows the same message. web.config still reads 400 for maxInstalledPrerequisites and 22000 for maxCachedUpdates. That is symptom 1, so the server settings are the change to make.

Fix

Raise the limits on the WSUS server

Microsoft's web.config page gives this fix for the symptom 1 error, parameters.InstalledNonLeafUpdateIDs, and says "This change increases maxInstalledPrerequisites from 400 to 800 and maxCachedUpdates from 22,000 to 44,000." The troubleshooting page lists the two as resolution 1 and resolution 2.1 (it spells the second value maxCachedUpdate there), and recommends declining all superseded updates on the server as resolution 2. It does not say which resolution answers symptom 2 or symptom 3, so match the fix to the fault text you read.

Open an elevated Command Prompt on the WSUS server and go to %programfiles%\Update Services\WebServices\ClientWebService.

Before you change it, copy web.config to a new file name in the same folder, for example web.config.before, in File Explorer. Do not overwrite the copy later. Then read the file's current owner and write it down. Microsoft's dir page says the /q option "Displays file ownership information":

dir /q web.config

Then save the file's permissions to a new file name. Microsoft's icacls page says /save "Stores DACLs for all matching files into an access control list (ACL) file for later use with /restore." Create C:\Temp first if it does not exist:

icacls web.config /save C:\Temp\webconfig-acl-before.txt

Risk: the next commands change the owner of web.config and grant the Administrator account full control of it, then open it for editing. Microsoft's takeown page says that without the /a option "file ownership is given to the user who is currently logged on". The values you save apply to every WSUS client that scans this server, and IISReset interrupts WSUS while the web service restarts.

Run Microsoft's commands:

takeown /f web.config
icacls web.config /grant administrator:(F)
notepad.exe web.config

In web.config, change the two entries to Microsoft's values:

<add key="maxInstalledPrerequisites" value="800"/>
<add key="maxCachedUpdates" value="44000"/>

Save the file, then restart the web service:

IISReset

To undo it: open web.config again, put the two values back to the numbers you wrote down, and save it. Then restart the web service:

IISReset

If the file itself is damaged, close the editor and copy web.config.before back over web.config, then run IISReset again.

Then put the permissions back. Microsoft's icacls page says /restore applies the stored DACLs from the ACL file to files in the specified directory, and that it must be used with the directory parameter, so name the folder, not the file:

icacls "%programfiles%\Update Services\WebServices\ClientWebService" /restore C:\Temp\webconfig-acl-before.txt

Last, put the owner back. Microsoft's icacls page says /setowner "Changes the owner of all matching files to the specified user." In an elevated Command Prompt in the same folder, replace the placeholder with the owner you noted from dir /q:

icacls web.config /setowner "<owner you noted>"

Keep C:\Temp\webconfig-acl-before.txt and web.config.before until WSUS has run without errors for a few days.

Microsoft's resolution 2 says to decline all superseded updates on the WSUS server and points to a PowerShell script and to its WSUS maintenance guide. Microsoft's page gives no command in the page text and does not say how to reverse a decline, so plan it as a separate change.

Resolution 3: reset the WSUS client

Microsoft's page does not say which symptom this resolution answers. It is the one that deals with the WSUS client identity, so use it for the 0x803d0013 and InternalServerError text only if your earlier checks point there.

Microsoft's prerequisite for Azure VMs running Windows is to "back up the OS disk". For any computer, save the registry key the commands change.

Before you reset it, export the key to a new file name. Create C:\Temp first if it does not exist:

reg export "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" C:\Temp\wu-before.reg

If the export reports that the key cannot be found, there is nothing to save and no file to import, so do not run the import in the back-out below. Stop here and check the key path before running the reset.

Risk: the next commands stop the Windows Update service on this client and delete four values (PingID, AccountDomainSid, SusClientId and SusClientIDValidation) that identify the client to WSUS, then restart the service and ask for a new authorisation. Updates on this client pause while the service is stopped.

In an elevated Command Prompt on the affected client, run Microsoft's commands in this order:

net stop wuauserv
reg Delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v PingID /f
reg Delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v AccountDomainSid /f
reg Delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v SusClientId /f
reg Delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v SusClientIDValidation /f
net start wuauserv
wuauclt.exe /resetauthorization /detectnow

Microsoft says messages such as "ERROR: The system was unable to find the specified registry key or value" are "expected and don't require mitigation."

To undo it, stop the service, import the saved file, and start the service again. This overwrites any other value under that key that changed since the export, so use it only if you want the whole key back as it was:

net stop wuauserv
reg import C:\Temp\wu-before.reg
net start wuauserv

Confirm the fix

  • Microsoft says to wait 10 to 15 minutes after the commands, then check for updates in Windows Update and monitor the status.
  • In WindowsUpdate.log on the client, the [80244007] line should not appear after the next scan.
  • For the server change, watch SoftwareDistribution.log on the WSUS server for the InvalidParameters exception; it should stop for the clients that failed.
  • A client reset (resolution 3) should report to the WSUS server again. Check it in the console.

What to watch afterwards

  • The count of superseded updates on the WSUS server. Microsoft's resolution 2 says declining them is part of the fix, and its WSUS maintenance guide is the reference it names.
  • Clients that still fail with a different message in the fault detail. The three symptoms have different texts, so one fix does not cover all of them.
  • Other WSUS codes on the same clients. For HTTP 503 and the WsusPool application pool, the code is 0x80244022, which is a different fault.
  • Servers on older systems. Microsoft's older page ties the code on Windows RT, Windows 8 and Server 2012 to rollup 2883201.

Risks and limits

These commands have not been run or lab-tested.

Microsoft's pages give no folder for the server's SoftwareDistribution.log and no rule for choosing values other than 800 and 44000. Microsoft's web.config page names Windows Server 2012 to 2019 as the original product versions, and its troubleshooting page names "Supported versions of Windows Server" and says it applies to Windows VMs. Neither page says what happens on a WSUS server whose web.config already holds other values. The reset deletes identity values at the client, and Microsoft's page does not describe how WSUS shows the client afterwards.

Sources