Windows 11 24H2 End of Support on October 13, 2026: How to Upgrade to 25H2 or 26H2

What actually happens on October 13, 2026

On October 13, 2026, Windows 11 version 24H2 stops receiving monthly security updates and optional preview updates on the Home, Pro, Pro Education and Pro for Workstations editions. Microsoft's lifecycle page lists the end of servicing for 24H2 as 10/14/2026 at 6:59 AM UTC, which is 11:59 PM Pacific on October 13, and it lines up with the October Patch Tuesday. The Enterprise and Education editions of 24H2 are on a longer servicing timeline that runs to October 2027, so a school or a large company with a managed fleet is not on the same clock as a family laptop.

Nothing breaks on that day. Your PC keeps starting, your apps keep opening, and your files stay exactly where they are. What changes is silent: the stream of security fixes stops. Every month Microsoft closes holes that attackers have already learned to abuse, and a machine that no longer receives those fixes becomes easier to attack with every passing month, even if it feels perfectly normal to use.

The good news is that the exit is cheap. Moving from 24H2 to 25H2 or to the new 26H2 does not require a reinstall, does not wipe your programs, and in most cases takes a download, one restart and a few minutes. This guide shows how to check your version in ten seconds, how to get the upgrade offered, what to do when Windows Update refuses to offer it, and how to handle a whole office of computers without losing a day of work.

If you only need the short version, the quick-fix box above covers it. The rest of the guide is for the moment something does not go as planned, for people who manage more than one computer, and for anyone who wants to understand the decision before clicking.

How to check which Windows version you have (10 seconds)

Press the Windows key and the R key together, type winver, and press Enter. The window that opens shows your Windows 11 version, for example "Version 24H2", and the OS build number. If it says 25H2 or 26H2, you are already on a release that is supported beyond October 13, 2026, and you can stop reading here, apart from keeping Windows Update turned on.

You can also open Settings, choose System, then About, and look under "Windows specifications". That screen shows the edition (Home, Pro, Enterprise, Education), the version and the installation date. The edition matters, because the October 13 date applies to Home and Pro, while Enterprise and Education follow a longer schedule.

Why Microsoft ends support for 24H2 now

Microsoft supports each Windows 11 feature release for a fixed window, 24 months for Home and Pro and 36 months for Enterprise and Education, counted from the release date. Version 24H2 reached general availability in October 2024, so the 24-month window for consumer and small business editions closes in October 2026. This is the normal lifecycle, not a punishment and not a surprise.

What makes this release different is how painless Microsoft has made the exit. Since 24H2, the company ships newer annual releases such as 25H2 as enablement packages. An enablement package is a small update that switches on features that were already delivered, dormant, inside the monthly updates you installed over the past year. Because the heavy files are already on your PC, the "upgrade" is closer to flipping a switch than to reinstalling an operating system. That is why it needs only one restart.

The newest release, Windows 11 26H2, follows the same pattern. Microsoft released it on September 29, 2026, again as a small enablement package for devices running 24H2 or 25H2. For Home and Pro it carries 24 months of support. Microsoft's lifecycle page lists the end of servicing for 26H2 as 10/10/2028 at 6:59 AM UTC, which is the evening of October 9, 2028 in Pacific time, so you will see both "October 9" and "October 10" quoted in articles. Enterprise and Education get 36 months.

A practical consequence follows from all this. You do not need to choose between 25H2 and 26H2 in a panic. Either one takes a 24H2 machine out of the October 13 danger zone. 26H2 simply restarts the support clock later, so it is the better long-term landing spot once it is offered to your device.

The decision in one table: what to do based on your situation

Most people should let Windows Update install 25H2 or 26H2 this week, after a quick backup. The exceptions are managed company PCs, which should follow the IT administrator's policy, and devices Microsoft has placed under a compatibility hold. The table below turns that into concrete next steps.

Before you click anything: the 15-minute safety routine

An enablement-package upgrade is low risk, but "low" is not "zero", so spend fifteen minutes on a backup, free space, and a pending-update check before you start. Those three steps remove the large majority of problems people report during a feature update, and they are the same steps a technician performs before touching a client's computer.

1. Back up what you cannot replace

Copy your documents, photos, desktop files and browser bookmarks to an external drive or confirm they are synced to OneDrive or another cloud service. Open the cloud folder on a second device or on the web to confirm the files are really there, because a sync icon that says "up to date" is not proof. If you use a password manager, make sure you can sign in on your phone, so that a bad day on the PC does not lock you out of everything.

For a family computer with irreplaceable photos, a second copy on a USB drive costs less than a coffee and ends the worry. If you are not sure what is on the machine and what is safe, our comparison of data recovery versus data backup explains why a backup you tested beats a recovery you hope for.

2. Free up disk space

Windows needs breathing room to stage and apply an update, and a nearly full system drive is the single most common reason updates fail halfway. Aim for at least 15 to 20 GB free on the C: drive before you start. Open Settings, then System, then Storage, and use Temporary files and Storage Sense to clear the update cache, the Recycle Bin and old download folders. Do not delete anything inside the Windows folder by hand.

3. Install pending updates and restart once

Open Settings, then Windows Update, install anything that is waiting, and restart. This matters because the enablement package depends on the cumulative update that carries the dormant features. If a previous update is half-installed, the new one can stall at a percentage and sit there. A clean restart before the upgrade removes that variable.

4. Plug in, disconnect extras, and pause the antivirus drama

Keep a laptop plugged in. Unplug USB drives, docking stations and printers you do not need for the next hour. Leave your normal Microsoft Defender or business antivirus on; do not uninstall it for the upgrade. Some third-party "optimizer" and driver-updater tools do interfere, so if you have one, close it fully for the duration.

Method 1: upgrade through Windows Update (works for most people)

Open Settings, choose Windows Update, select Check for updates, and when the Windows 11 25H2 or 26H2 feature update appears, choose Download and install and restart when prompted. This is the supported path and the one Microsoft recommends, because it respects compatibility checks and driver readiness for your specific hardware.

1. Open Settings (Windows key + I) and select Windows Update.
2. Select Check for updates. Wait for the scan to finish.
3. If you see "Windows 11, version 25H2" or "version 26H2" with a Download and install button, select it. If you see a toggle labelled "Get the latest updates as soon as they are available", turning it on can bring the newest release into view sooner.
4. Let the download finish. This is usually quick, because the files are small compared with a full operating system image.
5. Select Restart now when it is ready, or schedule the restart for a time that suits you. The screen shows "Working on updates" with a percentage during the restart. Do not turn the PC off.
6. After you sign in, run winver again to confirm the new version.

Press coverage of Microsoft's announcement reports that unmanaged PCs still on 24H2 will be moved to 25H2 automatically as end of support approaches, with the user keeping the choice of when to restart or to delay. Do not rely on that for planning. Automatic rollouts arrive in waves, and your computer may be in the last wave. Starting the upgrade yourself, with a backup behind you, is calmer than discovering a restart prompt on the morning of an important call.

Method 2: when Windows Update does not offer the upgrade

If Windows Update says "You're up to date" but winver still shows 24H2, the most likely causes are a staged rollout that has not reached your PC yet, a compatibility safeguard hold, a paused update setting, or a managed policy that pins your version. Work through the causes in this order, because the first three take a minute each.

Check 1: is updating paused?

In Settings, Windows Update, look at the top for a "Updates paused" banner and select Resume updates. People pause updates before a trip or a deadline and forget about it for months.

Check 2: is the PC managed by an organization?

Open Settings, Accounts, Access work or school. If a work or school account is connected, your administrator may control feature updates. In that case, do not fight the policy. Ask your IT contact to approve the target release. If you are the administrator, skip ahead to the managed-device section.

Check 3: is there a safeguard hold?

Microsoft can block a feature update on specific hardware or driver combinations until the problem is fixed. This protects you from a known crash. The block usually appears as a message in Windows Update that says the update is on its way and is not ready for your device. The correct action is to wait, update your drivers from the manufacturer's site (graphics, storage, Wi-Fi and chipset in that order), and check again in a few days. Forcing the upgrade around a hold is how people end up with blue screens.

Check 4: run the Windows Update troubleshooter and repair system files

Open Settings, System, Troubleshoot, Other troubleshooters, and run Windows Update. Then open Windows Terminal as administrator and run these two commands, one after the other, waiting for each to finish:

sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth

The first command checks protected system files, and the second repairs the component store that Windows Update draws from. Restart and check for updates again. If you see an error code such as 0x80073712, our page on error 0x80073712 walks through that specific corruption, and the broader Windows Update stuck or failing guide covers resets of the update components.

Method 3: the Installation Assistant or an in-place upgrade from the ISO

If Windows Update stays silent after the checks above, Microsoft's Windows 11 Installation Assistant or an in-place upgrade using the official ISO will install the newer release while keeping your files, apps and settings. Both tools come from Microsoft's Windows 11 download page. Never download "Windows 11 installers" from other sites, because fake download pages are a classic way to distribute malware to people in a hurry.

Option A: Installation Assistant

1. Go to Microsoft's official Windows 11 download page and choose Windows 11 Installation Assistant.
2. Run the downloaded program as administrator and accept the license terms.
3. Let it check your PC, download the files and prepare the update.
4. Restart when it asks. Keep the PC plugged in and leave it alone until you reach the sign-in screen.

Option B: in-place upgrade from the ISO

1. From the same Microsoft page, download the Windows 11 disk image (ISO) for your language.
2. Right-click the ISO file in File Explorer and choose Mount. A new virtual drive appears.
3. Open the virtual drive and run setup.exe.
4. Choose Change how Setup downloads updates and, if you want the safest path, select "Not right now" so the upgrade does not depend on a flaky connection. Then continue.
5. On the "Ready to install" screen, confirm it says Keep personal files and apps. If it does not, choose "Change what to keep" and select that option.
6. Install, wait for the restarts, and verify with winver.

An in-place upgrade from the ISO is also the standard repair technique when the update component is damaged beyond a simple fix. It reinstalls the operating system files over the existing ones and leaves your documents and programs in place.

Managed PCs: how to pin a target release for a small office

Administrators can control which Windows 11 release a PC moves to with the "Select the target Feature Update version" Group Policy, the Intune feature update profile, or the equivalent registry values, and pin the fleet to 25H2 or 26H2 so that nothing surprises users. For an office of a handful of computers without a domain, the registry method is the simplest and works on Pro editions.

The policy sits at Computer Configuration, Administrative Templates, Windows Components, Windows Update, Manage updates offered from Windows Update, then Select the target Feature Update version (older policy templates list it under Windows Update for Business). Set it to Enabled, enter "Windows 11" as the product version, and set the target to the release you tested, for example 25H2 or 26H2. The underlying registry values live under HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate:

TargetReleaseVersion        (DWORD)  1
TargetReleaseVersionInfo    (String) 25H2
ProductVersion              (String) Windows 11

Replace 25H2 with 26H2 when you have tested that release. With these set, the PC stays on the chosen version and will move to it, and only to it, when you allow feature updates. In Intune, the equivalent is a Feature updates for Windows 10 and later policy where you choose the Windows 11 version and a rollout schedule, which also lets you stagger groups of devices.

A sound rollout for a small business follows four steps. Pick one low-risk PC as the pilot. Run the upgrade and test your line-of-business software, printers, scanners and VPN for a full working day. Roll to a small group, then to the rest, leaving the owner's or the accountant's PC for the last wave. Document the date and result of each machine, which is also useful evidence if a customer or insurer asks about your patching discipline.

25H2 or 26H2: which one should you install?

If Windows Update offers you 26H2 and you are comfortable being among the first people on a brand-new release, take it, because it restarts your support clock until October 2028. If you prefer to wait for a few weeks of real-world feedback, 25H2 is a perfectly safe stop that also takes you past the October 13 deadline. Both are delivered as enablement packages on top of the same platform as 24H2, so the difference between them for everyday use is small.

A note on the 25H2 support horizon: Microsoft's lifecycle page for Windows 11 Home and Pro lists 25H2 (available since September 30, 2025) ending at 6:59 AM UTC on October 13, 2027, which is the evening of October 12 in Pacific time. That is the date to use if an audit asks.

The September 2026 cumulative update caused trouble for some users, and Microsoft shipped follow-up fixes. That is not a reason to stay on 24H2, because the problems came from the monthly update and not from the enablement package itself. It is a reason to take the backup step seriously and to avoid starting the upgrade at the last minute on a day when you cannot afford a hiccup.

When the upgrade fails: error codes and what each one means

Most failed feature updates trace back to one of five causes: a full or tiny system partition, a corrupted component store, an outdated or incompatible driver, security software that interferes, or a policy that blocks the update. The error code on the failure screen or in Windows Update history tells you which one to chase first.

The reset-Windows-Update routine

If errors repeat, resetting the update components clears most stale state. In an administrator Command Prompt, run these commands in order:

net stop wuauserv
net stop bits
net stop cryptsvc
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old
net start cryptsvc
net start bits
net start wuauserv

Restart the PC and check for updates again. Windows rebuilds the folders you renamed. If this works, you can delete the .old folders later to reclaim space. If it does not work, run the DISM and sfc commands from earlier and try the ISO in-place upgrade, which bypasses the Windows Update client entirely.

After the upgrade: a five-minute health check

After the restart, confirm the version with winver, run Windows Update once more, open the three or four programs you rely on, print a test page, and check that your VPN and cloud sync clients are signed in. Issues after a feature update are rare, but they are easiest to fix on the first day, while you still remember what changed.

• Version: winver should show 25H2 or 26H2.
• Updates: Check for updates again. A second small cumulative update often follows the enablement package.
• Drivers: Look in Device Manager for yellow warning icons, especially under Display adapters, Network adapters and Sound.
• Apps and printers: Open your accounting software, browser, email client and print a page.
• Security: Open Windows Security and confirm real-time protection is on and that no third-party product shows as expired.
• Performance: If the PC feels slower for the first day, that is usually background indexing and app updates finishing. If it stays slow, our guide on how to speed up Windows 11 covers the real causes.

Can you roll back?

For a short period after a feature update, Windows keeps the information needed to go back. Open Settings, System, Recovery, and look for Go back under Recovery options. This window is limited, and clearing temporary files with Disk Cleanup or Storage Sense can remove it. If you plan to roll back, do it within the first days and before you run any cleanup tool. For an enablement package the practical value of rollback is smaller than for a full reinstall, because there is little to undo, but it exists as an escape hatch.

What is the real risk of staying on 24H2 after October 13?

The risk is gradual and cumulative: from the first Patch Tuesday after the cutoff, newly discovered Windows vulnerabilities will be fixed for supported releases but not for your 24H2 install, and attackers routinely study each month's fixes to build exploits against unpatched machines. The danger does not arrive on October 14. It grows each month the PC stays behind, and it grows fastest for computers that browse the web, open email attachments, or connect to office networks and remote desktop services.

There are also softer costs. Microsoft Defender and the browser keep receiving their own updates through separate channels, which helps, but the operating system underneath is what malware ultimately targets. Cyber insurance questionnaires commonly ask whether all endpoints run supported operating systems, and a "no" can complicate a renewal or a claim. Accountants, lawyers, clinics and anyone handling personal information in Quebec should also remember that Law 25 expects reasonable security measures; running an unsupported OS on a computer that holds client data is difficult to defend after an incident.

Third-party vendors move on as well. Software makers test against supported Windows releases, and support desks will tell you to update first. A printer driver bug on an unsupported build is your problem, not theirs.

Three realistic scenarios

These are illustrative examples based on common situations we see, not specific clients.

What it costs: doing it yourself versus getting help

For one healthy PC, the upgrade is free and takes under an hour. Paid help makes sense when the update fails repeatedly, when the PC holds business data, or when you manage several machines and want a tested, documented rollout. The table compares realistic Canadian costs.

Hardware replacement is a separate question. A PC that runs 24H2 can almost always run 25H2 and 26H2, because they share the same system requirements, so this deadline is not a reason to buy a new computer. If your machine is very slow, has a failing drive, or is more than seven or eight years old, upgrading the operating system will not fix that, and our guide on SSD versus HDD upgrades and repair costs helps you decide between a drive swap and a new PC.

Five myths about the October 13 deadline

The most common wrong beliefs are that the PC stops working, that you must buy new hardware, that the upgrade deletes your files, that Windows 10 is affected by the same date, and that antivirus alone makes an unpatched Windows safe. Each one is false, and each one causes people to either panic or ignore a simple task.

1. "My PC will stop working on October 13." False. It keeps running. Only security and preview updates stop for 24H2 Home and Pro.
2. "I need a new computer." False. Anything that runs 24H2 runs 25H2 and 26H2 with the same requirements.
3. "The upgrade erases my programs." False for an enablement package or a Keep files and apps in-place upgrade. A backup is still wise, as with any system change.
4. "This is the Windows 10 deadline." No. Windows 10 has its own separate lifecycle, covered in our Windows 10 end of life guide.
5. "Antivirus will protect me anyway." Partly. Antivirus reduces risk but cannot patch operating system flaws. Layers work together; they do not replace each other.

Your countdown plan: what to do between now and October 13

The simplest plan is to check versions this week, back up and upgrade a test machine by the weekend, and have every Windows 11 PC on 25H2 or 26H2 before the second Tuesday of October. Treat the cutoff as a deadline for your own calendar, because automatic rollouts do not guarantee that your device is upgraded before the date.

If you truly cannot upgrade yet: how to reduce risk in the meantime

If a critical application or a compatibility hold keeps a PC on 24H2 past the deadline, compensate by restricting what that computer does: keep the browser and Microsoft Defender fully updated, avoid using it for email and web browsing, use a standard account instead of an administrator account, and isolate it from sensitive network resources. This is a temporary containment plan with an end date, not a permanent solution.

• Use a standard user account for daily work and keep the administrator password separate.
• Keep Microsoft Defender (or your business endpoint product) on and updating.
• Keep the web browser updated; browser fixes arrive independently of the operating system.
• Do not use the PC for remote desktop exposed to the internet or as a file server.
• Put an owner and a date on the exception, for example "upgrade by November 15 after vendor update".
• Ask the software vendor for the supported-versions statement in writing, since they usually have a roadmap.

When to stop and call a professional

Call a technician if the PC fails to boot after an update, if the update keeps failing with the same error after the reset routine, if the machine holds data you cannot afford to lose and you have no backup, or if you manage more than a handful of computers and cannot afford downtime. Stopping early is cheaper than a fifth failed attempt, because repeated forced restarts can damage the file system and turn a repairable problem into a recovery job.

IT Cares has provided remote and on-site IT support in Quebec and across Canada since 2014. A remote session lets a technician connect to your PC while you watch, repair the update components, move the upgrade forward, and explain what was wrong. If a drive is failing or files have gone missing, our article on data recovery after a Windows update or reinstall shows what is and is not recoverable. For a computer that has become unusually slow after any update, try the steps in our Windows 11 25H2 update guide before assuming the hardware is at fault.

To talk to someone now, call 1 (888) 711-9428 or book a remote session. If you have a failed update and a deadline, say so on the call; we triage by urgency.

Frequently asked questions

Related guides

• Windows 11 25H2 update guide
• Windows 10 end of life: migrating to Windows 11
• Windows Update stuck or failing: how to fix it
• Fix Windows 11 update error 0x800f0922
• Fix error 0x80070005 (access denied)
• Fix error 0x80073712
• How to speed up Windows 11
• Data recovery after a Windows update or reinstall

Sources and official references

Last verified: October 1, 2026

• Windows 11 24H2 Home and Pro reach end of support on October 13 (gHacks, Sept 18, 2026)
• Microsoft releases the Windows 11 2026 Update, version 26H2, as a small enablement package (gHacks, Sept 30, 2026)
• Microsoft Lifecycle: Windows 11 Home and Pro (release table with end of servicing dates)
• Microsoft Windows release health
• Microsoft: Download Windows 11 (Installation Assistant and ISO)