Fix it now
0x80240017 is a verdict rather than a fault: Microsoft publishes it as WU_E_NOT_APPLICABLE, the operation was not performed because there are no applicable updates. The package and the machine were compared and the answer was no. The useful work is establishing why, because only one of the reasons is a licensing question.
winver
dism /online /get-currentedition
DISM /Online /Cleanup-Image /ScanHealth
- Compare what
winverreports against the Microsoft Update Catalog row you downloaded. Catalog rows are specific about release, edition family and architecture, and taking the wrong one is the most common cause by a distance. - Check whether the update is already present or superseded:
Get-HotFixin PowerShell, or Settings, Windows Update, Update history. - Install any prerequisite the package needs, normally the current servicing stack update for that build, then reboot and retry.
- Install a downloaded package with
dism /online /add-package /packagepath:C:\path\to\package.cab, which reports the applicability result more clearly than the graphical installer does. - If the installed release is out of support, no package will ever apply. Moving to a serviced release is the only route forward.
Do not try to force an update past this. Applicability rules exist because a package built for another build or edition leaves an installation servicing cannot repair.
If the right package installed, you are done. Below is how applicability is actually decided and what each of the companion codes adds.
Why it happens
Every update package declares what it applies to: a product, a release, an architecture, an edition family and, very often, a base build it has to be layered onto. The client evaluates those declarations locally and answers before contacting anything. When the answer is no you get 0x80240017, and the identical package on the machine beside it may install without complaint.
Supersedence produces the same verdict for a completely different reason. Cumulative updates contain everything before them, so an older package offered to a machine that already carries a newer one genuinely does not apply. Microsoft’s companion code here is 0x80240024, WU_E_NO_UPDATE, published simply as “there are no updates”. Seeing that after a scan is usually good news wearing an alarming costume.
0x8024002D is the one that sends people down the wrong path. Microsoft publishes it as WU_E_SOURCE_ABSENT: a full-file update could not be installed because it required the source. That is an installation source problem, not an applicability problem, and it turns up most often when enabling an optional feature rather than when applying a security update. 0x80240026, WU_E_INVALID_UPDATE_TYPE, means the update type presented to the client is not valid, which points at damaged metadata or a malformed package rather than at the machine.
The package targets a different build, edition or architecture
You have this one if A manually downloaded update refuses immediately while Windows Update itself works normally on the same machine.
- Note the exact version and build from
winverand the edition fromdism /online /get-currentedition. - Return to the Microsoft Update Catalog and pick the row naming that release and your architecture.
- Install it with
dism /online /add-package /packagepath:<path>so the applicability result is stated plainly.
It is already installed, or something newer is
You have this one if 0x80240017 or 0x80240024 for a package that update history already shows, or one older than the current cumulative update.
- Check
Get-HotFixand the update history for the package or a later one. - If a later cumulative update is present, stop. The content is already on the machine.
- If you are chasing a security advisory, compare build numbers rather than package names. The advisory names the build that contains the fix.
A prerequisite is missing
You have this one if The device has been offline or unpatched for a long period and several packages return the same result.
- Install the current servicing stack update for the build first, then reboot.
- Install the latest cumulative update, then reboot again.
- Retry the original package. It is frequently unnecessary by then, because the cumulative update contains it.
The operation needs installation source files
You have this one if 0x8024002D while enabling an optional feature rather than while installing a security update.
- Mount installation media of the same build.
- Enable the feature with an explicit source, for example
dism /online /enable-feature /featurename:NetFx3 /all /source:D:\sources\sxs /limitaccess. - On a managed device, check that policy is not preventing the machine from obtaining optional components from Windows Update. That is a separate failure with its own codes.
The release itself is out of support, or the installation is not licensed
You have this one if Every update reports as not applicable, and the release is one Microsoft no longer services, or Windows reports itself as unlicensed or as an expired evaluation.
- Confirm the release with
winverand check its servicing status. - Confirm activation in Settings, System, Activation and fix it if the device is unlicensed.
- Upgrade to a supported release by running
setup.exefrom mounted media matching the edition and language you are licensed for. - For an expired Windows Server evaluation, convert to a full edition rather than trying to patch the evaluation.
Full reference
The four codes side by side
| Code | Published name | Published description |
|---|---|---|
0x80240017 |
WU_E_NOT_APPLICABLE | The operation was not performed because there are no applicable updates |
0x80240024 |
WU_E_NO_UPDATE | There are no updates |
0x8024002D |
WU_E_SOURCE_ABSENT | A full-file update could not be installed because it required the source |
0x80240026 |
WU_E_INVALID_UPDATE_TYPE | The type of update is invalid |
Matching a symptom to a cause
| What you were doing | The likely reason for the refusal |
|---|---|
| Installing a downloaded .msu by hand | The catalog row does not match your build, edition or architecture |
| Installing an update that is months old | It has been superseded by a later cumulative update |
| Enabling an optional feature such as the older .NET runtime | Installation source files were required and were not available |
| Patching a device that has not updated in a long time | A prerequisite servicing stack update is missing |
| Patching a device on an old Windows release | The release is out of support and no packages are being built for it |
In-place upgrade, without the folklore
Where the answer is that the release has to move, an in-place upgrade from mounted media keeps files, applications and activation on a licensed device. It is still a full operating system replacement, so it deserves the same care as one.
Take a backup first, make sure you have the recovery key for any encrypted volume, and do not start an upgrade on a machine with a failing disk. The process cannot be reversed once it is under way.
The edition question, answered honestly
Two different things get muddled at this point. Moving a licensed device from an old build to a current build of the same edition needs no new key: the existing entitlement carries across and activation reattaches on its own. Buying enters the picture only in two cases. The installation is not properly licensed today, in which case servicing is refusing correctly. Or the device needs to be on a different edition to reach a supported or manageable configuration, which is a deliberate change rather than a repair.
When the hardware is the blocker
Some devices report everything as not applicable because they cannot run the current release at all. Check the requirements honestly before spending anything, because a licence does not change a hardware verdict. If the machine genuinely cannot meet them, the decision becomes hardware replacement or extended support coverage for the release it is on, and both of those are budget conversations rather than troubleshooting.
Checks when nothing above fits
- Run
Get-WindowsUpdateLogand read the applicability evaluation for the specific package. It names the condition that failed. - Confirm the language of the package matches the installation. A language mismatch produces the same verdict as an architecture mismatch.
- On a managed device, check whether the update is approved for the group the device is in. An unapproved update is simply never offered.
- Look for a pending reboot. A machine with a servicing operation half-finished evaluates applicability against a state that is about to change.
- Confirm the package is not a dynamic update or a component intended for offline servicing, which behave differently from ordinary cumulative updates.
When a licence is the actual fix
There is one situation on this page where a licence is genuinely the fix rather than a workaround: when the device is running an installation it is not entitled to, such as an expired evaluation or an edition no key you hold covers. Servicing will keep refusing regardless of which package you feed it. A Windows 11 Pro upgrade licence resolves that, and it is also what you need if a machine has to move from Home to Pro to reach a manageable, serviced configuration. Arco supplies those licences and will check the device’s existing entitlement first. If the device already holds a valid Windows licence, moving it to a current supported build costs nothing extra and we will tell you that rather than sell you a key you do not need.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
0x80240017 |
WU_E_NOT_APPLICABLE. The operation was not performed because there are no applicable updates | Microsoft Learn |
0x80240024 |
WU_E_NO_UPDATE. There are no updates, which is the usual answer when the package is already installed or superseded | Microsoft Learn |
0x8024002D |
WU_E_SOURCE_ABSENT. A full-file update could not be installed because it required the source | Microsoft Learn |
0x80240026 |
WU_E_INVALID_UPDATE_TYPE. The type of update is invalid | Microsoft Learn |
Confirm the fix worked
winverreports a version and build that is currently serviced.- The specific update, or a later cumulative update containing it, appears in the update history.
- A fresh scan in Settings, Windows Update offers updates rather than stopping.
- Settings, System, Activation reports the device as activated.
Questions people ask about this
Do I have to buy Windows 11 to keep this device patched?
Not if it already carries a valid Windows licence and the hardware qualifies. Upgrading a licensed device to a current supported release does not need a new key. You would buy a licence only for a different edition, or if the installation is not properly licensed today.
Why does Windows Update never even offer me the update?
Because it reached the same applicability verdict silently. Not being offered an update and being told it is not applicable are the same decision made in two places.
Can I force an update to install anyway?
No, and you should not want to. Applicability rules exist because a package built for another build or edition leaves an installation that servicing cannot subsequently repair.
What is the difference between 0x80240017 and 0x80240024?
Microsoft publishes the first as the operation not being performed because there are no applicable updates, and the second as simply “there are no updates”. In practice the first follows an attempt on a specific package and the second follows a search that found nothing to do.
My device fails the requirements for the current release. What now?
Check the requirements properly before spending anything. If the hardware genuinely cannot run the current release, a licence changes nothing, and the real decision is between replacing the hardware and buying extended support coverage for the release it is on.
