Windows 11 24H2 Home and Pro Stop Getting Updates on October 14, 2026 - A Year Before Enterprise

Windows 11, version 26H2 moved to the Release Preview channel on August 27, 2026, at build 26300.9278. That is the headline. The date buried inside the same announcement is the one worth acting on: Windows 11 24H2 Home and Pro reach end of servicing on October 14, 2026. Enterprise and Education editions of the exact same 24H2 build keep getting security updates for another full year, until October 13, 2027.

Same build number. Same servicing branch. A twelve-month gap in how long each edition is allowed to stay patched. If your estate has any device running Home or Pro on 24H2, that device is on a clock that most of your Enterprise fleet is not.

The problem: a green checkmark on a device that stopped being patched weeks ago

There is no error code for this one. That is what makes it dangerous.

A Windows 11 Home or Pro device sitting on 24H2 past October 14, 2026 does not throw a warning. Settings › Windows Update keeps showing the same screen it always has. Windows Update Compliance reports in Intune, if the device is even enrolled, keep showing the device as compliant against whatever update-ring deadline it last met - because the device is not failing a policy, it is simply no longer being offered anything to fail against. There is nothing left in the pipe for that edition, on that version, so the client checks in, finds nothing new, and reports back exactly what a healthy, fully-patched device reports.

The devices most likely to be sitting on Home or Pro in a managed estate are exactly the ones least likely to be watched closely: personally-enrolled BYOD laptops, contractor machines bought off the shelf because procurement could not turn around an Enterprise-licensed device in time, meeting-room PCs, and any device where someone selected "Windows 11 Home" at setup because nobody told them to look for Pro.

Why it happens: one build, two support tiers

Windows 11 24H2, 25H2, and 26H2 share a single servicing branch. Since 24H2 shipped, each annual feature update has arrived as an enablement package - a small file that flips already-staged features on, rather than a full in-place upgrade. The practical result: the underlying binaries for 24H2 and 26H2 are largely the same files. What changes between them is which features are turned on, not the servicing lifecycle.

The lifecycle itself is decided separately, per edition, under Microsoft's Modern Lifecycle Policy. Home, Pro, Pro Education, Pro for Workstations, and SE get 24 months of servicing per annual release. Enterprise, Education, and Enterprise multi-session get 36 months. Same release, same code, different clock, and the clock starts on the same release date for every edition.

The pattern is consistent going back to launch: every Home/Pro release loses support almost exactly one year before the same release's Enterprise/Education edition does. 24H2 is not a special case. It is just the one whose deadline lands three weeks after this post is published.

How to verify: find every Home/Pro 24H2 device in the estate

Edition and version both live in the same registry key, so one read gets you both. This does not require the device to be domain-joined or Intune-enrolled - it works on any Windows 11 machine you can get a PowerShell session on.

EditionID is the value that matters here. Core and CoreN mean Home. Professional and ProfessionalN mean Pro. Enterprise, Education, and EnterpriseS (the LTSC channel) are the ones with the longer clock. DisplayVersion confirms the feature-update version; CurrentBuild plus UBR together give you the exact build, useful for cross-checking against the 26300.9278 Release Preview number if you want to see how far behind the front of the queue a device actually is.

Doing this across a fleet takes two real steps, not one query. Intune's managedDevice Graph resource has no property for Windows edition at all - there is no skuFamily, no editionId, nothing. It tells you the build. It does not tell you Home, Pro, Enterprise, or Education. Step one narrows the fleet to "every 24H2 device." Step two adds edition on top of that shortlist.

Step one: every 24H2 device, straight from the admin center

No script needed for this part - the device list you already have open does this natively.

1. Sign in to the Microsoft Intune admin center, select Devices, then All devices.
2. Select Columns and add OS version and OS bucket if either is missing. OS bucket groups devices by feature-update version - Windows 11 23H2, 24H2, and so on - which is exactly the grouping this check needs.
3. Sort or filter on OS bucket = Windows 11 24H2.
4. Select Export. The CSV comes back with device name, primary user, compliance state, and last sync time for every matching device.

Step two: which of those are Home or Pro

That export gets you every 24H2 device, but not which of them are Home or Pro - Intune's console does not show edition, and neither does Microsoft Graph. Edition lives in exactly one other place worth knowing about: the OSEdition field in Windows Update for Business reports, Microsoft's Azure Monitor-based reporting solution, if your organisation already has it turned on.

That is a big "if." Most fleets do not have this running, and standing it up just for one deadline is not worth it. So the realistic path for most readers is the same one already covered above: run the registry check by hand on the devices that came out of step one, or hand that shortlist to whoever runs your device compliance scripts and ask them to run it for you.

The fix: move the version, or move the edition

There are exactly two ways off this clock: get the device onto a version that still has runway left on Home/Pro's 24-month tier (25H2 or 26H2), or move the device to an edition that has 36 months instead of 24. Which one is realistic depends entirely on what licensing the device already has behind it.

1. Run the inventory above first. You cannot fix what you have not counted, and this is the one step every remediation path depends on.
2. For devices with no Enterprise/Education entitlement behind them: push the 25H2 or 26H2 enablement package. Because it is the same servicing branch, this is a single restart, not a full upgrade cycle - the fastest way to buy back another 24 months on the Home/Pro tier without touching licensing at all.
3. Control feature-update timing with the TargetReleaseVersion policy - Pro only, not Home:
   • CSP / Intune: ./Device/Vendor/MSFT/Policy/Config/Update/TargetReleaseVersion, paired with the ProductVersion node. Supported on Pro, Enterprise, Education, and IoT Enterprise/LTSC.
   • Group Policy: Computer Configuration › Administrative Templates › Windows Components › Windows Update › Manage updates offered from Windows Update › Select the target Feature Update version.
4. For Home devices specifically, skip step 3 entirely. There is no policy lever. Home has no Local Group Policy Editor, and the TargetReleaseVersion CSP's own applicability table does not list Home as a supported edition. A Home device will take whatever version Windows Update decides to offer it, on Windows Update's own schedule, with no admin override.
5. Where the entitlement exists, upgrade the edition instead of the version. The WindowsLicensing CSP's UpgradeEditionWithProductKey node (./Vendor/MSFT/WindowsLicensing/UpgradeEditionWithProductKey) takes a 29-character product key from the Volume Licensing Service Center and runs changepk.exe against it. It reboots automatically to complete.

For the devices that turn up on Home with no Enterprise/Education/Pro entitlement anywhere and no realistic path to one - genuinely personal BYOD hardware - the honest fix is not a technical one. Flag them in whatever conditional access or compliance policy already gates access for unmanaged devices, and treat "runs Windows 11 Home" the same way you would treat any other unpatchable-by-policy device category.

Proof it worked: a fleet with no edition sitting past its own deadline

Re-run the same Intune export after remediation, filtered the same way - OS bucket = Windows 11 24H2 - and check edition on whatever came back the same way you did the first time. Watch version and edition together, not separately: a device that moved from 24H2 to 25H2 but is still Home edition has only bought itself until October 13, 2027, not solved the underlying gap.

The target state is that filter returning nothing at all.

Zero rows is the target state, not a device count that merely went down. Anything still showing up here on the day after your own internal deadline is a device that either has no path to a longer-lived edition, or has one you have not actioned yet - both are worth a name attached to them before October 14.

References

• Releasing Windows 11, version 26H2 to the Release Preview Channel - the announcement this post is responding to: build 26300.9278, the eKB delivery model, and the new commercial-default features.
• Windows 11 Home and Pro - Microsoft Lifecycle - the full release-by-release end-of-service table for Home/Pro, including the 10/14/2026 date for 24H2.
• Windows 11 Enterprise and Education - Microsoft Lifecycle - the matching table showing 24H2 Enterprise/Education running through 10/13/2027.
• Policy CSP - Update - the TargetReleaseVersion node's exact applicability table (Pro/Enterprise/Education/IoT Enterprise, not Home) and its Group Policy mapping.
• WindowsLicensing CSP - the UpgradeEditionWithProductKey node, its four valid upgrade paths, and why Home to Enterprise is not one of them.
• Windows as a Service (WaaS) quick start - how the enablement-package model keeps 24H2, 25H2, and 26H2 on one servicing branch.

Related on EndpointWeekly

• The Enablement Package: How 24H2 Becomes 25H2 in a Reboot - the mechanics behind why this is a single restart, not a real upgrade.
• Windows 11 26H2 Is Now in Release Preview - how to pilot 26H2 itself before GA, upgrade paths, and Intune update-ring setup.
• Windows Settings Backup Is On by Default From 26H2 - one of the commercial-default changes riding along with this same release.