SCCM scan failed 0x80244022 is the error that fills WUAHandler.log when your Windows clients cannot complete a software update scan, and the compliance column in the console turns to Unknown. It looks like a client problem, but it almost never is. The code is a WSUS HTTP 503 coming back from IIS on your software update point, and the fix is a couple of settings on the WSUS application pool, not a rebuild of client WMI.
What SCCM Scan Failed 0x80244022 Really Means
Windows Update Agent error 0x80244022 translates to HTTP status 503, service temporarily overloaded. When a Configuration Manager client scans for updates, the Windows Update Agent connects to the WSUS server on the software update point. If IIS answers with a 503, the scan fails and the client logs the error. As Microsoft explains in its WSUS troubleshooting article, the usual reason SCCM scan failed 0x80244022 appears is that the WsusPool application pool is stopped, with the Private Memory Limit still at the default of 1843200 KB.
That matters for how you troubleshoot SCCM scan failed 0x80244022. If one machine fails and the rest are fine, look at that client. If many clients fail at the same time, or the failures come and go during the day, look at the server. A pool that hits its memory limit recycles or stops, every client that connects in that window gets a 503, and the pool comes back until the next burst of scans.
Symptoms: How to Spot the Error in the Logs
On an affected client, open C:\Windows\CCM\Logs\WUAHandler.log in CMTrace. The pattern for SCCM scan failed 0x80244022 looks like this:

Scan failed with error = 0x80244022.OnSearchComplete - Failed to end search job. Error = 0x80244022.- Software updates show as Unknown in the console compliance view, because the site never received a state message from those clients.
- On the WSUS server itself, opening Update Services gives a Connection Error, and browsing to
http://WSUS01:8530returns HTTP Error 503. The service is unavailable. - WSUS synchronization fails with message ID 6703 and the text “The request failed with HTTP status 503: Service Unavailable”.
Microsoft documents that last group of symptoms for the same root cause as SCCM scan failed 0x80244022, so if you see them on the SUP, you can skip client-side troubleshooting entirely.
Step 1: Confirm the Cause of SCCM Scan Failed 0x80244022 on the Server
Run this on the software update point from an elevated PowerShell prompt. The first command shows whether the pool is running, and the second asks the WSUS client web service for a response the same way a client does:
Import-Module WebAdministration
Get-WebAppPoolState -Name WsusPool
(Invoke-WebRequest -Uri "http://WSUS01:8530/ClientWebService/client.asmx" -UseBasicParsing).StatusCodeCode language: JavaScript (javascript)Replace WSUS01 with your SUP name, and use port 8531 with https if your SUP is configured for SSL. A healthy server returns 200. A stopped pool returns a 503 error instead. Then look for the recycle events in the System log:
Get-WinEvent -FilterHashtable @{LogName="System"; ProviderName="WAS"} -MaxEvents 100 |
Where-Object { $_.Message -like "*WsusPool*" } |
Select-Object TimeCreated, Id, MessageCode language: JavaScript (javascript)Messages that say the pool requested a recycle because it reached its private bytes memory limit confirm the diagnosis. Also glance at Task Manager during a scan wave: a w3wp.exe process for WsusPool sitting near the limit tells you the same thing.
Step 2: Raise the WsusPool Private Memory Limit
The WsusPool Private Memory Limit is the setting that most often decides whether SCCM scan failed 0x80244022 shows up in your environment.
Microsoft recommends increasing the WsusPool Private Memory Limit to 4 GB (4000000 KB) and restarting the application pool, and notes that you may need 8 GB (8000000 KB) or higher depending on your environment. In IIS Manager, open Application Pools, right-click WsusPool, choose Advanced Settings, and set Private Memory Limit (KB) under Recycling. To script it:
Import-Module WebAdministration
Set-ItemProperty -Path "IIS:\AppPools\WsusPool" -Name recycling.periodicRestart.privateMemory -Value 4000000
Get-ItemProperty -Path "IIS:\AppPools\WsusPool" -Name recycling.periodicRestart.privateMemoryCode language: CSS (css)The same change with appcmd, if you prefer the classic tool:
%windir%\system32\inetsrv\appcmd.exe set apppool /apppool.name:WsusPool /recycling.periodicRestart.privateMemory:4000000Code language: JavaScript (javascript)Size the value to the server. Make sure the SUP actually has the RAM to give, because raising the limit on a starved server only moves the failure. Some community guides suggest 0, which removes the limit, but that lets a runaway pool consume the whole server, so a fixed higher value is the safer choice.
Step 3: Increase the Queue Length and Restart the Pool
During a big scan wave thousands of clients hit the pool at once. The IIS Queue Length setting defines how many requests can wait before IIS starts answering 503. Community guidance for this exact error, such as Anoop Nair’s write-up, recommends raising it from the default of 1000 to 30000. Microsoft’s WSUS article does not list this value, so treat it as a practical hardening step and test it in your environment.
Set-ItemProperty -Path "IIS:\AppPools\WsusPool" -Name queueLength -Value 30000
Restart-WebAppPool -Name WsusPool
Get-WebAppPoolState -Name WsusPoolCode language: JavaScript (javascript)
Restarting the pool briefly interrupts client scans and the SUP, and it is the step that actually clears SCCM scan failed 0x80244022 for waiting clients, so do it outside the monthly patch window if you can. The state should come back as Started.
Step 4: Trigger a Software Updates Scan Cycle and Verify the Fix
After the fix, SCCM scan failed 0x80244022 should disappear on the next scan. Do not wait for the next scan schedule. On a test client, run the Software Updates Scan Cycle. Microsoft notes that this action is a forced online scan, so it always connects to WSUS, which makes it the right test for this problem. The schedule ID for the scan cycle is 113:
Invoke-CimMethod -Namespace root\ccm -ClassName SMS_Client -MethodName TriggerSchedule -Arguments @{ sScheduleID = "{00000000-0000-0000-0000-000000000113}" }
Get-Content "C:\Windows\CCM\Logs\WUAHandler.log" -Tail 30Code language: JavaScript (javascript)You should no longer see the SCCM scan failed 0x80244022 line. The client now sends state messages, which flow to the management point in bulk every 15 minutes and then to the site server. After that, the Unknown entries in compliance should turn into Required or Installed. Check that the server answers with 200 as well:

Once the server answers with 200, SCCM scan failed 0x80244022 is resolved for every client that can reach the SUP. If the pool is healthy and your clients still fail, the failure is probably not a 503 any more. Compare the exact code in WUAHandler.log against the Windows Update error tables before changing anything else.
Step 5: Stop SCCM Scan Failed 0x80244022 from Coming Back
A bloated WSUS database makes every scan heavier and makes a WSUS HTTP 503 more likely, and heavy scans are what push the pool over its limit. Microsoft says that declining updates in WSUS improves performance by trimming the catalog sent to clients. Since Configuration Manager version 1906, the software update point can do this for you. In the console, go to Administration, Site Configuration, Sites, select the top-level site, choose Configure Site Components, open Software Update Point, and on the WSUS Maintenance tab enable these options (see Microsoft’s software updates maintenance guidance):
- Decline expired updates in WSUS according to supersedence rules
- Add non-clustered indexes to the WSUS database
- Remove obsolete updates from the WSUS database
Two caveats from the same page: remote software update points that use the Windows Internal Database cannot be reached for index and obsolete update maintenance, and the obsolete-update removal runs for a maximum of 30 minutes per synchronization. Those SUPs need maintenance scheduled manually, which Microsoft covers in its complete guide to WSUS and Configuration Manager SUP maintenance. For a one-off cleanup on a WSUS server, the built-in cmdlet works:
Invoke-WsusServerCleanup -CleanupObsoleteUpdates -DeclineExpiredUpdates -CleanupUnneededContentFilesRun it during a quiet window, because it can take a long time on a database that has never been cleaned. You can confirm the Configuration Manager side by looking for Successfully completed WSUS Cleanup. in WSyncMgr.log on the site server.
When SCCM Scan Failed 0x80244022 Is Not a Pool Problem
If the WsusPool is running with a high limit and you still see SCCM scan failed 0x80244022 on only a few machines, check the client network path. A reader of the Anoop Nair article reports fixing a handful of devices by excluding the SCCM server from the WinHTTP proxy settings. Check what the client is using with netsh winhttp show proxy and test a direct connection to the SUP port. If the server itself ran out of memory for an extended time, a reboot plus the settings above is the cleaner path.
For deployment follow-ups, the same logic applies to other SCCM issues: verify the server side before you touch clients. Read more: How To Allow Clients to Download Delta Content in SCCM
Read more: How to Best Using SCCM Filter Devices in a Specific Organizational Unit (OU)
Read more: How to Fix “PXE Boot Aborted” When a Task Sequence Isn’t Deployed Correctly
What does SCCM scan failed 0x80244022 mean?
It maps to HTTP status 503, service temporarily overloaded. The Windows Update Agent on the client reached the WSUS server on the software update point, and IIS answered with a 503, so the update scan failed.
What is the main cause of error 0x80244022 in Configuration Manager?
Microsoft names the WsusPool application pool in IIS being stopped, usually because the Private Memory Limit is still at the default of 1843200 KB. The pool hits the limit, recycles or stops, and clients get 503 responses.
What Private Memory Limit should I set for WsusPool?
Microsoft recommends 4 GB (4000000 KB) and restarting the pool, and says you may need 8 GB (8000000 KB) or more depending on the environment. Make sure the server has the RAM to support it.
Should I reinstall the SCCM client or repair WMI on affected machines?
Not first. When many clients fail with 0x80244022 at the same time, the cause is on the software update point. Fix the WSUS application pool, then trigger a Software Updates Scan Cycle on a test client.
How do I keep the WSUS 503 error from coming back?
Enable the WSUS Maintenance options in the Software Update Point component properties (decline expired updates, add indexes, remove obsolete updates) and keep enough memory on the SUP. Remote SUPs on Windows Internal Database need manual maintenance.
References
Microsoft Learn: WSUS messages and troubleshooting tips
Microsoft Learn: Software updates maintenance in Configuration Manager
Microsoft Learn: Introduction to software updates in Configuration Manager
Microsoft Learn: The complete guide to WSUS and Configuration Manager SUP maintenance
Anoop Nair: Fix Scan failed with error 0x80244022 Service is Temporarily Overloaded Issue SCCM





