Windows 11 23H2 EOL: Options Before Nov 2025

The November 11 Deadline and What It Means for Windows 11 23H2

Microsoft Windows 11 23H2 reaches both end of active support and end of life on November 11, 2025. This release carries build version 10.0.22631 and is not an LTS release, meaning there is no built-in long-term servicing channel to fall back on.

Nine months is a realistic planning window, but the wrong choice can cost more in operational disruption than the support fees you are trying to avoid. Here is a clear-eyed comparison of your three paths.

Option 1: Migrate or Upgrade to a Supported Release

What it involves Move your fleet to a newer Windows 11 feature update (e.g., 24H2) before November 11, 2025.

Cost profile

• No direct licensing fee for the OS upgrade itself if you already have Software Assurance or a Windows E3/E5 license.
• Significant indirect costs: application compatibility testing, user training, and potential hardware refresh cycles if older devices fail the new build’s hardware requirements.
• Timeline: 2–6 months for planning, pilot, and phased rollout in a mid-size environment.

Risk

• Low-to-moderate if you stay within the same hardware generation and have strong patch management.
• Higher if you delay and rush the upgrade in the final two months before EOL.

Best suited for

• Environments under active development where you need the latest security features and driver support.
• Organizations with spare deployment capacity or existing Windows Update for Business workflows.

Option 2: Vendor Extended Support (If Offered)

Microsoft does offer paid Extended Security Updates (ESU) for some Windows versions, but at the time of writing no ESU program has been announced for Windows 11 23H2. This option may become available later, but it is speculative.

If it becomes available, the profile would likely mirror past ESU programs:

• Per-device annual cost that doubles each year.
• Covers only critical security patches — no new features, no design changes, no non-security fixes.
• Requires the base OS to already be licensed and in active support at the time of enrollment.

Best suited for

• Highly regulated industries that need vendor-attested patching for compliance.
• Small numbers of devices that cannot be upgraded due to legacy application dependencies.

Option 3: Third-Party Support

Third-party maintenance providers can deliver security patches and break-fix support for Windows 11 23H2 well after Microsoft’s November 2025 cutoff, without requiring an OS upgrade.

Cost profile

• Typically 50–60% of what you pay Microsoft for active support + ESU (if available).
• Fixed annual fee that does not escalate over time.
• No new hardware or retraining costs — the OS stays put.

Risk

• Low if the third party has a proven track record of patching Windows and maintaining compatibility with your custom apps.
• Requires due diligence: check the provider’s SLA, patch testing methodology, and incident response track record.

Best suited for

• Stable, business-critical workloads that “just work” on 23H2 and would be disrupted by an upgrade.
• Large fleets migrating slowly to a new platform (e.g., Windows 11 LTSC or a non-Windows environment) but that need support in the interim.
• Cost-conscious teams that want predictable budgets without surprise per-device escalation.

Decision Checklist for IT Leaders

Criterion	Favor upgrade if …	Favor third-party support if …
Workload stability	You are already planning a feature update	The current build is stable and performs well
Hardware lifecycle	Most devices are under 3 years old	Fleet is mixed age and upgrading OS would also force hardware swap
Compliance requirement	You need Microsoft’s attestation (e.g., ISO 27001 audit)	Your compliance framework accepts third-party patching with documented SLAs
Budget predictability	You have a one-time capex cycle for 2025 H2	You need flat opex with no per-device per-year escalation
Internal skill capacity	You have dedicated desktop engineering team bandwidth	Your team is focused on server/cloud projects and cannot absorb a desktop upgrade cycle

Next Steps: Your Nine-Month Window

November 11, 2025, will arrive faster than most quarterly planning cycles. The safest move is to pick your path by Q2 2025 so you have six months for execution buffer.

• If staying on 23H2 after EOL is non-negotiable, contact us to discuss a third-party support plan tailored to your environment.
• If you are leaning toward an upgrade, start your app inventory and compatibility testing now — those activities alone can take 8–12 weeks in a complex enterprise.

The choice is not binary between “move now” and “do nothing.” Third-party support gives you a third lever: keep running what works, safely, while you plan the next transition on your own schedule.