Still on Windows 11 24H2? Check Your Edition and Upgrade Plan

Moving your business to Windows 11 was a milestone. It was not the last operating-system decision you would need to make. Last week brought a reminder: Microsoft says Windows 11 version 24H2 Home and Pro reached end of updates on 13 October 2026. Those editions no longer receive monthly security and non-security preview updates. See Microsoft’s 24H2 status notice.

The immediate question for an Australian business is therefore more specific than “Are we on Windows 11?” It is: which edition and version is each device running, and what happens next for the devices whose update support has ended?

Check the edition before deciding the deadline

The same Microsoft notice confirms that Windows 11 24H2 Enterprise and Education remain supported until 12 October 2027. Do not apply the Home and Pro deadline to every computer labelled 24H2. Specialised long-term servicing editions also need their own lifecycle check; Microsoft’s Windows 11 release information separates these support paths.

This distinction matters in a mixed fleet. A recently purchased laptop, a shared reception computer and a managed staff device may have different editions or release versions. Purchase date and a Windows 11 sticker are not enough to establish their update status.

Start with a usable device list

Ask your IT team or provider for a current inventory, including the date each device last checked in. For an individual computer, Microsoft explains how to find the edition and version in Settings, under System, then About. Record both fields under Windows specifications.

For each business device, capture the person or function it supports, edition, version, support deadline, update status and next action. Include spare laptops, remote workers and shared machines. Mark devices with stale or missing information as needing investigation; silence is not evidence that an upgrade succeeded.

• Confirmed supported: keep normal update monitoring in place and record the next lifecycle date.
• 24H2 Home or Pro: prioritise a supported upgrade path and assign someone to deliver it.
• Blocked or uncertain: identify the application, hardware or management issue before agreeing a dated resolution.

Choose an upgrade path around real work

A business upgrade should start with the applications and equipment people rely on. Ask the application vendor about support for the proposed Windows release, then test the workflows that matter: processing an invoice, printing a label, joining a meeting, signing in remotely or accessing a specialist system.

Select a small, representative pilot that includes different device models and job roles. A successful test on the IT team’s laptop does not prove that a warehouse scanner or finance add-in will work. Check the target release’s known issues and device eligibility before deployment, and investigate compatibility restrictions rather than forcing past them.

Agree a maintenance window with the business, confirm current backups and a workable recovery route, and explain the expected interruption to users. After the pilot, expand in manageable groups. Have an application owner confirm the key tasks work before calling each group complete.

These checks create a trade-off: moving quickly reduces time on an unsupported release, while testing reduces the chance of interrupting operations. The answer is a short, owned plan with visible exceptions, not an indefinite pause or an untested fleet-wide change.

Give every exception an owner and an end date

Imagine a shared computer runs an older label-printing application that has not been validated on the target release. Record who is contacting the vendor, when a test will happen, how the business will operate during the change and who can approve replacement if needed. This is an illustrative scenario, not a customer case study.

Where an immediate upgrade is blocked, have your IT lead assess interim exposure and access restrictions appropriate to that device. Additional controls do not restore Microsoft’s operating-system updates. Keep the exception visible until the device is upgraded, replaced or retired, and confirm the result in the inventory.

Make lifecycle dates part of routine IT reporting

At Zarbtech, our practical recommendation is to track supported operating-system coverage alongside patch status. Ask for the number of devices approaching a deadline, the number already outside support and the unresolved exceptions. A report should show which machines were checked, not just a percentage without a clear denominator.

That turns last week’s deadline into an ongoing maintenance habit. Review upcoming lifecycle dates early enough to allow application testing, business approval and procurement where necessary. Confirm who follows up devices that are offline or repeatedly fail an upgrade.

Turn the device list into a plan

Zarbtech’s Managed IT services include proactive monitoring and maintenance. Our IT Projects services cover planning, procurement, deployment and staging. If your device inventory has unsupported versions or unclear upgrade ownership, talk with us about the scope needed to assess the gaps and plan the work around your business.