Plan Windows 10 ESU Year 2 without confusing 22H2 and LTSC

As of August 4, 2026, Windows 10 ESU Year 2 planning requires an edition-and-version inventory. Commercial 22H2 ESU is annual and cumulative; LTSC and LTSB releases follow separate lifecycles and must not be grouped with 22H2.

A controlled technology lifecycle progressing from assessment to approved production.
DSE visual intelligenceManaged IT operationsGuide · 3 min read
Executive summary

What you need to know

As of August 4, 2026, Windows 10 ESU Year 2 planning requires an edition-and-version inventory. Commercial 22H2 ESU is annual and cumulative; LTSC and LTSB releases follow separate lifecycles and must not be grouped with 22H2.

Potentially affected

Organizations still operating Windows 10 version 22H2 under commercial ESU, Windows 10 Enterprise LTSC or LTSB, embedded or special-purpose devices, and applications or hardware delaying Windows 11 migration.

DSE recommendation

Classify every remaining Windows 10 device by exact edition, version, and servicing channel; verify its current Microsoft lifecycle and licensing path; then approve either migration, retirement, or a time-bounded support bridge.

Source fact: commercial 22H2 ESU is a bridge

Microsoft states that Windows 10 reached end of support on October 14, 2025. Its commercial Extended Security Updates program allows eligible enrolled PCs to receive Critical and Important security updates after that date. Devices must run Windows 10 version 22H2. ESU does not add features, customer-requested nonsecurity updates, design changes, or general support for an out-of-support Windows release.

The program is annual. Microsoft says customers cannot purchase a partial period and that a customer entering in Year 2 must also acquire Year 1 because coverage is cumulative. Microsoft’s lifecycle FAQ lists Windows 10 ESU Year 1 through October 13, 2026 and Year 2 through October 12, 2027. Pricing, program channel, and eligibility can change, so this article does not quote a budget figure; obtain a current written quote and licensing confirmation for the actual estate.

Source fact: LTSC and LTSB are not 22H2

Microsoft’s LTSC overview explains that the Long-Term Servicing Channel was previously called the Long-Term Servicing Branch and that each release maps to a particular Windows feature version. LTSC is intended for special-purpose devices and has release-specific support. A device labeled Windows 10 Enterprise does not reveal enough to select an ESU or migration plan.

  • Windows 10 Enterprise LTSC 2021 corresponds to version 21H2 and has a five-year lifecycle for the non-IoT Enterprise edition. Microsoft’s lifecycle page lists January 12, 2027 as its support end; IoT Enterprise LTSC 2021 has a different lifecycle.
  • Windows 10 Enterprise LTSC 2019 corresponds to version 1809 and follows its own lifecycle.
  • Windows 10 Enterprise 2016 LTSB corresponds to version 1607 and reaches support end on October 13, 2026. Microsoft has published a separate transition path for that release.

Do not apply the 22H2 ESU prerequisite or dates to LTSC or LTSB by analogy. Verify the exact edition in Microsoft Lifecycle and the applicable licensing terms. An IoT label, embedded use, or appliance form factor can also change which product lifecycle and support contract govern the device.

DSE recommendation: build a decision-grade inventory now

For every remaining Windows 10 endpoint, record hardware identifier, owner, user or device purpose, exact edition, display version and build, servicing channel, architecture, management platform, update source, last successful security update, ESU activation state where applicable, Windows 11 eligibility, application and peripheral blockers, data sensitivity, network exposure, replacement dependency, and target exit date. Reconcile management data with procurement and physical inventory so offline and special-purpose systems are not invisible.

Divide devices into four owned outcomes: upgrade in place to a supported Windows release; replace hardware; retire or consolidate the workload; or retain temporarily under a verified support bridge. A bridge requires an approved business reason, licensing evidence, update-health monitoring, compensating controls based on exposure, and a funded migration milestone. It is not a permanent operating model.

DSE recommendation: prove Year 2 readiness and migration separately

  1. Confirm which 22H2 devices truly need Year 2 and which will exit before Year 1 ends. Do not purchase from a stale device count.
  2. Verify licensing eligibility, cumulative prior-year requirement, activation method, management prerequisites, and support route with Microsoft or the authorized licensing partner.
  3. Use a representative pilot to prove activation, update detection, deployment, restart behavior, reporting, and rollback procedures before broad reliance.
  4. Track monthly update success and exceptions using device-level evidence. ESU entitlement without successful deployment does not reduce operational exposure.
  5. Maintain a separate migration board with each blocker, accountable owner, decision date, test result, procurement dependency, and retirement evidence.

Escalate devices that cannot be inventoried, updated, isolated, or tied to an exit owner. Review LTSC suitability rather than treating it as a general-purpose refuge; Microsoft’s documentation describes LTSC as a special-use channel and warns that support from applications and tools designed for the general availability channel may be limited.

Official sources

Primary reference

Review the official source

Microsoft Learn — Extended Security Updates program for Windows 10 · Published November 17, 2025

Open official reference ↗
Plan the next step

Need help applying this guidance safely?

DSE can help confirm applicability, protect service continuity, and validate the result across physical security and IT systems.

Talk with DSE