Windows 11 23H2 (W) End of Life: Budget Planning

Understanding the End of Life Date for Windows 11 23H2 (W)

Microsoft Windows 11 23H2 (W), with version number 10.0.22631, reaches the end of its lifecycle on November 11, 2025. This is not an LTS (Long-Term Servicing) release, meaning it lacks the extended support timeline that some enterprise customers rely on for stable, legacy deployments.

On that date, Microsoft will terminate active support and security updates for this specific feature update. For IT directors and procurement leads, this marks the deadline by which all devices running 23H2 must be upgraded to a supported build—or be retained via an alternative support method.

Why This EOL Matters for Your Next Fiscal Year Budget

With the EOL landing roughly 13 months from today, it falls squarely within the next fiscal year for most organizations. Budget cycles often close 6 to 9 months before the start of the new fiscal year, so the decision window is effectively now. If you wait until the current fiscal year ends, you could miss the opportunity to secure funding for migration or extended support.

A line item for Windows 11 23H2 lifecycle management should include:

• Migration costs: License upgrades, testing, deployment tools, user downtime, and third-party application compatibility.
• Extended support fees: Microsoft’s ESU (Extended Security Update) program for Windows 11 feature updates (if available).
• Third-party support contracts: A lower-cost alternative that provides security patches and technical support beyond the vendor’s EOL.
• Contingency buffer: For unforeseen delays in testing or deployment, which are common at scale.

The Real Cost of Migrating at Scale

Migrating a fleet of workstations from one Windows 11 feature update to another involves more than simply clicking "Update." At enterprise scale, you must:

• Test and re-certify every line-of-business application against the new build.
• Validate driver support across your hardware inventory (especially for specialized peripherals or legacy systems).
• Plan a phased rollout, often requiring both user training and support over several months.
• Coordinate with security teams to ensure compliance during the cutover.

Even with automated tools, full migrations for large organizations often stretch 6 to 12 months. The November 2025 deadline is tight—especially if you also need to manage the parallel EOLs of other Windows 11 feature updates.

Why Teams Often Fail to Migrate in Time

Common reasons IT teams miss a vendor EOL deadline include:

• Underestimation of testing scope: Application compatibility testing can uncover blockers that require vendor updates or custom workarounds.
• Hardware refresh cycles: Some devices capable of running 23H2 may not qualify for the next feature update, requiring hardware replacement that has its own budget cycle.
• User resistance or compliance delays: Regulatory or audit requirements can slow the rollout of a new OS build.
• Coordination burdens: Multiple feature updates landing in succession can cause fatigue or prioritization conflicts.

Rather than scrambling for a last-minute vendor extension, having a fallback plan—like third-party support—built into your budget now avoids panic later.

Compare Your Options: Migration vs. Extended Support vs. Third-Party Support

When planning your line item, weigh these three approaches:

• Migration: One-time cost, but requires full execution before EOL. If you miss the deadline, devices become unpatched and non-compliant.
• Vendor Extended Support: If Microsoft offers ESU for Windows 11 feature updates, this is typically priced per device per year and often escalates over time. It buys you 1-3 years but at a premium.
• Third-Party Support: A flat annual fee covers all devices running 23H2, including security patches and technical support. It does not require upgrading or changing the OS. This is especially attractive if:
  • You have a stable, tested environment.
  • The cost of migrating exceeds the support fee.
  • You need to defer migration for one or two budget cycles.

Gather quotes for all three options before finalizing your budget. Knowing the third-party support cost gives you a transparent benchmark to compare against vendor renewal fees.

What to Put in Your Budget Request Now

Include the following narrative and numbers in your next budget proposal:

1. The EOL date and the number of devices affected.
2. Two scenario costs: Full migration vs. third-party support for 12 months.
3. A recommended decision timeline: Set a go/no-go date 6 months before the EOL (May 2025) to evaluate whether migration is on track.
4. A contingency line item: 15-20% above the primary option to cover delays.

If you choose to budget for third-party support, you can keep the migration project as a lower-priority, non-critical initiative—freeing resources for other urgent projects.

Get a Third-Party Support Quote as a Benchmark

Before you enter vendor renewal or ESU negotiations, get a quote from a third-party support provider. This serves two purposes:

• It gives you a factual cost comparison to present to your finance team.
• It prevents vendor lock-in by showing an alternative can deliver security coverage without an OS upgrade.

Contact us for a custom benchmark quote for your Windows 11 23H2 estate. You’ll receive a fixed annual price per device, coverage details, and a service-level agreement—so you can enter your budget cycle with data, not estimates.

---

Lifecycle data sourced from endoflife.date/windows. For more about our third-party support for Microsoft software, see our Microsoft support page.