Fix it now
Neither code means an update is broken. Microsoft publishes 0x80240023 as WU_E_EULAS_DECLINED, the licence terms for all updates were declined, and 0x8024000A as WU_E_COULDNOTCANCEL, cancellation of the operation was not allowed. The second is the opposite of what its name suggests to most people: something tried to cancel and was refused.
net stop wuauserv
net stop bits
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
net start bits
net start wuauserv
- Try the install interactively from Settings, Windows Update, so a licence terms prompt can actually be answered by somebody.
- If you are scripting the install, accept the terms in code on each update object before adding it to the collection you install. A script that never accepts will fail on exactly the updates that carry terms and succeed on everything else.
- On WSUS, re-run the approval and accept the licence agreement when the server asks. An update whose agreement has not been accepted on the server will not install on clients.
- For 0x8024000A, find out what else is driving updates on the device. A management platform and a separate patching agent competing for the same session is the usual explanation.
Accepting licence terms programmatically commits your organisation to them. Make sure whoever owns that decision knows the script does it on their behalf.
If the update installed, that is the job done. Below is where terms are recorded, and why a refused cancellation is a different problem from a declined agreement.
Why it happens
Some updates carry licence terms of their own. Driver updates published by hardware vendors are the common case, along with a handful of product updates delivered through the same channel. The update client will not install one until the terms have been accepted, and it records that acceptance rather than asking again. Microsoft’s description of 0x80240023 is exact: the licence terms for all updates were declined.
Acceptance has to happen wherever the install is being driven from. Interactively, the prompt appears and somebody answers it. In a scripted install there is nobody to prompt, so acceptance has to be expressed by the code. This is why the failure looks intermittent: the script works perfectly until the month a driver update with terms appears in the list.
0x8024000A is a different animal and the v1 of this page had it backwards. WU_E_COULDNOTCANCEL means cancellation of the operation was not allowed. Something asked the update session to stop and the session refused. That is not policy cancelling an install; it is an attempt to cancel that did not take. In practice it means two callers are competing for one update session, or a script tried to abort an operation that had already passed the point where cancelling is permitted.
The two supporting codes are narrower again. 0x80240028 is WU_E_UNINSTALL_NOT_ALLOWED: the update could not be uninstalled because the request did not originate from a WSUS server. 0x80240010 is WU_E_TOO_DEEP_RELATION, update relationships too deep to evaluate were evaluated, which points at damaged or looping metadata in the local store.
A script installs updates without accepting terms
You have this one if Automated runs fail on a small subset of updates, usually drivers, while the same updates install by hand from Settings.
- In the script, accept the terms on each update object before adding it to the collection you install.
- Log which updates required acceptance so you can see whether the set is stable or growing.
- Prove the diagnosis by installing one failing update manually from Settings.
The licence agreement was never accepted on the update server
You have this one if Clients managed by WSUS fail while unmanaged machines install the same update normally.
- In the WSUS console, find the update and re-run the approval, accepting the agreement when prompted.
- Confirm the server has been able to download the agreement text. A server blocked from the internet can hold an approval without it.
- Force a client to re-detect afterwards and retry.
Two mechanisms are fighting over one update session
You have this one if 0x8024000A, on a device driven by both a management platform and a separate patching tool, or where a script runs while a scheduled scan is already in progress.
- Establish which tool owns patching on the device and disable the other, or at least stagger the schedules so they do not overlap.
- Confirm no scan or install is already running before starting another. An operation in progress raises its own code; a cancel attempt against it raises this one.
- Retry when the machine is idle.
An uninstall was refused
You have this one if 0x80240028 while trying to remove an update rather than install one.
- Check whether the update is removable at all. Many are not, and none is on a machine whose component store has been reset.
- On a managed device, remove it through the managing server. Microsoft’s description of this code is explicitly that the request did not originate from a WSUS server.
- If removal is genuinely impossible and the update must go, what remains is a restore point taken before installation, or a repair upgrade.
The local metadata has looped
You have this one if 0x80240010, or errors that move around between scans with no pattern.
- Stop
wuauservandbits, renameC:\Windows\SoftwareDistribution, then start the services again. - Run a fresh scan so the client rebuilds its view from scratch.
- If it returns, repair the servicing components with
DISM /Online /Cleanup-Image /RestoreHealthfollowed bysfc /scannow.
Full reference
The four codes as Microsoft states them
| Code | Published name | Published description |
|---|---|---|
0x80240023 |
WU_E_EULAS_DECLINED | The licence terms for all updates were declined |
0x8024000A |
WU_E_COULDNOTCANCEL | Cancellation of the operation was not allowed |
0x80240028 |
WU_E_UNINSTALL_NOT_ALLOWED | The update could not be uninstalled because the request did not originate from a WSUS server |
0x80240010 |
WU_E_TOO_DEEP_RELATION | Update relationships too deep to evaluate were evaluated |
The wording of 0x8024000A matters more than most. It is a refusal to cancel, not a cancellation. Any article that reads it as “policy cancelled the operation” will send you looking at Group Policy for a problem that lives in whatever asked the session to stop.
Where acceptance is recorded
Acceptance is per update rather than global, and it is recorded in three separate places depending on how the install was driven: by the interactive user who answered the prompt, by the code that set acceptance on the update object, and by the administrator who accepted the agreement while approving on the server. There is no single switch that pre-accepts everything, and that is deliberate, because the terms belong to different publishers.
Diagnosing a competing caller
- List what is scheduled: check Task Scheduler for update-related tasks and your management platform for its own schedule.
- Look at the update history and the timestamps. Two mechanisms usually leave a visible interleaving of attempts.
- Run
Get-WindowsUpdateLogand find the session that was asked to cancel. The caller is normally identifiable from the trace. - Pick one owner for patching on that device and turn the other off rather than trying to make them coexist.
- Re-test with the machine idle, from a single caller, before concluding anything.
Uninstalling updates, and when you cannot
0x80240028 is worth taking at face value. Microsoft’s published reason is that the removal request did not come from a WSUS server, which is the designed behaviour on a managed client rather than a fault. On an unmanaged machine the more common blocker is simply that the update is not removable, which is true of many cumulative updates and of anything applied after a component store reset. Neither state is repairable by retrying the removal a different way.
Checks when none of the causes fit
- Confirm the failing update actually carries licence terms. Most do not, so if the set of failures is broad, terms are probably not the explanation.
- Check whether the same update installs on a comparable machine driven the same way. A single-machine failure and an estate-wide failure have different root causes.
- Confirm the client is talking to the update server you think it is, since an approval on the wrong server changes nothing on the client.
- Rebuild the update data store before assuming metadata corruption, and rescan afterwards so the store is repopulated from the service.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
0x80240023 |
WU_E_EULAS_DECLINED. The licence terms for all updates were declined | Microsoft Learn |
0x8024000A |
WU_E_COULDNOTCANCEL. Cancellation of the operation was not allowed, which means something tried to cancel and was refused | Microsoft Learn |
0x80240028 |
WU_E_UNINSTALL_NOT_ALLOWED. The update could not be uninstalled because the request did not originate from a WSUS server | Microsoft Learn |
0x80240010 |
WU_E_TOO_DEEP_RELATION. Update relationships too deep to evaluate were evaluated | Microsoft Learn |
Confirm the fix worked
- The previously failing update installs rather than being declined.
- It appears in Settings, Windows Update, Update history.
- On a managed device, the update server records the client as compliant after the next detection cycle.
- The automated job runs again and completes without the same code.
Questions people ask about this
Does this cost anything to fix?
No. Accepting licence terms, correcting an approval on your update server and separating two patching tools are all free. Nothing on this page is solved by buying a licence.
Which updates actually carry licence terms?
Most do not. Driver updates published by hardware vendors are the usual case, along with a small number of product updates delivered through the same channel, which is why the failure looks intermittent.
Does 0x8024000A mean a policy cancelled my update?
No, and this is the most common misreading of it. Microsoft publishes it as cancellation of the operation not being allowed. Something asked the update session to stop and was refused, so look at what else is driving updates on that device.
Can I accept all licence terms in advance?
No. Acceptance is recorded per update, so scripts and management servers have to accept as they go. That is deliberate, because the terms belong to different publishers and are not interchangeable.
Why does the same script work on some machines?
Because those machines were offered a set of updates that happened to carry no licence terms. The flaw in the script only shows when an update with terms turns up in the list.
