Microsoft Ends Windows 11 24H2 Support as Final Patch Arrives on October 13

Microsoft stopped servicing Windows 11 version 24H2 for its consumer editions on October 13, 2026, making the October Patch Tuesday release the last cumulative quality and security update that Home, Pro, Pro Education, Pro for Workstations and SE installations will ever receive. From that date forward, those machines still boot and run, but they no longer receive monthly security fixes, non-security fixes or technical support from the vendor.

The cutoff follows a fixed rhythm rather than a decision made in the moment. Windows 11 ships one feature update per year in the second half of the calendar year, and each release gets a servicing window measured from general availability: 24 months for Home, Pro, Pro for Workstations and Pro Education, and 36 months for Enterprise and Education. Version 24H2 reached general availability on October 1, 2024, which puts the consumer clock at exactly October 2026.

Microsoft Learn, the company's official documentation site, reported on October 13, 2026 that the lifecycle table lists the consumer end of updates for version 24H2 at October 13, 2026, while the commercial end of updates for the same version sits at October 12, 2027. That single year of separation is the most consequential detail in the retirement, because it splits machines that appear identical on an inventory report into two groups with patch deadlines twelve months apart.

Replacements are already on the market. Version 25H2 arrived on September 30, 2025, with consumer support running to October 12, 2027 and Enterprise and Education support to October 10, 2028. Version 26H2 shipped on September 29, 2026, supported until October 10, 2028 for Home and Pro and until October 9, 2029 for Enterprise and Education. Microsoft also notes that version 26H1 is scoped to new devices and is not offered as an in place upgrade from 24H2 or 25H2, closing off the assumption that any higher number is a valid destination.

Key Facts

Windows 11 version 24H2 reached general availability on October 1, 2024 and burned through the standard 24 month consumer servicing window at the October 2026 Patch Tuesday release. The latest revision builds published by Microsoft are 26100.9550 for 24H2, 26200.9550 for 25H2 and 26300.9550 for 26H2, according to Microsoft Learn.

What stops after the deadline is precise. PC Master Insider reported on October 12, 2026 that Home, Pro, Pro Education and Pro for Workstations editions will no longer receive monthly updates, technical support or security bug fixes once the final cumulative patch lands, and that unsupported software exposes personal and business data to unpatched exploits. The machines themselves are not disabled.

Consumers are largely being moved automatically. TechRepublic reported on August 20, 2026 that unmanaged devices on 24H2 upgrade to version 25H2 through an enablement package, and that users can schedule reboots, pause the installation or trigger the upgrade manually through Settings, Windows Update and the check for updates option. Standard Home and Pro installations of 24H2 are not eligible for Extended Security Updates, so there is no paid extension available. Windows 10 Enterprise LTSB 2016 reached its own end of updates on the same day, and Microsoft recommends migrating to Windows 11 Enterprise LTSC 2024 or buying paid Extended Security Updates for that older platform.

Enterprise managed devices follow a different calendar. Because 24H2 Enterprise and Education editions retain support until October 12, 2027 under their 36 month lifecycle, a 24H2 Pro laptop and a 24H2 Enterprise laptop can carry the same version string while sitting a full year apart on patch deadlines. The upgrade for those managed machines happens when administrators orchestrate it, not when Microsoft pushes it.

The October release is not only a farewell. Windows Central reported on October 7, 2026 that the update brings one identical set of changes to versions 26H2, 25H2 and 24H2, including a Settings option that lets users decide whether apps always open maximized, File Explorer improvements such as previews for downloaded HTML files and automatic PDF previews, a Home page that remembers expanded or collapsed sections, refreshed Magnifier toolbar icons, new touchpad controls, Copilot key remap options to Right control or the Context menu key, a new Tips widget and a Windows Recovery Environment that can reuse previously configured Wi Fi credentials.

Analysis

The headline number is 24 months, but the operative number is one year. What this really means is that the 24H2 retirement is not a single event but two staggered events, and only the first has arrived. Consumer machines are now on their own unless they move, while corporate machines carrying the same build number keep receiving patches through October 12, 2027. Any organization that counts, licenses or reports its Windows estate by version number alone is now measuring the wrong thing.

The upgrade itself is nearly invisible for consumers, and that is the point of the enablement package design. Many users will effectively reboot into version 25H2 without ever choosing it, which keeps the installed base current but also means a device can change feature version without its owner noticing. For administrators the opposite is true, and the planning work falls entirely on them.

Making 26H1 a new device release rather than an in place upgrade is a deliberate wall. It prevents a messy free for all migration and pushes the mainstream audience toward 25H2 or 26H2, both of which are supported well into 2027 and beyond. The trade is simple: less confusion about destinations, more pressure on the two versions Microsoft actually wants people to use.

The risk curve is also gradual rather than sudden. Nothing breaks the day after the deadline, and no dialog box will appear to announce the change. What breaks arrives later, quietly, on the second Tuesday of some future month, when a fix that every supported machine receives simply never shows up on a 24H2 installation, and the missing patch is only noticed when someone goes looking for it.

Why It Matters

Unsupported does not mean unusable, and that gap is where most of the trouble hides. A 24H2 PC will keep booting, opening documents and joining networks. What it will not do is receive the monthly cumulative security update that Microsoft ships on the second Tuesday of each month, and every month that passes widens the distance between what attackers can test against and what those machines can defend against. That asymmetry favors whoever moves first, and it penalizes whoever assumes the operating system will keep looking after itself.

For organizations, the compliance angle is sharper than the technical one. A mixed fleet containing both 24H2 Pro and 24H2 Enterprise hardware creates an auditing problem, because a patch management report will show the same version string on machines with different support status. Teams that track lifecycle by version alone will either understate their exposure or overstate their readiness.

Consumers face a narrower but real risk. With no paid Extended Security Updates path open to standard 24H2 Home and Pro, the only options are moving to 25H2 or 26H2 or living with a permanently unpatched operating system. Since the shift to 25H2 is automatic for unmanaged devices, the practical advice is to let it happen, or trigger it manually, and to resist pausing it indefinitely.

Next Up

Attention now moves to the next dates in the same chain. Microsoft Learn reported on October 9, 2026 that its Windows message center carries a 30 day reminder that Windows 11 version 23H2 Enterprise and Education editions reach end of updates on November 10, 2026, with the November 2026 security update as the last for those editions. The same notice board tells administrators to prepare for Windows Update certificate rotation in 2027, because the certificates used to trust Windows Update connections expire on May 17, 2027 and June 19, 2027, and devices without replacements lose access to Windows Update.

Windows 11 25H2 and later need no action for that rotation, but machines on 24H2 and Windows Server 2025 must install the September 2025 update or later before June 19, 2027. The message center also flags interim guidance for Manitoba time zone changes, a permanent move to UTC minus 5 with a fix arriving in October 2026. For anyone still on 24H2, the calendar now reads: move to 25H2 or 26H2, then confirm certificate readiness long before the 2027 expiry dates.