Windows Server 2025 vs 2022 comes down to support runway and security defaults: Server 2022 left mainstream support on 13 October 2026, while Server 2025 stays in mainstream support until November 2029 and adds hotpatching, stronger Active Directory and SMB hardening, and much larger Hyper-V limits. For most small businesses replacing Server 2016 before January 2027, 2025 is the better target.
| Area | Windows Server 2022 | Windows Server 2025 |
|---|---|---|
| Released | 18 August 2021 | 1 November 2024 |
| Mainstream support ends | 13 October 2026 (already ended) | 13 November 2029 |
| Extended support ends | 14 October 2031 | 14 November 2034 |
| Hotpatching on your own hardware | Azure Edition only | Standard and Datacenter via Azure Arc |
| SMB over QUIC | Datacenter: Azure Edition only | Standard and Datacenter |
| New AD functional level and 32k database pages | No | Yes (optional, forest-wide) |
| Hyper-V Gen 2 VM maximum | Lower limits | 240 TB RAM, 2,048 virtual processors |
| CPU requirement | x64, no SSE4.2 requirement | x64 with SSE4.2 and POPCNT |
| Licensing model | Per core plus CALs | Per core plus CALs, or pay-as-you-go via Azure Arc |
Dates are taken from Microsoft's lifecycle pages for Windows Server 2025 and Windows Server 2022, shown here in UK date order.
Is Windows Server 2025 better than Windows Server 2022?
For new deployments, yes. Windows Server 2025 has three more years of mainstream support than 2022, enables more security protections by default, scales Hyper-V much further and adds hotpatching for on-premises Standard and Datacenter servers. Windows Server 2022 remains a stable, fully patched platform, but it now receives security fixes only.
"Better" depends on what you run. A file server or small domain controller sees the biggest gains from the new security defaults, while a Hyper-V host gains from the scale and GPU features. A server running a line-of-business application gains nothing if the vendor has not certified it for 2025 yet.
What we commonly see: small businesses rarely upgrade for a headline feature. They upgrade because a lifecycle date forces the decision, and then choose the newest version so that the next forced decision is as far away as possible.
When does support end for Windows Server 2022 and 2025?
Windows Server 2022 moved from mainstream to extended support on 13 October 2026 and receives security updates until 14 October 2031. Windows Server 2025 receives mainstream support until 13 November 2029 and extended support until 14 November 2034, giving it roughly three extra years of patches.
Mainstream support includes feature fixes and non-security bug fixes, while extended support delivers security updates only. That matters for servers you plan to keep for five or more years, because a non-security bug discovered on 2022 after October 2026 may never be fixed.
Windows Server 2016 is the more urgent case. Its extended support ends on 12 January 2027, so any 2016 machine should already be on a migration plan. Our guide to Server 2012 R2 and 2016 end of support covers the risks and paid Extended Security Update options.
What is new in Windows Server 2025 compared with 2022?
The main additions are hotpatching through Azure Arc, a new Active Directory functional level with optional 32k database pages, SMB over QUIC in Standard and Datacenter, Credential Guard on by default, delegated Managed Service Accounts, GPU partitioning in Hyper-V, faster NVMe storage and built-in tools such as WinGet, OpenSSH server and Windows Terminal.
Microsoft's What's new in Windows Server 2025 page lists the full set. The changes most relevant to small and mid-sized businesses are:
- Active Directory: a new domain and forest functional level, Kerberos no longer issuing RC4 tickets, LDAP signing required by default on new deployments and TLS 1.3 for LDAP.
- SMB file sharing: SMB signing required for all outbound connections, optional NTLM blocking and SMB over QUIC for secure remote access without a VPN.
- Hyper-V: hosts support up to 4 PB of memory and 2,048 logical processors, plus GPU partitioning with live migration.
- Desktop Experience: Wi-Fi and Bluetooth support, built-in WinGet and native ZIP, 7z and TAR handling.
Does Windows Server 2025 support hotpatching without Azure?
Partly. Windows Server 2025 Standard and Datacenter can hotpatch on your own hardware or other clouds, but each machine must be connected to Azure Arc and hotpatching enabled in the Azure Arc portal. On Windows Server 2022, hotpatching is limited to Datacenter: Azure Edition running in Azure or Azure Local.
Hotpatching installs monthly security updates into running processes without a restart. You still restart for the quarterly baseline cumulative update, so Microsoft's own example works out at about four planned restarts a year instead of twelve.
Cause and effect: Microsoft's hotpatch documentation now states that Azure Arc-enabled hotpatching for Windows Server 2025 is available at no extra cost, which removes the main objection small businesses raised when it launched as a paid subscription. The Arc agent, virtualisation-based security and UEFI Secure Boot are still required, so older hardware may not qualify.
Can I upgrade Windows Server 2022 to 2025 in place?
Yes. Microsoft supports in-place upgrades to Windows Server 2025 from 2012 R2, 2016, 2019 and 2022, up to four versions in one step for non-clustered servers. You need a valid Windows Server 2025 licence, a full (not evaluation) installation, the same language and the same installation type.
Microsoft's upgrade overview adds several conditions worth checking before you start:
- Take a full backup and confirm you can restore it.
- Check the edition: Standard can move to Datacenter during the upgrade, but Datacenter cannot move down to Standard.
- Disable NIC Teaming before the upgrade and re-enable it afterwards.
- Confirm you are not switching between Server Core and Desktop Experience, which is not supported in place.
- If the server is an evaluation copy, convert the evaluation to a full licensed version first or perform a clean install.
Domain controllers deserve extra care. Many administrators prefer to build a new 2025 domain controller, transfer roles and retire the old one, as described in our domain controller migration guide.
Will my hardware run Windows Server 2025?
Most servers bought in the last ten years will, but Windows Server 2025 needs a 1.4 GHz x64 processor that supports SSE4.2 and POPCNT, NX/DEP, CMPXCHG16b, LAHF/SAHF, PrefetchW and second-level address translation. Very old CPUs and some virtual CPU profiles that hide SSE4.2 will fail setup.
TPM 2.0 and UEFI Secure Boot are not required to install the operating system, but features such as BitLocker, hotpatching and Secured-core depend on them. If you plan to hotpatch, confirm that virtualisation-based security can be enabled before you commit to in-place upgrades.
Advanced nuance: on Hyper-V and VMware hosts, a guest can fail the SSE4.2 check because the host is running in processor-compatibility mode with a reduced instruction set. Turning compatibility mode off, or using Server 2025's dynamic processor compatibility, usually resolves it.
How much does Windows Server 2025 cost compared with 2022?
At the time of writing (November 2026), Microsoft's US list price for Windows Server 2025 is $1,176 for Standard and $6,771 for Datacenter, each covering 16 cores, with Client Access Licences bought separately. The licensing model mirrors 2022: per-core licences with a 16-core minimum per server and eight cores per processor.
Server 2025 adds a pay-as-you-go option through Azure Arc, which Microsoft lists at $33.58 per core per month in the US, billed to an Azure subscription. It suits short projects but costs more than a perpetual licence for a server kept several years.
CALs are the cost people forget. Every user or device that accesses the server needs a CAL of the same version or later, so moving to 2025 usually means buying 2025 CALs too. Our Windows Server CALs guide explains user and device CALs.
Should I choose Standard or Datacenter for Server 2025?
Choose Standard if the server runs on physical hardware or hosts up to two virtual machines per full licence, which covers most small businesses. Choose Datacenter if you run many virtual machines on one host or need Storage Spaces Direct, Software-Defined Networking or unlimited Windows Server guests.
You can stack additional Standard licences to cover more virtual machines, but the cost overtakes Datacenter as the VM count rises. Our comparison of Standard vs Datacenter vs Essentials works through the break-even point.
For a typical single-host office server, Windows Server 2025 Standard is the usual choice; see the current price on the product page. Larger virtualised estates should look at Windows Server 2025 Datacenter.
When should you stay on Windows Server 2022?
Stay on Windows Server 2022 when a critical application vendor has not certified Server 2025, when your hardware lacks SSE4.2 support, or when the server will be retired before October 2031. In those cases 2022 still receives monthly security updates and remains a supportable choice.
Plan the move anyway. A 2022 server installed today has under five years of patches left, while a 2025 server has eight, so the earlier you switch the less often you repeat the migration work.
Frequently asked questions
Is Windows Server 2022 still supported in 2026?
Yes. Windows Server 2022 left mainstream support on 13 October 2026 but remains in extended support until 14 October 2031. It continues to receive monthly security updates, but Microsoft no longer accepts design-change or feature requests and non-security fixes are limited, so new deployments are better placed on Windows Server 2025.
Can a Windows Server 2022 CAL access a Windows Server 2025 server?
No. CALs must be the same version as the server they access or later, so a 2022 CAL does not cover access to a Windows Server 2025 server. A 2025 CAL, however, can access servers running 2025 and earlier versions, which makes buying 2025 CALs sensible during a mixed-version migration.
Is Windows Server 2025 stable enough for production?
Windows Server 2025 has been generally available since 1 November 2024 and has received two years of cumulative updates. It is widely deployed in production. As with any server operating system, test line-of-business applications, backup agents and security tools in a pilot before upgrading critical machines.
Do I need to reinstall applications after upgrading to Server 2025?
Not usually. An in-place upgrade keeps installed applications, settings and data, although some applications may need updating or reconfiguring afterwards. Check vendor support statements first, and keep the backup taken before the upgrade until you have confirmed that every service starts and behaves normally on Windows Server 2025.
Do I need an Azure subscription to use Windows Server 2025?
No. Windows Server 2025 Standard and Datacenter install, activate and run entirely on-premises with a product key, and receive monthly updates through Windows Update or WSUS. Azure Arc is optional and is needed only for extras such as hotpatching, Azure Update Manager or pay-as-you-go licensing, so offline and air-gapped servers remain fully supported.
Related guides
- Windows Server 2025 Standard: download, install and activate
- Windows Server 2012 R2 and 2016 end of support
- Set up Remote Desktop Services on Windows Server
- Windows Server Standard vs Datacenter vs Essentials
Links in this guide
| Link | Type | Why it helps |
|---|---|---|
| Windows Server 2025 lifecycle | External | Official mainstream and extended support dates for Server 2025 |
| Windows Server 2022 lifecycle | External | Official support dates confirming 2022 is in extended support |
| Server 2012 R2 and 2016 end of support | Internal | Risks and ESU options for Server 2016 before January 2027 |
| What's new in Windows Server 2025 | External | Microsoft's full list of Server 2025 features and security defaults |
| Windows Server upgrade overview | External | Supported in-place upgrade paths and edition rules |
| Convert Windows Server evaluation to full | Internal | Required step before upgrading an evaluation install |
| Migrate a domain controller to Server 2025 | Internal | Safer alternative to upgrading a domain controller in place |
| Windows Server CALs explained | Internal | Explains the CALs needed for a 2025 server |
| Standard vs Datacenter vs Essentials | Internal | Edition comparison and virtualisation break-even |
| Windows Server 2025 Standard | Internal | Licence for the typical single-host office server |
| Windows Server 2025 Datacenter | Internal | Licence for heavily virtualised hosts |
| Server 2025 Standard install guide | Internal | Step-by-step installation and activation |
| Remote Desktop Services setup | Internal | Configure RDS on the new server |