Windows Server 2022 Mainstream Support Ends October 2026

Every date below comes from Microsoft's lifecycle site, fetched August 23, 2026. One convention note that explains a discrepancy between sources: Microsoft's raw tables list end timestamps as 6:59:59 AM Pacific on the day after the commonly cited date — the instant support lapses, not the last supported day. Microsoft's blog and the press use the last full day, and so does this article. Both are in the table.

Rows one and four catch a common shop. Server 2012 R2's ESU Year 3 runs to the same October 2026 boundary as Server 2022's mainstream end. Pay for 2012 R2 ESU on a lingering application server while running a fleet of Server 2022 boxes, and both safety nets change status in the same week — one for real, the other only on paper.

All five follow the Fixed Lifecycle Policy — five years mainstream, five extended. For Server 2022 and 2025 that covers the Datacenter, Datacenter: Azure Edition, Essentials and Standard editions; the older releases predate Azure Edition and list their own edition sets. Server 2022 and 2025 are both Long-Term Servicing Channel releases; the Annual Channel is a separate, much shorter track for containers and Azure Edition, and nothing here applies to it.

Green is mainstream support, blue is extended, brown is paid Extended Security Updates. Dates from Microsoft product lifecycle pages, checked August 23, 2026.

Microsoft publishes exactly what each phase includes. Per the Fixed Lifecycle Policy, mainstream covers “incident support”, “security update support” and “the ability to request non-security updates”; extended covers “paid support” and “security updates at no additional cost”. The comparison table is blunter: security updates are Available in both phases, non-security updates and design-change requests only in mainstream.

For most small and mid-sized shops nothing in that table is felt. If you have never opened a Microsoft support incident against a licence entitlement or requested a non-security hotfix, October 14 changes nothing you touch. Server 2019 crossed the same boundary in January 2024 and is still patched every Patch Tuesday.

The second-order effects, where the real risk lives

None of this comes from Microsoft's policy text. These are the operational consequences of sliding out of mainstream, and the reason to have a plan rather than a panic.

• ISV support matrices. Software vendors set their own supported-OS lists, and many anchor them to whatever Microsoft still calls mainstream. That is a vendor-by-vendor decision, and the most likely thing to bite you. Pull the support matrix for every business-critical application, backup product and EDR agent, and note which ones list Server 2022 with an end date attached.
• Driver and firmware certification. Dell, HPE and Lenovo keep shipping Server 2022 drivers for platforms already certified, but new hardware certifies to the current release first. The Dell history two sections down shows the pattern.
• Compliance and insurance paperwork. We found no framework whose published text requires “mainstream” specifically — PCI-DSS and SOC 2 questions ask whether a system is supported and patched, which Server 2022 answers yes until 2031. What does happen is that blunt checklists read “mainstream ended” as “unsupported”. Write the one-page note citing October 14, 2031 now; you will be asked for it.

Server 2016's extended support ends January 12, 2027: no free security updates after that, only paid Extended Security Updates or a migration. Under five months is not a long runway for a domain controller estate. We covered that case separately — ESU cost mechanics, side-by-side versus in-place migration, the SQL Server matrix, and which refurbished hardware runs which target release. If that is your situation, read the Windows Server 2016 upgrade guide instead. The rest of this article assumes you are choosing, not being forced.

Server 2025 went generally available November 1, 2024. What follows is what matters on premises, from Microsoft's “What's new” documentation and the GA announcement, with marketing figures labelled as such.

Hotpatching. Monthly OS security updates without rebooting, requiring Server 2025 Standard or Datacenter, virtualization-based security, and Azure Arc. It launched at $1.50 per CPU core per month; as of May 19, 2026, per Microsoft's Azure Update Manager documentation, it is “available at no additional cost” with “no per-core meter, no hourly charge”, wherever the machine runs. The catch is the Arc dependency: an Azure tenant and an agent on every server, a governance decision as much as a technical one.

Storage and Hyper-V. Microsoft's GA post claims Server 2025 “delivers up to 60% more storage IOPs performance compared to Windows Server 2022 on identical systems”, footnoted as 4K random read with DiskSpd 2.2 on Kioxia CM7 NVMe — a best case, not a number you will see on SAS disks. Alongside it: native ReFS deduplication and compression, thin-provisioned Storage Spaces Direct volumes, Storage Replica compression, and LZ4 SMB compression. Hyper-V host limits rise to 4 petabytes of memory and 2,048 logical processors. Nobody reading this will hit those; two smaller changes do matter — GPU partitioning with high availability and live migration, and better processor compatibility for mixed-generation clusters.

Active Directory. The 32K database page size replaces the 8K ESE page size AD has used since Windows 2000, raising the multivalued-attribute ceiling to roughly 3,200 values. It is opt-in and forest-wide: every DC needs a 32K-capable database first, an upgraded DC keeps 8K, and it requires functional level 10. AD DS also gained NUMA awareness, so it can use CPUs outside processor group 0 and scale past 64 cores, and delegated Managed Service Accounts give a migration path off ordinary service accounts.

Security, including the change that breaks things. Credential Guard is on by default on qualifying hardware, SMB over QUIC is no longer Azure Edition only, and new AD deployments require LDAP signing by default. And then there is SMB:

Start with the story that shows how OEM certification really works. Dell's Wave 1 list of PowerEdge platforms certified for Server 2025, RTW November 1, 2024, named 23 models: C6615, R960, R660, T560, R660XS, HS5610, R6615, HS5620, R6625, R450, R760, R550, R760XA, R650, R760XD2, R6515, R760XS, R6525, R7615, R750, R7625, R7525 and R860 — 15th and 16th generation, top to bottom. Not one 14G model is on it.

Then it gets murky. Dell's BIOS notes for version 2.22.2 — R740, R740xd, R640, R940 and Precision 7920 Rack, released October 1, 2024 — list “Support for Microsoft Windows Server 2025 Operating System for R740 and R640”. Firmware enablement for 14G therefore predates Server 2025's own GA date, while formal certification excluded it. And on December 26, 2025 a Dell representative told a customer the R740 “does not support Server 2025, nor do I see it being added” — corrected in March 2026 by a customer quoting those same BIOS notes. The reading: 14G runs Server 2025, but it was never the priority and Dell's support organisation is inconsistent about it. Price that in if you are buying to run 2025 through 2034.

The RAID controller is the gate, not the CPU

This is the check most buyers skip, and the one that actually stops an installation. We fetched Dell's Server 2025 PERC driver page directly on August 23, 2026. The current driver, 7.730.02.00 (A01) of June 20, 2025, lists the H740P Adapter and Mini, H840, H745P MX, H745 Adapter and Front, H345 Adapter and Front, H755 Front, H755N, H755 Adapter, H755 MX, H750 Adapter, H355 Adapter and Front, and H350 Adapter and Mini — the same set as the original 7.729.01.00 (A00) release of October 2024.

Neither the PERC H730P nor the H730 is on that list. Those are the PERC 9 generation, standard on 13G and carried onto plenty of 14G builds, and they are everywhere in used stock — several R640 and R740xd listings in our own catalog ship with an H730P. If Server 2025 is the target, buy a machine with an H740P, H750, H755 or H355, or budget for a controller swap.

The instruction-set floor is a non-issue. Microsoft's hardware requirements page adds SSE4.2 and POPCNT for Server 2025, which 2016 through 2022 did not require. Both have been on Intel server parts since Nehalem in 2008, so every Xeon E5 v3/v4 and Scalable part clears it. TPM and Secure Boot are not required to install either — TPM 2.0 with SHA-256 PCR banks is needed for BitLocker, and Secured-core additionally wants Secure Boot, DMA remapping, Kernel DMA Protection and DRTM. On 14G and Gen10 a TPM 2.0 module is a cheap add-in, but check whether the unit has one.

HPE ProLiant. HPE's white paper on implementing Server 2025 covers Gen10, Gen10 Plus and Gen11, and states that a system ROM update to a stated minimum version is required before installing, because all three launched first. Gen9 does not appear in it. We could not verify Server 2025 driver status for the Smart Array P408i-a and P408i-p, nor confirm per-generation EOSL dates — check the serial against HPE's own tools before committing a fleet.

Controller driver support, not the drives, is what decides whether an older platform can run Server 2025. Photo: Antonio Kless, CC BY-SA 3.0, via Wikimedia Commons.

Nobody who sells licences frames this around hardware, and it is the part that changes what you should buy. Microsoft's pricing page lists US suggested MSRP at $1,176 for Standard and $6,771 for Datacenter, both for a 16-core licence — $73.50 and $423.19 per core. Microsoft's licensing guidance sets the floor: licence every physical core, minimum 8 per processor and 16 per server. Priced against real machines in our stock, checked August 23, 2026:

Read the fourth row twice. That R640 costs $1,310.62 as a machine and $20,313 to licence under Datacenter — the operating system is 15× the hardware. The 16-core R640 in row one is $785 cheaper as hardware and $13,542 cheaper to licence. Used listings are priced on core count, and the licence consequence is invisible at the point of sale. CALs are extra and Microsoft does not publish their pricing, so get a quote with a real SKU rather than a blog's estimate — ours included.

Standard or Datacenter: the break-even, computed

Microsoft's pricing page states the rights plainly: Standard gives “2 virtual machines, plus one Hyper-V host per license”, Datacenter “unlimited virtual machines”. Running more than two VMs on Standard means licensing every physical core again. The ratio is independent of core count — both editions scale linearly, so it cancels. Datacenter costs 5.76× Standard, so six Standard stacks are where Standard loses:

• Up to 10 VMs — five Standard stacks, $5,880 per 16 cores. Standard wins.
• 11 or 12 VMs — six stacks, $7,056 against Datacenter's $6,771. Datacenter is ahead by $285, with unlimited headroom.
• 13 and up — Datacenter wins, and the gap widens per VM.

The honest break-even at list price is 11 VMs per host, not the four-to-nine quoted around the web. Two things push it lower in practice: Standard stacking is unpleasant to track through an audit, and if consolidation is the purpose of the refresh you will cross 11 sooner than the plan says. Microsoft also lists pay-as-you-go at $33.58 per core per month — $402.96 a year against $423.19 to own a Datacenter core outright, and its own page notes unlimited virtualization is not available that way on Arc-enabled on-premises servers. It suits short-lived capacity and nothing else.

Hardware from PCSP stock, August 23, 2026. Licensing at Microsoft list price, Standard edition, 16-core minimum, CALs not included.

Three constraints shape the shortlist at once: OEM certification for Server 2025, a RAID controller with a driver, and the 2026 memory market. Prices and quantities are our live catalog, checked August 23, 2026.

Compare row six against row two. The DL360 Gen10 at $588.89 with 16 cores and 64 GB carries a $1,176 Standard licence; the R750 barebone at $3,784.99 carries whatever CPUs you put in it. If the workload fits in 16 cores — and for file, print, AD, backup targets and ordinary databases it usually does — the certified path costs thousands more for a tick you may not need. Make that trade consciously.

Server 2025's memory minimums are trivial; its practical sweet spot is not, and dense virtualization pushes toward high-RAM configurations at the wrong point in the DRAM cycle. We priced this in our DDR4 versus DDR5 breakdown: on August 21, 2026 refurbished DDR4 ECC RDIMMs in our stock ran $5.84 per gigabyte (32 GB PC4-2666V at $186.99) against a $36.34 per gigabyte median for new DDR5 RDIMM. That six-fold gap argues for putting a Server 2025 deployment on a DDR4 platform this year: a 14G or Gen10 host with 256 GB of refurbished DDR4 installed costs less than the memory alone on a current-generation box. The counter-argument — twelve DDR5 channels against eight — matters only for bandwidth-bound workloads.

We sell servers. It would be convenient to end with a refresh recommendation. For most shops reading this, the correct answer is to stay where you are.

Staying on Server 2022 until 2031 is a legitimate, fully supported plan. Every security update Microsoft ships, free, for five more years. No new features and no non-security fixes — for a stable file, print, directory and application estate, that describes a quiet life rather than a risk, and it costs nothing. Revisit in 2028, by which point the memory market may have normalised and Server 2025's early defects will be long fixed. The shops that should not take it need something specific: hotpatching, GPU partitioning, ReFS dedup, or the 32K AD page size.

Azure Local (formerly Azure Stack HCI) fits a narrow but real category: shops already committed to hybrid Azure that want Arc-native management, hyperconverged clustering and branch deployments on a subscription. Microsoft's own comparison is direct about the trade — on Azure Local everything runs inside VMs or containers rather than as roles on the cluster. If you need a file server and a domain controller, it is the wrong shape.

Linux with KVM, usually via Proxmox VE, removes the licensing arithmetic entirely: no per-core OS licence, no CALs. KVM is mature, and Proxmox's clustering, backup and ZFS integration run well on exactly the refurbished hardware above. What you give up is not performance — it is Active Directory as a first-class citizen, Group Policy, and anything that expects a Windows host. Samba can serve files and act as a domain controller, enough for many small estates and not enough for anyone with a .NET line-of-business application. We covered the mechanics and host sizing in switching from VMware to Proxmox. The realistic outcome is a mixed estate with a few licensed Windows hosts.

One planning trap if you buy 2025 licences now and run 2022 for a while: a 2025 key will not activate an older version. You need the specific media and key for the target version through volume licensing or your OEM, governed by Microsoft's Product Terms rather than forum answers. Confirm with your reseller first.

Microsoft's upgrade-path documentation changed with Server 2025: “nonclustered systems can upgrade up to four versions at a time”, against two for 2022 and earlier. In practice:

• In-place upgrade from installation media is supported from Server 2012 R2, 2016, 2019 and 2022. Windows Server 2012 (non-R2) is not — that is a two-hop via 2012 R2 or 2016.
• Upgrade through Windows Update, without media, works only from 2019 and 2022, and needs the prerequisite cumulative update.
• Cluster OS rolling upgrades advance one version at a time. A 2019 cluster going to 2025 is two passes, not one.
• Edition moves are one-way. Standard can become Datacenter during an upgrade; Datacenter cannot go back.
• Disable NIC Teaming before an in-place upgrade. Server Core and Desktop Experience cannot be swapped mid-upgrade, and boot-from-VHD installations cannot be upgraded in place at all.

Active Directory prerequisites. You do not need the Server 2025 functional level to run 2025 as a member server or to promote a 2025 DC into an existing domain. New forests and AD LDS configuration sets require functional level 2016 or later, and promoting a replica requires the existing domain to be at 2016 or later already. Level 10 is needed only for the 32K page feature, which is forest-wide.

Problems reported in the field. From September 2024, Server 2019 and 2022 machines were in documented cases upgraded overnight to Server 2025 without administrator approval, some to editions the organisation did not hold licences for; Microsoft blamed misconfigured third-party update management software — the vendors blamed Microsoft's release classification — and confirmed a fix in April 2026. If your patch management still carries a workaround from then, check it is not blocking an upgrade you now want. On both Dell and HPE, update BIOS or system ROM to the vendor's minimum before starting setup — HPE has an advisory about setup hanging on the first screen on certain platforms.

The pattern that keeps upgrades boring: firmware first, drivers checked against the target OS on the vendor's own site, a signing audit a week ahead, and a tested restore. Moving to different hardware instead? Our used server buying checklist covers the receiving end.

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

No. That date ends mainstream support only. Microsoft's lifecycle page lists extended support for Windows Server 2022 ending October 14, 2031, and under the Fixed Lifecycle Policy security updates are available at no additional cost throughout extended support — another five years of monthly patching.

What is the difference between mainstream and extended support?

Mainstream includes incident support, security updates and the ability to request non-security updates. Extended includes paid support and security updates at no additional cost. What you lose at the boundary is non-security bug fixes, the ability to request a hotfix or design change, and the no-charge incident support bundled with a licence or Software Assurance.

Should I upgrade to Windows Server 2025 if I am already on Server 2022?

Not on the strength of the October 2026 date alone. Server 2022 is patched until October 2031, so there is no security pressure. Upgrade if you need something specific: hotpatching without reboots, GPU partitioning, native ReFS deduplication and compression, the 32K Active Directory page size, or SMB over QUIC outside Azure Edition. Otherwise the reason to move is a hardware refresh you were doing anyway.

Can I upgrade directly from Windows Server 2016 or 2019 to Server 2025?

Yes, from installation media. Starting with Server 2025, nonclustered systems can upgrade up to four versions at a time, so 2012 R2, 2016, 2019 and 2022 all upgrade directly. Windows Server 2012 without R2 needs a two-hop. Upgrading via Windows Update is supported only from 2019 and 2022, and cluster rolling upgrades still advance one version at a time.

How much does Windows Server 2025 licensing cost?

Microsoft's US suggested MSRP is $1,176 for Standard and $6,771 for Datacenter, both covering 16 cores — $73.50 and $423.19 per core. You license every physical core, minimum 8 per processor and 16 per server. CALs are required for every user or device and priced separately; Microsoft does not publish CAL prices, so get a quote with a real SKU.

When is Windows Server Datacenter cheaper than Standard?

At 11 or more virtual machines per host, computed from Microsoft's list prices. Standard grants two VMs plus a Hyper-V host per license, and running more means licensing every physical core again. Datacenter costs 5.76 times Standard, so five Standard stacks (10 VMs, $5,880 per 16 cores) stay cheaper and six stacks (12 VMs, $7,056) do not. The ratio is independent of core count.

Will my Dell PowerEdge R740 or R640 run Windows Server 2025?

Yes, though Dell has been inconsistent about it. No 14th-generation model appeared on Dell's Wave 1 Server 2025 certification list of November 1, 2024, which was entirely 15G and 16G. But Dell's BIOS 2.22.2, released October 1, 2024, explicitly lists Windows Server 2025 support for the R740 and R640. The bigger practical issue is the storage controller: neither the PERC H730P nor the H730 appears in Dell's Server 2025 PERC driver 7.730.02.00, while the H740P, H750, H755, H355 and H350 do.

What breaks when you upgrade to Windows Server 2025?

SMB signing, most often. Server 2025 requires it by default for all outbound SMB connections, where previously it was required only for the SYSVOL and NETLOGON shares on domain controllers. Connections to NAS boxes and third-party file servers that do not allow signing fail with STATUS_INVALID_SIGNATURE (0xc000a000), and requiring signing also disables SMB guest access. Credential Guard on by default and LDAP signing for new AD deployments catch people too.

Which refurbished servers make sense for a Windows Server 2025 deployment?

Prices checked August 23, 2026. For Dell-certified hardware, the PowerEdge R750 from $3,784.99 as a barebone (27 units) or the R650 from $2,884.90 (2 units). For value, an HPE ProLiant DL360 Gen10 with 16 cores and 64GB at $588.89 (80 units) licenses at the 16-core floor, saving more on licensing than the machine costs. For memory capacity, a PowerEdge R640 with 36 cores, 256GB DDR4 and a PERC H740p at $2,170.51 (34 units). Avoid a PERC H730P if Server 2025 is the target.