0x80244007 Error When Running Win Updates (Windows Server 2022 Standard)

Question

0x80244007 Error When Running Win Updates (Windows Server 2022 Standard)

Saunders Kimberly 0

How do I resolve error 0x80244007? Troubleshooted did not find any issues.

0 comments

3 answers

Your answer

Answer 1

Adam J. Marshall 11,031 MVP

I'll echo @Harry Phan 's comments. What I'll add is that WSUS maintenance is not just declining superseded updates, but rather a much more complex system including running SQL scripts (reindexing and other scripts) and running the Server Cleanup Wizard (SCW).

https://www.ajtek.ca/wsus/how-to-setup-manage-and-maintain-wsus-part-8-wsus-server-maintenance/

0 comments

Answer 2

Hello,

Error 0x80244007 on Windows Server 2022 typically points to a WSUS communication issue where the client cannot process the update metadata due to default limits being exceeded. The fix is to adjust the WSUS server configuration and reset the client’s update identity. On the WSUS server, edit %programfiles%\Update Services\WebServices\ClientWebService\web.config and increase the values for maxInstalledPrerequisites to 800 and maxCachedUpdates to 44000, then run iisreset to apply. On the affected client, stop the Windows Update service, clear the registry values under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate such as SusClientId, then restart the service and run wuauclt.exe /resetauthorization /detectnow. This forces the client to re-register with WSUS and request updates cleanly. If you are not using WSUS, confirm the server is set to scan directly against Microsoft Update, as this error is rare in that configuration. Also, regularly decline superseded updates in WSUS to reduce metadata size and prevent recurrence.

I hope you've found something useful here. If it helps you get more insight into the issue, it's appreciated to accept the answer. Should you have more questions, feel free to leave a message. Have a nice day!

HP.

Answer 3

Error 0x80244007 is a Windows Update SOAP fault. In WSUS-based environments, it is commonly caused by WSUS metadata/configuration issues, cached update ID issues, or a missing WSUS client identity entry.

For Windows Server 2022, use this troubleshooting path:

Confirm whether the server is scanning against WSUS This error in the provided guidance is tied to WSUS or Configuration Manager update endpoints.
If WSUS is in use, check the WSUS server first On the WSUS server:
- Verify Update Services and World Wide Web Publishing Service are running.
- Verify the Default website or WSUS Administration website is running.
- Review IIS logs in c:\inetpub\logfiles for WSUS errors.
Increase WSUS client web service limits On the WSUS server, edit: %programfiles%\Update Services\WebServices\ClientWebService\web.config Update these values:
```
   <add key="maxInstalledPrerequisites" value="800"/>
   <add key="maxCachedUpdates" value="44000"/>
```
This raises the defaults from 400 to 800 and from 22,000 to 44,000. Then run:
```
   IISReset
```
Decline superseded updates in WSUS Excess superseded updates can contribute to this issue. Decline superseded updates on the WSUS server.

Reset the affected WSUS client Warning: the following steps delete Windows Update client identity registry values and should be run in an elevated Command Prompt. Run these commands in 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

If The system was unable to find the specified registry key or value appears, that is expected. After that, wait 10–15 minutes, then open Control Panel > All Control Panel Items > Windows Update, check for updates, and monitor the result.

If the server is not using WSUS The provided material does not include a separate non-WSUS fix path for Windows Server 2022. The documented 0x80244007 resolutions here are WSUS-focused.