Windows 11 24H2 Home and Pro: updates end on 13 October

On 13 October 2026, Windows 11 24H2 Home and Pro reaches end of updates. Microsoft states that devices running these editions will no longer receive monthly security updates or preview updates after this date. Source: the Windows message center.

Breachroad’s conclusion: organisations should establish every device’s version and edition, assign a change owner and collect evidence of migration to a supported release. An inventory entry saying Windows 11 does not establish its servicing deadline. The plan below is our recommendation for IT, application owners and people coordinating team operations.

Same version, different deadlines

Version and edition	End of updates
Windows 11 24H2 Home / Pro	13 October 2026
Windows 11 24H2 Enterprise / Education	12 October 2027
Windows 11 23H2 Enterprise / Education	10 November 2026

The dates come from the Windows 11 release table and apply to the listed editions in the General Availability Channel. LTSC releases have separate dates. Our recommendation is to record the servicing channel as well, rather than apply one group’s deadline to another.

Turn inventory into a decision

We suggest a list containing the device, user or owner, running version, edition, channel and update management method. Include spare computers, shared workstations and devices that rarely connect to the company network. Each entry should record when its state was last confirmed.

Group the results by the action required: ready for migration, awaiting application verification or requiring a separate technical decision. This is our suggested way to organise the work. Do not assume that computers sharing a version number have identical limitations or the same update policy.

Prepare migration with application owners

We recommend choosing a supported release appropriate for the device and environment. Check important applications, drivers and management arrangements. Identify a representative group for verification and the minimum business tasks that will confirm operation afterwards.

The plan should cover user availability, the required restart, data protection and handling of an unsuccessful upgrade. Go beyond announcing that IT will deploy a new version. The process owner needs to know when the workstation will return to use and who resolves a problem with a critical application.

If a migration blocker remains, record the reason, decision owner and review date. In our assessment, a visible, time-limited exception helps direct follow-up work. Deferring a ticket alone does not establish when someone will next assess the device.

Verify the state after migration

We suggest closing the task only after confirming the running version and edition, update process status and required user functions. A record that a package was sent to a device describes a deployment stage, rather than its final outcome.

Also verify that the computer remains under organisational management and can receive subsequent scheduled updates. Record the evidence, review time and accountable owner. If a device stops reporting to management systems, document the visibility gap and establish how its state will be confirmed.

Give employees a concrete instruction

Our recommendation is to include the date, expected interruption, user actions and approved IT contact in migration communications. Employees should recognise where legitimate update instructions originate and know where to verify an unusual request.

If someone receives an unexpected file or installation instruction outside the agreed process, they need a clear reporting route. Practise that route with a fictional message. This is Breachroad’s suggested training scenario, rather than a report of a specific campaign impersonating this deadline.

A scenario to discuss with the team

A company has two groups of 24H2 computers: Pro and Enterprise. A manager assumes they all share a deadline, while some workstations have not recently appeared in inventory. In this hypothetical scenario, participants identify the relevant groups, missing evidence and owners for further decisions.

The exercise aims to connect support information with everyday device management. For more on setting priorities, read our guide to vulnerability management. IT teams and employees can practise change communications and verification of unusual requests in our cybersecurity training for organisations.