Windows 11 24H2 and Office 2021 Hit End of Support October 13—Here’s Your 2026 Survival Guide

Microsoft has confirmed that over a dozen of its most widely used products will reach end of support in 2026. The single biggest date for consumers is October 13, when Windows 11 24H2 Home and Pro—the version shipping on most new PCs since late 2024—and every edition of Office 2021 stop receiving security updates, bug fixes, or technical support. The same day also marks the final cutoff for Windows Server 2012 and 2012 R2 Extended Security Updates, closing a three-year bridge for countless organizations still running those platforms.

But before that, a separate cluster of deadlines arrives on July 14, hitting SQL Server 2016, SharePoint Server 2016 and 2019, Project Server, and developer tooling. The result is what IT managers are calling a “support pile-up”: a year in which routine maintenance isn’t enough, and inaction could leave both home users and enterprise fleets exposed to unpatched vulnerabilities.

The 2026 Deadline Calendar at a Glance

Microsoft’s lifecycle policy sets fixed support windows for each product: typically five years of mainstream support plus five of extended for enterprise software, or 24 months of servicing for Windows feature updates. When a deadline passes, the product stops receiving all updates, and any available extension—such as Extended Security Updates—must be purchased and activated separately.

Below is the critical timeline for the rest of 2026. Several older products, including Dynamics CRM 2016 and Configuration Manager 2409, already lost support in January, April, and June; those require immediate remediation rather than planning.

Publisher—the desktop publishing application still beloved by churches, community groups, and small businesses—gets a special callout. It retires entirely after October 2026. There is no Publisher 2024, and the perpetual version within Office LTSC 2021 will stop receiving updates even if the program still opens. Microsoft recommends converting .pub files to Word or PDF before the deadline.

What This Means for You: Home Users vs. Business vs. Developers

The impact of these deadlines falls very differently depending on who you are.

Home and Small Office Users

If you’re running Windows 11 24H2 on a personal laptop or family PC, and you have a one-time-purchase copy of Office 2021, October 13 is a hard stop. After that date, no security patches for either the operating system or your productivity suite. Using the devices will still be possible, but every month without updates increases the risk of malware or data loss.

Fortunately, the fix for Windows is simple. Microsoft began force-installing Windows 11 25H2 on eligible Home and Pro machines earlier this year, and the process usually takes only a few minutes with one reboot. Open Settings > Windows Update and check for updates. If 25H2 hasn’t arrived yet, you can trigger it manually. The migration is free.

Office 2021 is a different story. There is no free upgrade path to Office LTSC 2024, the next perpetual release (supported until 2029). You must either purchase a new license for Office 2024 or subscribe to Microsoft 365. Microsoft 365 subscribers already receive continuous updates and can ignore this deadline entirely, but anyone who paid a one-time fee to avoid subscriptions will be paying again—much sooner than the decade of support older Office versions enjoyed.

IT Administrators and Business Owners

For businesses, the July and October deadlines create a cascading set of projects that can’t all be tackled at once. SQL Server 2016’s July 14 cutoff is the most urgent: countless ERP systems, reporting tools, and line-of-business applications depend on it. Microsoft offers Extended Security Updates for up to three years, but Year 1 pricing starts the next day, and ESUs only cover critical vulnerabilities—not feature bugs or performance fixes. Migrating to SQL Server 2019, 2022, or Azure SQL takes time and testing; if you haven’t started, ESU enrollment may be your only bridge.

SharePoint Server 2016 and 2019 farms, Project Server, and aging Exchange or Skype for Business installations all demand work across the same window. The July date means discovery must happen now: which servers exist, what they run, who owns them. October’s broader deadline then applies to Windows Server 2012, Office 2021 perpetual licenses, and Windows 11 24H2 workstations that are still on the older feature release.

Windows Server 2012 and 2012 R2 lose their final ESU coverage on October 13. Many of these machines are domain controllers, file servers, or legacy application hosts that have evaded upgrade cycles for a decade. Moving to Windows Server 2025 or Azure is the recommended path, but the discovery and testing timeline makes July the effective start of this project—not October.

Developers and DevOps Teams

November 10 bundles the end of support for .NET 8 (LTS), .NET 9 (STS), and PowerShell 7.4 (LTS) with the enterprise Windows 11 23H2 deadline. If your build servers, containers, or production applications run on these runtimes, they must be updated. The good news: .NET 10 and PowerShell 7.6 are already available as supported replacements. The catch: runtime upgrades, even from an LTS release, aren’t drop-in. Automated pipeline testing and staging environments are non-negotiable.

Also watch Visual Studio 2022 LTSC users: version 17.12 support ends July 14. If your team pinned to that channel for stability, you need to move to a current LTSC release or switch to the mainstream servicing channel.

Why This Year Is Different

Microsoft’s support clock is always ticking, but 2026 stands out for two reasons. First, the sheer volume of expirations—including the most popular consumer Windows version since Windows 10—means a much larger population must take action than in a typical year. Second, the confluence of Windows servicing, Office permanent licenses, and on-premises server retirements forces organizations to manage licensing, migration, and security simultaneously.

Windows 10’s 2025 end of support was a landmark because of the user base; 2026 feels like a hangover for the enterprise, with years of postponed upgrades now coming due all at once. The five-year lifecycle for Office 2021, half the 10-year support that Office 2016 enjoyed, has also caught small businesses and individuals off guard.

Your Next Steps: A Practical Checklist

The actions you need to take depend on which deadlines apply to you. Here is a prioritized guide.

For home users:
- Press Win + R, type winver, and confirm your Windows version. If it says “Version 24H2” and you’re on Home or Pro, run Windows Update immediately to get 25H2.
- Open any Office app (Word, Excel, Outlook) and go to File > Account. If the product name says “Office 2021” or “Office LTSC 2021,” plan to either purchase Office 2024 or subscribe to Microsoft 365 before October 13.
- If you have .pub files from Publisher, convert them to PDF or another format now; after October, the safe editing window closes permanently.

For IT administrators:
- Before July 14: inventory every SQL Server 2016 instance. Run SELECT @@VERSION and SERVERPROPERTY queries to confirm version and edition. For farms, open SharePoint Central Administration and check the build version against Microsoft’s documentation. Enroll in ESU for SQL Server if migration won’t finish in time.
- During July: document all Windows Server 2012 and 2012 R2 machines, Exchange servers, and Skype for Business deployments. Use Get-ComputerInfo and Get-ExchangeServer cmdlets. Identify owners and business criticality.
- August–September: test Windows 11 feature updates for any remaining 24H2 endpoints (Home/Pro) and begin piloting Office 2024 deployments or Microsoft 365 subscriptions. Migrate SharePoint farms to Subscription Edition or plan a shift to SharePoint Online.
- Before October 13: finish Windows Server 2012 migrations, deploy Office upgrades, and ensure all user devices are on Windows 11 25H2 or later. Preserve critical Publisher files.
- Before November 10: update enterprise Windows 11 23H2 devices and validate all applications against .NET 10 and PowerShell 7.6 in staging environments.

For developers:
- Run dotnet --list-runtimes and dotnet --list-sdks on all hosts. Update .NET 8 and 9 apps to .NET 10 after testing.
- Check $PSVersionTable for PowerShell 7.4. Upgrade automation scripts, modules, and remoting endpoints.
- If using Visual Studio 2022 LTSC 17.12, update to a supported LTSC channel before July 14.

Beyond 2026

Microsoft’s lifecycle calendar never stops. Windows 11 26H2 and .NET 11 will eventually have their own deadlines, and the shift to subscription-based models (Microsoft 365, Azure SQL, SharePoint Online) means fewer “set it and forget it” perpetual licenses. The lesson of 2026 is that proactive inventory and ownership of every software asset—not just servers, but desktops, runtimes, and tools—is the only way to avoid panic when the next October arrives.

For now, mark July 14 and October 13 on your calendar in ink, not pencil. The work doesn’t start on those dates. It ends.