Windows 11 version 24H2 for Home and Pro systems is approaching a critical juncture, with security updates ceasing on October 13, 2026. For those who thrive on pushing their systems to the edge, or perhaps have been preoccupied with high-stakes AI projects, this deadline serves as a crucial reminder to take action. IT teams are urged to transition affected PCs to a supported release before the cutoff.
As outlined in Microsoft’s 24H2 release-health notice, after the deadline, these editions will no longer receive monthly security updates, fixes for known issues, time-zone updates, or any form of technical support. While PCs will still boot on October 14, they will be operating on an unsupported version of Windows—an unsettling scenario that can lead to unforeseen complications during routine inventory checks or vulnerability scans.
However, it’s important to note that not all 24H2 installations face the same fate. Editions such as Windows 11 Enterprise, Education, IoT Enterprise, and Enterprise multi-session will continue to receive support until October 12, 2027. Microsoft’s release-information table clearly delineates the October 13, 2026, cutoff for Home, Pro, Pro Education, and Pro for Workstations editions.
Check what you actually have
For smaller organizations that may not utilize an endpoint management system, the first step is to verify the version and edition of your systems, rather than relying on assumptions based on purchase dates or device models. On an individual PC, navigate to Settings > System > About to check the Windows specifications, or simply type “winver” in the search box. Microsoft provides guidance on both methods in its Windows version-checking guide. Be prepared for slower manual updates, as many users will be scrambling to get their systems up to speed.
For those managing a fleet of devices, consult your endpoint-management or asset-inventory platform for details on edition, version, and OS build. The 24H2 version corresponds to the 26100 build family, while 25H2 uses 26200, and 26H2 employs 26300, as noted in Microsoft’s release data. Your initial report should categorize devices into at least four groups:
- 24H2 Home and Pro-family devices that must migrate immediately.
- 24H2 Enterprise and Education devices that remain supported but require a future migration plan.
- Devices already upgraded to 25H2 or 26H2.
- Devices that are offline, stale in inventory, or failing to report.
The last category often includes forgotten loaners, conference-room PCs, and temporary lab machines—ensure these are verified rather than left unchecked as deadlines approach.
Pick 25H2 or 26H2
Windows 11 25H2 remains a viable upgrade option, with support for Home and Pro editions extending through October 12, 2027, while Enterprise and Education editions are covered until October 10, 2028. For devices transitioning from 24H2, Microsoft offers 25H2 as an enablement package, meaning much of the necessary code is already present on fully patched systems.
On the other hand, Windows 11 26H2, which was released on September 29, presents a newer alternative, supported until October 10, 2028, for Home and Pro editions, and until October 9, 2029, for Enterprise and Education. Eligible devices running 24H2 and 25H2 can receive 26H2 through a servicing technology similar to a monthly update, requiring only a small download and a single restart. It’s crucial to distinguish between 26H2 and 26H1, the latter being intended for new devices entering the market in early 2026 and not available as an in-place update for existing systems.
For many organizations, the decision between 25H2 and 26H2 hinges on validation status rather than the allure of the latest version number. If 26H2 has been thoroughly tested with your business applications, security agents, VPN clients, drivers, and deployment tools, it offers a longer support runway. Conversely, if testing is still in progress, 25H2 serves as a stable landing point while you finalize 26H2 validation.
Respect safeguard holds
The rollout of 26H2 is phased, with Microsoft indicating that availability will gradually expand over several months. Some devices may not receive the update immediately if incompatibilities are detected. Microsoft’s 26H2 release-health page tracks current known issues and rollout status.
If Windows Update indicates an update is pending but not yet ready for a device, a safeguard hold may be in place. Microsoft implements these holds when quality or compatibility data suggests that a feature update could fail or lead to a subpar experience. The company advises against forcing an update until the issue is resolved and the hold is lifted. While administrators can disable safeguards for validation in managed environments, Microsoft cautions that bypassing a hold does not guarantee a successful update—this option should be reserved for test hardware only, not as a blanket solution shortly after a deadline.
Use a short deployment plan
With the deadline looming, maintaining a disciplined approach is essential:
- Inventory affected systems: Identify every 24H2 Home, Pro, Pro Education, and Pro for Workstations device, including those that are remote or rarely connected.
- Patch before upgrading: Ensure devices are current on cumulative updates, confirm available disk space, and verify backup or recovery procedures.
- Test the target release: Validate line-of-business applications, identity and sign-in workflows, endpoint security, VPN software, printers, and any hardware with specialized drivers.
- Deploy in rings: Start with IT and a small representative pilot, then expand by department, hardware model, or risk profile. Avoid a sweeping upgrade of the entire fleet.
- Watch failures and holds: Utilize Intune’s Windows feature-update reports to monitor deployment status, device-level details, errors, and recommendations when the required reporting settings are configured.
- Verify the result: Confirm that upgraded PCs report 25H2 or 26H2 and have installed the latest quality update. An assigned policy does not equate to a completed deployment.
- Handle exceptions explicitly: Document devices blocked by compatibility issues, systems awaiting repair, and endpoints that cannot be reached. Assign ownership and next actions for each.
Unmanaged Home and Pro devices on 24H2 are set to receive 25H2 automatically, allowing users to choose or postpone the restart. Managed Pro devices, however, may not experience the same automatic transition due to IT control measures, which do not extend the support for 24H2. It is advisable to review policies that may keep devices pinned to 24H2.
Do not stop at Tuesday
While meeting the October 13 deadline mitigates immediate risks, it does not conclude the lifecycle management tasks. Microsoft supports Windows 11 Home and Pro feature releases for 24 months, and Enterprise and Education releases for 36 months. This cadence transforms feature-update readiness into a recurring operational responsibility rather than an occasional migration project.
To ensure ongoing compliance, maintain visibility of edition and version data in your regular endpoint reporting. Set alerts well in advance of servicing deadlines, keep a standing pilot group, and regularly review the Windows release-health dashboard before broad deployments. This proactive approach will spare you the discomfort of discovering the next cutoff through a news alert over your morning coffee.
