Windows 10 22H2 End of Life Oct 2025: 3 Options Compared

The Three Options for Windows 10 22H2 After October 14, 2025

With Microsoft ending support for Windows 10 22H2 (build 10.0.19045) on October 14, 2025, IT leaders have roughly nine months to choose a path forward. This isn't an LTS release, so there’s no built-in extended support window. Here’s an honest comparison of your three realistic options, including cost, risk, timeline, and the environments each best serves.

Option 1: Migrate or Upgrade to Windows 11

What it is – Move current workstations to a supported version of Windows 11 (or, in some cases, to Windows 10 22H2 on devices that can't run Windows 11).

Cost profile – Potentially high. Hardware that doesn't meet TPM 2.0 and processor requirements must be replaced. Licensing costs include new Windows licenses if you aren't covered by Software Assurance. Deployment labor for imaging, testing, and user training adds to the total.

Risk – Medium. Application compatibility is the primary risk; line-of-business apps or custom peripherals may not work on Windows 11. Regression in performance or driver support on older hardware can also occur.

Timeline – Tight but feasible if started immediately. A phased rollout of 200–500 endpoints typically takes 3–6 months including testing. Cleaning up app inventory and addressing hardware gaps could push this to 12 months for larger organizations.

Ideal for – Environments under active development where new features (e.g., security enhancements, WSL improvements) are a priority, and hardware refresh cycles align with the OS upgrade.

Option 2: Microsoft’s Extended Security Updates (ESU)

What it is – Paid extended support from Microsoft that continues critical security patches for up to three years after end of life. Pricing is per-device and increases each year.

Cost profile – Predictable but escalates yearly. Year 1 is roughly $61 per device (for enterprise), doubling in years 2 and 3. For 1,000 devices, Year 1 alone could cost $61,000, not including volume discounts or partner costs.

Risk – Low for security compliance. Microsoft will issue patches for critical and important CVEs. No functional or feature updates; stability is preserved. You must still remediate any underlying non-security vulnerabilities yourself.

Timeline – Available immediately after October 14, 2025. Requires enrolling each device and possibly applying a preview patch. Lead time is minimal; you can decide in September 2025 and still enroll.

Ideal for – Organizations that need security compliance without change, with well-understood budgets, and that can afford per-device costs that double each year.

Option 3: Third-Party Support With Patch Backporting

What it is – A third-party maintenance provider (like 3rd Party Support) continues to provide security patches, hotfixes, and functional updates for Windows 10 22H2 after Microsoft stops. Patches are backported from later builds or custom-developed.

Cost profile – Typically a fixed annual fee per device or site, often lower than Microsoft’s ESU for large fleets. No escalating yearly cost. Cost depends on the number of devices, support level (security-only vs. full break-fix), and contract term.

Risk – Medium. Patches are not from Microsoft, so while they cover the same CVEs, they undergo independent testing. The provider must prove its patch quality process. For environments with external compliance audits (PCI-DSS, SOC 2), you need to confirm that a third party's patches meet the standard.

Timeline – Can be in place within weeks of signing a contract. No hardware changes or user training required. Reverts easily if you later migrate: you end the support contract and migrate when ready.

Ideal for – Stable workloads that just need to keep running safely – e.g., factory-floor PCs, air-gapped systems, medical devices, or fleets with hardware that cannot run Windows 11.

Decision Checklist

Use this table to weigh your options against your specific environment:

Factor	Migrate to Windows 11	Microsoft ESU	Third-party support
Capital expenditure	High (new hardware, licenses)	Low (per-device fee only)	Low (fixed fee, no hardware change)
Operating expenditure	Ongoing (licensing, management)	Predictable, escalates	Fixed, no escalation
Timeline to implement	3–12 months	< 1 month	2–4 weeks
Security patch coverage	Full, current	Critical CVEs only	Critical & important CVEs
Compliance readiness	Native support	Scripted enrollment	Needs provider validation
Application compatibility risk	High	Low	Low
Hardware replacement needed	Yes (likely)	No	No
Best for	Active development, refresh cycle	Security-only, short-term hold	Stable systems, long-term lifecycle management

Making Your Choice

Nine months is enough time to execute any of these paths, but they require different lead times. If you haven’t started a Windows 11 migration, an October 2026 timeline is more realistic – meaning you need either ESU or third-party support for at least one year.

For most organizations with stable line-of-business systems, third-party support offers the strongest flexibility: no hardware change, fixed annual cost, and the ability to migrate when ready rather than on a vendor deadline. It’s also the only option that keeps you on Windows 10 22H2 indefinitely, avoiding the forced feature change of a new OS.

Contact us to discuss the right path for your fleet – we’re happy to provide a cost comparison or run a compatibility assessment. In the meantime, review our resources on Microsoft lifecycle for more decision data.

Note: All lifecycle dates and versions are based on endoflife.date/windows. No vendor statements or pricing are implied beyond what is stated here.