Windows 11 24H2 End of Updates: What October 13, 2026 Actually Means

The story being told about Windows 11 24H2’s end-of-life is not the story worth paying attention to. The headline — “Windows 11 24H2 Home and Pro lose support October 13, 2026” — is correct as far as it goes. Microsoft’s lifecycle documentation says so. The Windows release health dashboard says so. Five months from now, devices on 24H2 will stop receiving security updates, bug fixes, time zone updates, and technical support.

The problem with the headline is what it leaves out. Microsoft is not waiting until October to retire 24H2; it is force-upgrading 24H2 machines to 25H2 now, through a staged rollout that has been escalating since late 2025 and reached “all unmanaged consumer devices” in April 2026. The end-of-life date is not the deadline. The force-upgrade is.

And as of late April 2026, that force-upgrade is going wrong on a meaningful subset of PCs.

The dates Microsoft is publishing

The cleanest summary of the lifecycle is this:

EditionEnd of updatesNote
Windows 11, version 24H2 — Home and ProOctober 13, 2026Auto-upgrade to 25H2 in progress
Windows 11, version 24H2 — Enterprise, Education, IoT EnterpriseOctober 13, 2027Same package, longer support window
Windows 11, version 23H2 — Home and ProNovember 11, 2025Already EOL
Windows 11, version 23H2 — Enterprise, Education, IoT EnterpriseNovember 10, 2026Six months later than 24H2 Home/Pro
Windows 11 SEOctober 2026Last supported version is 24H2; SE retiring entirely
Office 2021October 13, 2026Aligned with Windows 11 24H2 retirement

Microsoft Learn’s published documentation says it plainly: “Windows 11, version 24H2 Home and Pro editions will reach end of updates on October 13, 2026. Devices running these editions will no longer receive fixes for known issues, time zone updates, technical support, or monthly security and preview updates containing protections from the latest security threats.”

What the documentation does not say — and what most coverage of the lifecycle date is missing — is that the path to 25H2 is not a manual step. Microsoft’s release health dashboard now states that “devices running Home and Pro editions of Windows 11, version 24H2 that are not managed by IT departments will receive the Windows 11, version 25H2 update automatically.” Users get to choose when to restart, and they can postpone the install. They cannot decline it.

Why this is the harder story

Microsoft has positioned 25H2 as a “localized refinement” of 24H2 — a small package, mostly architectural, that activates features already present in 24H2 rather than introducing new code paths. In theory, that should make the upgrade trivial. The version string in winver.exe changes; everything else stays the same.

In practice, three things have gone wrong with this rollout, and they are worth tracking individually because they will affect different audiences.

The KB5083769 boot loop on force-upgraded machines. As of April 28, 2026, Notebookcheck and other outlets are reporting that some unmanaged consumer PCs receiving the 24H2-to-25H2 staged upgrade alongside the April 2026 cumulative update (KB5083769) are entering unrecoverable boot loops. Microsoft has not announced a fix timeline. The recovery procedure — boot to recovery media, roll back the upgrade, defer 25H2 — is not a procedure most consumers can execute without help. The audience most exposed is exactly the audience Microsoft is targeting first: home users on Home and Pro who do not have IT administrators managing their devices.

The “you cannot refuse” framing. TechPowerUp described Microsoft’s deployment language accurately: “users cannot refuse this update. They can only schedule the restart for the update to be applied or postpone it slightly before it is finally installed.” That is true for unmanaged consumer devices. For managed devices — corporate Windows 11 fleets running through Intune, WSUS, or Configuration Manager — IT administrators retain control over whether and when 25H2 deploys. The asymmetry matters: enterprise admins can hold the line at 24H2 until October 2027 if they want to. Home users cannot.

The 26H1 carve-out. This one is buried in Microsoft’s release notes but matters for anyone shopping for a new Arm-based Windows PC. Windows 11 26H1 is being released exclusively for Windows-on-Arm devices, supporting Snapdragon X2 Elite/Plus and the upcoming NVIDIA N1/N1X laptop SoCs. If you are reading 24H2 EOL coverage and wondering why the next version is not 26H2, that is why: 26H1 is a parallel Arm-only branch. The mainline x86 version after 25H2 is 26H2, expected later in 2026.

What “end of updates” actually means for you

The framing matters here because Microsoft’s communication has been deliberately ambiguous. After October 13, 2026:

Your 24H2 PC will continue to boot. It will continue to run all your installed software. Standard Windows updates from the Microsoft Store and from individual application vendors (Chrome, Adobe, Office) will continue to install normally. The internet will not stop working. BitLocker will not unbind. Files will not become inaccessible.

What stops is monthly cumulative security updates from Microsoft for the operating system itself. No patches for newly disclosed Windows vulnerabilities. No fixes for newly identified bugs. No time zone updates if a country redefines its DST schedule. No mitigations for boot-level threats discovered after the EOL date.

For a consumer PC used primarily for browsing and email, the practical risk in the first 30 days post-EOL is low. The risk compounds. Six months without security updates and your PC is running an attack surface that exploit kits will be specifically targeting. Twelve months and the gap is significant. There is a reason Microsoft is force-upgrading rather than letting consumers stay on a version that will rapidly become a security liability — but that does not make the force-upgrade itself safe.

For a small-business PC running Microsoft 365, the calculation is harder. Office 2021’s end-of-support also lands on October 13, 2026, so there is no shelter in deferring. Microsoft 365 subscriptions remain supported regardless of OS version, but several enterprise security features (Conditional Access device compliance policies, BitLocker recovery automation) require an in-support OS to function correctly.

The 23H2 ghost story

Worth flagging for IT administrators: Windows 11 23H2 Enterprise, Education, and IoT Enterprise editions reach end of updates on November 10, 2026 — almost a month after 24H2 Home/Pro. That sequence is unusual. Normally, older versions retire before newer ones. The reason this matters is that some enterprise fleets have deferred the 24H2 rollout because of known compatibility issues — the August 2025 Phison SSD crashes, the 2024–2025 Outlook profile-corruption bugs, the printer driver regressions — and have been planning a direct 23H2-to-25H2 leap.

That plan still works. 23H2 Enterprise gives you until November 10, 2026 to land. If you can get your environment validated on 25H2 by mid-October, you have an extra four-week buffer. If you cannot, you are on 25H2 anyway because 23H2 is dead.

What to actually do

For consumer PCs (Home/Pro 24H2):

  1. Check your current version. Press Windows key + R, type winver, press Enter. The dialog tells you which version you are on (24H2 or 25H2) and the OS build (the 26100.x or 26200.x number).
  2. Decide whether to accept the staged upgrade or defer. Settings → Windows Update → Pause updates lets you postpone for up to 5 weeks at a time. That buys you time to monitor whether the KB5083769 boot loop issue gets resolved before you are forced through.
  3. Make a recovery USB before any major upgrade. Settings → System → Recovery → “Create a recovery drive.” A 16 GB USB stick is enough. Without this, an unrecoverable boot loop becomes a reinstall-from-scratch.
  4. Back up your files. This is the advice that everyone gives and almost nobody follows. The boot loop issues affecting 25H2 force-upgrades in April 2026 are not data-destructive yet, but recovery procedures for unrecoverable boot states often are.

For small-business and enterprise PCs:

  1. Confirm your management posture. Devices managed by Intune, WSUS, or Configuration Manager are not subject to the staged consumer rollout. You control the upgrade timeline.
  2. Validate KB5083769 in a test ring before broad deployment. The April 2026 update has produced enough field issues that staged ring testing is justified — even on environments where you have historically pushed updates broadly.
  3. Note the October 13, 2026 deadline for 24H2 Home/Pro. If any of your fleet is on Home or Pro editions, those devices will be force-upgraded regardless of management. Plan for it.

The pattern worth watching

This is the third consecutive Windows 11 feature update where Microsoft’s stated rollout plan has produced more friction than the technical change should warrant. 23H2 was uncontroversial in scope but had a slow, error-prone install path. 24H2 introduced significant features and shipped with a string of high-profile regressions (SSD crashes, audio driver issues, Outlook profile corruption). 25H2 is a “minimal” update being delivered through an aggressive force-upgrade mechanism that is producing boot loops on real machines.

Three data points are not a trend. They are enough to note that Microsoft’s deployment confidence appears to exceed its quality validation. That is the pattern to watch through the May and June 2026 Patch Tuesdays. If May produces another out-of-band update — and the trajectory of Q1 2026 suggests it likely will — the right inference is not “this happens sometimes” but “the deployment cadence has gotten ahead of the QA process.”

When to stop

If your PC has already been force-upgraded to 25H2 and is running normally: do nothing. The upgrade is mostly cosmetic, and reverting carries more risk than staying.

If your PC is in a boot loop after the upgrade: do not download a “Windows 11 repair tool” from a search result. Microsoft does not produce one, and the legitimate-looking tools that show up in search ads for these queries are uniformly suspicious. Use a Microsoft-issued recovery USB created on another PC, or take the device to a reputable repair shop. This is one of the cases where the cost of professional help is justified by the consequences of getting it wrong.

If you are an IT administrator and your management tools are reporting that managed devices are upgrading to 25H2 without your authorization: check your update ring policies. The staged rollout respects management policies, but it does not respect unconfigured policies. A device that should be managed but is not properly enrolled will be treated as unmanaged.

FAQ

Will my Windows 11 24H2 PC stop working on October 13, 2026? No. It will continue to boot, run installed software, and connect to the internet. What stops is monthly Windows security updates from Microsoft. The PC becomes progressively less protected against newly discovered vulnerabilities, but it does not become non-functional.

Can I refuse the upgrade to 25H2? For unmanaged Home and Pro devices, no — you can postpone, but you cannot permanently decline. For managed enterprise devices (Intune, WSUS, Configuration Manager), yes — IT retains full control. The asymmetry is deliberate.

Should I upgrade to 25H2 now or wait? As of late April 2026, there is an active boot loop issue affecting some force-upgraded 24H2 PCs. If your PC is running 24H2 and stable, deferring through Settings → Windows Update → Pause updates for the next 4–5 weeks is reasonable. Re-evaluate after the May 12 Patch Tuesday to see whether Microsoft has resolved the issue.

What is the difference between 24H2 and 25H2? Functionally, very little for most users. 25H2 is what Microsoft calls a “localized refinement” — primarily a version bump that activates features already shipped in 24H2 cumulative updates. The biggest practical change for most users is that the support clock resets to October 2027 for Home and Pro editions.

What about Windows 11 26H2? Expected late 2026. The 26H1 release branch was carved out exclusively for Arm-based Windows PCs (Snapdragon X2, NVIDIA N1) and is not relevant to mainstream x86 hardware. The next x86 mainline version is 26H2.

What happens if I have Office 2021 installed? Office 2021 reaches end of support on the same day, October 13, 2026. After that date the apps will continue to run but will not receive security updates. The two practical migration paths are Office 2024 (perpetual license, supported through October 2029) or a Microsoft 365 subscription.

Will the October 13 date slip? It could. Microsoft has slipped published deadlines before — the new Outlook for Windows opt-out phase moved from April 2026 to March 2027 in late February. Office 2021’s deadline appears firm. The 24H2 Home/Pro deadline could plausibly extend if the 25H2 rollout produces enough field issues to delay it. There is no announcement of a slip as of late April 2026.

Official references

Last updated: April 28, 2026.

↑ Back to top