Windows 11 24H2 End of Life 2026: Options

The Clock Is Ticking on Windows 11 24H2 (W) — October 13, 2026, and Counting

Microsoft Windows 11 24H2 (W) — build 10.0.26100 — reaches end of life on October 13, 2026. That is roughly nine months from today. This is not an LTS release, so there is no extended servicing channel for this specific version. After that date, Microsoft will no longer provide security updates, bug fixes, or technical support for this operating system.

If you are running Windows 11 24H2 in your enterprise, you now have a clear deadline and three realistic paths to choose from:

1. Upgrade/migrate to a newer Windows 11 release still under active support.
2. Purchase vendor extended support if Microsoft offers it for this build (limited and costly).
3. Move to third-party support to keep your current 24H2 environment secure and compliant without upgrading.

This article compares each option honestly — cost, risk, timeline, and best-fit scenarios — so you can make an informed decision before the cut-off.

Path 1: Upgrade / Migrate to a Newer Release

What it is: Migrate workstations running 24H2 to a later Windows 11 version that is still receiving mainstream support. Microsoft typically releases one feature update per year (e.g., 23H2, 24H2, and now 25H2). If a newer build is available and under active support, upgrading restarts the support clock.

Cost profile: Moderate to high. Internal IT labor for testing application compatibility, orchestrating deployment via SCCM/Intune, user training, and potential hardware upgrades if the new build has higher system requirements. Licensing costs do not change if you already have Software Assurance, but migration projects often run into hidden costs (downtime, lost productivity).

Risk: Medium. Regression risks from new drivers, app incompatibility, and changes to group policy objects. The newer OS itself will have its own end-of-life date, meaning you cycle into another upgrade within 18–24 months.

Timeline: Feasible in nine months if your environment is well-tested and you have a mature change management process. For large, distributed fleets with many legacy applications, nine months is tight.

Best suited for: Organizations that are already planning a hardware refresh, have a modern desktop estate, and can absorb the disruption of a full OS upgrade. Not ideal if the current configuration is stable and simply needs to keep running securely.

Path 2: Purchase Vendor Extended Support (if available)

What it is: Some Microsoft OS releases qualify for paid Extended Security Updates (ESU) after end of life. For Windows 11 24H2, however, ESU has historically been reserved for LTSB/LTSC editions or specific volume-licensed versions. Microsoft has not officially announced ESU for this general-purpose 24H2 build. If it does become available, it would be a per-device subscription covering only critical security patches — not bug fixes or new features.

Cost profile: High and recurring. ESU pricing typically increases each year. For a few hundred devices, annual costs can quickly exceed the expense of a full migration. Additionally, the cost often rises 100% year-over-year.

Risk: Low patching risk, but high financial and dependency risk. You remain locked into the vendor’s timeline and pricing. There is also no guarantee that Microsoft will offer ESU for this specific build — check the vendor page for updates.

Timeline: You can purchase ESU after the EOL date, but you must decide early to avoid a gap in coverage.

Best suited for: Extremely stable, compliance-heavy environments where the cost of a single missed security patch is massive and where the OS is deeply embedded in a validated (e.g., FDA, SOX) workflow. Otherwise, it is rarely the most economical path.

Path 3: Move to Third-Party Support

What it is: Engage a third-party maintenance provider to deliver security patches and technical support for your Windows 11 24H2 install base after Microsoft stops providing them. The third-party vendor reverse-engineers patches for critical CVEs and provides SLAs for break-fix issues, all without requiring you to upgrade or purchase ESU. This is the same model widely used for server hardware and enterprise software.

Cost profile: Fixed, predictable, and typically 40–60% less than vendor extended support. No per-device escalators. One annual contract covers all patching and support for as long as you need.

Risk: Low. Reputable third-party providers have proven track records for delivering timely security patches. The only risk is vendor dependency — but that risk is identical to staying on any vendor’s version, and you retain the option to migrate later on your own timeline.

Timeline: You can engage a provider now or right after EOL. Implementation is quick (days) — no migration testing, no user disruption. Nine months is more than enough to evaluate and onboard.

Best suited for: Any environment where stability is paramount — production floor PCs, point-of-sale terminals, kiosks, air-gapped systems, or enterprise VDI pools that are working perfectly and do not need feature churn. Also ideal for IT teams that want to defer the next migration to a less busy cycle.

Quick Decision Checklist

Use this checklist to decide which path fits your environment before October 13, 2026.

• Do you have a hardware refresh or major application upgrade already scheduled for 2026–2027? → Path 1 (upgrade) likely makes sense and aligns with that timeline.
• Are you in a highly regulated industry where even short patch gaps are unacceptable, and budget is not the primary concern? → Path 2 (ESU) may be worth exploring if Microsoft offers it.
• Do you have 200+ devices running stable, business-critical workloads that cannot tolerate OS changes? → Path 3 (third-party support) is the most pragmatic choice.
• Is your IT team already stretched with other projects? → Avoid Path 1 unless you can dedicate full-time resources. Path 3 requires zero migration effort.
• Do you need to keep using 24H2 for at least two more years while gradually migrating other systems? → Path 3 provides flexibility; ESU only works if you stop using the OS after the subscription ends.
• Is your budget fixed year-over-year? → Path 3 offers predictable costs. Paths 1 and 2 have variable, often rising costs.

What to Do Next

Regardless of which path you choose, the nine-month window is manageable — but only if you start planning now. Begin by auditing your current Windows 11 24H2 inventory, identifying which machines are mission-critical, and assessing your tolerance for downtime.

If you want to explore the third-party support option — either as a primary path or as a bridge to a future migration — contact our team to discuss how we can keep your Windows 11 24H2 environment secure, compliant, and fully supported long after October 13, 2026.

Note on lifecycle accuracy: End-of-life dates can shift if Microsoft issues an exception. Always confirm with official Microsoft documentation and reference the lifecycle source for the most current information.