Windows 11 24H2 EOL October 13, 2026: Last-Call Action Plan

The Clock Is Ticking: Windows 11 24H2 (W) Ends Support on October 13, 2026

Microsoft Windows 11 24H2 (W)—the latest version in this line, build 10.0.26100—hits end of life on October 13, 2026. This is a fixed lifecycle for a non-LTS release: both active support and security patches end on the same date. If you haven't completed migration, you're not alone, but the time for denial is over. Here's what changes and what to do in the roughly 90 days left.

What Exactly Happens on October 13, 2026?

On the EOL date, Microsoft stops providing for Windows 11 24H2 (W):

• No more security patches. Any new vulnerabilities discovered after that date will remain unpatched.
• No bug fixes. Non-security issues will not be addressed.
• No vendor SLA. Microsoft’s support obligations end; you can’t open tickets for this OS version.

There is no extended support phase for this release (it's not an LTS channel). Staying on 24H2 (W) after October 13 means running an unsupported OS—a risk that auditors, insurers, and compliance frameworks increasingly flag.

Realistic Goal: Manage Risk, Not Full Migration

If you still have significant numbers of 24H2 (W) devices, completing a full migration by October 13 is likely unrealistic. Instead, use the remaining weeks to reduce exposure and build a defensible position. Focus on four tracks: inventory, hardening, documentation, and support continuity.

Week-by-Week Action Checklist

Here’s a concrete plan for the next 12 weeks.

Weeks 1–3: Inventory and Triage

• Inventory every device running Windows 11 24H2 (W). Include VMs, physical machines, and cloud instances.
• Identify critical vs. non-critical roles. Prioritize anything handling sensitive data, internet-facing services, or compliance-scoped workloads.
• Check upgrade paths. The latest version in the 24H2 line is 10.0.26100; confirm which devices can upgrade to a newer Windows 11 feature update or Windows 12 if available.
• Create a migration candidate list for devices that can be moved quickly.

Weeks 4–6: Isolate and Harden

• Segment unsupported systems from the rest of the network. Put them on separate VLANs or subnets with strict firewall rules.
• Apply all available patches now. Even if you’re heading to EOL, get the last updates installed to reduce known vulnerabilities.
• Harden configurations: disable unnecessary services, enforce least-privilege access, and enable logging.
• Review security policies—ensure unsupported devices are blocked from high-risk internet traffic where possible.

Weeks 7–9: Document Exposure

• Map each remaining 24H2 (W) system to its owner, data sensitivity, and risk.
• Prepare a risk register documenting the EOL date, why migration wasn’t completed, and mitigation controls in place.
• Flag to auditors and insurers that unsupported systems exist. Proactive disclosure is better than discovery later.
• Create a rollback plan for any last-minute migrations, so you can revert if issues arise.

Weeks 10–12: Secure Support and Final Checks

• Confirm your third-party support contract is in place before October 13. This ensures you have a vendor with an SLA to call on day one after EOL.
• Test your incident response plan for an unpatched OS—what will you do if a critical CVE drops in November?
• Run a final audit of inventory and documentation. Ensure all stakeholders know the go-live date of unsupported status.

What About After EOL?

Even after October 13, 2026, you can continue to run Windows 11 24H2 (W) if you must. The key is having a support partner who can provide security patches and fixes beyond the vendor’s lifecycle end. Third-party support can keep your systems running safely, giving you time to complete migration without a panic-induced weekend. Contact us to line up cover before the deadline.

Final Thought

The EOL date is fixed, but your response doesn’t have to be chaotic. With a structured 90-day plan, you can shrink your attack surface, document the risk, and ensure you have support in place. Start today—three months goes faster than you think.

For more lifecycle details, see end of life data for Windows. You can also visit our Microsoft software page for broader support options.