## TL;DR
Error 0x80244022 is an HTTP 503 class failure: the server answering the update scan, often WSUS or a proxy in front of it, is overloaded or its application pool has stopped. Check whether the failure is fleet-wide, restore the WSUS application pool and IIS health, then retry the scan in smaller waves. On a single machine pointed at Microsoft Update, wait, verify time and proxy settings, and retry rather than rebuilding local components first.

```text
windows update error 0x80244022 service unavailable how to fix
```

## Use this when
- Several machines report 0x80244022 in the same window, or clients fail during peak scan hours.
- WSUS clients fail while the WSUS console is also slow, unresponsive, or resetting connections.
- WindowsUpdate.log shows an HTTP 503 response from the update server URL.

## Not for this skill when
- Only one machine fails and its logs show a local store error. Repair that client locally.
- The server returns a proxy authentication error instead of 503. Fix proxy credentials and bypass rules.

## Steps
1. Establish scope first: check two or three other clients and the WSUS console. A shared failure window means server side, so stop making changes on individual clients and record the start time and the server name clients are configured to use. Verify: you can state whether the fault is fleet-wide or single-client, with evidence from more than one machine
2. On the WSUS server, open IIS Manager and check the WsusPool application pool state. Start or recycle it, then check the WSUS Administration site is running and the server has free memory, because WsusPool recycles under memory pressure and drops scans with 503 responses. Verify: WsusPool is running and the WSUS console opens without a reset server node error
3. Review IIS and WSUS event logs plus available memory and database responsiveness. If the private memory limit on WsusPool is at its old default, raise it in line with Microsoft guidance for busy servers and recycle the pool during a quiet period. Verify: the pool stays up through a scan wave and event logs stop showing pool shutdown or connection reset entries
4. Reduce scan pressure: stagger client scan schedules or group policy detection frequency so hundreds of clients do not hit the server in the same minute, and temporarily pause any reporting job that hammers the WSUS database. Verify: client scans spread across the window and the server CPU and memory stay below saturation during the wave
5. From one test client, run a manual scan and confirm it completes, then watch the next scheduled wave. Keep the test client unchanged as your control so a later failure is clearly server side again. Verify: the test client completes its scan and reports results, and the wave shows a normal success rate

## Why it happens
The Windows Update client treats an HTTP 503 or a service unavailable response from its update endpoint as 0x80244022. With WSUS, the usual cause is the IIS application pool that hosts the client web service: it recycles on its private memory limit, stops after rapid failures, or is starved when a synchronized scan storm arrives while the WSUS database is busy. The client software itself is healthy, so local cache resets do nothing. Restoring pool health, giving it enough memory, and flattening scan demand remove the 503 responses at their source. Once service is restored, note the pool settings and the scan schedule change in the server record, because a later administrator who restores old defaults or a single mass scan schedule can recreate the same 503 pattern within one cycle.

## Variants and edge cases
### 0x80244022 only at Patch Tuesday scale
Demand spikes expose a pool that copes the rest of the month. Raise pool memory, pre-sync content, and stagger waves by collection or OU.

### 0x80244022 through a forward proxy to Microsoft Update
The proxy itself may return 503 under load or during its own restart. Capture the response source, add update endpoints to the bypass or allow list per vendor guidance, and retry.

### WsusPool keeps stopping after every recycle
Repeated stops point to database timeouts or a corrupt WSUS database rather than memory alone. Run WSUS database maintenance and decline superseded updates before tuning the pool further.

Compatibility: Applies to WSUS on Windows Server 2016 and later with IIS, and to Windows 10 and 11 clients scanning WSUS or Microsoft Update.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_IoUYdocxCsFtqYaKU7P9hQ