ErrorBase
Independent technical referenceOfficial site
  • Software and digital services
  • Operating system

0x80240017

Microsoft Windows Update 0x80240017: no applicable update

Verified with sources1 sourceReviewed Oct 19, 2026
Technician coming? See the 2 steps they must show you

Risk level

Low

Usually safe to check without specialist tools.

Urgency

Medium

Quick answer

Error 0x80240017 (WU_E_NOT_APPLICABLE) means the operation was not performed because there are no applicable updates for your PC. Note the KB number, check whether the update or a superseding package is already installed, verify OS version and CPU architecture, and do not force it.

Safety first

Stop and check this first

  • Never download standalone update packages from unofficial websites or attempt to bypass applicability checks on a package meant for another Windows version or CPU architecture; Microsoft states that only advanced users and administrators should download packages from the official Microsoft Update Catalog.

Safe checks you can perform

  • Check Windows Update history and installed hotfixes for the KB or a superseding update
  • Compare your Windows version, build, and processor architecture with the KB 'Applies To' section
  • Check for prerequisite updates with Get-HotFix and run a fresh Check for updates after restarting

Leave these tasks to a qualified professional

  • Do not attempt this professional task: Verify WSUS or deployment group targeting and supersedence in the Microsoft Update Catalog
  • Do not attempt this professional task: Install missing Servicing Stack Updates before applying the target package

What a technician must be able to justify

Technician visit

These are the steps they must carry out and show you. Tick them as they work: if steps are skipped, do not accept a part swap.

These are not instructions for opening or handling the equipment yourself. They are the checks that should support a technical conclusion.

  1. Verify WSUS or deployment group targeting and supersedence in the Microsoft Update Catalog

    What they doOn managed computers, have the IT administrator inspect the Microsoft Update Catalog entry for supersedence, check OS Build, OS Branch, OS Locale, and OS Architecture targeting on the WSUS or deployment server, and review EEHandler applicability lines in WindowsUpdate.log.

    They must show youthe Microsoft Update Catalog supersedence tab for the KB and the EEHandler applicability lines from static WindowsUpdate.log.

    In writingwhether the KB is superseded or mis-targeted, the superseding KB number if applicable, and the updated deployment group assignment.

  2. Install missing Servicing Stack Updates before applying the target package

    What they doIf a required cumulative update returns 0x80240017 on a matching Windows version and architecture because prerequisite servicing components are absent, have the administrator install the latest matching Servicing Stack Update (SSU) and prerequisite KBs from the Microsoft Update Catalog first, restart, and then apply the update.

    They must show youthe Get-HotFix InstalledOn dates for the prerequisite Servicing Stack Update and the target KB.

    In writingthe exact prerequisite KB numbers installed, the restart timestamp, and the final OS build number.

Before accepting a part or repair

Nothing has been shown yet. Do not accept a part swap based on the code alone.

Follow these steps

Note: Follow the documented order. An error code identifies the affected system, but it does not prove by itself which part has failed.

  1. Check Windows Update history and installed hotfixes for the KB or a superseding update

    No special tools

    Who:
    You in Windows Settings or Windows PowerShell.
    How:
    Open Start > Settings > Windows Update > Update history (or run Get-HotFix in Windows PowerShell) to check whether the KB that returned 0x80240017 or a newer cumulative update is already listed in the InstalledOn output.
    Result that matters:
    Microsoft notes that if a package or a newer superseding payload is already present on your system, Windows marks the older update as not applicable.
    If the KB or a newer cumulative update for the same Windows build is already installed, that confirms 0x80240017 is normal and no further installation is needed.
    If neither the KB nor a superseding update is installed, that rules out duplicate installation and points to checking OS version, architecture, and prerequisites.
    Evidence to keep:
    Save a screenshot of Update history or the Get-HotFix InstalledOn output.

    Evidence: Windows Update error reference · Guidance for troubleshooting Windows Update issues · Windows Update issues troubleshooting

  2. Compare your Windows version, build, and processor architecture with the KB 'Applies To' section

    No special tools

    Who:
    You checking system specifications and the Microsoft Knowledge Base article.
    How:
    Compare your installed Windows version, OS build, and processor architecture (x64, x86, or ARM64) against the 'Applies To' section of the Microsoft KB article and the package filename downloaded from the Microsoft Update Catalog.
    Result that matters:
    Microsoft states that updates are published by CPU architecture and OS version, so a mismatched package will be rejected as not applicable.
    If the downloaded package is for x86 on an x64 system or targets a different Windows release, that confirms a package selection mismatch caused 0x80240017.
    If the Windows version, OS build, and CPU architecture match the KB article exactly, that rules out an architecture or edition mismatch.
    Evidence to keep:
    Record your Windows edition, OS build, processor architecture, and the exact filename of the update package.

    Evidence: Guidance for troubleshooting Windows Update issues · How to download updates that include drivers and hotfixes from the Microsoft Update Catalog · Windows Update issues troubleshooting

  3. Check for prerequisite updates with Get-HotFix and run a fresh Check for updates after restarting

    Tools required

    Who:
    You or your IT administrator in Windows PowerShell and Windows Settings.
    How:
    Read the KB article to identify any required prerequisite or Servicing Stack Updates, run Get-HotFix <KB_number> in PowerShell to verify their InstalledOn date, and if the PC has a pending reboot, select Start > Power > Update and restart followed by Start > Settings > Windows Update > Check for updates.
    Result that matters:
    Pending actions from a previous update must finish restarting before new updates apply, and missing prerequisite updates prevent applicability rules from passing.
    If Get-HotFix shows a prerequisite update is missing or Update and restart reveals earlier updates in the queue, that identifies the missing prerequisite step.
    If all listed prerequisite updates are installed and Check for updates reports your device is up to date, that confirms the system needs no action for this KB.
    Evidence to keep:
    Keep the Get-HotFix console output and a screenshot of the Check for updates result.

    Never use Dism /online /add-package to force an update package that belongs to a different Windows version or processor architecture.

    Evidence: Microsoft Windows Update troubleshooting · Guidance for troubleshooting Windows Update issues · Windows Update issues troubleshooting

Still not solved

If the error persists, stop here. See what the technician must do and show you.

Where this code applies

A code is meaningful only inside the right product and version context.

Primary scope

System
Software and digital services
Brand
Microsoft Windows
Product type
Operating system

Known code variants

  • 0x80240017
  • Windows Update 0x80240017
  • WU_E_NOT_APPLICABLE

What it means

In Microsoft's Windows Update error reference and Wuerror.h, 0x80240017 maps to WU_E_NOT_APPLICABLE: the operation was not performed because there are no applicable updates. During a scan or standalone package install, the Windows Update Agent (via EEHandler and detector updates carrying IsInstalled applicability rules) evaluates OS Build, OS Branch, OS Locale, OS Architecture, supersedence chains, and prerequisite servicing updates. Code 0x80240017 alone never indicates a broken Windows Update service or disk corruption.

Warnings and stop conditions

  • Lowsource verified

    Never download standalone update packages from unofficial websites or attempt to bypass applicability checks on a package meant for another Windows version or CPU architecture; Microsoft states that only advanced users and administrators should download packages from the official Microsoft Update Catalog.

    Evidence: Guidance for troubleshooting Windows Update issues · How to download updates that include drivers and hotfixes from the Microsoft Update Catalog

Symptoms and causes

Probable causes · in order

  • Update is already installed or superseded by a newer package on the systemCommon

    Microsoft documents that 'The update is not applicable to your computer' occurs when the package was previously installed or when a newer component already on the system supersedes the older update.

    Evidence: Windows Update error reference · Guidance for troubleshooting Windows Update issues · Windows Update issues troubleshooting

  • Package targets a different Windows version, edition, or CPU architectureCommon

    Updates are published by Windows version and processor architecture; for example, Microsoft notes that an x86-based update cannot be installed on an x64-based installation of Windows, and Windows Server 2019 updates cannot be installed on Windows Server 2016.

    Evidence: Guidance for troubleshooting Windows Update issues · Windows Update issues troubleshooting

  • Missing prerequisite servicing stack or cumulative updatePossible

    Some updates require a prerequisite update (or a pending restart from a prior update) before they become applicable to the system, and WUA uses detector updates with IsInstalled rules to evaluate prerequisites.

    Evidence: Guidance for troubleshooting Windows Update issues · How Windows Update works · Windows Update issues troubleshooting

Virtual technician

Does 0x80240017 still appear after these checks?

Answer a few questions to narrow down the likely cause and the safest next action. Guidance only - it never replaces a professional.

Start diagnosis

Sources and technical references

  1. 1

    Windows Update error reference

    Microsoft · 2026 · official_doc

Sources: Windows Update error referencereviewed 2026-10-19 · verified

Was this entry useful?