Windows Server 2022 leaves mainstream support on 13 October 2026 but stays in extended support, with monthly security updates, until 14 October 2031. You do not have to migrate urgently. Moving to Windows Server 2025 makes sense for new deployments, hardware refreshes and anyone who wants new features or support until 2034.
Written by the Softkeyworld technical team · Updated October 2026
Key takeaways
- The end of mainstream support is not the end of security patches. Server 2022 keeps receiving them for five more years.
- What you lose is non-security fixes, feature changes and free incident support, along with any chance of a design-change request.
- Server 2025 can in-place upgrade directly from 2012 R2, 2016, 2019 and 2022.
- Licensing is per physical core (minimum 16 per server), and the new version needs matching 2025 CALs.
The key dates, verified
Windows Server 2022 follows Microsoft's Fixed Lifecycle Policy, which means five years of mainstream support followed by five years of extended support. Microsoft's Windows Server 2022 lifecycle page lists the cut-offs in Pacific Time as 14 October 2026 06:59 and 15 October 2031 06:59. In UK terms, the last mainstream Patch Tuesday is Tuesday 13 October 2026 and the final extended update lands on Tuesday 14 October 2031.
| Version | Released | Mainstream ends | Extended ends |
|---|---|---|---|
| Windows Server 2016 | October 2016 | January 2022 (ended) | January 2027 |
| Windows Server 2019 | November 2018 | January 2024 (ended) | January 2029 |
| Windows Server 2022 | August 2021 | 13 October 2026 | 14 October 2031 |
| Windows Server 2025 | November 2024 | November 2029 | November 2034 |
The dates apply to every edition: Standard, Datacenter, Datacenter: Azure Edition and Essentials. Note the row above 2022 as well. Windows Server 2016 leaves extended support in January 2027, just over three months away. If you still run 2016 boxes, they are the urgent job. Server 2022 is not.
Mainstream vs extended support: what actually changes
"End of mainstream support" headlines cause more unnecessary panic than any other lifecycle event. Here is what really changes after 13 October:
| What you get | Mainstream (to Oct 2026) | Extended (Oct 2026 – Oct 2031) |
|---|---|---|
| Monthly security updates | Yes | Yes |
| Non-security bug fixes | Yes | No (except via paid Unified/Premier-style agreements) |
| New features / design changes | Can be requested | No |
| Complimentary incident support | Yes, where included with licence | No; paid support only |
| Warranty claims | Yes | No |
In practice, for a typical small business file server, domain controller or line-of-business host, nothing on the server changes this month. Patch Tuesday keeps arriving and WSUS keeps approving updates. The difference shows up in edge cases. If a non-security bug starts hurting you in 2028, for example an SMB performance regression with a particular NAS or a print spooler quirk, Microsoft is unlikely to fix it for 2022, and its answer will be to move to 2025.
Should you move to Server 2025? A decision framework
Stay on Server 2022 for now if…
- the hardware is under four years old and the workload is stable;
- a line-of-business application vendor has not yet certified Server 2025 (check this before anything else, because accounting, EPOS and practice-management software is often slow to certify);
- you plan to retire or move the workload to the cloud before 2031 anyway.
Move to Server 2025 if…
- you are buying new server hardware. Newer platforms are validated for 2025, and installing a version that is already in extended support on day one makes little sense;
- you still run Server 2016 or 2019 alongside 2022 and want one consistent target. Server 2025 is the only version that will be in mainstream support for the next three years;
- you want a specific 2025 feature (see below), such as hotpatching, SMB over QUIC on Standard edition, or Hyper-V GPU partitioning;
- compliance frameworks or customer contracts specify "vendor mainstream-supported software".
What Server 2025 actually adds
Microsoft's What's new in Windows Server 2025 page is long. These are the changes that matter most in day-to-day administration:
- Hotpatching for Standard and Datacenter through Azure Arc (a paid subscription). Most monthly security updates install without a reboot, with a baseline restart roughly once a quarter.
- Active Directory upgrades. New domain and forest functional level 10, an optional 32k database page size, LDAP over TLS 1.3, LDAP signing required by default on new deployments, and delegated Managed Service Accounts (dMSA).
- SMB hardening. SMB signing is required by default for outbound connections, an authentication rate limiter blocks brute-forcing, and SMB over QUIC is now in Standard and Datacenter (it was previously Azure Edition only).
- Credential Guard on by default on hardware that supports it.
- Hyper-V scale and GPU partitioning. Up to 2,048 logical processors and 4 PB of memory per host, GPU-P with live migration, and workgroup clusters without AD.
- Quality-of-life changes. A Windows 11-style desktop, Windows Terminal, WinGet and OpenSSH server installed by default, plus faster NVMe storage I/O.
The SMB and LDAP signing defaults are the main thing to test. Old NAS units, copiers that scan to SMB shares and legacy applications that bind to LDAP without signing are the usual casualties. Check them in a lab or on a single member server first.
In-place upgrade paths to Server 2025
Server 2025 relaxes the old "two versions back" rule. According to Microsoft's upgrade overview, non-clustered servers can now jump up to four versions at once.
| From | Direct in-place upgrade to 2025? |
|---|---|
| Windows Server 2022 | Yes (also offered as a feature update via Windows Update) |
| Windows Server 2019 | Yes |
| Windows Server 2016 | Yes |
| Windows Server 2012 R2 | Yes |
| Evaluation or preview builds | No; clean install required |
Rules that catch people out
- You cannot switch between Server Core and Desktop Experience during an upgrade.
- You can go from Standard to Datacenter during the upgrade, but never from Datacenter to Standard.
- The installation language must match.
- Disable NIC Teaming before upgrading and recreate it afterwards (or move to Switch Embedded Teaming).
- Domain controllers can be upgraded in place, but best practice is to build a new 2025 DC, transfer FSMO roles and demote the old one.
Step by step: in-place upgrade from 2022
- Take a full backup and a VM checkpoint or snapshot if the server is virtual. Test that the backup restores.
- Record the current state:
Get-ComputerInfo -Property WindowsProductName, OsVersion, the installed roles viaGet-WindowsFeature | Where Installed, and network settings withipconfig /all. - Install all pending 2022 cumulative updates and restart.
- Mount the Server 2025 ISO and run
setup.exe. Choose Upgrade and select the same edition and installation type. Enter your 2025 product key when prompted. - Choose Keep files, settings and apps. Expect between 30 and 90 minutes and several restarts.
- Afterwards, check Event Viewer, services, shares, scheduled tasks and application connectivity. Confirm activation with
slmgr /dli.
For a clean build instead, our Windows Server 2025 download, install and activation guide covers media, edition selection and activation. That includes the common 0xC004F069 error when a key does not match the installed edition.
Audit what you are running first
Before you decide anything, find out exactly what is in the estate. On a domain, this PowerShell one-liner (from a machine with the RSAT Active Directory module) lists every server OS and its build:
Get-ADComputer -Filter 'OperatingSystem -like "*Server*"' -Properties OperatingSystem,OperatingSystemVersion | Sort OperatingSystem | Format-Table Name,OperatingSystem,OperatingSystemVersion
Build 20348 is Server 2022, 17763 is 2019, 14393 is 2016, and 26100 is 2025. For each server, record its core count (Get-CimInstance Win32_Processor | Measure-Object NumberOfCores -Sum), its roles, the applications it hosts and the vendor's stance on Server 2025. That one spreadsheet answers your licensing questions and your upgrade order at the same time.
A realistic timeline
- Now to January 2027: replace or upgrade any remaining Server 2016 systems before their extended support ends.
- 2027: build Server 2025 in a lab, test SMB and LDAP hardening against printers, NAS units and legacy apps, and collect vendor certifications.
- 2027–2029: move Server 2019 and 2022 workloads as hardware comes up for renewal, starting with domain controllers and file servers.
- Before 2031: no Server 2022 left in production.
Licensing basics: cores, editions and CALs
Windows Server Standard and Datacenter are licensed per physical core. The rules are the same as for 2022:
- All physical cores in the server must be licensed, with a minimum of 8 cores per processor and 16 cores per server.
- A single-CPU server with 8 or 12 cores still needs 16 core licences. A dual 16-core server needs 32.
- Standard allows two Windows Server VMs (OSEs) on a fully licensed host. You can stack licences to add two more each time.
- Datacenter allows unlimited Windows Server VMs on the licensed host and adds features such as Storage Spaces Direct and Shielded VMs.
- Client Access Licences (CALs) are needed for every user or device that accesses the server. CALs must be the same version as, or newer than, the server they access, so a 2025 server needs 2025 CALs. Remote Desktop Services needs its own RDS CALs on top.
Two other routes are worth knowing about. Essentials remains an option for very small businesses on a single small server: it is limited to 25 users and 50 devices, needs no CALs, and is usually sold with hardware through OEMs. Server 2025 also offers pay-as-you-go licensing through Azure Arc, billed monthly per core to your Azure subscription. That suits short-lived or seasonal servers, but for a box that runs for five years, a perpetual licence is normally the simpler choice.
The rule of thumb: once you need more than about ten to twelve Windows Server VMs on one host, Datacenter usually works out simpler than stacking Standard licences. Our Server Standard vs Datacenter breakdown explains the feature differences, which carry over to 2025. For larger virtualisation hosts, Windows Server 2025 Datacenter is the edition to price up.
A licensing detail often missed: Microsoft's product terms generally grant downgrade rights for volume-licensed and OEM Windows Server, so a 2025 licence can cover a 2022 installation while application vendors catch up. Check the terms that come with your specific licence type before relying on this.
Frequently asked questions
Will Windows Server 2022 still get security updates after October 2026?
Yes. Security updates continue every month through extended support until 14 October 2031.
What is the difference between mainstream and extended support?
Mainstream support includes security updates, non-security fixes, feature changes and complimentary support. Extended support delivers only security updates, plus paid support.
Can I upgrade Windows Server 2022 to 2025 without reinstalling?
Yes. Run setup.exe from the 2025 media and choose to keep files, settings and apps, or accept the feature update through Windows Update. You need a valid 2025 licence.
Do my Server 2022 CALs work with Server 2025?
No. CALs must match or exceed the server version, so users or devices accessing a 2025 server need 2025 CALs.
How long is Windows Server 2025 supported?
Mainstream support runs until November 2029 and extended support until November 2034.
Is it worth buying Server 2022 now?
Only if a specific application requires it. Even then, a 2025 licence that carries downgrade rights usually gives more runway. If you simply need to license an existing 2022 box, a Windows Server 2022 Standard licence is still fully supported for security updates until 2031.
Our recommendation
Don't let the headline rush you. A well-patched Server 2022 machine is perfectly safe to run while you plan. Use the next 12 to 24 months to retire any 2016 servers first, confirm vendor support for 2025, and move to Server 2025 at your next hardware refresh or maintenance window. For most small and mid-sized businesses running a handful of VMs on one host, Windows Server 2025 Standard is the right default. It is in mainstream support until 2029, can be in-place upgraded from everything you are likely to run today, and uses the same core-based licensing model you already know.
Get Windows Server 2025 Standard
Related reading
| Resource | Why read it |
|---|---|
| Server 2025 install and activation | Clean install, edition choice and activation fixes |
| Standard vs Datacenter | Pick the right edition for your VM count |
| Windows Server 2025 Datacenter | Unlimited VMs for dense virtualisation hosts |