Windows 10 1607 (LTS) EOL Oct 2026: 3 Options to Consider

The Timeline and What It Means for You

Microsoft Windows 10 1607 (LTS), build 10.0.14393, reaches final end of life (EOL) on October 13, 2026. That is roughly nine months from today. Active support ended on October 12, 2021, so this EOL date is the absolute cut-off for all security patches and updates — even for the Enterprise Long-Term Servicing (LTS) channel.

If you are running this release, you are now in the “last mile.” Nine months is a realistic window to execute a migration, buy vendor extended support (if available), or arrange third-party support. But the right choice depends on your workload, risk tolerance, and budget.

Option 1: Migrate or Upgrade

What it involves — Moving to a currently supported Windows release, such as Windows 10 22H2 (EOL October 2028) or Windows 11. Requires hardware compatibility checks, application testing, and a phased rollout.

Cost profile — High upfront licensing and labor. New OS licenses may be needed if your current agreement does not include upgrade rights. Testing and deployment labor is often the largest expense.

Risk — Medium. Upgrades risk application incompatibility and driver issues, especially for legacy line-of-business apps. Regression testing is essential.

Timeline — 4 to 8 months for a well-resourced team. Nine months is tight but feasible if planning starts now.

Best for — Environments under active development, where new features and modern hardware support justify the migration cost.

Option 2: Buy Vendor Extended Support (If Offered)

What it involves — Purchasing Microsoft’s Extended Security Updates (ESU) for Windows 10 1607 LTS. Note: ESU is typically offered for broadly released versions, not LTSB/LTSC, but some enterprise customers may negotiate custom terms. You should verify directly with Microsoft or your reseller.

Cost profile — Per-device annual fees that increase each year. Typically lower than a full upgrade in year one, but can exceed upgrade cost by year three.

Risk — Low from a compliance standpoint (patches still arrive), but no feature updates. Relies on Microsoft continuing the program.

Timeline — Can be purchased immediately. Provides up to three additional years, but must be renewed annually.

Best for — Environments that cannot upgrade due to hardware or application constraints, and that have budget for recurring fees.

Option 3: Move to Third-Party Support

What it involves — Engaging a third-party maintenance provider (like 3rd Party Support) to deliver custom security patches and technical support after Microsoft stops. The vendor’s source code and binaries remain untouched; patches are applied at the OS layer.

Cost profile — Flat annual fee, typically 30–50% less than Microsoft’s ESU pricing, and doesn’t increase steeply over time. No per-device licensing complexity.

Risk — Medium. Patches are provided by an independent lab, not Microsoft. However, reputable providers offer SLAs, regression testing, and patch validation. For stable, static workloads (e.g., air-gapped industrial controllers, fixed-function POS terminals), this risk is often acceptable.

Timeline — Can be arranged within weeks. Coverage begins the day after EOL.

Best for — Stable, non-development workloads that just need to keep running securely. Ideal when hardware cannot be replaced and the OS version is proven stable.

Decision Checklist

Use this checklist with your team to decide which path fits:

Criterion	Migrate/Upgrade	Vendor ESU	Third-Party Support
Hardware supports latest OS?	Must verify	Not needed	Not needed
Apps compatible with new OS?	Must test	Not needed	Not needed
Budget for one-time upgrade cost?	Yes	No	No
Budget for recurring annual fees?	No	Yes	Yes
Stable workload with minimal change?	No	Maybe	Yes
Under active development or new features needed?	Yes	No	No
In-house patch management capability?	Yes	Yes	Possibly needed (provider may offer managed service)
Need absolute Microsoft-origin patches?	Yes	Yes	No

Scoring: Tally the “yes” responses per column. The column with the most matches is your best starting point for detailed evaluation.

Next Steps

No matter which option you choose, start now. Nine months can pass quickly, and the worst scenario is running unsupported with no fallback.

If third-party support fits your profile — especially for stable, long-life deployments — contact our team to discuss coverage scope, pricing, and onboarding. We support Windows 10 1607 LTS and thousands of other enterprise products past their vendor EOL dates.

For full lifecycle details, see Microsoft’s official lifecycle page at endoflife.date/windows and our vendor page for more on supported versions.