The Windows Server 2025 system requirements are a 1.4 GHz 64-bit processor that supports SSE4.2 and POPCNT, 2 GB of RAM, 32 GB of disk space and a gigabit Ethernet adapter. Those are Microsoft's absolute minimums for installation, not a sizing target. This guide explains each requirement, what changed from Server 2022 and how to check existing hardware before you buy a licence.
| Component | Windows Server 2025 minimum | Windows Server 2022 minimum |
|---|---|---|
| Processor | 1.4 GHz 64-bit, NX/DEP, CMPXCHG16b, LAHF/SAHF, PrefetchW, SLAT, SSE4.2 and POPCNT | 1.4 GHz 64-bit, NX/DEP, CMPXCHG16b, LAHF/SAHF, PrefetchW, SLAT |
| RAM (Server Core) | 2 GB | 1 GB |
| RAM (Desktop Experience) | 2 GB, 4 GB recommended | 2 GB |
| Memory type (physical hosts) | ECC or similar | ECC or similar |
| Disk space | 32 GB absolute minimum | 32 GB absolute minimum |
| Storage controller | PCI Express compliant; no PATA/IDE boot or data drives | Same |
| Network | 1 Gbps Ethernet, PCI Express compliant | Same |
| TPM 2.0, UEFI and Secure Boot | Only for specific features (BitLocker, Secured-core, hotpatch) | Only for specific features |
Figures are taken from Microsoft's Windows Server hardware requirements page, which covers Server 2016 to 2025. The main hardware changes in 2025 are the new SSE4.2 and POPCNT instructions and the higher Server Core memory floor.
What are the minimum CPU requirements for Windows Server 2025?
Windows Server 2025 needs a 64-bit x64 processor of at least 1.4 GHz that supports NX and DEP, CMPXCHG16b, LAHF/SAHF and PrefetchW instructions, and Second Level Address Translation (Intel EPT or AMD NPT). New for 2025, the processor must also support the SSE4.2 instruction set and the POPCNT instruction, or setup will not complete.
Clock speed is rarely the issue. The SSE4.2 and POPCNT requirements are what rule out very old hardware, mainly processors from before roughly 2008 to 2011 depending on the vendor and model line. Any server-class Intel Xeon or AMD EPYC system still in a supported warranty period will meet them.
Processor performance depends on cores and cache as much as frequency. Microsoft deliberately does not publish recommended specifications because roles differ so much, so size the CPU for your workload (file serving, Hyper-V, SQL Server, Remote Desktop) rather than for the operating system itself.
How much RAM does Windows Server 2025 need?
Windows Server 2025 needs at least 2 GB of RAM for both Server Core and Server with Desktop Experience, with 4 GB recommended for Desktop Experience. Physical hosts should use ECC (error-correcting) memory or similar technology. These minimums only cover the operating system; every role and application you add needs memory on top.
Virtual machines have one quirk worth knowing. Microsoft warns that a VM configured with 1 processor core and 1,024 MB of RAM fails during installation. Allocate at least 1,280 MB while setup runs; afterwards you can reduce the allocation, depending on the server's configuration.
What we commonly see: small offices running a single file and print server are comfortable on 8 GB, while a host running Hyper-V guests should be sized from the sum of its guests' memory plus headroom for the host. Starting a new physical server on the 2 GB minimum almost always leads to an early memory upgrade.
How much disk space does Windows Server 2025 need?
Windows Server 2025 needs at least 32 GB for the system partition, which Microsoft describes as an absolute minimum that allows a Server Core install with the IIS web server role. A Desktop Experience installation is roughly 4 GB larger, and servers with more than 16 GB of RAM need extra space for paging, hibernation and dump files.

In practice, 32 GB fills up quickly once cumulative updates, logs and the component store grow. A boot volume of 100 GB to 150 GB on SSD storage is a sensible floor for a production server, with data kept on separate volumes.
The storage controller must comply with the PCI Express architecture specification. Windows Server does not allow PATA, ATA, IDE or EIDE for boot, page or data drives, so very old controllers are excluded regardless of disk size.
Does Windows Server 2025 require TPM 2.0 and Secure Boot?
No, Windows Server 2025 does not need TPM 2.0, UEFI or Secure Boot simply to install and run, unlike Windows 11. They are required only for specific features: TPM 2.0 for BitLocker and Secured-core, and UEFI with Secure Boot for Secured-core server and for virtualization-based security, which hotpatching depends on.
That said, treat them as practical requirements on new hardware. When a TPM is used, Microsoft specifies TPM 2.0 with an EK certificate and SHA-256 PCR banks. Secured-core server additionally needs IOMMU (Intel VT-d or AMD-Vi), Kernel DMA Protection and DRTM.
Cause and effect: installing Server 2025 in legacy BIOS mode works today, but it blocks you from enabling virtualization-based security later. Because hotpatching needs VBS, a server built on legacy BIOS cannot use hotpatch without reinstalling in UEFI mode. On Hyper-V, that means choosing a Generation 2 virtual machine from the start.
If you are comparing with desktop rules, our Windows 11 TPM and Secure Boot requirements guide shows how much stricter the client operating system is.
What network adapter does Windows Server 2025 need?
Windows Server 2025 needs an Ethernet adapter capable of at least 1 gigabit per second throughput that complies with the PCI Express architecture specification. Support for PXE network boot and for kernel network debugging (KDNet) is useful for deployment and diagnostics, but Microsoft lists neither as a minimum requirement.
Most current server boards ship with dual gigabit or faster ports, so this is rarely a blocker. If you plan NIC teaming, Switch Embedded Teaming on Hyper-V hosts, or SMB over QUIC for remote file access, check that the adapter's driver is certified for Windows Server 2025 on your vendor's support site.
How do I check if my server meets the Windows Server 2025 requirements?
Check the processor with Microsoft's free Coreinfo tool, confirm installed RAM and disk space in Task Manager or Server Manager, and check firmware mode and Secure Boot in System Information. Coreinfo lists every instruction set the CPU supports, so you can confirm SSE4.2, POPCNT and SLAT before you attempt an install or upgrade.
- Download Coreinfo from Microsoft Sysinternals and extract it.
- Open an elevated Command Prompt in that folder and run
coreinfo64 -accepteula. - Look for an asterisk next to SSE4.2, POPCNT, NX and CX16, and run
coreinfo64 -vto confirm EPT or NPT (SLAT) support. - Run
msinfo32and check BIOS Mode (UEFI or Legacy) and Secure Boot State. - Run
tpm.mscto see whether a TPM is present and its specification version.
For VMs, also confirm in the hypervisor that the guest CPU exposes SSE4.2 and POPCNT. Some VMware and Proxmox clusters use a conservative CPU compatibility mode that hides newer instructions, and setup fails even though the physical host is modern.
Can I run Windows Server 2025 on older hardware?
You can run Windows Server 2025 on older hardware only if the processor supports SSE4.2 and POPCNT, the storage controller is PCI Express based and the system meets the memory and disk minimums. Hardware that passes those checks may still lack vendor-certified drivers, so confirm support with the server manufacturer before upgrading production machines.
Age alone is not the deciding factor. A ten-year-old Xeon server often meets every technical requirement, but its firmware may never receive updates for Secure Boot certificate changes or new drivers. For a server you expect to run until Windows Server 2025 leaves extended support on 14 November 2034, replacing hardware near the end of its warranty is usually the more economical choice.
Advanced nuance: the hardware minimums do not change your licensing count. Windows Server 2025 Standard and Datacenter are licensed per physical core, with a minimum of 8 core licences per processor and 16 per server, so a small single-CPU box and a 16-core server cost the same to license.
Which Windows Server 2025 edition fits my hardware?
Choose Windows Server 2025 Standard for physical servers or light virtualisation, because each fully licensed server covers two virtual machines. Choose Datacenter for heavily virtualised hosts, because it covers unlimited virtual machines on the licensed host. Both editions share identical hardware requirements, so the decision rests on virtualisation and features rather than specifications.
For most small businesses running one or two workloads on a single host, Windows Server 2025 Standard is the natural fit; see the current price on the product page. If you plan to consolidate many VMs onto one machine, Windows Server 2025 Datacenter becomes more cost-effective. Our Standard vs Datacenter vs Essentials comparison covers the licensing detail, and you will also need Windows Server CALs for users or devices that access the server.
Once the hardware is ready, our Windows Server 2025 Standard installation guide walks through setup and activation.
Frequently asked questions
Can Windows Server 2025 run with 1 GB of RAM?
No. Microsoft's minimum for Windows Server 2025 is 2 GB for both installation options, up from 1 GB for Server Core in Windows Server 2022. Virtual machines with 1,024 MB of RAM fail during setup, so allocate at least 1,280 MB to install and then adjust the allocation once the server is running.
Why does Windows Server 2025 setup fail on my old server?
The most common reason is a processor without SSE4.2 or POPCNT support, which Windows Server 2025 now requires. Other causes include a PATA or IDE storage controller and, in virtual machines, a CPU compatibility mode that hides those instructions. Run Coreinfo to confirm what the processor reports before trying again.
Do Server Core and Desktop Experience have different requirements?
Mostly not. Both installation options share the same processor, network and 2 GB memory minimums in Windows Server 2025. The differences are that Microsoft recommends 4 GB of RAM for Desktop Experience and that a Desktop Experience install uses roughly 4 GB more disk space. You cannot switch between the two during an in-place upgrade.
Do I need ECC memory for Windows Server 2025?
Microsoft lists ECC (error-correcting code) memory or similar technology as a requirement for physical host deployments. It protects against silent memory errors that can corrupt data or crash the server. Virtual machines inherit memory protection from the host, so you do not configure ECC inside a VM.
What is the hardware requirement for hotpatching?
Hotpatching on Windows Server 2025 needs virtualization-based security, which at minimum requires UEFI firmware with Secure Boot enabled; on Hyper-V, that means a Generation 2 VM. Outside Azure, the server must also be connected to Azure Arc. The requirement affects how you install the server, so decide before deployment.
Related guides
- Windows Server 2025 vs 2022: what changed
- Windows Server 2025 new features
- Windows Server Standard vs Datacenter vs Essentials
- Convert Windows Server Evaluation to a full licence
Links in this guide
| Link | Type | Why it helps |
|---|---|---|
| Windows Server hardware requirements (Microsoft Learn) | External | Official CPU, RAM, storage and network minimums |
| Coreinfo (Microsoft Sysinternals) | External | Checks SSE4.2, POPCNT and SLAT support |
| Windows 11 TPM and Secure Boot requirements | Internal | Contrast with stricter client requirements |
| Windows Server 2025 Standard | Internal | Licence for physical or lightly virtualised servers |
| Windows Server 2025 Datacenter | Internal | Licence for heavily virtualised hosts |
| Standard vs Datacenter vs Essentials | Internal | Choosing the right edition |
| Windows Server CALs explained | Internal | Access licences needed alongside the server licence |
| Windows Server 2025 Standard installation guide | Internal | Setup and activation once hardware is ready |
