Skip to content

Est. 2011·Microsoft Partner 7033487·Delivery under 3 min·Support 7 days a week

Your vault is empty.

Review

Windows Server 2022 vs 2025: Is There Any Reason to Buy the Older One?

10 min read Updated October 4, 2026 Microsoft Licensing Guides

Fix it now

Buy Windows Server 2025. Windows Server 2022 leaves mainstream support on 14 October 2026 and extended support on 15 October 2031, while 2025 runs to 14 November 2029 and 15 November 2034, and a 2025 licence bought through Commercial Licensing lets you deploy 2022 under downgrade rights anyway if a supplier has not caught up.

  1. Buy 2025 and deploy 2022 under downgrade rights if an application vendor certifies only the older release. You keep the longer entitlement and move up without buying twice.
  2. Buy 2025 CALs at the same time. A user CAL covers the corresponding version of the server software or earlier, so 2022 CALs will not cover a 2025 server.
  3. Deploy 2022 rather than 2025 only for a named compatibility reason: vendor certification, a missing driver, a backup product with no 2025 support, or a cluster you are adding a node to.
  4. Deploy 2025 if you want SMB over QUIC on Standard or Datacenter, Hyper-V GPU partitioning, workgroup Hyper-V clusters, ReFS deduplication and compression, or Azure Arc hotpatching.
  5. Plan for tightened defaults on 2025: SMB signing and encryption required by default on outbound client connections, an SMB authentication rate limiter, and Credential Guard on by default where the hardware supports it.
  6. Do not buy 2022 licences to save money. You are buying five fewer supported years for the same administrative effort and no route up without repurchasing.

If nothing in your estate pins you to the older release, the purchase is settled and you can stop. Below is what actually changed in 2025, the upgrade paths, and the CAL rule that catches people out.

Why it happens

The lifecycle dates decide this before any feature does. Windows Server 2022 was released on 18 August 2021; its mainstream support ends on 14 October 2026 and extended support on 15 October 2031. Windows Server 2025 was released on 1 November 2024, with mainstream support to 14 November 2029 and extended support to 15 November 2034. Both follow the Fixed Lifecycle Policy, so those dates do not move. Buying the older release today means buying a server that leaves mainstream support within weeks.

Downgrade rights are what make the decision one-sided. Application, system and server software obtained through Commercial Licensing programmes includes downgrade rights, so a Windows Server 2025 licence entitles you to install and run 2022 under it. You get the older media and keys through your licensing channel, deploy exactly the version your supplier has certified, and move up when they certify the newer one – with no second purchase. Buying 2022 licences instead gives you the shorter runway and locks you out of the newer release.

The 2025 release itself is substantial rather than cosmetic. Security defaults moved: SMB signing and encryption are required by default for outbound client connections, an SMB authentication rate limiter is on by default, and Credential Guard is enabled by default on devices that meet the requirements. SMB over QUIC, previously confined to Datacenter: Azure Edition, is now available in Standard and Datacenter, which matters if you want file access over the internet without a VPN. Active Directory gained a 2025 functional level with an optional 32k database page size, TLS 1.3 for LDAP, and the removal of RC4-HMAC ticket-granting tickets.

A supplier has certified 2022 and not 2025

You have this one if A line-of-business application, a specialised card with no 2025 driver, or a backup product that has not added 2025 support.

  1. Buy the 2025 licence and deploy 2022 under downgrade rights. Get the certification timeline from the supplier in writing so the arrangement has an end date.
  2. Never deploy a server version your backup or replication product cannot protect – that is the one compatibility gap with no workaround.
  3. When the supplier catches up, upgrade in place: Windows Server 2025 supports in-place upgrades from 2012 R2, 2016, 2019 and 2022, and non-clustered systems can jump up to four versions at once.

An old device breaks on the tightened defaults

You have this one if A scanner, multifunction printer or controller that stops reaching a share after a 2025 deployment.

  1. The usual culprits are the SMB signing and encryption requirements and the removal of RC4-HMAC ticket-granting tickets from the KDC.
  2. Treat it as a device replacement plan with an interim workaround, not as a reason to weaken the whole server permanently.
  3. The 2025 firewall profile change is worth knowing about too: the File and Printer Sharing (Restrictive) group excludes NetBIOS ports 137 to 139.

You are extending an existing cluster

You have this one if Adding a node to a cluster that already runs Windows Server 2022.

  1. Cluster OS rolling upgrades advance one version at a time, unlike the four-version jump allowed for non-clustered systems.
  2. Match the existing cluster now, using downgrade rights on 2025 licences, then upgrade the cluster together.
  3. Edition changes during an in-place upgrade go one way only: Standard to Datacenter is allowed, Datacenter to Standard is not.

Full reference

What is actually different

Dimension Windows Server 2022 Windows Server 2025
Released 18 August 2021 1 November 2024
Mainstream support ends 14 October 2026 14 November 2029
Extended support ends 15 October 2031 15 November 2034
SMB over QUIC Datacenter: Azure Edition only Standard and Datacenter
SMB signing and encryption defaults Signing required for SYSVOL and NETLOGON Signing and encryption required by default on outbound client connections
Credential Guard Opt-in On by default where hardware supports it
Active Directory functional level As previously shipped 2025 level, with an optional 32k database page size
Hyper-V GPU partitioning Not available Available, with live migration and failover
Workgroup Hyper-V clusters Not available Available, without domain membership
Hyper-V host maximums As shipped in 2022 4 PB memory, 2,048 logical processors
ReFS deduplication and compression Not available Available
Hotpatching without a reboot Datacenter: Azure Edition only Standard and Datacenter, as an Azure Arc-enabled service at no extra cost
In-place upgrade jump Up to two versions for non-clustered systems Up to four versions for non-clustered systems
Licensing model Per physical core plus CALs Identical: per physical core plus CALs

Hotpatching is no longer an edition argument

Hotpatching applies operating system security updates without restarting the machine, and on Windows Server 2025 it arrives as an Azure Arc-enabled service on both Standard and Datacenter, at no extra cost, rather than as a Datacenter: Azure Edition exclusive. That removes a reason people used to give for buying up an edition, and adds a genuine reason to prefer 2025 over 2022 on servers where reboots are expensive. The prerequisite is connecting the machine to Azure Arc and enabling the feature; it is not something the licence alone turns on.

CALs are the part people forget to budget

Windows Server has two halves: the server, licensed by physical core with a minimum of eight core licences per processor and sixteen per server, and Client Access Licences for the users or devices that connect. The Product Terms describe a user CAL as allowing access to the corresponding version of the server software or earlier versions. Read that in the direction that costs money: 2025 CALs cover a 2025 server and a 2022 one, but 2022 CALs do not cover a 2025 server. Upgrade one server and your existing CALs do not automatically carry over.

Remote Desktop Services states the same rule explicitly and is worth quoting because it is the version people most often get wrong. Microsoft’s documentation says you cannot use RDS CALs for earlier versions to access later versions of Windows Server, but you can use later versions of RDS CALs to access earlier versions – so Windows Server 2025 RDS CALs reach a 2022 session host, and 2022 RDS CALs do not reach a 2025 one. RDS CALs are additive: they sit on top of the base Windows Server CAL, not instead of it.

Upgrade paths, and where they stop

Windows Server 2025 supports in-place upgrades from Windows Server 2012 R2, 2016, 2019 and 2022, and non-clustered systems may now advance up to four versions in a single upgrade, where 2022 and earlier allowed two. Cluster OS rolling upgrades still move one version at a time. Edition changes during the upgrade are allowed upwards only: Standard to Standard or Datacenter, Datacenter to Datacenter or Datacenter: Azure Edition, and no route back down.

On a server already running Windows Server 2025, converting Standard to Datacenter is a licensing change rather than a rebuild. Confirm what the machine is and what it can become, then set the edition with the Datacenter key. Buy the licence first, and note there is no documented route back to Standard afterwards.

Run from an elevated command prompt on the server

DISM /online /Get-CurrentEdition
DISM /online /Get-TargetEditions
DISM /online /Set-Edition:ServerDatacenter /ProductKey:<product key> /AcceptEula

One edition you cannot simply buy

Windows Server 2025 Datacenter: Azure Edition appears in Microsoft’s edition comparison alongside Standard and Datacenter, and it carries capabilities the others do not. It is not a shelf product for your own hardware: it is intended for Azure and Azure Local, so treat it as a deployment target rather than a purchasing option when you are specifying a server for your own rack.

When a licence is the actual fix

For essentially every new deployment Windows Server 2025 Standard is the correct purchase: the same core-based licensing model as 2022, roughly five more years of supported life, and downgrade rights that let you deploy 2022 today if a supplier has not certified the newer release. Arco supplies 2025 Standard and Datacenter core licences with the count worked out against your actual processor and core layout, along with the matching User or Device CALs and Remote Desktop Services CALs at the right version. Tell us which applications the server will run and we will check their certification status before the order goes in rather than after, and if your virtual machine count makes Datacenter cheaper than relicensing Standard we will say so.

Questions people ask about this

Can I install Windows Server 2022 using a 2025 licence?

Yes. Application, system and server software obtained through Commercial Licensing programmes includes downgrade rights, so you may run an earlier version under a current-version licence. You obtain the older media and keys through your licensing channel. Your entitlement remains a 2025 licence, so moving up later costs nothing further.

When does Windows Server 2022 actually stop being supported?

Mainstream support ends on 14 October 2026 and extended support on 15 October 2031. Extended support means security fixes only – no new features and no non-security updates – so a 2022 server bought now spends almost all of its life in that phase.

Do I need new CALs when I upgrade a server?

Yes, if the new server is a newer version than your existing CALs. A user CAL allows access to the corresponding version of the server software or earlier versions, so a 2025 server needs 2025 CALs. Remote Desktop Services documents the same rule directly: earlier-version RDS CALs cannot reach a later Windows Server session host. Budget for CALs at the same time as the server; they are frequently the larger number.

Is there a performance reason to stay on 2022?

Not generally. Windows Server 2025 includes NVMe optimisation, ReFS deduplication and compression, Storage Replica compression and a much larger Hyper-V host ceiling. The reasons to run 2022 are compatibility reasons, and every one of them should have an expiry date attached.

Will an in-place upgrade from 2022 to 2025 work?

It is a supported path, and Windows Server 2025 additionally allows non-clustered systems to jump up to four versions at once, so 2012 R2, 2016 and 2019 are also direct sources. Clusters still advance one version at a time through a rolling upgrade. Whichever route you take, take a full backup and test the restore before you start, and remember an edition change during upgrade only goes upwards.

Does 2025 change how the server is licensed?

No. It is the same core-based model: every physical core on the licensed server, minimum eight core licences per physical processor and sixteen per server, sold in 2-packs and 16-packs, with CALs for every user or device. Standard still permits two operating system environments per fully licensed server and Datacenter still permits any number.

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

Review Microsoft 365 Apps for Business vs Enterprise: Which Office Install? Review Windows Server Core Licensing Explained Without the Spreadsheet Headache Review Planner and Project Plans 1, 3 and 5: Which Licence Matches How You Run Projects Review Exchange Server SE Standard vs Enterprise: It Is About Databases
← Back to Knowledge Base