Software update error codes in Configuration Manager: 0x80244022, 0x800F081F and more

When a Configuration Manager client fails to scan for or install software updates, the console and the logs give you a number, not a reason. This quick reference lists the Windows Update Agent, network and servicing codes that software update deployments report most often, with the official meaning, the usual cause in a Configuration Manager environment and the first thing to check.

How to read these codes#

• Console: in Monitoring › Deployments, select the software update deployment and View Status; the Error tab groups devices by error code. Software Center shows the code on a failed update.
• WUAHandler.log (in C:\Windows\CCM\Logs) records scan and install results. It only passes on what the Windows Update Agent reported, so the detail is in WindowsUpdate.log, which you generate with Get-WindowsUpdateLog.
• UpdatesDeployment.log and UpdatesHandler.log track deployment evaluation, downloads and installs; CAS.log, ContentTransferManager.log and DataTransferService.log show content downloads.
• CBS.log holds the detail for servicing stack errors such as 0x800F081F.

The prefix tells you the layer: 0x8024xxxx comes from the Windows Update Agent, 0x80072xxx from the network stack, 0x800Fxxxx and most 0x8007xxxx codes in CBS.log from servicing, and 0x800Bxxxx from certificate trust checks. Configuration Manager's own 0x87D0xxxx codes aren't covered here; use the Error Lookup tool in CMTrace (Tools menu). Some reports show negative decimals, which PowerShell converts:

'0x{0:X8}' -f -2145107934   # returns 0x80244022

Feature update failures such as 0xC1900101 are in the feature update and upgrade error codes quick reference; for Intune-managed devices, see the Windows Update error codes for Intune admins.

Scan: reaching the software update point#

These codes appear in WUAHandler.log as a failed scan. Start by testing, from the client, the WSUS URLs that Microsoft's scan troubleshooting uses, with your SUP's name and WSUS port (80/443 or 8530/8531):

$sup = 'http://sup01.contoso.com:8530'
Invoke-WebRequest "$sup/Selfupdate/wuident.cab" -UseBasicParsing | Select-Object StatusCode
Invoke-WebRequest "$sup/ClientWebService/wusserverversion.xml" -UseBasicParsing | Select-Object StatusCode
Test-NetConnection -ComputerName sup01.contoso.com -Port 8530
netsh winhttp show proxy

Network and proxy#

HTTP status returned by WSUS or a proxy#

WSUS protocol and policy#

Client components#

For damaged Windows Update components, Microsoft's reset is to stop the service, rename the data store and scan again:

net stop wuauserv
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
net start wuauserv

Download and content trust#

Installation#

Servicing stack and component store#

These come from the servicing stack; search %windir%\Logs\CBS\CBS.log for the code around the failure time. The repair for most of them:

Dism.exe /Online /Cleanup-Image /RestoreHealth
Sfc.exe /Scannow

If the device can't reach Windows Update for repair files, point DISM at matching media, for example /Source:wim:D:\sources\install.wim:1 /LimitAccess.

Codes that aren't failures#

How to verify a fix#

1. On the client, open the Configuration Manager control panel and, on the Actions tab, run Software Updates Scan Cycle and then Software Updates Deployment Evaluation Cycle.
2. WUAHandler.log shows a completed scan with no error code, and the update is listed as missing or installed as you expect.
3. Check for a pending restart and for deployed updates that are still waiting or failed (ErrorCode is shown in decimal):

Invoke-CimMethod -Namespace root\ccm\ClientSDK -ClassName CCM_ClientUtilities -MethodName DetermineIfRebootPending
Get-CimInstance -Namespace root\ccm\ClientSDK -ClassName CCM_SoftwareUpdate |
    Select-Object ArticleID, Name, EvaluationState, ErrorCode

4. In the console, the devices move from Error to Compliant in the deployment status after the client sends its next state messages.

For full walk-throughs, see updates not installing, software update point sync failures, WSUS maintenance and deployments waiting for a maintenance window.

References#

• Windows Update error codes by component (Microsoft Learn): names and meanings
• Windows Update common errors and mitigation (Microsoft Learn): CBS, network and agent mitigations
• Troubleshoot software update scan failures in Configuration Manager (Microsoft Learn)
• Troubleshoot software update deployments in Configuration Manager (Microsoft Learn)
• Third-party updates fail to install with error 0x800b0109 (Patch My PC knowledge base): 0x800B0109 and 0x800B0004