Fix it now
The 0x8024Axxx codes come from the Automatic Updates client rather than from the network. Microsoft publishes 0x8024A000 as “unable to service incoming requests” and 0x8024A004 as “unable to process incoming requests because it was paused”. Look at pause state, policy and service registration before you look at a firewall.
sc query wuauserv
net start wuauserv
gpresult /h C:\gp.html
- Open Settings, Windows Update. If a pause is shown, choose Resume updates. A greyed-out control means policy is setting the pause, not a person.
- Open the report
gpresultproduced and read the Windows Update section, or inspectHKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdateand itsAUsubkey directly. - Trigger a detection cycle from an elevated PowerShell prompt with
(New-Object -ComObject Microsoft.Update.AutoUpdate).DetectNow(), which calls the documented Automatic Updates detection method. - If the device is pointed at an update server that no longer exists, correct or remove
WUServerandWUStatusServerat the policy source, rungpupdate /force, restartwuauservand rescan.
Every one of these values lives under the Policies branch of the registry. Anything you write there by hand on a domain-joined machine is overwritten at the next policy refresh, so change it where it is set.
If a scan now completes, stop here. Below is what the Automatic Updates client decides on its own, and which of the six codes tells you which decision went wrong.
Why it happens
There are two layers inside Windows Update and it pays to keep them apart. The update agent knows how to find, download and install. The Automatic Updates client sits above it and decides whether it is allowed to and when. Pause windows, deferral policy, active hours, metered rules and which service the device is registered against all live in that upper layer, and every code beginning 0x8024A is that layer refusing before the agent is ever asked to contact anything.
That is the practical value of recognising the prefix. Chasing proxies, endpoints and firewall rules for an 0x8024A code is wasted time, because no request left the machine. Microsoft’s published descriptions confirm the shape: 0x8024A000 is WU_E_AU_NOSERVICE, unable to service incoming requests; 0x8024A004 is WU_E_AU_PAUSED, paused; 0x8024A005 is WU_E_AU_NO_REGISTERED_SERVICE, no unmanaged service registered with Automatic Updates.
Two of the six are historical and say so plainly. 0x8024A003 is WU_E_AU_LEGACYCLIENTDISABLED, the old version of the Automatic Updates client was disabled, and 0x8024A002 is WU_E_AU_NONLEGACYSERVER, the old client stopped because the WSUS server was upgraded. If you see either on a current build, you are almost certainly looking at a policy set for an estate that no longer exists. The sixth, 0x8024A10A, is USO_E_SERVICE_SHUTTING_DOWN: the service was on its way down when the call arrived.
Updates are paused, by a person or by policy
You have this one if Settings shows a pause date, or the device is in a ring with quality or feature update deferrals configured.
- Resume in Settings, Windows Update. If the option is greyed out, the pause is coming from policy and has to change there.
- On a managed device, adjust the deferral or pause in the management platform, then run
gpupdate /forceon the client. - Restart
wuauservand rescan.
A pause whose window has expired can still leave the client stuck if the policy that set it was removed mid-window. Restarting the service after clearing the policy normally settles it.
No update service is registered with the client
You have this one if 0x8024A005, on a machine recently unenrolled from a management platform or stripped of a third-party patching agent.
- List what the client knows about from an elevated PowerShell prompt:
(New-Object -ComObject Microsoft.Update.ServiceManager).Services | Select-Object Name, ServiceID. - Turn Microsoft Update back on the supported way, in Settings, Windows Update, Advanced options, by allowing updates for other Microsoft products.
- Remove any leftover patching agent that keeps reclaiming the registration, then restart
wuauservand run a detection cycle.
The device is aimed at a server it cannot work with
You have this one if 0x8024A002 or 0x8024A003, on a device whose policy names an update server that was rebuilt, renamed or retired.
- Read
WUServerandWUStatusServerunderHKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdateand confirm the server they name still exists. - Test it from the client: the client web service on the WSUS port should return a service description page rather than an error.
- Move the device to a current server, or remove the policy so it uses Windows Update directly, then restart
wuauserv.
The service was shutting down when the call was made
You have this one if 0x8024A10A, usually once, alongside a service stop or a restart in the System log at the same minute, or after the machine has sat idle for a long stretch.
- Start with Microsoft’s own mitigation for this code: it describes the error as following a long period of inactivity, in which the system stops responding, the service goes idle and is eventually shut down. Keep the machine awake and the connection established until the operation finishes.
- Check Event Viewer, Windows Logs, System for service stop events around that timestamp.
- Confirm nothing is stopping
wuauservon a schedule. Some optimiser utilities do exactly this. - Retry once the service has been running steadily. A single occurrence during a restart is noise, not a fault.
Full reference
Where these settings actually live
The registry side of this is worth getting exactly right, because the wrong branch is the most common way people convince themselves they have changed something when they have not. Microsoft documents the Automatic Updates values under the Group Policy branch only.
| Value | Key | What it controls |
|---|---|---|
NoAutoUpdate |
HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU |
0 enables Automatic Updates, which is the default. 1 disables it |
AUOptions |
HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU |
How downloads and installs are notified and scheduled |
UseWUServer |
HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU |
1 sends the client to a WSUS server instead of Windows Update |
WUServer |
HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate |
The update server the client talks to, by HTTP name |
WUStatusServer |
HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate |
Where the client reports status |
The non-policy branch, HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate, holds client state such as SusClientId. It is not where these settings are read from, and writing UseWUServer there produces a value the update agent never reads.
Which code points at which decision
| Code | Microsoft’s name | What it is telling you |
|---|---|---|
0x8024A000 |
WU_E_AU_NOSERVICE | The client could not service the request at all |
0x8024A002 |
WU_E_AU_NONLEGACYSERVER | The old client stopped because the WSUS server was upgraded |
0x8024A003 |
WU_E_AU_LEGACYCLIENTDISABLED | The old version of the Automatic Updates client was disabled |
0x8024A004 |
WU_E_AU_PAUSED | Paused, so incoming requests are not processed |
0x8024A005 |
WU_E_AU_NO_REGISTERED_SERVICE | No unmanaged service is registered with Automatic Updates |
0x8024A10A |
USO_E_SERVICE_SHUTTING_DOWN | The Windows Update service is shutting down |
Before you edit anything
Export the policy branch first: reg export "HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" C:\wu-policy-backup.reg. On a domain-joined machine a local edit under a policy key survives only until the next refresh, so treat the export as a record of what was there rather than as a change you can rely on.
One thing worth knowing about WSUS itself
If the answer here turns out to be a policy pointing at a WSUS server, it is worth knowing where that product stands. Microsoft lists Windows Server Update Services among the features no longer in development, while stating that all existing capabilities and content continue to be available for your deployments. Nothing breaks today, and there is no emergency, but a decommissioned or unmaintained WSUS that is still named in policy is exactly the condition that produces the legacy codes above.
When the client will not move at all
- Confirm the service start type has not been changed:
sc qc wuauservshould not report a disabled service. - Look for two things managing updates at once. A management platform plus a separate patching agent is a common source of contradictory state.
- Check whether the connection is set as metered, which suppresses some downloads independently of any of these codes.
- Run
Get-WindowsUpdateLogand read the most recent detection attempt; the client records which service it tried to use. - Confirm the device is the edition you think it is. Microsoft’s Update policies are documented as applying to Pro, Enterprise, Education and IoT Enterprise, and Home is not in that list.
When a licence is the actual fix
Nothing on this page needs a purchase: resuming updates, clearing a stale policy and restarting a service are all free, and that is the answer for most readers. There is one honest licensing angle. Microsoft documents its Windows Update management policies as applying to Pro, Enterprise, Education and IoT Enterprise; Home is not listed for them. If you are trying to control deferral rings, a WSUS assignment or an update service URL on Home devices, you are writing settings that edition does not process, and no amount of registry work changes that. A Windows 11 Pro upgrade licence gives you an edition that does process them. Arco supplies Pro upgrade licences and will check what your devices are already entitled to first, because if all you need is to press Resume, you should spend nothing.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
0x8024A000 |
WU_E_AU_NOSERVICE. Automatic Updates was unable to service incoming requests | Microsoft Learn |
0x8024A004 |
WU_E_AU_PAUSED. Automatic Updates was unable to process incoming requests because it was paused | Microsoft Learn |
0x8024A005 |
WU_E_AU_NO_REGISTERED_SERVICE. No unmanaged service is registered with Automatic Updates | Microsoft Learn |
0x8024A10A |
USO_E_SERVICE_SHUTTING_DOWN. The Windows Update service is shutting down | Microsoft Learn |
0x8024A003 |
WU_E_AU_LEGACYCLIENTDISABLED. The old version of the Automatic Updates client was disabled | Microsoft Learn |
0x8024A002 |
WU_E_AU_NONLEGACYSERVER. The old version of the Automatic Updates client stopped because the WSUS server was upgraded | Microsoft Learn |
Confirm the fix worked
- Settings, Windows Update shows no pause and a scan completes.
sc query wuauservreports the service running.- The update history contains an entry dated after your change, proving a full cycle ran.
- On a managed device, the client appears against the correct update server after the next detection cycle.
Questions people ask about this
Does this cost anything to fix?
No. Resuming updates, correcting a policy and restarting a service are free. The only money on this page is the optional move of Home devices to Pro so they process update policies at all, and that is a choice about management, not a fix for the code.
Why is the Resume button greyed out?
Because a policy is setting the pause rather than you. Change it where it is set, in Group Policy or your management platform, then refresh policy on the client and restart the update service.
Do Windows Home devices obey update policies?
Microsoft’s documentation for the Update policies lists Pro, Enterprise, Education and IoT Enterprise as the editions they apply to. Home is not listed. Pausing and resuming from Settings still works there; deferral rings and update server assignment do not.
We removed our old WSUS server. Why are clients still stuck?
Because the policy naming it is almost certainly still applying. Remove the policy at source, run gpupdate /force on a client, restart wuauserv and rescan before you look anywhere else.
Is 0x8024A10A worth investigating?
Usually not on its own. It means the Windows Update service was shutting down when the call arrived, and Microsoft’s published mitigation is to keep the system active and the connection established, because the code typically follows a long spell of inactivity that lets the service go idle and stop. One occurrence around a restart is normal. A pattern of them means something is stopping the service on a schedule, and that is what to find.
