Quick fix: Windows 11 25H2 ships as an enablement package (eKB) that flips dormant features on. It requires 24H2 as the prerequisite base. SKUs not on 24H2 (Education limited edition, IoT LTSC variants, some N-edition installs) reject the eKB. Confirm winver reports 24H2 first, then re-run the update.

Windows Update offers you 25H2 as a simple “enablement package.” You click install, it processes for a moment, then fails with an error like This update is not applicable to your computer or 0x80073712. The reason isn’t a corrupt download — it’s that 25H2 only works on systems already running 24H2, and your edition may be on something else.

Symptom: Windows 11 25H2 enablement package fails to install on certain SKUs.
Affects: Windows 11 22H2, 23H2, and certain Education/IoT/N variants.
Fix time: 30–60 minutes including the prerequisite update.

How enablement packages work

Microsoft ships annual feature updates as enablement packages (eKB) when consecutive versions share the same servicing branch. 24H2 was the “real” feature update; 25H2 is just a switch that activates features Microsoft was staging in 24H2’s monthly cumulatives. The eKB is small (~10 MB) and installs in 60 seconds because nothing actually changes — it just flips a registry value and bumps the version reported by winver.

The catch is that eKB requires the exact baseline it was built against. 25H2’s eKB requires 24H2 of the same edition and architecture. If you’re on 23H2, on an LTSC variant that didn’t get the 24H2 staging, or on a regionally-restricted SKU, the eKB refuses.

Method 1: Verify you’re on 24H2 first

Press Win + R, type winver, press Enter.
Check the line Version 24H2. If it shows 23H2 or older, you need to update to 24H2 first — the 25H2 eKB won’t apply.
Open Settings → Windows Update. Look for a Feature update to Windows 11, version 24H2 offer.
If no 24H2 offer appears, use the Windows 11 Installation Assistant from https://www.microsoft.com/software-download/windows11. Run it to upgrade to 24H2 in place (keeps apps and files).
After the upgrade completes, run winver — should show 24H2. Then retry the 25H2 eKB.

Most 25H2 install failures resolve at this step. Users on 23H2 simply weren’t offered 24H2 yet through normal Update channels.

Method 2: Check for SKU-specific blocks

Some Windows 11 SKUs don’t get the 25H2 eKB at all.

Run winver. Note the edition (Home, Pro, Pro for Workstations, Enterprise, Education, IoT Enterprise, etc.).
Reference Microsoft’s Lifecycle and Update Channel docs for your edition:

  Home/Pro: 25H2 supported

  Enterprise/Education: 25H2 supported

  IoT Enterprise LTSC 2024: stays on 24H2; no 25H2 offered

  Pro for Workstations: 25H2 supported

  N editions (European): typically supported but may install with delay
If your edition isn’t in the supported list, the 25H2 eKB is the wrong update for you. Stay on 24H2 until Microsoft offers a feature update appropriate for your SKU.
For region-restricted features blocked under DMA or similar regulations, the eKB may install but specific new features (Recall, certain Copilot integration) stay off — that’s by design.

If you’re on a supported edition and still blocked, continue to Method 3.

Method 3: Force the eKB install via the Update Catalog

For users on a supported edition where Windows Update repeatedly fails to offer 25H2, install it manually.

Visit https://catalog.update.microsoft.com.
Search for Windows 11 25H2 or the matching KB number.
Find the eKB matching your architecture (x64, ARM64).
Download the .msu file.
Run it from elevated Command Prompt: wusa.exe C:\path\to\windows11.0-kbXXXXX-x64.msu /quiet /norestart.
Reboot when prompted. winver should now show 25H2.

The manual install bypasses the offer pipeline but still respects the underlying eligibility checks — if 25H2 truly isn’t applicable, wusa will report so and decline.

How to verify the fix worked

Run winver. Reports Version 25H2 with the matching OS Build.
Open Settings → System → About. The Windows specifications section shows 25H2.
Open Windows Update; no 25H2 feature update offer remains.
Check Event Viewer → Setup. The most recent entry shows the eKB applied successfully.

If none of these work

If 25H2 install fails on a system that’s definitely on 24H2 and a supported edition, the error code matters: 0x80070643 usually means servicing stack mismatch — install the latest Servicing Stack Update from the Update Catalog and retry. 0x80073712 means corrupted component store — run Dism /Online /Cleanup-Image /RestoreHealth and retry. For managed devices, your IT may be blocking 25H2 via WSUS or Intune Update Rings — coordinate with admin. For ARM64 devices, check that your ARM64-specific eKB matches the hardware; an x64 eKB won’t install on ARM hardware.

Bottom line: The 25H2 eKB needs 24H2 as the base. Update to 24H2 first, then the eKB applies in under a minute. For SKUs that aren’t in the upgrade path, staying on 24H2 is correct — you’ll get the next feature update when Microsoft offers it.