footer-logofooter-logo
Windows Dedicated Servers: How to Choose the Right Version

Windows Dedicated Servers: How to Choose the Right Version

A Windows dedicated server gives you a whole physical machine running Windows Server directly on the hardware — but which version and edition should you run on it? Windows Server 2019, 2022, and 2025 sit at different points on the support timeline, and Standard versus Datacenter changes what you can do with virtualisation. This guide explains what a bare-metal Windows server actually is, when it beats a VPS or cloud instance, and how to pick a version and edition by workload, support window, and licensing — with a side-by-side comparison and links to the right server.

07 juillet 2026

par Jesse Schokker

Windows

Dedicated Servers

Windows Server

Licensing

Loading...

What is a Windows dedicated server?

A Windows dedicated server is a single physical machine, rented by one tenant, running Windows Server directly on the hardware. There is no hypervisor and no other customers sharing the CPU, memory, or NVMe — you get every physical core and predictable, uncontended performance, along with full Administrator access over RDP.

That is the key difference from a Windows VPS or a cloud instance, where you rent a slice of a shared host: another tenant's workload can eat into your I/O, and metered egress makes the monthly bill a moving target. It also matters for licensing: Windows Server is licensed per physical core, so a machine whose cores are entirely yours is the clean case to reason about.

When bare metal beats a VPS or cloud instance

A dedicated Windows server is the right call when you need one or more of the following:

  • Licence-sensitive workloads — SQL Server and Windows Server both bill per core, so a known, fixed physical core count keeps the licence bill predictable and the throughput high.
  • Sustained, predictable load — Active Directory, IIS, and .NET application hosting that would be throttled or billed unpredictably on shared cloud.
  • Raw I/O — local NVMe with no virtualised storage layer in between, which matters for I/O-bound SQL Server queries.
  • GPU and game servers — Windows game servers benefit from consistent frame times and dedicated hardware.
  • Cost stability at scale — a flat monthly price instead of metered egress and IOPS.

If your workload is spiky and mostly idle, a VPS may be more economical. If it is steady, performance-sensitive, or licence-heavy, bare metal usually wins on both performance and total cost.

Choosing a version: the short version

Every currently supported Windows Server version will run your software. The choice is really about support window, feature set, and hardware requirements, not core capability. Here is the quick version:

  • Want the longest support runway and the newest features — hotpatching, SMB over QUIC in Standard, TLS 1.3 by default? Windows Server 2025.
  • Need maximum compatibility with software certified against a proven release, still years of support left? Windows Server 2022.
  • Only pick 2019 if a specific application requires it — its extended support ends in January 2029, so treat it as legacy, not a fresh-deploy default.

Version comparison

VersionReleasedEnd of extended supportStandout featuresWhen to pick
Windows Server 2019Nov 20189 Jan 2029Established, widely certified; older kernelOnly when an app requires it — legacy
Windows Server 2022Aug 202114 Oct 2031Secured-core, TLS 1.3, mature and broadly certifiedMaximum compatibility, proven track record
Windows Server 2025Nov 202414 Nov 2034Hotpatching, SMB over QUIC in Standard, newer kernelLongest runway, newest feature set

Extended support means security updates only — no new features or non-security fixes. All three are still in support today; 2019 is simply closest to the end of its runway.

Windows Server 2025

Windows Server 2025 reached general availability on 1 November 2024 as the current Long-Term Servicing Channel release, with extended support running to 14 November 2034 — the longest runway of the three. On bare metal, the deltas that matter most are:

  • Hotpatching — apply many security updates to running code without a reboot, cutting the number of restart months per year. It is delivered through Azure Arc, and Microsoft's commercial terms for it have shifted since launch, so confirm the current arrangement rather than assuming a fixed fee.
  • SMB over QUIC now ships in Standard and Datacenter, not just Azure Edition — encrypted SMB over UDP 443 without a VPN.
  • TLS 1.3 is enabled by default, plus credential and Active Directory hardening and a newer kernel with performance gains.

Note the raised floor: 2025 wants a newer CPU baseline and more headroom than 2019 did. On a modern dedicated box that is a non-issue, but it is worth knowing if you are matching an older workload to old hardware assumptions.

If reboot-free patching or the longest support window is a priority, this is the version to pick.

Windows Server 2022

Windows Server 2022 is the safe, broadly certified middle ground, with extended support to 14 October 2031. It introduced secured-core server, TLS 1.3, and SMB hardening, and by 2026 it has years of production track record and the widest pool of ISV certifications behind it.

Pick 2022 when a piece of enterprise or third-party software is certified specifically against it, or when you simply want the most-tested current release. You give up 2025's hotpatching and its longer runway, but you gain maturity.

Windows Server 2019

Windows Server 2019 left mainstream support in January 2024 and reaches end of extended support on 9 January 2029. It still receives security updates until then, but it is the oldest supported release: an older kernel, no hotpatching, and SMB over QUIC absent entirely.

Deploy 2019 only when an application explicitly requires it. For anything new, start at 2022 or 2025 so you are not planning a migration inside the first couple of years.

Standard vs Datacenter edition

Version is one axis; edition is the other, and it is mostly about virtualisation rights.

  • Standard grants two operating-system environments per fully-licensed server — in practice the host plus two Windows Server VMs (or two VMs if the host runs only the Hyper-V role). Stacking a second set of core licences over the same cores buys another two VMs.
  • Datacenter grants unlimited Windows Server VMs on the licensed cores, and unlocks the storage features Standard does not have — Storage Spaces Direct and Storage Replica among them.

The crossover is roughly eight to ten Windows VMs per host: below that, restacking Standard is cheaper; above it, Datacenter wins. If you are not virtualising Windows at all and just want a single Windows workload on the metal, Standard is the right call.

Licensing on a dedicated server

Windows Server is licensed per physical core, with a minimum of 8 core licences per processor and 16 per server — not per VM. That is why high-clock, moderate-core CPUs are often the economical pick for Windows workloads: fewer cores to license, more throughput per core.

On dedicated single-tenant hardware you generally have two routes. You can bring your own licence (BYOL) — because the box is fully dedicated, you can typically deploy your own Windows Server licences under Microsoft's Outsourcing Software Management Rights and Flexible Virtualization Benefit, which shared and multi-tenant hosting cannot offer. Eligibility depends on your specific licence and its Software Assurance or subscription status, so confirm those details with your reseller; note that Windows Server itself is not covered by classic License Mobility through Software Assurance. Alternatively, a provider can license the server for you through a SPLA — Microsoft's monthly, per-physical-core model for hosting providers, with no CALs to manage and no up-front purchase. Either way the edition (Standard or Datacenter) is chosen at order.

How to decide

  1. Need the longest support runway and reboot-free patching? Windows Server 2025.
  2. Need certification against a specific, proven release? Windows Server 2022.
  3. Bound to a legacy application that requires it? Windows Server 2019 — and plan the migration.
  4. Running many Windows VMs or want Storage Spaces Direct / Storage Replica? Datacenter edition; otherwise Standard.

Deploying on Serverside

Every Serverside dedicated server can run Windows Server 2022 or 2025, imaged onto bare metal and RDP-ready in under a minute — the hardware is identical, so the version and edition choice is purely about the trade-offs above. You bring your own Windows licence or add one through our SPLA at order, and full Administrator access comes either way. Always-on DDoS mitigation is included on our ASN 55285 network, which matters for internet-facing Windows application and game servers.

Ready to deploy? See our Windows dedicated servers page for configurations and licensing detail, or browse the full dedicated server range. Weighing Windows against Linux? Our Linux distro guide covers the other side of the decision.

Partager l'article

Partager le lien

Jesse Schokker

À propos de l'auteur

Jesse Schokker

Co-founder & CTO, Serverside.com

Jesse is the co-founder and CTO of Serverside.com, where he leads the engineering behind the company's bare-metal cloud — from the ASN 55285 backbone to sub-minute server provisioning. He writes about dedicated servers, operating systems, and running production workloads on bare metal.

Partager l'article

Partager le lien