Windows Server 2025: Release Date, Editions, Pricing, and What Changed

The Windows Server 2025 release date was November 1, 2024. That day Microsoft made the Long-Term Servicing Channel release generally available. Standard and Datacenter shipped the same day. We’d note the build number too: 26100, shared with Windows 11 version 24H2.

If you haven’t looked at it yet, now is a good moment.

Microsoft posted the release on the Windows release health page, and the 180-day evaluation ISO went up on the Evaluation Center. A test VM the same week, production later. That’s the order we’d follow too.

The focus here is everyday server administration, mostly Active Directory, Hyper-V and file services.

It covers what 2025 changed, what broke at launch and how the upgrade goes. The facts come from Microsoft Learn and Microsoft’s own pricing page.

All of that went into this page, plus a short note on SQL Server 2025, which people often mix up with it.

The Windows Server 2025 release date

Microsoft released it on November 1, 2024. That’s the date of general availability for Standard, Datacenter and Datacenter: Azure Edition.

It carries build number 26100 and shares its code base with Windows 11 version 24H2.

Microsoft first confirmed the next Server release on the Windows Server blog in January 2024.

Insider builds trickled in through spring. General availability landed on November 1.

Microsoft then showcased the release at its Ignite conference later that month.

Under the hood it’s the same Germanium code that powers Windows 11, minus the consumer extras and plus the server roles.

That shared base explains the look. It also explains why some client bugs showed up on servers in the first months.

One example: a network driver issue in a preview build. A later cumulative update fixed it.

Version history

For context, the table lists every major release since 2003.

Editions and prices at the Windows Server 2025 release

There are four editions. The wrong choice either wastes money or hits a licensing wall the day you need more VMs.

The list prices come from Microsoft’s Windows Server pricing page, checked in November 2026.

They’re Microsoft’s suggested US prices for 16-core licenses. A Client Access License comes on top for every user or device.

Prices vary by country and seller.

Standard

Standard covers the usual roles.

• AD
• DNS
• DHCP
• File shares
• IIS
• Hyper-V

Each fully licensed host gets 2 VM licenses. For a third and fourth VM, you license all the cores again with another Standard license.

That’s called stacking, and each stack adds two VMs. It gets expensive fast with many VMs on one box.

Datacenter

Datacenter costs far more on paper, and the sticker price hurts. But it comes with unlimited VMs.

Run as many as your hardware can handle. You also get features Standard lacks.

• Storage Spaces Direct
• Shielded VMs
• Software-defined networking
• Network Controller

At Microsoft’s list prices, six Standard stacks for 12 VMs already cost more than one Datacenter license for the same 16 cores.

So somewhere around 10 to 12 VMs per host, Datacenter starts to win.

We’d count the VMs you plan to run in two years, not the ones you run today.

Essentials

Essentials barely exists anymore. It targets tiny offices of up to 25 users.

You can only get it preinstalled from a hardware OEM. Microsoft stopped developing the old Essentials Experience back in 2019.

So today it’s mostly a licensing shortcut for small servers.

Windows Server 2025 Essentials isn’t in our catalog. The newest Essentials release we sell is Windows Server 2022 Essentials.

Licensing

Licensing trips people up. It follows a per-core model: count the physical cores on your server and license all of them.

Then come CALs. Every user or device that connects to the server needs a Windows Server CAL.

Remote Desktop Services users need their own RDS CALs on top, bought separately.

Cores alone don’t make a server legal. In a license review the CALs count too, so we’d keep the proof of purchase next to the server documentation.

Microsoft also added a pay-as-you-go option through Azure Arc. It costs $33.58 per core per month at list price, billed to your Azure subscription.

A typical fit: a trade show season, when a company needs extra capacity for three months. There it makes sense.

For permanent workloads, the math rarely works out.

Need a key? Our Windows Server 2025 Standard key comes as a genuine license. Delivery is instant to email.

For many VMs on one host, we’d look at the Windows Server 2025 Datacenter key.

What changed in the Windows Server 2025 release

This release changed more than any since 2016. The jump from 2019 to 2022 felt minor by comparison.

There’s real substance here. These are the parts that matter if you manage servers day to day.

Hotpatching in Standard and Datacenter

Only Azure Edition had hotpatching before, which was frustrating. Now Standard and Datacenter get it too.

• Connect the server to Azure Arc.
• Turn on Hotpatch for that machine in the Azure Arc portal. It launched as a paid subscription in July 2025; Microsoft now offers Arc-enabled Hotpatch for Server 2025 at no extra cost.
• Most monthly security updates then install with no reboot.

You still restart for the quarterly baseline updates.

Not everything qualifies. Non-security fixes, .NET updates, drivers and firmware still want a restart. No automatic rollback either. A bad hotpatch? Uninstall it, back to the last baseline, reboot. Microsoft’s Hotpatch page on Microsoft Learn has the calendar.

Faster NVMe storage

Microsoft claims up to 60% more IOPS on identical hardware compared with Server 2022. A reworked NVMe storage stack is behind that.

On typical NVMe machines the gain is clearly noticeable, though often below the headline number.

With SQL Server or heavy Hyper-V storage, you feel the difference.

Security

Security brought the biggest changes in the whole release.

The TLS part catches people out. Old line-of-business apps that only speak TLS 1.0 simply stop connecting, and the real fix comes from their vendor.

So check your apps before you upgrade.

The other big one is SMB over QUIC. It now works in Standard and Datacenter too, where it used to need Azure Edition.

Field staff open the file shares over the internet, no VPN. The traffic runs through a TLS 1.3 tunnel on UDP port 443 instead of TCP 445.

What it needs. A server certificate, from your own CA or a public one. Windows 11 on the clients. An opt-in on the server. On 2025 we’d set it up in PowerShell, since Windows Admin Center can’t configure it there yet.

Active Directory

Active Directory gets functional level 10. The headline feature is optional 32K database pages, up from 8K pages.

That sounds boring until you manage a large forest. There, big multivalued attributes start hitting limits.

Microsoft also added delegated Managed Service Accounts, dMSA for short. Service account passwords then rotate automatically.

No more PowerShell scripts doing password resets on a schedule.

Hyper-V scale and GPU partitioning

On paper the specs are wild.

Few environments need that today. It’s clearly aimed at AI and SAP HANA style workloads.

What we do care about is GPU partitioning, GPU-P for short. Put a GPU in the host, carve it into slices and hand each slice to a different VM.

It suits a VDI proof of concept with a workstation GPU well.

Better still, GPU-P VMs can now live migrate. On Server 2022, a VM with a GPU was stuck on its host.

Maintenance called for shutting it down. Now you just migrate it.

The interface

The first RDP session to it makes you look twice. It looks like Windows 11.

• Rounded corners
• A Start menu with pinned apps
• Task Manager in dark mode

Windows Terminal is installed out of the box, and so is winget. That’s great for scripted deployments.

A right-click in Explorer can compress to 7z or TAR, not just to ZIP archives. Bluetooth and Wi-Fi are in too.

Nobody runs Wi-Fi on a rackmount server, obviously. For test labs and small office boxes, these little things add up.

Known issues at the Windows Server 2025 release

There were three notable bugs at launch. Later cumulative updates fixed all three, so a current ISO and a patched server aren’t affected.

The processor bug was the nasty one. Machines with 128 logical processors or fewer never came near it.

The fix came with the November 12, 2024 cumulative update.

If someone hands you the original November 2024 ISO, we’d install the latest cumulative update right after setup. A fresh ISO from the Evaluation Center or the Volume Licensing portal works too.

Windows Server 2025 system requirements

Two CPU requirements arrived with this release: SSE4.2 and POPCNT.

So unless you deploy on truly ancient hardware, this won’t bite you.

With no SLAT on the CPU, setup won’t even start. Coreinfo from Sysinternals checks that in about ten seconds.

Secure Boot and a TPM 2.0 chip matter only for certain features, such as BitLocker.

VM installs have a gotcha. Give a test VM the bare minimum of memory, and the installer just sits there, frozen, no error code.

Microsoft documents this. With 1 core and 1,024 MB of RAM, installation fails.

So allocate at least 1,280 MB during setup, and lower it afterwards if you must. In practice, we’d give Server Core 2 GB and Desktop Experience 4 GB.

Downloading Windows Server 2025

The Microsoft Evaluation Center offers a free 180-day evaluation ISO. It includes Standard and Datacenter.

Install the evaluation on a VM or on bare metal and run it for six months. That shows if it fits your environment.

When the 180 days are up, buy a key and activate. Or use DISM to convert the evaluation to a licensed edition, with no wipe.

A retail key activates the evaluation later.

One warning: after the evaluation expires, the server shuts itself down every hour.

At first glance it looks like a power or hardware fault.

It’s just a forgotten evaluation. We’d put the expiry date in the calendar.

How to upgrade to Windows Server 2025

The upgrade runs in place and in one step. That single-step path is the best thing about this release.

Older releases were slower here. An in-place upgrade reached at most two versions back. So an older file server often went through an intermediate release first. Waits, reboots, checks.

A whole Saturday could go on one server.

1. Take a full backup or a VM checkpoint, and note the current edition.
2. For domain controllers, run the two ADPREP lines below from the 2025 media first.
3. On VMware guests, update VMware Tools before you start, or the upgrade can stall.
4. On physical servers, check firmware and drivers against your vendor’s compatibility list.
5. Run setup.exe from the mounted ISO and choose to keep files, settings and apps. The feature update from Windows Update does the same job.
6. Activate with your Windows Server 2025 key after the first sign-in.

adprep /forestprep
adprep /domainprep

A typical result of skipping ADPREP on a test DC: replication failures within hours.

Hyper-V guests update their integration components by themselves. Dell and HPE publish compatibility lists, and so does Lenovo.

An evaluation copy converts to full Standard or Datacenter with DISM, and no reinstall is needed. Our DISM activation guide for Windows Server covers every step.

Our Windows Server 2012 R2 page covers those older machines. If one is still running, we’d upgrade it in place to 2025. That’s the fastest way back to a patched server.

What the Windows Server 2025 release removed

If any of these still live in your environment, find alternatives before you upgrade. Not after.

A second group still ships, but Microsoft has marked it for later removal.

Microsoft will probably pull some of these from the next major release. So we’d start planning replacements now.

WINS has been on that list since Server 2022, so plan the move to DNS.

By the way, 32-bit applications still run through WOW64. Only the operating system itself is 64-bit only, as it has been since 2008 R2.

Compared with Server 2022

For most environments the 2025 release is the better choice.

We also set it beside the older releases in our comparison of the three current releases.

The security defaults alone justify the upgrade for most shops.

The two things admins mention most on Reddit are Credential Guard by default and required SMB signing.

On 2022, both needed manual Group Policy work, and most shops never did it. Now it’s automatic.

Our explainer on Windows vs Windows Server covers how the server system differs from the desktop one.

Common mistakes with Windows Server 2025

• Buying Standard for a host that will carry a dozen VMs.
• Forgetting CALs, or RDS CALs for Remote Desktop users.
• Upgrading a domain controller without ADPREP.
• Leaving VMware Tools outdated before the upgrade.
• Giving a VM 1,024 MB of RAM for setup.
• Installing from the original ISO and skipping the cumulative update.
• Finding out about the disabled TLS versions after the migration.
• Forgetting the expiry of an evaluation install.
• Counting on the SMTP Server feature after the upgrade.

Related guides

• Windows 13 Release Date
• Windows 12 Release Date
• Windows Server versions compared

Terms used on this page

Typical Windows Server 2025 rollout problems

Too many Standard stacks

Twelve VMs on one 16-core host. Six Standard stacks at $1,176 each come to $7,056. One Datacenter license lists at $6,771. Count before you buy.

A domain controller without ADPREP

Upgrading a DC first and preparing the forest later. Replication errors follow. Forest prep, domain prep, then setup.

A frozen installer in a VM

No error, no progress. With 1 core and 1,024 MB of RAM setup fails by design. Give it at least 1,280 MB.

A server that shuts down every hour

The 180-day evaluation ran out. A key plus a DISM conversion to Standard or Datacenter stops it.

An app that stops connecting

TLS 1.0 and 1.1 are off by default. Apps that only speak those versions go quiet. Ask the vendor for an update.

SQL Server 2025 release date

Different product, same year in the name. SQL Server 2025, version 17.x, reached general availability at Microsoft Ignite in November 2025, a year after Windows Server 2025.

• Standard edition: up to 32 cores or 4 sockets, 256 GB of buffer pool memory per instance.
• Express edition: databases up to 50 GB.
• Web edition: discontinued.
• New free Standard Developer and Enterprise Developer editions for test and dev work.

Planning both on one box? Check the app vendor’s list first. If it still names the older release, our SQL Server 2022 Standard key fits. Microsoft’s What’s new in SQL Server 2025 has the full list.

Windows Server 2025 editions and sources this page covers