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.
\r\nThe 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.
\r\nMicrosoft’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.
\r\nDo 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.
\r\nFor 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.
\r\nDivide 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.
\r\nEscalate 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.
\r\n