Windows 11 version 24H2 end of support (Oct 2026): everything business users need to know

Microsoft support for Windows 11 version 24H2 is ending in October 2026. Your devices won’t suddenly stop working, but once a Windows version reaches end of support, it stops receiving the security and quality updates that keep it safe, compliant, and supported.

If you’re running 24H2 on any devices, the simple message is: plan to move those devices to a supported Windows 11 release (e.g., 25H2) as part of your normal patching and lifecycle management.

What is “Windows 11 version 24H2”?

Windows 11 gets feature updates that are identified by a version label.24H2 means the second major feature release in 2024 (“H2” = second half of the year).

Each version has a servicing window. During that window, Microsoft ships:

• Security updates (patches)
• Quality/reliability updates
• Fixes and support coverage for that specific version

When that window ends, the version reaches end of support (sometimes called “end of servicing”).

When is it happening?

October 2026 is the expected end-of-support point for Windows 11 24H2.After that date:

• Devices still power on and run apps
• But they no longer receive security updates for 24H2
• Microsoft might make you to upgrade to a supported release before troubleshooting can continue.

Does it affect me?

It affects you if any business devices are currently running Windows 11 24H2 (including laptops used for hybrid/remote work).How to find out (quick checks):

• Go to Settings → System → About → Windows specifications
• Look for Version: 24H2

• Use your endpoint management/reporting (e.g., Intune / endpoint management tooling, RMM, device inventory reports) to list devices by Windows version.
• If you don’t already have an “OS version” report, get one set up now — it’s one of the fastest ways to avoid last‑minute surprises.

If you’re not sure how to pull that report, we can help you identify exactly which devices are in scope and what upgrade path makes sense.

What should I do if it does?

Treat this like a normal lifecycle milestone, but don’t leave it too late.

Recommended next steps:

• Build a list of devices running 24H2 (and who uses them)

• Check disk space, hardware compatibility, and app compatibility (especially line-of-business apps, security tooling, VPNs, printing, and any legacy drivers)

• Pilot a small group first (IT + a few typical users)
• Roll out by department/site in waves
• Schedule around peak business periods

• Move to the next supported Windows 11 feature release in your environment (for many orgs this will be Windows 11 25H2, subject to your update rings and policies)

• For security and compliance, keep a record of what’s upgraded, what’s deferred, and why

Why it matters: once a version is out of support, you’re exposed to avoidable risk (unpatched vulnerabilities), and you can run into compliance and vendor-support issues.

How can I stay ahead of these things in future?

 

For many businesses, that is the real benefit of professional patch management and monitoring: fewer last-minute scrambles, clearer priorities and more confidence that the devices people rely on are secure, supported and working as they should.

 

Want a a quick check of your estate and a simple upgrade plan?

Get in touch with your One2Call Account Manager, or book a quick consultation here.