Windows 11 22H2 EOL: 3 Options for IT Leaders

The Clock Is Ticking on Windows 11 22H2 (W)

Microsoft Windows 11 22H2 (W) — version 10.0.22621 — reaches end of life on October 8, 2024. That is roughly nine months away. Unlike an LTS release, this version will receive no further security patches or bug fixes from Microsoft after that date.

For IT leaders managing fleets of Windows 11 22H2 devices, the question is straightforward: what do you do with these machines once support ends? You have three realistic paths — and nine months is enough time to execute any of them. Here is an honest assessment of each option, with the cost, risk, timeline, and environments each suits best.

Option 1: Migrate or Upgrade to a Supported Windows Release

What it involves: Moving all workstations running Windows 11 22H2 to a newer version of Windows 11 that is still under active support (e.g., 23H2 or later). Depending on your licensing, this may be a free in-place upgrade or require new licenses.

Cost profile: Low to medium. In-place upgrades are often included in existing volume licensing agreements. However, the real cost is labor: testing application compatibility, managing user rollout, and handling potential driver or hardware issues. For large fleets, this can mean significant IT hours.

Risk: Moderate. While Microsoft publishes compatibility tools, in-place upgrades can break custom applications, line-of-business software, or hardware drivers. Rollback can be messy if not planned carefully. The risk is highest in environments with legacy apps or specialized peripherals.

Timeline: Feasible within nine months for most organizations, especially if you start now. Staggered rollouts (pilot, then wave) are standard.

Best suited for: Platforms under active development where users need the latest features and security updates. Also a good fit for organizations with a standard, well-tested hardware and software stack.

Option 2: Purchase Extended Security Updates (ESU) from Microsoft

What it involves: Microsoft offers paid Extended Security Updates for some Windows versions after end of life. At the time of writing, ESU programs are commonly available for enterprise and education editions, but terms, pricing, and availability for Windows 11 22H2 have not been finalized by Microsoft. (Vendor page: Microsoft software.)

Cost profile: High for large-scale deployments. ESU costs scale per device per year and typically double in each subsequent year. For a fleet of hundreds or thousands of devices, the annual bill can be substantial.

Risk: Low — the updates are official Microsoft patches, tested and delivered through normal channels. However, ESUs do not include non-security hotfixes or feature updates; they only cover critical vulnerabilities.

Timeline: ESU programs are usually announced closer to the end-of-life date. You have nine months to prepare, but you cannot purchase ESU until Microsoft releases the program details and pricing. That adds uncertainty.

Best suited for: Environments that need a temporary bridge while planning a full upgrade — for example, a few dozen critical machines that cannot be upgraded immediately but must remain compliant.

Option 3: Move to Third-Party Maintenance and Support

What it involves: Contracting with a third-party provider (like 3rdpartysupport.com) to deliver ongoing security patches, bug fixes, and technical support for Windows 11 22H2 after Microsoft's end-of-life date. Third-party support covers the product as-is, without forcing an upgrade or feature change.

Cost profile: Predictable and typically lower than ESU for large fleets. Third-party providers often charge a flat annual fee per device, with no year-over-year price escalation built in. Compared to the per-device cost of ESU over three years, third-party support can save 40–60%.

Risk: Low to moderate. Patches are developed and tested by the provider, not Microsoft. Reputable providers follow rigorous vulnerability research and testing processes. However, you should evaluate the provider's track record, SLA, and patch verification procedures. For stable workloads that do not change frequently, the risk is minimal.

Timeline: You can sign a contract now and have support active the day after Microsoft stops updates. No need to wait for vendor programs or plan complex migrations.

Best suited for: Stable workloads that just need to keep running — for example, fixed-function workstations in manufacturing, healthcare, or retail. Also an excellent option for organizations that want to defer the cost and disruption of a full operating system upgrade for one to three years.

Side-by-Side Comparison

Factor	Migrate/Upgrade	Vendor ESU	Third-Party Support
Cost	Low–medium (labor)	High (per-device, escalates)	Low–medium (flat fee)
Risk	Moderate (app compatibility)	Low (official patches)	Low–moderate (reputable provider)
Timeline to implement	3–9 months	Depends on vendor program launch	1–4 weeks
Best for	Active development environments	Temporary bridge	Stable, static workloads
Feature updates	Yes	No	No
Long-term viability	Best (stays supported)	Up to 3 years	As long as contract is active

Decision Checklist for Windows 11 22H2

Before October 8, 2024, work through these questions with your team:

• Have we inventoried all devices running Windows 11 22H2?
• Can we afford the IT hours and risk of an upgrade within nine months?
• Do we have any devices that cannot be upgraded due to hardware or software dependencies?
• Has Microsoft announced ESU pricing for Windows 11 22H2? If so, what is the per-device cost for three years?
• For stable workloads, what would the total cost of third-party support be compared to ESU?
• Do we have a change-freeze period (e.g., year-end) that would conflict with a migration timeline?
• Which provider will we use if we choose third-party support? Have we vetted their patching and response SLAs?

Making the Right Call

Nine months is a generous window — but it will disappear fast. Start your evaluation now. For many organizations, a hybrid approach works best: migrate the flexible workstations and place locked-down, stable machines on third-party support.

If you would like to discuss how third-party maintenance can keep your Windows 11 22H2 fleet secure and supported past October 2024, contact our team for a no-obligation assessment.

Bottom line: You have options. Choose the one that matches your risk tolerance, budget, and operational reality.