top of page

Windows Server 2022 End of Support: Everything IT Admins Need to Know Before October 2026

  • May 26
  • 5 min read

Windows Server 2022 mainstream support ends on October 13, 2026. After this date, Microsoft will no longer release new features, non-security hotfixes, or provide free technical support. Extended support (security patches only) continues until October 14, 2031. IT admins should begin planning their migration or upgrade path now.


Windows Server 2022 End of Support: Everything IT Admins Need to Know Before October 2026

What "End of Support" Actually Means for Windows Server 2022?


Microsoft follows a Fixed Lifecycle Policy for its server operating systems. This policy defines two distinct support phases that every IT admin needs to understand:


Mainstream Support covers the full support experience: security updates, non-security hotfixes, feature updates, warranty claims, and design change requests. This is the "full support" phase.


Extended Support is the reduced-support phase that follows the mainstream phase. During this period, Microsoft continues providing critical security updates at no additional cost, but stops releasing new features, non-security updates, or free technical support.


For Windows Server 2022, that transition happens on October 13, 2026. The product then enters Extended Support until October 14, 2031, at which point it reaches true End of Life (EoL) with no further updates of any kind.


This distinction matters enormously for IT admins. Many organizations confuse the mainstream support cutoff with full end of life, and either panic unnecessarily or, more dangerously, assume they have until 2031 to act without understanding the risks of running on extended-only support.


Key Dates at a Glance

Milestone

Date

Windows Server 2022 General Availability

August 18, 2021

End of Mainstream Support

October 13, 2026

End of Extended Support (End of Life)

October 14, 2031

Microsoft 365 Apps support on WS2022 ends

October 10, 2028


What Changes After October 13, 2026?


Once mainstream support ends, the following changes take effect immediately for organizations running Windows Server 2022:


What stops:

  • New feature releases and functionality improvements.

  • Non-security hotfixes and bug fixes.

  • Free technical support for incidents with Microsoft.

  • Design change requests (DCRs).

  • Warranty claims.


What continues (during Extended Support until 2031):

  • Critical security updates and patches, at no additional cost

  • Security advisories and bulletins


What this means practically: If your organization discovers a non-security performance bug or compatibility issue after October 13, 2026, Microsoft will not release a fix. You also lose access to complimentary support from Microsoft's technical teams, meaning paid support contracts become your only recourse for assistance.


For Microsoft 365 Apps users: Microsoft will continue providing security updates for M365 desktop apps running on Windows Server 2022 until October 10, 2028, giving those environments a slightly longer migration runway.


What Are Your Options?


IT admins running Windows Server 2022 have several paths forward. The right choice depends on your infrastructure complexity, budget, compliance requirements, and long-term cloud strategy.


Option 1: In-Place Upgrade to Windows Server 2025


The fastest and least disruptive path for most organizations. Microsoft now supports in-place upgrades from Windows Server 2022 directly to Windows Server 2025, even via Windows Update. This keeps your existing hardware, roles, features, and installed applications intact, requiring only a reboot.


Best for: Organizations that want to stay on-premises, minimize downtime, and preserve existing configurations.


Important caveat: In-place upgrades are not recommended for Domain Controllers. Active Directory DCs require a separate promotion/demotion process.


Option 2: Clean Install of Windows Server 2025


A fresh installation on new or existing hardware. This approach gives you a clean baseline but requires reinstalling applications, roles, and migrating data.


Best for: Organizations refreshing aging hardware, consolidating server roles, or wanting to eliminate configuration drift from years of accumulated changes.


Option 3: Migrate to Azure (and receive free ESUs)


For organizations moving toward hybrid or cloud-native infrastructure, migrating workloads to Azure Virtual Machines is a compelling option. Microsoft offers free Extended Security Updates for Windows Server workloads hosted on Azure, meaning you can effectively extend your support runway at no additional licensing cost while planning a full modernization.


Best for: Organizations with active cloud migration initiatives, or those not ready to upgrade on-premises infrastructure immediately.


Option 4: Purchase Extended Security Updates (ESU) via Volume Licensing


For organizations that cannot migrate before October 2026, Microsoft offers paid Extended Security Updates through volume licensing agreements (EA, EAS, SCE, MPSA, and CSP). This buys additional time but is not a long-term solution.


Best for: Organizations with complex dependencies or regulatory freezes that prevent near-term migration.


Option 5: Do Nothing (Not Recommended)


Operating without updates after extended support expires in 2031 creates severe security exposure. Even during the extended support window (2026–2031), running without mainstream support means unpatched bugs and no access to Microsoft technical support. This is rarely a viable strategy for regulated industries.


Migration Checklist for IT Admins


Use this checklist to prepare your organization for the October 13, 2026 mainstream support transition:


Inventory and Assessment (Do Now)

  • Audit all servers running Windows Server 2022 across your environment.

  • Identify workloads, roles, and applications on each server.

  • Flag any dependencies on deprecated features (PowerShell 2.0, NTLM, VBScript).

  • Check Software Assurance status for upgrade rights to Server 2025.


Planning (3–6 Months Out)

  • Define migration path for each server (in-place upgrade, clean install, or cloud migration).

  • Identify Domain Controllers requiring the promotion/demotion upgrade process.

  • Establish maintenance windows for production server upgrades.

  • Verify hardware compatibility with Windows Server 2025.

  • Procure Windows Server 2025 licenses where Software Assurance doesn't cover the upgrade.

  • Validate KMS configuration for post-upgrade activation.


Pre-Migration (4–6 Weeks Out)

  • Install the latest cumulative updates on source servers (minimum KB5078766 for WS Update path).

  • Take full backups or snapshots of each server before the upgrade.

  • Test restore procedures. Don't just create the backup, verify it.

  • Test the upgrade process in a non-production environment first.

  • Configure the AllowWindowsServerFeatureUpdate registry key if using the Windows Update path.


Post-Migration

  •  Verify all services and applications are running correctly.

  •  Activate server via appropriate method (KMS, AD-based, or MAK).

  •  Run Windows Update for remaining patches.

  •  Review Secured-core and UEFI Secure Boot settings.

  •  Remove the Windows.old directory after confirmation.

  •  Update CMDB and documentation to reflect the new OS version.

  •  Notify relevant compliance and security teams.


Summary


Windows Server 2022 mainstream support ends October 13, 2026 — less than five months away. While extended support keeps security patches flowing until 2031, the loss of bug fixes, new features, and free Microsoft support means IT admins should be planning their migration strategy now, not later.


The good news: Microsoft has made the upgrade path to Windows Server 2025 more accessible than ever, including via Windows Update for eligible servers. Most organizations running standard workloads can perform in-place upgrades with minimal disruption.

Start with an inventory, audit for deprecated feature dependencies, validate your licensing position, and build your migration schedule around maintenance windows before the October deadline. The organizations that struggle most are those that wait until September to start a process that benefits from months of planning.


Get Hands-On Ready Before the Deadline


Knowing the dates is one thing. Being confident in the upgrade is another. If you or your team need to build real, hands-on skills with Windows Server 2025 before the October transition, the Windows Server 2025 Bootcamp by Invictus Training Solutions is designed exactly for this moment.


In 5 intensive days (40 hours) of virtual, instructor-led training, you'll cover everything that matters for a successful migration: installation and automation with PowerShell, Active Directory and DNS design, storage and Hyper-V, high availability and security hardening, and hybrid cloud management with Azure Arc. Every day includes hands-on lab exercises and Day 5 closes with a full multi-role server deployment capstone you can take back to your team.


An early-bird discount of 15% applies to enrollments on or before July 10, 2026. Seats are limited.



Don't upgrade under pressure. Get trained, get confident, and migrate on your terms.

Comments


bottom of page