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

NetLeverage
NetLeverage

Windows Update error 0x80244022 against WSUS: HTTP 503 and the WsusPool application pool

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.

A client that scans against your WSUS server and fails with 0x80244022 has been told "Service unavailable" by the server. Microsoft's Windows Update error list gives 0x80244022 as WU_E_PT_HTTP_STATUS_SERVICE_UNAVAIL, "Same as HTTP status 503 – The service is temporarily overloaded." On a WSUS server, the web site that answers is served by the WsusPool application pool in IIS, so that pool is where to look first.

Two situations are documented by Microsoft: the pool is stopped or hitting its default memory limit, and a build-up of test records in the WSUS catalogue that overloads the pool. Check which one you have before changing anything. The catalogue cleanup deletes data from the WSUS database and needs a database backup first.

What the error means

Windows Update clients talk to WSUS over HTTP or HTTPS (ports 80, 443, 8530 and 8531 are the ones Microsoft lists for WSUS). 0x80244022 is the code a client reports when the server answers with HTTP 503. Microsoft's description of the code says "temporarily overloaded", so a server that is busy, and not only one that is down, can produce it.

Microsoft's WSUS messages page describes the matching console and web symptoms: the WSUS console shows "Error: Connection Error", and browsing to the WSUS Administration website, for example http://WSUS01:8530, fails with "HTTP Error 503. The service is unavailable". It then says: "In this situation, the most likely cause is that the WsusPool Application Pool in IIS is in a stopped state." It adds that the pool's Private Memory Limit (KB) "is probably set to the default value of 1843200 KB".

A second Microsoft page (KB 5121986, "Resolved: Windows Server Update Services sync operations issues and timeouts") describes a service degradation caused by a build-up of published test detectoids in the WSUS channel. Its error table lists 0x80244022 with HTTP 503 and "Service unavailable", and says it indicates "The WSUS application pool (WsusPool) is overloaded." The page names Windows Server 2012 ESU, 2012 R2 ESU, 2016, 2019, 2022 and 2025 among the products it applies to. It says Microsoft deployed a mitigation on 18 July 2026 for new and rebuilt WSUS servers, and gives cleanup steps for servers that are still affected.

Likely causes

Cause What you see How to confirm
WsusPool is stopped Browsing to the WSUS site shows "HTTP Error 503. The service is unavailable"; clients log 0x80244022 In IIS Manager, Application Pools shows WsusPool as stopped
WsusPool hit its Private Memory Limit The same 503 page; Microsoft says the limit "is probably set to the default value of 1843200 KB" Advanced Settings for WsusPool shows Private Memory Limit (KB) at 1843200
Test detectoids built up in the WSUS catalogue Slow or timed-out syncs; clients also log 0x80244010, 0x8024400E, 0x80244007, 0x80240439 or 0x80072EE2 The read-only query in the last step of the checks below returns rows (titles starting "Product Detectoid for ProductName TestProduct")

Prove the cause before changing anything

All of these checks only read.

  1. On a client that fails, find the WSUS address in the registry key Microsoft names for scan troubleshooting, HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate.
  2. From that client, browse to the WSUS site address, for example http://wsus01.contoso.com.au:8530. Microsoft's WSUS page shows that an unavailable pool returns "HTTP Error 503. The service is unavailable".
  3. On the WSUS server, open Internet Information Services (IIS) Manager and select Application Pools. Look at the state of WsusPool.
  4. Right-click WsusPool, select Advanced Settings, and read Private Memory Limit (KB). Write the number down.
  5. Open the WSUS console. Microsoft's WSUS page lists "Error: Connection Error" in the console alongside the 503 page, so the same pool is where that message points too.
  6. Check for the detectoids before any cleanup. In SQL Server Management Studio, run only the SELECT taken from Microsoft's cleanup query, against each SUSDB. It changes nothing. Go on to the cleanup only if it returns rows:
SELECT u.UpdateID
FROM dbo.tbUpdate u
JOIN dbo.tbRevision r ON r.LocalUpdateID = u.LocalUpdateID AND r.IsLatestRevision = 1
JOIN dbo.tbProperty p ON p.RevisionID = r.RevisionID
JOIN dbo.tbLocalizedPropertyForRevision tbrp ON tbrp.RevisionID = r.RevisionID
JOIN dbo.tbLocalizedProperty tlp ON tlp.LocalizedPropertyID = tbrp.LocalizedPropertyID
WHERE p.UpdateType = 'Detectoid'
  AND tbrp.LanguageID = p.DefaultPropertiesLanguageID
  AND tlp.Title LIKE 'Product Detectoid for ProductName TestProduct%';

Example (illustrative): at contoso.com.au the WSUS server wsus01 serves about 200 servers and laptops. Clients log 0x80244022 from Monday morning. http://wsus01.contoso.com.au:8530 returns "HTTP Error 503. The service is unavailable". IIS Manager shows WsusPool stopped, and Private Memory Limit (KB) reads 1843200, the default Microsoft names. That matches the first two rows of the table, so the memory limit is the first change to make, not the database cleanup.

Fix

Pool stopped or memory limit reached

Microsoft's WSUS page says to increase the Private Memory Limit to 4 GB (4000000 KB) and restart the application pool, and that "It may be necessary to increase the Private Memory Limit to 8GB (8000000 KB) or higher depending on the environment."

Before you change it, write down the value you read in the last section (for example 1843200). That number is your way back.

Disruptive step: the next steps change the WsusPool memory limit and restart the pool. WSUS stops answering clients and the console while the pool restarts. Choose a time when few clients are scanning.

  1. In IIS Manager, select Application Pools in the Connections pane, then select WsusPool, right-click and select Advanced Settings.
  2. Set Private Memory Limit (KB) to 4000000.
  3. Select OK to apply the setting, then restart the application pool. If WsusPool is stopped, start it.

To undo it: repeat steps 1 and 2 and enter the value you wrote down (for example 1843200), select OK, then restart the application pool.

Test detectoids still in the catalogue

Use this only if the SELECT in step 6 of the checks returned rows. Microsoft's page asks you to back up each SUSDB database first, because "The cleanup permanently deletes update metadata and cannot be reversed without a backup."

Before you run the cleanup, back up the database with Microsoft's command, replacing the folder path with a real one. Use a different file name for each SUSDB and for each run, because WITH INIT overwrites an existing file of the same name, and an earlier backup must never be overwritten:

BACKUP DATABASE SUSDB
TO DISK = N'<C:\Backup folder>\SUSDB_PreDetectoidCleanup.bak'
WITH INIT, STATS = 5;

Risk: the next step deletes the mis-published detectoid records from the WSUS database and sets the MaxXMLPerRequest value to 0, which removes the 5 MB request limit. Microsoft says it must be run from SQL Server Management Studio against every SUSDB database, including WSUS replicas, because deletions do not propagate between WSUS servers.

Run Microsoft's cleanup query against each SUSDB. The query below is Microsoft's, without its comments:

SET NOCOUNT ON;
UPDATE tbConfigurationC SET MaxXMLPerRequest = 0
DECLARE @updateID uniqueidentifier;
DECLARE @retcode  int;
DECLARE @deleted  int = 0;
DECLARE @skipped  int = 0;
DECLARE detectoid_cur CURSOR LOCAL FAST_FORWARD FOR
    SELECT u.UpdateID
    FROM dbo.tbUpdate u
    JOIN dbo.tbRevision r ON r.LocalUpdateID = u.LocalUpdateID AND r.IsLatestRevision = 1
    JOIN dbo.tbProperty p ON p.RevisionID = r.RevisionID
    JOIN dbo.tbLocalizedPropertyForRevision tbrp ON tbrp.RevisionID = r.RevisionID
    JOIN dbo.tbLocalizedProperty tlp ON tlp.LocalizedPropertyID = tbrp.LocalizedPropertyID
    WHERE p.UpdateType = 'Detectoid'
      AND tbrp.LanguageID = p.DefaultPropertiesLanguageID
      AND tlp.Title LIKE 'Product Detectoid for ProductName TestProduct%';
OPEN detectoid_cur;
FETCH NEXT FROM detectoid_cur INTO @updateID;
WHILE @@FETCH_STATUS = 0
BEGIN
    BEGIN TRY
        EXEC @retcode = dbo.spDeleteUpdateByUpdateID @updateID;
        IF @retcode = 0 SET @deleted += 1; ELSE SET @skipped += 1;
    END TRY
    BEGIN CATCH
        SET @skipped += 1;
        PRINT CONCAT('Skipped ', CONVERT(varchar(40), @updateID), ' : ', ERROR_MESSAGE());
    END CATCH
    FETCH NEXT FROM detectoid_cur INTO @updateID;
END
CLOSE detectoid_cur;
DEALLOCATE detectoid_cur;

To undo it: restore the backup you took first; there is no other way back from the deletion. Microsoft's page gives no restore command, so use your normal SQL Server restore procedure and plan for the WSUS service being stopped while you do it.

Microsoft's note on the cleanup says it may be necessary to limit the maximum concurrent connections setting for the WSUS Administration site in IIS and raise it slowly, aiming to keep IIS around 80% CPU, so clients can finish scanning.

Once clients scan successfully, Microsoft says to put the limit back to its default. The value you are leaving behind is the 0 that the cleanup query set. Microsoft's page gives no command that reads the value the server held before the cleanup, so the step sets Microsoft's default of 5242880, which may differ from what the server used earlier.

Risk: the next command writes the MaxXMLPerRequest value back to 5242880, which re-applies the 5 MB request limit that the cleanup removed. Run it only after WSUS is stable and clients have scanned.

UPDATE tbConfigurationC SET MaxXMLPerRequest = 5242880

To undo it, run this statement. That removes the limit again, so use it only if clients begin failing to scan once the limit is back:

UPDATE tbConfigurationC SET MaxXMLPerRequest = 0

Microsoft's page lists three follow-up jobs after the cleanup: reindex SUSDB, run the WSUS Server Cleanup Wizard, and run IISReset or recycle the WsusPool application pool to clear cached catalogue state. Microsoft's page gives no steps for the first two. The Server Cleanup Wizard deletes data and a reindex works on the database itself, so each needs its own backup and plan.

Disruptive step: running IISReset, or recycling WsusPool, interrupts the WSUS site and the console for the moment the web service restarts, and every client scanning at that moment sees a failed request.

Once the cleanup and any follow-up jobs you chose are done, run IISReset from an elevated command prompt:

IISReset

Recycling the WsusPool pool in IIS Manager is the portal alternative. Nothing needs undoing: the web service starts again by itself.

Confirm the fix

  • Browse to the WSUS site address from a client. The 503 page should be gone.
  • WsusPool shows as started in IIS Manager and stays started.
  • Trigger a scan on a client. Microsoft says the first scan after cleanup does a one-time catch-up and "may take longer than usual".
  • In the client's WindowsUpdate.log, the scan entry "evaluated appl. rules of X out of N deployed entities" should show a much lower N after the next scan. Microsoft notes that searching the log for the detectoid IDs returns nothing, so use that count.

What to watch afterwards

  • Whether WsusPool stops again. Microsoft's page says it may be necessary to raise the limit to 8 GB (8000000 KB) or higher depending on the environment.
  • Other codes in the same table on clients that still fail, for example 0x80244010, which Microsoft calls the key symptom of the detectoid problem.
  • Downstream WSUS servers. Microsoft says clients that report to a downstream server that has not been cleaned will keep reporting the detectoids.
  • The client-side DataStore.edb file does not shrink after the cleanup. Microsoft says this is expected and does not affect scan performance.

Risks and limits

These commands have not been run or lab-tested.

Microsoft's WSUS messages page says the pool's limit is "probably set to the default value of 1843200 KB", and gives no rule for sizing the limit to a number of clients. The 4 GB and 8 GB values are Microsoft's examples. KB 5121986 describes an incident dated July 2026; a WSUS server built after Microsoft's 18 July 2026 mitigation is described as not affected by that particular cause, so a 503 there points back to the pool state and load.

The database cleanup deletes data. Take the backup before the query on every SUSDB, and run the query on each one separately.

Sources