Windows 11 version 24H2 has a fixed expiration date. For Home and Pro editions, Microsoft will stop shipping security updates in October 2026. That is not a guess or a rumour - it is the published servicing lifecycle for annual feature releases. If you are running 24H2 on an older laptop, especially one that needed a TPM bypass or sits on the edge of the CPU compatibility list, you have roughly six months to decide what comes next.
I have walked through this kind of deadline with hundreds of machines across refurbishment workshops, small offices, and home setups. The pattern is always the same: the people who plan ahead have a smooth transition, and the people who wait until the last week end up panicking. This guide gives you a structured timeline and clear decision points so you can make the move on your terms, not Microsoft's. For related context on the 24H2 hardware requirements that may affect your upgrade path, see our 24H2 compatibility check guide. Visit our Guides hub for more practical hardware and software guidance.
The Support Timeline You Need to Know
Microsoft releases one major feature update per year for Windows 11. Each Home and Pro release receives exactly 24 months of security updates. Enterprise and Education editions get 36 months. For 24H2, the maths works out as follows.
24H2 Home/Pro: released October 2024, end of support October 2026. 24H2 Enterprise/Education: released October 2024, end of support October 2027. After the support date, no more security patches arrive through Windows Update. The machine keeps running, but every newly discovered vulnerability stays unpatched permanently.
The successor, 25H2, is expected in the second half of 2025. If your hardware accepts it, the upgrade extends your support window by another 24 months. If your hardware does not - because of TPM enforcement, CPU generation blocks, or the SSE4.2 requirement Microsoft introduced in 24H2 - then October 2026 is your hard deadline for running a supported Windows installation.
There is no announced ESU programme for Windows 11 versions. Unlike Windows 10 ESU, which gives consumers a $30-per-year lifeline, Microsoft expects Windows 11 users to simply move to the next release. If your hardware cannot, you fall off the supported map with no paid safety net.
What Actually Stops Working After End of Support
End of support does not mean your laptop stops booting. It means a specific set of protections disappear, and other consequences cascade over weeks and months.
Security patches stop completely
The monthly cumulative updates that patch kernel vulnerabilities, networking stack flaws, and privilege escalation bugs will no longer arrive. Known exploits that are disclosed after the cutoff date will never be fixed on your installation. This is the primary risk - and it compounds every month.
Microsoft Defender definitions continue (for now)
Antivirus signature updates for Defender typically continue beyond the OS end-of-support date, but Microsoft does not guarantee a specific duration. Historically, Defender definitions have continued for 12-24 months after OS support ends, but this is discretionary. Third-party antivirus products set their own timelines independently.
Third-party software starts dropping support
Application developers watch Microsoft's support calendar. When a Windows version goes out of support, browsers, productivity suites, and communication tools begin removing it from their testing matrices. You may not notice immediately, but within 6-12 months certain applications will stop installing or updating on an unsupported build.
Driver updates dry up
Hardware vendors stop testing and certifying new driver releases for unsupported OS versions. On older laptops this matters less since the hardware itself is stable, but if you connect newer peripherals or need updated GPU drivers for a specific application, you may hit dead ends.
Checking Whether Your Laptop Can Run 25H2
The first and most important question is whether your hardware will accept the next feature release. If 25H2 works, your October 2026 problem evaporates - you simply upgrade and gain another two years of patches. Here is how to check.
Run the PC Health Check app
Download Microsoft's PC Health Check tool from their official site. Run it and look at the compatibility summary. If it reports your machine as compatible with Windows 11, the 25H2 upgrade should work. If it flags TPM, CPU, or Secure Boot issues, you have a problem.
Verify your CPU generation
Open Settings > System > About and note the processor model. Microsoft officially supports Intel 8th generation (Coffee Lake) and later, plus AMD Ryzen 2000 series and later. If you are running a 7th-gen Intel or first-gen Ryzen via a bypass, 25H2 may tighten enforcement. The SSE4.2 and POPCNT check is also still relevant - any CPU that lacks these instructions is excluded from 24H2 onward.
Check TPM and Secure Boot status
Press Win+R, type tpm.msc, and confirm you have TPM 2.0. For Secure Boot, open System Information (msinfo32) and look for "Secure Boot State: On". If either is missing and you bypassed it for your current installation, the same bypass may or may not work for 25H2. Do not assume it will.
Test with a USB installation
The safest approach is to create a 25H2 installation USB using the Media Creation Tool and boot from it on your laptop. You do not need to install - just confirm the installer launches and passes the compatibility check. If it does, you know the upgrade path is viable. For USB boot issues on older hardware, see our USB boot troubleshooting guide.
Backup and Migration Strategies
Regardless of which path you choose - upgrade, switch, or stay - backups are non-negotiable. A failed upgrade on older hardware is not hypothetical; it happens regularly. Here is a practical backup and migration framework.
Full disk image: Use a free tool like Clonezilla or Macrium Reflect to create a full disk image on an external drive. This captures everything - the OS, applications, settings, and files. If an upgrade fails or a Linux installation goes wrong, you can restore the exact state you started from. Test the restore process once on any machine to verify the image is valid. An untested backup is not a backup.
File-level backup: Separately copy your Documents, Desktop, Downloads, and any application-specific data folders to an external drive or cloud storage. This is your insurance against image corruption - even if the disk image fails, your files are safe.
Application inventory: List every application you use daily, including licence keys or login credentials. Check whether each application runs on Linux or has a web-based alternative. This list becomes critical if you end up switching operating systems. Missing a single application dependency mid-migration is the number one reason people give up and roll back.
Driver export (Windows-specific): If you plan to attempt a clean Windows installation rather than an upgrade, export your current drivers using DISM /Online /Export-Driver /Destination:D:\DriverBackup. Older laptops sometimes rely on drivers that are no longer available from the manufacturer's website. Having a local copy prevents post-installation headaches, particularly for Wi-Fi and network drivers.
Your Three Decision Paths
After checking compatibility and creating backups, you face a three-way choice. Each path has clear trade-offs.
Upgrade to 25H2 (if hardware allows)
This is the simplest path. If your laptop passes the compatibility check, upgrade through Windows Update when 25H2 is available. You get another 24 months of security patches with minimal disruption. The upgrade preserves your applications, files, and settings. Budget 1-2 hours for the process and ensure the laptop is plugged in with a stable internet connection.
Switch to Linux
If your hardware cannot run 25H2 - or if you want to step off the Microsoft upgrade treadmill - a lightweight Linux distribution is the strongest alternative. Distributions like Linux Mint, Zorin OS, and Xubuntu provide a familiar desktop, run well on older hardware, and receive security updates for 3-5 years. The transition takes a few hours and the learning curve is smaller than most people expect. Our lightweight Linux comparison covers the best options for aging hardware, and our ChromeOS Flex vs Linux guide helps if you are choosing between those two paths.
Stay on 24H2 without patches
This is technically an option but carries increasing risk. If you choose this path, apply every hardening measure available: use a standard (non-admin) account for daily work, keep your browser updated as long as it supports your OS version, run a reputable antivirus, enable the firewall, and restrict what software you install. Our Windows 10 security checklist covers most of these hardening steps - the principles apply equally to an unsupported Windows 11 installation. Understand that this is a risk management decision, not a safe option.
A Practical Six-Month Countdown
Here is a month-by-month framework for working through the decision. Adjust the specific dates to match your circumstances, but do not skip the sequence.
April-May 2026: Run the compatibility checks described above. Create your full disk image and file backup. Start the application inventory. This is information-gathering - no commitments yet.
June 2026: If your hardware passes the 25H2 check, wait for the official release and monitor early adoption reports. If it does not pass, download a Linux live USB and spend a weekend testing your workflow. Does your browser work? Can you access your documents? Does Wi-Fi connect automatically? These are the make-or-break questions.
July-August 2026: Make your decision and execute. If upgrading to 25H2, do it now while you have two months of buffer before the deadline. If switching to Linux, install it alongside Windows in a dual-boot configuration first, then migrate fully once you are comfortable. If staying on 24H2, implement every hardening measure now.
September 2026: Final check. Is your chosen path working? Are there any loose ends? Verify your backup is current. If you dual-booted Linux and are ready to commit, reclaim the Windows partition.
October 2026: Support ends. If you have followed the plan, you are already on a supported OS or fully aware of the risks you are accepting. No surprises, no panic.
The Hardware Question: Is the Laptop Worth the Effort?
Before investing hours in migration planning, honestly assess whether the laptop deserves the effort. A machine with 4 GB of RAM, an SSD, and a dual-core processor from 2015 or later is still perfectly viable for web browsing, document work, and media consumption - especially on Linux. A machine with 2 GB of RAM, a spinning hard drive, and a single-core Atom is not worth the time regardless of which OS you install.
If the laptop sits in the middle - decent CPU but slow storage - an SSD upgrade can transform it enough to justify continued use. This is often the single highest-impact upgrade for the cost. If you are going to switch to Linux or attempt 25H2, do the SSD swap first. The migration itself will go faster, and the resulting system will feel dramatically better. See our lab notes on when an SSD actually helps for a realistic assessment.
Frequently Asked Questions
The Bottom Line
October 2026 is a fixed date, not a negotiable one. When it arrives, your Windows 11 24H2 installation stops receiving security patches, and unlike Windows 10 there is no paid extension programme to fall back on. The machines that navigate this well will be the ones whose owners spent the next six months testing 25H2 compatibility, evaluating Linux, or making a clear-eyed decision to accept the risks of running unpatched.
The practical framework is straightforward: check your hardware, back everything up, test your chosen path in May or June, execute in July or August, and verify in September. If you treat this as a weekend project spread across a few months rather than a crisis in late October, the transition is manageable regardless of which direction you go.
For most older laptops running 24H2 through bypass methods, a lightweight Linux distribution is the most sustainable long-term answer. It is free, it is secure, and it runs well on the exact hardware you already own. But that is a decision you should make after testing, not before - which is exactly why starting now matters.