Skip to content

Commit 4be5931

Browse files
ryanberg-aquentryanberg-aquent
committed
updates for 8138
1 parent 2848cbf commit 4be5931

2 files changed

Lines changed: 126 additions & 0 deletions

File tree

‎support/windows-server/installing-updates-features-roles/media/troubleshoot-windows-update-error-0x80244007/error0x80244007.png‎

233 KB
Loading

‎support/windows-server/installing-updates-features-roles/troubleshoot-windows-update-error-0x80244007.md‎

Lines changed: 126 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,126 @@
1+
---
2+
title: Troubleshoot Windows Update Error 0x80244007
3+
description: Learn how to resolve the Windows Update error 0x80244007, which occurs during update scans.
4+
manager: dcscontentpm
5+
audience: itpro
6+
ms.date: 11/7/2025
7+
ms.topic: troubleshooting
8+
ms.reviewer: scotro, mwesley, jarretr, v-ryanberg, v-gsitser
9+
ms.custom:
10+
- sap:windows servicing,updates and features on demand\Windows Update - Install errors starting with 0x8024 (WU E Setup)
11+
- pcy:WinComm Devices Deploy
12+
appliesto:
13+
- <a href=https://learn.microsoft.com/windows/release-health/windows-server-release-info target=_blank>Supported versions of Windows Server</a>
14+
---
15+
16+
# Troubleshoot Windows Update error 0x80244007
17+
18+
**Applies to:** :heavy_check_mark: Windows VMs
19+
20+
## Summary
21+
22+
The Windows Update error 0x80244007 normally occurs when Windows clients or virtual machines (VMs) attempt 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 returned by the server during the update process. This indicates issues with communication or configuration between the client and the update service.
23+
24+
:::image type="content" source="./media/troubleshoot-windows-update-error-0x80244007/error0x80244007.png" alt-text="Windows Update error 0x80244007" lightbox="media/troubleshoot-windows-update-error-0x80244007/error0x80244007.png":::
25+
26+
## Prerequisites
27+
28+
For VMs running Windows in Azure, make sure that you back up the OS disk. For more information, see [About Azure Virtual Machine restore](/azure/backup/about-azure-vm-restore).
29+
30+
## How to identify the issue
31+
32+
### Symptom 1
33+
34+
When a WSUS client computer scans for updates on the WSUS server, you might see the following error message in the `WindowsUpdate.log` file on the client computer:
35+
36+
```output
37+
WS error: <detail><ErrorCode>InvalidParameters</ErrorCode><Message>parameters.InstalledNonLeafUpdateIDs</Message><ID>GUID</ID><Method> http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"</Method></detail>"
38+
*FAILED* [80244007] SyncUpdates_WithRecovery failed
39+
```
40+
41+
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`.
42+
43+
### Symptom 2
44+
45+
Updates fail to install, and the scan itself fails due to an issue with `OtherCachedUpdateIDs`. You might see similar log entries in *C:\Windows\Logs\WindowsUpdate.log* as shown in the following example:
46+
47+
```output
48+
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
49+
2015-10-30 17:12:54:073 880 1160 WS WARNING: Nws Failure: errorCode=0x803d0013
50+
2015-10-30 17:12:54:073 880 1160 WS WARNING: The body of the received message contained a fault.
51+
2015-10-30 17:12:54:073 880 1160 WS WARNING: Soap fault info:
52+
2015-10-30 17:12:54:073 880 1160 WS WARNING: reason: Fault occurred
53+
2015-10-30 17:12:54:073 880 1160 WS WARNING: code: Client
54+
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>
55+
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"'
56+
2015-10-30 17:12:54:073 880 1160 WS FATAL: OnCallFailure failed with hr=0X80244007
57+
2015-10-30 17:12:54:073 880 1160 PT WARNING: PTError: 0x80244007
58+
2015-10-30 17:12:54:073 880 1160 PT WARNING: SyncUpdates_WithRecovery failed.: 0x80244007
59+
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
60+
```
61+
62+
### Symptom 3
63+
64+
The check for updates fails with the internal server `error code: 0x80244007` along with `error code: 0x803d0013`. These are caused by a missing WSUS client entry used for authentication and authorization of client access. The `Windows Update` log shows:
65+
66+
```output
67+
2017-05-04 18:00:07:807 1676 117c PT +++++++++++ PT : Synchronizing server updates +++++++++++
68+
2017-05-04 18:00:07:807 1676 117c PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = https://<wsusserver>/ClientWebService/client.asmx
69+
2017-05-04 18:00:07:807 1676 117c EP Got WSUS SimpleTargeting URL: " https://<wsusserver> "
70+
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
71+
2017-05-04 18:00:07:807 1676 117c PT Initializing simple targeting cookie, clientId = , target group = special-01, DNS name = byolaq.bayer.cnb
72+
2017-05-04 18:00:07:807 1676 117c PT Server URL = https://<wsusserver>/SimpleAuthWebService/SimpleAuth.asmx
73+
2017-05-04 18:00:07:807 1676 117c WS Service URL='https://<wsusserver>/SimpleAuthWebService/SimpleAuth.asmx'.
74+
2017-05-04 18:00:07:807 1676 117c WS Proxy List: '(null)', Bypass List: '(null)'.
75+
2017-05-04 18:00:07:807 1676 117c WS Current service auth scheme='None'.
76+
2017-05-04 18:00:07:807 1676 117c WS No proxy settings for this web service call.
77+
2017-05-04 18:00:07:854 1676 1184 WS The SOAP message content is not xpress encoded.
78+
2017-05-04 18:00:07:854 1676 117c WS WARNING: Nws Failure: errorCode=0x803d0013
79+
2017-05-04 18:00:07:854 1676 117c WS WARNING: The body of the received message contained a fault .
80+
2017-05-04 18:00:07:854 1676 117c WS WARNING: Soap fault info:
81+
2017-05-04 18:00:07:854 1676 117c WS WARNING: reason: Fault occurred
82+
2017-05-04 18:00:07:854 1676 117c WS WARNING: code: Server
83+
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>
84+
2017-05-04 18:00:07:854 1676 117c WS FATAL: OnCallFailure failed with hr= 0X80244007
85+
2017-05-04 18:00:07:854 1676 117c WS FATAL: NwsCallWithRetries<Functor>( Functor(_clientId, _targetGroupName, _dnsName, &_result)) failed with hr=0x80244007
86+
```
87+
88+
## Root cause
89+
90+
This error is primarily caused by SOAP faults returned by the server during the update process. This can occur due to:
91+
92+
- Exceeding the maximum number of installed prerequisites that a WSUS client can pass to `SyncUpdates`.
93+
- Issues with `OtherCachedUpdateIDs` during the update scan.
94+
- A missing WSUS client entry used for authentication and authorization of client access.
95+
96+
## Resolution or troubleshooting steps
97+
98+
### Mitigation 1: Increase `maxInstalledPrerequisites` in WSUS configuration
99+
100+
Edit the `web.config` file on the WSUS server located at *%programfiles%\Update Services\WebServices\ClientWebService\web.config*. Change the value for **maxInstalledPrerequisites** from **400** to **800**.
101+
102+
For more information, see [Error 80244007 when a WSUS client scans for updates](/mem/configmgr/update-management/error-80244007-when-wsus-client-scans-updates).
103+
104+
### Mitigation 2: Decline superseded updates in WSUS
105+
106+
Decline all superseded updates on the WSUS server. Detailed instruction on how to do this can be found at [PowerShell script to decline superseded updates in WSUS](/mem/configmgr/update-management/decline-superseded-updates).
107+
108+
For more information, see [The complete guide to WSUS and Configuration Manager SUP maintenance](/mem/configmgr/update-management/wsus-maintenance-guide).
109+
110+
### Mitigation 2.1: Increase `maxCachedUpdate` in WSUS configuration
111+
112+
Edit the `web.config` file on the WSUS server at *C:\Program Files\Update Services\WebServices\ClientWebService\web.config*. Change the **maxCachedUpdate** value to a larger number.
113+
114+
### Mitigation 3: Resetthe WSUS client
115+
116+
Open an elevated command prompt on the affected WSUS client and run the following commands in this order:
117+
118+
1. `net stop wuauserv`
119+
2. `reg Delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v PingID /f`
120+
3. `reg Delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v AccountDomainSid /f`
121+
4. `reg Delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v SusClientId /f`
122+
5. `reg Delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v SusClientIDValidation /f`
123+
6. `net start wuauserv`
124+
7. `wuauclt.exe /resetauthorization /detectnow`
125+
126+
Messages like **ERROR: The system was unable to find the specified registry key or value** are normal and don't need mitigation. Once all the commands are run, wait for 10-15 minutes, go to **Control Panel > All Control Panel Items > Windows Update**, check for updates, and monitor the status.

0 commit comments

Comments
 (0)