Windows Server 2022 Mainstream Support Ends October 13, 2026

Windows Server 2022 will leave mainstream support on October 13, 2026, giving administrators less than three months to decide whether five more years of security-only servicing is sufficient or whether key workloads should move to Windows Server 2025. Microsoft’s Lifecycle documentation lists October 14, 2031 as the end of extended support for the 2021-era server release.
The warning, highlighted this week by Windows Report and echoed by Neowin, is not an end-of-support notice. Windows Server 2022 will remain a supported operating system after October 13, and it will continue to receive security updates during extended support. But the calendar marks a meaningful change in what Microsoft will service—and in what IT teams can reasonably expect from the platform.
Microsoft’s Windows Server release information page currently identifies Windows Server 2025 as the latest Long-Term Servicing Channel, or LTSC, release. For organizations standardizing on the conventional five years of mainstream support followed by five years of extended support, the 2022-to-2025 transition is now the upgrade decision that needs to enter formal change planning.

Security coverage continues, but the platform stops moving​

The distinction between mainstream and extended support matters because Windows Server 2022 does not suddenly become unsafe or unpatched on October 14. Under Microsoft’s Fixed Lifecycle Policy, extended support continues to include security updates at no additional charge. The separate, paid Extended Security Updates program is a post-extended-support measure used for much older products; it is not required for Windows Server 2022 in 2026.
What organizations lose after the October 13 cutoff is the broader servicing relationship. Microsoft will no longer take feature requests, deliver design changes, or generally provide non-security updates. Paid support can remain available, but that does not restore mainstream-level servicing or turn enhancement requests into patches.
That changes the operating model for infrastructure teams. A Windows Server 2022 file server, domain controller, print server, Hyper-V host, application server, or cluster node can continue operating through October 2031 with monthly security servicing. A business that depends on future platform capabilities, deeper vendor certification windows, hardware refreshes, or newer hybrid-management features should not interpret those security updates as a reason to postpone upgrade planning indefinitely.
Microsoft also notes one specific feature boundary: Hotpatch support for Windows Server 2022 Datacenter: Azure Edition Core runs only through the end of mainstream support. Organizations using that edition to reduce reboot-driven maintenance windows should account for the October deadline separately from the broader security-update timeline.

---

Windows Server 2025 becomes the forward-looking option​

Windows Server 2025 reached general availability on November 1, 2024, and Microsoft lists its mainstream support end date as November 13, 2029, with extended support running until November 14, 2034. That makes it the obvious successor for organizations that want to reset the lifecycle clock, though it does not turn every Server 2022 estate into an automatic in-place upgrade candidate.
Microsoft documents direct in-place upgrade support to Windows Server 2025 from Windows Server 2012 R2 and later, up to four versions at a time. That reduces the number of technical hops for many environments, but a supported upgrade path is not the same as a low-risk production change. Domain controllers, failover clusters, Hyper-V hosts, line-of-business application servers, and systems with endpoint security or backup agents all deserve validation in representative test environments.
Windows Server 2025 also has a different operational proposition from Server 2022. Microsoft is emphasizing security, performance, storage, and hybrid-cloud capabilities, while its newer release documentation presents the LTSC alongside the more frequently updated Annual Channel. For conventional infrastructure roles, LTSC remains the familiar choice: stable, long-lived, and designed for workloads that should not be constantly reshaped around a rapid release schedule.
The practical question is therefore not simply, “Can Server 2022 stay?” It can. The better question is whether a system’s business lifespan, vendor roadmap, and refresh schedule fit inside its remaining mainstream-support runway.
For many organizations, the sensible answer will be mixed:

• Stable, isolated workloads with well-understood dependencies may remain on Windows Server 2022 and receive security servicing through October 2031.
• Systems scheduled for hardware replacement, application modernization, or major virtualization changes are stronger candidates for Windows Server 2025.
• Workloads dependent on third-party agents, legacy drivers, or tightly controlled application stacks should be tested before an in-place upgrade is approved.
• Servers approaching retirement should not be upgraded merely to meet a lifecycle target if decommissioning or migration eliminates the workload sooner.

That portfolio approach is more realistic than treating “upgrade all servers” as a single project. A Server 2022 deployment can cover everything from branch-office file services to heavily customized application servers, and those systems rarely have matching maintenance windows or risk profiles.

The client-side deadline is similar—but not the same problem​

October 13, 2026 is also the end-of-updates date for Windows 11 version 24H2 Home and Pro editions. Microsoft’s Windows 11 release-health documentation says devices on those editions will no longer receive monthly security and preview updates, fixes for known issues, time-zone updates, or technical support after that date.
That deadline should not be folded into the Windows Server 2022 plan without careful inventory work. Windows 11 uses a different servicing model, and edition matters. The October 2026 date applies to Home and Pro, including Pro Education and Pro for Workstations; Enterprise and Education have their own lifecycle timetable.
Microsoft says unmanaged Windows 11 24H2 Home and Pro devices will be offered Windows 11 version 25H2 automatically. IT-managed endpoints should be governed through the organization’s established Windows Update for Business, Windows Server Update Services, Intune, or endpoint-management processes rather than relying on consumer-oriented upgrade behavior.
There is also an important current-state wrinkle: Microsoft’s lifecycle listings now show Windows 11 version 26H1 as an available Home and Pro release, alongside version 25H2. That makes an internal endpoint roadmap more important than simply setting “25H2” as a blanket destination. Administrators should select the release appropriate to their hardware, policies, application readiness, and deployment rings.

---

Inventory work now matters more than the deadline itself​

The approaching mainstream-support boundary is a reminder that lifecycle management starts with an accurate asset record. Organizations should identify not only every Windows Server 2022 installation, but also its edition, role, virtualization status, attached management agents, backup and disaster-recovery dependencies, and software-vendor support commitments.
The first review should separate systems where extended support is a deliberate strategy from systems that are simply unmanaged. Those are not equivalent. Retaining Server 2022 through 2031 can be a defensible decision for a stable workload, but only if the organization understands what it is giving up and has a plan for the next five-year boundary.
A useful upgrade test should include the less glamorous dependencies that often derail server projects: monitoring agents, EDR tooling, backup and restore workflows, certificate services, storage multipathing, printer drivers, bespoke scheduled tasks, and management scripts. It should also confirm that rollback and recovery procedures work before production systems are touched.
Microsoft’s reminder does not require a rushed migration in July 2026. It does establish the point at which Windows Server 2022 becomes a security-maintained platform rather than one still receiving the full breadth of mainstream product servicing. By October 13, administrators should know which servers are intentionally staying, which are moving to Windows Server 2025, and which workloads should disappear before the next lifecycle deadline becomes the urgent one.

---

References​

1. Primary source: Windows Report
   Published: 2026-07-17T05:02:26+00:00
   
   

   Microsoft Warns Windows Server 2022 Mainstream Support Ends Soon

   Microsoft warns that Windows Server 2022 mainstream support ends October 13, 2026, while security updates will continue until 2031.

   windowsreport.com
2. Official source: learn.microsoft.com
   
   

   Windows Server 2025 - Microsoft Lifecycle | Microsoft Learn

   Windows Server 2025 follows the Fixed Lifecycle Policy.

   learn.microsoft.com
3. Related coverage: cisecurity.org
   
   

   CIS Microsoft Windows Server 2012 R2 Benchmark v220

   PDF document

   www.cisecurity.org

 

[ChatGPT]

Windows Server 2022 should not be treated as an emergency retirement on October 13, 2026: administrators can retain stable, well-understood workloads through October 14, 2031 because Microsoft will continue supplying security updates at no additional cost. The stronger recommendation is to upgrade to Windows Server 2025 now where a workload needs ongoing platform improvement, has a pending application or hardware refresh, or would be expensive to move under pressure later; retain Server 2022 where compatibility, uptime, and operational predictability matter more than new features.
Microsoft’s lifecycle documentation makes the dividing line unusually clear. Windows Server 2022 mainstream support ends on October 13, 2026, while Extended Support runs until October 14, 2031. That means the October date is a change in the kind of servicing administrators receive, not a date on which Server 2022 suddenly becomes unpatched.
Windows Server 2025, available since November 1, 2024, is the current Long-Term Servicing Channel release. Its mainstream support runs through November 13, 2029, with Extended Support through November 14, 2034. For teams that need a platform with years of normal feature and quality servicing ahead, that timeline is the central argument for moving earlier rather than waiting.

October 13, 2026 changes the value of Server 2022, not its security posture​

After Windows Server 2022 enters Extended Support, Microsoft will still provide security updates without an added Extended Security Updates purchase. That fact should change the tone of upgrade planning. A Server 2022 estate does not need to be moved wholesale in the next three months simply to keep receiving security patches.
What changes is the operational contract around everything other than security. Non-security updates and support become paid, and Microsoft stops accepting requests for design changes or new features. In practical terms, a defect that is inconvenient, performance-related, or tied to a changing business requirement may no longer follow the familiar path from support case to broadly available product fix.
That distinction matters most when an organization is treating a server operating system as an actively evolving foundation rather than a deliberately stable appliance. A file server with mature agents and predictable storage behavior may be an excellent Extended Support candidate. A server hosting a rapidly changing line-of-business stack, a new hardware generation, or an application being modernized every quarter is a poor fit for a platform that has entered its security-only phase.
WindowsForum readers already discussing the October 2026 transition have focused on the five remaining years of patch coverage. That is necessary context, but the more useful planning question is narrower: Would a security update alone be enough to keep this workload healthy through 2031?

---

Classify every Server 2022 workload before choosing an upgrade path​

The decision should be made workload by workload, not by operating-system inventory count. Start with an owner, business criticality, application support status, backup method, recovery objective, server role, and next expected infrastructure change. Then place the system in one of four lanes.

Workload condition	Recommended lane	Why
The system is nonclustered, its application and drivers support Windows Server 2025, and downtime can be scheduled.	In-place upgrade to Windows Server 2025.	Microsoft supports direct in-place upgrades from Windows Server 2022 to Windows Server 2025 for eligible nonclustered systems.
The server carries a critical application, older dependencies, complex integrations, or a hard rollback requirement.	Build a new Windows Server 2025 host and migrate.	A parallel migration creates a cleaner validation and reversal path than changing the existing production instance.
The workload is cloud-oriented and eligible for the organization’s Azure design and support model.	Assess an Azure-based move.	This can align the workload with a broader cloud operating model, but it is an architecture decision rather than an automatic lifecycle fix.
The role is stable, secure, backed up, and has no near-term need for platform changes.	Retain Windows Server 2022 through Extended Support.	Security updates continue through October 14, 2031, preserving a viable runway for controlled retirement or later migration.

An in-place upgrade is a deployment mechanism, not a blanket recommendation. Microsoft’s direct path does not remove the need to validate the exact workload. Suitability still depends on edition, language, architecture, drivers, and application support. A server that technically meets upgrade conditions can still be the wrong candidate if its vendor only certifies the application through a separate migration process.
Clusters deserve special caution. Microsoft’s stated direct in-place upgrade support applies to eligible nonclustered systems. Do not convert that into an assumption that clustered roles should follow the same playbook. Treat cluster modernization as its own project with a tested design, documented failover behavior, and a recovery plan that does not rely on improvisation during a maintenance window.

Make the patch plan explicit before Extended Support begins​

Extended Support preserves security servicing, but it does not eliminate the work of operating a patched server fleet. The difference is that administrators should now be more disciplined about distinguishing a monthly security response from a broader remediation expectation.
Before October 13, create a Server 2022 Extended Support patch plan with clear ownership for approval, deployment, restart coordination, and recovery. The checklist does not need new tools; it needs decisions made before the next urgent update arrives.

1. Inventory every Windows Server 2022 instance and identify its role, environment, owner, maintenance window, and patch-management method.
2. Verify that WSUS or the organization’s chosen update-management process still has a defined approval path for Server 2022 security updates, including test rings and production deadlines.
3. Record which workloads use hotpatching, where applicable, and which require conventional reboot-based servicing so that maintenance communications do not promise a reboot-free outcome where one is not available.
4. Confirm that backup jobs complete successfully and that the team can restore the server, its application data, and required configuration before approving major production patch cycles.
5. Establish rollback criteria in advance, including who can pause rollout, what telemetry or application checks trigger that decision, and how the team will communicate a failed deployment.
6. Reconfirm application-vendor support commitments for every business-critical server that is intended to remain on Server 2022 after mainstream support ends.

The hotpatch item is particularly important for Azure-focused deployments. Microsoft has extended hotpatch update support for Windows Server 2022 Datacenter: Azure Edition through October 2027, but that should be treated as a workload-specific operational advantage, not evidence that all Server 2022 installations have the same restart profile. A reduced-reboot security-servicing model can improve maintenance flexibility; it does not replace testing, monitoring, or recovery discipline.
The key change is psychological as much as technical. Under mainstream support, an organization may be accustomed to resolving operational friction through normal vendor escalation and product evolution. During Extended Support, the default assumption should be that security patching continues, while non-security correction may involve paid support or a customer-side mitigation. That makes an accurate configuration baseline more valuable.

---

Upgrade early when the surrounding workload is already changing​

Windows Server 2025 should be the default destination for a Server 2022 workload already scheduled for an application upgrade, hardware replacement, data-center move, or major redesign. Combining related change windows can reduce duplicated testing and prevent the organization from investing heavily in a Server 2022 configuration it intends to discard.
This is also where licensing and procurement must enter the conversation early. An operating-system decision can fail on an application entitlement, a vendor support boundary, or a feature dependency that was never included in the technical migration plan. Put the licensing owner, application owner, infrastructure team, and backup team in the same planning review before selecting in-place upgrade or migration.
For eligible nonclustered servers, the direct Windows Server 2022-to-2025 in-place path is attractive when the application is supported, the server is not carrying hidden legacy dependencies, and the team has a proven restoration path. It preserves the existing instance and can minimize reconfiguration, but it also carries forward prior configuration choices. A clean migration is often the better engineering choice when the existing host has accumulated exceptions, undocumented agents, or years of manual changes.
A useful rule is simple: upgrade the systems that are changing anyway, and retain the systems whose greatest virtue is that they are not changing. The latter group still requires patching, monitoring, documented recovery, and periodic support reviews. Extended Support is a managed holding pattern, not permission to forget the server exists.

Do not let backup and rollback become the late-stage surprise​

The most common planning error is to treat a successful backup job as proof of recoverability. For an in-place upgrade, teams need confidence that they can restore the operating system, application state, data, service accounts, network settings, and any configuration that the workload needs to resume service. For a migration, they need to prove data consistency and cutover reversal, not merely the existence of a new server.
Test those claims before the upgrade window, not after a failed one. Document what the business accepts as a rollback: restoring the original Server 2022 instance, returning traffic to it, or reactivating an alternate service path. The answer may differ sharply between a departmental file service and a revenue-bearing application.
Application compatibility needs the same discipline. “Runs on Windows” is not a support statement. Ask whether the application vendor supports the exact Windows Server 2025 edition, language, architecture, and deployment design in use. Ask the same question of driver suppliers, backup agents, monitoring platforms, security tooling, and any specialized hardware tied to the host.

Frequently Asked Questions​

Does Windows Server 2022 stop receiving security updates on October 13, 2026?​

No. October 13, 2026 is the end of mainstream support. Microsoft continues security updates during Extended Support, which ends on October 14, 2031.

Are non-security fixes still included after Server 2022 enters Extended Support?​

No. Microsoft states that non-security updates and support are paid during Extended Support, and it no longer accepts design-change or new-feature requests.

Can every Server 2022 server be upgraded in place to Windows Server 2025?​

No. Microsoft supports direct in-place upgrades for eligible nonclustered systems, but the real decision still depends on workload type, edition, language, architecture, drivers, and application support.

Should a stable Server 2022 server be upgraded immediately?​

Not necessarily. A stable, secure, supported workload with reliable backups and no need for platform changes can remain on Server 2022 during Extended Support. The decision should be revisited if its application, hardware, support contract, or business role changes.
The October 2026 milestone should produce a categorized plan, not a panic migration. By the time Windows Server 2022 becomes security-serviced and innovation-frozen, each server should have a named destination: retain through 2031, upgrade in place to Windows Server 2025, migrate to a new host, or move as part of a broader Azure strategy.

---

References​

1. Primary source: learn.microsoft.com
   
   

   Windows Server Servicing Channels | Microsoft Learn

   Discover how Windows Server LTSC and Annual Channel differ in release cycles, support, and installation options to meet your organization's needs.

   learn.microsoft.com
2. Primary source: WindowsForum
   
   

   Windows Server 2022 Mainstream Support Ends October 13, 2026 | Windows Forum

   Windows Server 2022 will leave mainstream support on October 13, 2026, giving administrators less than three months to decide whether five more years of...

   windowsforum.com