Windows 11 23H2 Enterprise Support Ends November 10
Direct Answer
Windows 11, version 23H2 reaches end of updates for the Enterprise, Education and IoT Enterprise editions on November 10, 2026, which is also November’s Patch Tuesday. The Home and Pro editions of 23H2 ended a year earlier, in November 2025. The upgrade path is Windows 11, version 26H2, which Microsoft released as an enablement package in September 2026. Note that the operating-system upgrade does not update the third-party applications on those devices; those follow their own vendors’ lifecycles
Key Takeaways
- November 10, 2026 is the last Patch Tuesday for Windows 11 23H2 Enterprise, Education and IoT Enterprise.
- Windows 11 24H2 Home and Pro already ended on October 13, 2026; 24H2 Enterprise and Education run until October 12, 2027.
- 26H2 installs as an enablement package on eligible 24H2 and 25H2 devices, so a 24H2 fleet can skip 25H2.
- Running several Windows 11 versions at once makes application packaging, requirement rules and testing more complex, not less.
What ends on November 10
Microsoft publishes Windows 11 servicing dates on its release information page. For version 23H2, the Enterprise, Education, IoT Enterprise and Enterprise multi-session editions reach their end-of-updates date on November 10, 2026. After that date those devices stop receiving monthly security updates.
The devices keep working. The risk is that newly disclosed Windows vulnerabilities will no longer be fixed on them, which matters most for devices that handle untrusted content or face the internet.
Where the rest of the fleet stands
| Windows 11 version | Home / Pro | Enterprise / Education / IoT Enterprise |
|---|---|---|
| 23H2 | Ended November 11, 2025 | Ends November 10, 2026 |
| 24H2 | Ended October 13, 2026 | October 12, 2027 |
| 25H2 | October 12, 2027 | October 10, 2028 |
| 26H2 | October 2029 (consumer) | See Microsoft’s lifecycle pages |
Dates come from Microsoft’s Windows 11 release information page and the Windows lifecycle pages. Confirm them there before you build a migration plan, because Microsoft occasionally revises servicing dates.
The upgrade path: 26H2 as an enablement package
Windows 11, version 26H2 became generally available at the end of September 2026. It shares the same servicing foundation as versions 24H2 and 25H2 and is delivered to eligible devices on those versions as an enablement package, which activates features already present in the installed build and completes with a single restart.
Two practical consequences:
- A fleet still on 24H2 can move straight to 26H2 without stopping at 25H2.
- Devices on 23H2 are not on that servicing foundation, so they need a full feature update rather than an enablement package. Plan more time and more bandwidth for those.
Why version sprawl complicates third-party patching
An organization can easily be running 23H2, 24H2, 25H2 and 26H2 at the same time in November 2026. That affects application management in ways that are easy to underestimate:
- Requirement rules multiply. Win32 apps in Intune can target a minimum operating-system version. Several supported versions means several rules to maintain and review.
- Testing surface grows. An installer that behaves correctly on 26H2 may behave differently on 23H2, especially for software that hooks into the shell, the browser or drivers.
- Vendor support varies. Application vendors set their own supported Windows versions, independently of Microsoft’s servicing dates.
- Reporting gets noisy. Compliance numbers mix devices on supported and unsupported Windows versions unless you separate them in groups or collections.
A plan for the next four weeks
- Export every device still on 23H2, with edition, owner and business purpose.
- Decide per device: upgrade to 26H2, replace the hardware, or isolate it with a documented exit date.
- For 23H2 devices, schedule a full feature update rather than assuming an enablement package applies.
- Review Win32 app requirement rules and remove minimum-version rules you no longer need.
- Create or refresh device groups and collections based on operating-system version so you can target and report separately.
- Re-test your 15 most widely deployed third-party applications on 26H2 before the broad rollout.
- Keep third-party patching running on devices that stay behind, and report on them separately.
Operating-system lifecycle and application lifecycle are different jobs
Upgrading Windows does not update Google Chrome, Zoom, Adobe Acrobat Reader, Java runtimes or any other non-Microsoft application. A device freshly upgraded to 26H2 can still run a browser version with known, publicly documented vulnerabilities
The same applies in reverse on Windows 10 devices enrolled in Extended Security Updates, where Year 2 runs until October 12, 2027: ESU delivers Windows security updates only.
How Easy2Patch helps
Easy2Patch publishes third-party application updates into Microsoft Intune,Configuration Manager and WSUS from a single catalog, without an additional agent on endpoints. Because the updates are delivered through the groups and collections you already use, the same catalog can serve devices on different Windows versions during a migration, and its CVE information helps you decide which applications must reach the lagging devices first.
Frequently Asked Questions
Windows 11, version 23H2 reaches end of updates for the Enterprise, Education and IoT Enterprise editions on November 10, 2026, which is also November’s Patch Tuesday. The Home and Pro editions of 23H2 reached their end date on November 11, 2025. Microsoft lists these dates on its Windows 11 release information page.
Windows 11, version 26H2 is the current target. It became generally available at the end of September 2026. Devices already on 24H2 or 25H2 can receive it as an enablement package that completes with one restart. Devices on 23H2 are not on that servicing foundation and need a full feature update instead.
Yes, if the devices are on 24H2. Versions 24H2, 25H2 and 26H2 share the same servicing foundation, so the enablement package takes an eligible 24H2 device directly to 26H2. Confirm your specific builds and prerequisites on Microsoft Learn before you plan the rollout.
No. A Windows feature update changes the operating system; it does not update applications from other vendors such as browsers, PDF readers or runtimes. Those applications have their own release cycles and need a separate patching process through Intune, Configuration Manager, WSUS or another tool.
Separate them. In Intune, use dynamic device groups based on operating-system version and keep Win32 app requirement rules under review. In Configuration Manager, use collections based on operating-system version. Clear separation lets you target the right application versions, measure compliance per version and keep exceptions auditable.
Conclusion
November 10 is a hard date for one group of devices and a useful checkpoint for the rest. Confirm which devices move to 26H2, give the stragglers a documented exit date, and keep application patching running across every version in the meantime.
IT Automation Key Benefits and Best Practices

What Is Vulnerability Management?

Ultimate IT Risk Management Guide 2024: Best Practices, Strategies, and Tools

Best Practices for IT Infrastructure Management in 2024

What is Windows Patch Management? Features, Challenges, and Best Practices in 2024

What are the Cybersecurity Risks Associated with Outdated Software and Operating Systems?
