Windows Update error 0x80244007: what it means and how to fix it

Published Sources checked By helps.wiki editorial team

0x80244007 is the Windows Update code WU_E_PT_SOAPCLIENT_SOAPFAULT: the update server answered the scan with a SOAP fault. It appears mostly on PCs that scan against WSUS or Configuration Manager, where the fix is on the server or in the logs. On a home PC, resetting the update caches and repairing system files are sensible first steps, though they are general practice and not a documented fix for this code.

Applies to:Windows 11Windows 10Windows Server 2019, 2022, 2025 (as WSUS/SCCM clients)
On this page

What it means

The code 0x80244007 stands for WU_E_PT_SOAPCLIENT_SOAPFAULT. Windows Update talks to its update server using a protocol called SOAP, and this code means the server replied with a fault instead of a normal answer. It is a wrapper: the detailed reason is reported separately as one of the WU_E_PT_SOAP_* codes (0x8024400B to 0x8024400E), so the message alone does not say what went wrong.

You will mostly meet it on computers managed by an organisation, where updates come from WSUS or Configuration Manager (SCCM/MECM) instead of directly from Microsoft. Microsoft's error tables list the code for Windows 10 and Windows 11, but I found no Microsoft documentation describing it on an ordinary home PC scanning Microsoft's public update service. For that reason the fixes below are split into home-PC steps (general practice) and managed-device steps.

Symptoms and causes

You are likely dealing with this problem if:

  • The scan for updates fails with 0x80244007.
  • On a managed machine, WUAHandler.log (the Configuration Manager client log) contains "Scan failed with error = 0x80244007".
  • In an SCCM report, newer servers show 0 required updates while Windows Server 2016 and older scan normally.

The usual causes, most common first:

Windows cannot renew its Windows Update cookies
This is the cause Microsoft states on its Common Windows Update errors page. It does not explain further why the renewal fails on Windows 10 or 11.
WSUS server-side limits
One third-party SCCM blog reports that since about February 2026, Server 2019 and later clients fail with this code against the software update point. The author suspects the default maxInstalledPrerequisites limit is being hit. This is a suspicion, not Microsoft guidance.
Other SOAP-level failures on the server or in the path
Inferred from Microsoft's code table: a server error (0x8024400E), a malformed request (0x8024400D), or a changed server or invalid cookie (0x80244015). The detailed code in the logs tells you which one applies.

How to fix it

Work through these in order. They start with the quickest, safest checks and move to deeper repairs; stop as soon as the problem is gone.

1.Restart, check the clock, run the troubleshooter

Easy

Cheap first checks for an unmanaged PC. They are general practice, not specific to this code.

  1. Restart the PC and try Windows Update again.
  2. Confirm the date, time and time zone are correct in Settings > Time & language > Date & time.
  3. Open Settings > System > Troubleshoot > Other troubleshooters and click Run next to Windows Update.

2.Check whether a WSUS policy is redirecting updates

Moderate

If the PC is pointed at an internal update server that is failing, the error comes from that server, not from Microsoft. This check is my suggestion, not from a Microsoft source.

  1. Open an elevated Command Prompt and generate a policy report, then open report.html and look for a Windows Update specified intranet update service.
    Command Promptrun as administrator
    gpresult /h report.html
  2. You can also look for a WUServer value in HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate (read only, do not change it on a work PC). If one is present, the PC is managed and you should contact your IT department.

3.Rename the Windows Update caches

ModerateChanges settings

Forces Windows to rebuild its local update download data. Microsoft documents a cache reset like this for 0x80242006, not for this code, so treat it as a general repair.

Before you start: Create a restore point first. Do this only on a PC you own; on a managed device ask your IT team.

  1. Open Command Prompt as administrator and stop the services.
    Command Promptrun as administrator
    net stop wuauserv
net stop bits
  2. Rename the cache folders.
    Command Promptrun as administrator
    Ren %systemroot%\SoftwareDistribution\DataStore DataStore.bak
Ren %systemroot%\SoftwareDistribution\Download Download.bak
  3. Start the services again and check for updates.
    Command Promptrun as administrator
    net start bits
net start wuauserv

4.Repair system files with DISM and SFC

Moderate

Microsoft documents these for component store corruption errors. They are not documented for this code, but they rule out damaged system files.

  1. In an elevated Command Prompt, run DISM.
    Command Promptrun as administrator
    Dism.exe /Online /Cleanup-Image /Restorehealth
  2. When it finishes, run System File Checker, then restart.
    Command Promptrun as administrator
    Sfc.exe /Scannow

5.Find the underlying SOAP fault in the logs (managed devices)

Advanced

Because 0x80244007 is a wrapper, the real cause is in the logs and on the update server.

  1. On a Configuration Manager client, open C:\Windows\CCM\Logs\WUAHandler.log and look for the scan failure and any WU_E_PT_SOAP_* code.
  2. Generate the Windows Update log from PowerShell and look for the same codes.
    PowerShellrun as administrator
    Get-WindowsUpdateLog
  3. Check the WSUS or software update point server and its IIS logs for errors at the time of the scan.

6.Raise the WSUS web service limits (server admins)

AdvancedBack up first

A single third-party report (System Center Dudes, 2026) says this restored scans on Server 2019 and later clients. It is not validated by Microsoft.

Before you start: Back up web.config before editing and try it outside business hours. Editing the WSUS web service configuration wrongly can break client scans for every device.

  1. On the WSUS server, copy C:\Program Files\Update Services\WebServices\ClientWebService\web.config to a safe location.
  2. Edit the original as administrator: change maxInstalledPrerequisites from 400 to 800 and maxCachedUpdates from 22000 to 44000.
  3. Restart IIS.
    Command Promptrun as administrator
    iisreset
  4. Trigger a Software Update Scan Cycle on a client. The author reports required-update counts rising a few hours later.
  5. To keep the catalogue small, expire superseded updates and decline expired ones, as the same author advises.

Check that it worked

  • Run Check for updates (or a Software Update Scan Cycle on a managed client) and confirm it completes without 0x80244007.
  • On managed machines, WUAHandler.log no longer shows "Scan failed with error = 0x80244007".

If it still fails

  • If the PC belongs to a workplace or school, send your IT team the WUAHandler.log or WindowsUpdate.log lines containing the WU_E_PT_SOAP_* code; the fix is probably on their server.
  • On a home PC where nothing worked, consult Microsoft Support with the DISM and SFC output.

Questions

Is 0x80244007 a problem with my Windows 11 installation?

Usually not. It is a message that the update server returned a fault, and it is most often seen with WSUS or Configuration Manager.

Where can I see other Windows Update error codes?

Microsoft's Windows Update error code list by component covers the full range. For a related permission error see Windows Update error 0x80070005.

Sources

  1. Windows Update error code list by componentOfficial · Microsoft Learn
  2. Common Windows Update errorsOfficial · Microsoft Learn
  3. Fix 0x80244007 error in SCCM (2026) · System Center Dudes

Browse