Windows lifecycle
The date applies to the edition as well as the version
Windows 11 24H2 end of support has passed for Home and Pro editions. Microsoft's current lifecycle table lists 14 October 2026 for those editions and 13 October 2027 for Enterprise and Education 24H2. Check both the version and edition, then prioritise affected Home and Pro devices for a tested move to a supported release.
The dates here follow Microsoft's current lifecycle tables, which state that dates are shown in Pacific Time. See the Home and Pro lifecycle table [2] and the Enterprise and Education lifecycle table [1]. As checked on 25 October 2026, the Home and Pro deadline is already past. Treat any affected device still in use as an open upgrade action, with a named owner and a compatibility-aware plan.
This is a feature-version deadline, not a reason to replace every computer. Most compatible Windows 11 Pro devices can move to a newer supported release after application checks and a controlled pilot. Hardware replacement belongs only in the branch where a device is incompatible, unreliable, out of warranty or uneconomic to keep. Milnsbridge can manage the inventory, pilot, deployment and post-change support through its Sydney managed IT service.
Start with facts
Build a device list before choosing an upgrade date
A useful inventory identifies the computers that need work and the business tasks that could be affected. Record these four fields for every device.
Edition and version
Capture Windows edition, version and build. A label that only says Windows 11 is not enough to determine the support date.
Device owner and role
Name the user, location and job function. This makes scheduling practical and exposes shared or rarely used machines.
Business applications
List software, add-ins, printers, scanners, VPN clients and specialist equipment that the user needs after the change.
Readiness and owner
Record compatibility, upgrade holds, backup status, test result, scheduled date and the person responsible for closure.
Choose the right branch
An operating-system update and a hardware refresh are different jobs
Upgrade the current device
Use this path when the device is healthy, supported and compatible with the target Windows release. Confirm storage capacity, firmware, drivers and the readiness of business applications. Keep the user data protected, then test the full workday rather than stopping at a successful sign-in.
Microsoft recommends using Windows Update when the upgrade is offered. A missing offer can indicate that the release is not ready for the device or that a known compatibility issue remains. Review Microsoft's installation guidance [5].
Replace only where justified
A replacement can make sense when a device fails requirements, has unresolved driver issues, is near the end of its useful life or cannot run a critical application reliably. Match the new computer to the person's workload, peripherals and mobility needs.
Milnsbridge is an authorised HP and HPE partner and can procure, configure, deploy and support business hardware. The HP hardware service is an option when replacement is genuinely needed, not the default answer for every 24H2 device.
Upgrade flow
Move from inventory to verified completion
The work is complete only when the target version is installed and the user's applications, access and peripherals have been checked.
Prepare
Decide what should change
Deploy
Prove the result before closing
Pilot first
Test a representative workday before broad deployment
A pilot is useful when it represents real work. Pick devices from the roles that carry the greatest compatibility risk, then check the result against agreed pass criteria.
Protect recovery options
Confirm backup status and the recovery path before installation. A green backup job is useful evidence. A known restore method makes the fallback practical.
Exercise real applications
Open the line-of-business software, sign in, print, scan, use add-ins and connect to remote services. Generic browsing is not a complete compatibility test.
Schedule the restart
Microsoft describes scan, download, install, commit and restart as distinct phases. Give the user a clear window and keep the device powered and connected.
Record the outcome
Capture the installed version, application checks, defects, owner and closure date. Feed any failure back into the rollout plan before the next group starts.
Deployment rings let a business move from a small pilot to broader groups while monitoring errors and user impact. Microsoft documents this phased approach for Windows servicing. See Microsoft's update channels and tools guidance [3]. Businesses using Microsoft Intune can also connect device compliance, application deployment and update policy through Milnsbridge's Microsoft 365 management service.
Run the change
Give each rollout group a clear owner and stop rule
The Windows 11 24H2 end of support date creates urgency for Home and Pro devices. A sound plan still allows time for application testing, recovery checks and user communication.
Group devices by risk rather than by whichever names appear first in a spreadsheet. Standard office users can form one ring. Finance, design, legal or operational roles with specialist software belong in separate rings so a defect does not affect every person who relies on the same application. Microsoft describes deployment groups as a way to start with a limited pilot, monitor errors and user impact, then move to wider deployment. Microsoft's servicing guidance explains the phased model [3].
Set a stop rule before the first group begins. A failed sign-in, broken line-of-business application, unavailable printer, unstable network driver or missing security control should pause the next ring until the cause is understood. A minor cosmetic issue can be logged for follow-up without blocking the whole rollout. The decision belongs to the named change owner, not to whichever technician happens to see the ticket first.
Tell staff what will happen, when their device will restart and what they need to leave open or closed. Give them a simple way to report a problem after sign-in. The message should state the expected outage window and who will confirm completion. This closes a common operational gap. The install can finish overnight, while the first real test waits until the user arrives for a deadline.
Keep exceptions visible. A device on a temporary hold still needs an owner, reason, review date and protective controls. Microsoft states that Windows 11 feature releases receive monthly cumulative security updates while supported, and the 24H2 Home and Pro line is now beyond its listed support period. Check the current Windows 11 release table [4].
Microsoft lifecycle facts
Four dates and support rules to keep separate
24H2 Home and Pro end date in the Microsoft lifecycle table [2], shown in Pacific Time. This date has passed.
24H2 Enterprise and Education end date in the Microsoft lifecycle table [1], shown in Pacific Time.
Support period for Windows 11 Home and Pro feature releases. Source Microsoft release information [4].
Support period for Windows 11 Enterprise and Education feature releases. Source Microsoft release information [4].
FAQ
Windows 11 24H2 business questions
Which 24H2 editions reached end of support in October 2026?
Windows 11 24H2 Home, Pro, Pro Education and Pro for Workstations follow the Home and Pro lifecycle. Enterprise and Education 24H2 have a later end-of-updates date in October 2027.
Does every 24H2 computer need replacement?
No. Compatible, reliable devices can usually move to a newer supported Windows 11 release. Replace a device only when compatibility, condition, warranty, performance or business requirements justify the cost.
Why might the newer release not appear in Windows Update?
The device may need current quality updates first, the feature update may still be rolling out, or Microsoft may have identified a compatibility issue. Investigate the reason before forcing an installation.
What should we verify after the upgrade?
Confirm the target Windows version and current updates, then test sign-in, business applications, printers, scanners, remote access, security controls and the user's normal work. Record any defect and its owner before closing the device.
Sources
Microsoft guidance used for this checklist
Explore more
Plan the wider endpoint lifecycle
Managed IT Services Sydney
Device management, patching, support and lifecycle planning for Sydney businesses.
ExploreMicrosoft 365 Management
Intune, application deployment, identity and Microsoft cloud administration.
ExploreHP Hardware
Business hardware procurement and deployment where replacement is required.
ExploreWindows 10 Support Guide
A separate guide for devices still running Windows 10 after its support deadline.
ExplorePlan the rollout
Get a clear 24H2 upgrade plan
Milnsbridge can help identify affected devices, test business applications and plan a supported Windows rollout. Start with the devices and applications you have, then confirm where an upgrade is suitable and where replacement is justified.
Plan your Windows upgrade
