“The update is not applicable to your computer”: causes and fixes

You only see this message when you install an update by hand, usually a file downloaded from the Microsoft Update Catalog. Windows Update itself only offers updates that fit, so if you just want the latest patches, letting Windows Update check and install them is the easier route.

Why Windows says the update isn’t applicable

The installer (wusa.exe) checks the package against your system before it installs anything. Microsoft’s Windows Update troubleshooting guide names these causes:

Cause	How to tell	Fix
Already installed	The KB shows in Update history or Get-HotFix	Nothing to do
Superseded by a newer update	Your PC already has a later cumulative update	Nothing to do; the newer update contains the fix
Wrong Windows version or architecture	The KB’s “Applies to” list or file name doesn’t match your PC	Download the file for your version and x64 or Arm64
Missing prerequisite	The KB page lists a required earlier update	Install the prerequisite first, then this one

Microsoft’s own example of the architecture case is that an x86-based update can’t be installed on x64 Windows. The same applies between x64 and Arm64 files, and between Windows 10 and Windows 11 packages.

Check your Windows version and architecture

1. Right-click Start and open Settings > System > About.
2. Under Device specifications, note the System type (for example 64-bit operating system, x64-based processor).
3. Under Windows specifications, note the Edition, Version (such as 24H2 or 22H2) and OS build.

Now compare with the file you downloaded. Catalog file names include the target, for example windows11.0-kb...-x64.msu or ...-arm64.msu. Windows 11 24H2 and 23H2 updates are separate packages, so open the update’s KB page and check its Applies to list before you download again.

Check whether it’s already installed or replaced

Open Settings > Windows Update > Update history and look for the KB number. Or open PowerShell and run, with your KB number:

Get-HotFix -Id KB5043080

If it returns a line with an InstalledOn date, the update is already on the PC. If it returns an error saying it can’t find the hotfix, check Update history as well before you try again.

Superseded updates are the most confusing case. Windows cumulative updates include all earlier fixes, so an older cumulative update than the one you already have counts as not applicable. Microsoft’s guide suggests checking the update in the catalog; if your current build number is higher than the one the KB installs, you already have everything it contains.

Missing servicing stack updates used to be a common cause. Microsoft says that since February 2021 the cumulative update includes the latest servicing stack update for Windows 10 version 2004 and later, so on current Windows 10 and 11 this matters mainly for older or out-of-band packages. Microsoft’s guide still lists installing the latest servicing stack update as a step if one is listed as a prerequisite.

Windows 11 24H2: install checkpoint updates first

Windows 11 version 24H2 introduced checkpoint cumulative updates. Later updates only contain the changes since the last checkpoint, so they need that checkpoint installed first. If you download only the newest .msu for a PC that hasn’t been updated for a while, it may refuse to install.

The catalog lists every .msu file an update needs. Microsoft’s instruction is to install each MSU file individually, in order, checkpoint first, then the newer update, with either wusa or DISM. The simpler way is to let DISM do it in one go:

1. Create a folder such as C:\Packages and put the checkpoint .msu files and the target .msu in it, and nothing else.
2. Open Command Prompt as administrator and run:

DISM /Online /Add-Package /PackagePath:C:\Packages\<target-update>.msu

Microsoft says DISM discovers and installs the required checkpoints from the same folder, which is why only the target update and its checkpoints should be there. Restart when it finishes.

A related message, Operation is not supported, learn more about how to achieve this, appears when you double-click a post-checkpoint .msu on a PC where language packs or optional features were added from a local source. Microsoft’s fix is the same folder method above.

Install the package with DISM instead

When the version, architecture and prerequisites are right but wusa still refuses, Microsoft’s guide offers DISM, which skips the Windows Update agent’s applicability checks. From an elevated Command Prompt:

DISM /Online /Add-Package /PackagePath:C:\Updates\update.msu

DISM accepts an .msu directly on a running system from Windows 11 version 21H2. On Windows 10, extract the package first and point DISM at the .cab file inside:

wusa.exe C:\Updates\update.msu /extract:C:\Updates\extracted

Then run the same DISM command with the path to the update’s .cab file (not the WSUSSCAN.cab). Our guide to installing a CAB file covers that step. Be careful: Microsoft notes that DISM doesn’t run a full applicability and dependency check, so only use it for a package you’ve confirmed matches your PC. Forcing a wrong package won’t make it apply.

If none of that works

Restart first. A pending update or a half-finished installation can block new packages until the PC restarts.

Repair the component store. Microsoft’s guide lists this command as a standard step, run as administrator:

DISM /Online /Cleanup-Image /RestoreHealth

Then try the .msu again. If Windows Update itself is failing too, see Windows Update “Something went wrong” or Windows Update from the command line for scan and reset commands.

Related guides

• How to install a CAB file in Windows 11 and 10
• Windows Update from the Command Line: CMD and PowerShell Commands
• How to force Windows Update to check and install updates
• Windows Update “Something went wrong”: how to fix it

Official sources:

• Microsoft Learn: Windows Update troubleshooting guidance
• Microsoft Learn: Checkpoint cumulative updates and the Microsoft Update Catalog
• Microsoft Support: Windows Update Standalone Installer (wusa.exe)