Windows Server 2022 Hardware Requirements

Before installing Windows Server 2022 on bare metal or a virtual machine, the system has to clear a small set of minimum hardware requirements. They are minimum, not recommended — meeting the floor will let the OS install and boot, but production workloads need more headroom on every dimension. This article walks the per-component minimums and explains the technical concepts behind them, so “does this server meet the requirements” becomes a 30-second answer instead of a vendor-specs hunt.

The minimums apply equally to Server Core and Server with Desktop Experience installs, and to both Standard and Datacenter editions. The two installation modes have one difference (RAM); the two editions differ on licensing and feature set, not hardware floor.

CPU: 1.4 GHz x64 with DEP, NX, SLAT

The processor must be 64-bit (x64), at least 1.4 GHz, and support three security/virtualization features:

• x64 instruction set — native 64-bit operation. Windows Server 2022 has no 32-bit (x86) version. A 64-bit chip can address far more memory and process larger data values per cycle than a 32-bit chip; the entire OS, every driver, every server role assumes 64-bit native execution.
• DEP (Data Execution Prevention) — the CPU enforces that pages of memory marked as data cannot be executed as code. This blocks an entire class of buffer-overflow exploits where an attacker writes shellcode into a data page and tries to jump into it. Required, not optional.
• NX bit (No-Execute bit) — the hardware feature that backs DEP. The page-table entry has a bit that marks the page as non-executable; the CPU faults if execution is attempted. Modern x64 chips all have this; older chips that did not have it cannot run Windows Server 2022 at all.
• SLAT (Second Level Address Translation) — the CPU’s hardware-assisted virtualization page-table walker. SLAT is what makes Hyper-V VMs efficient — without it, the hypervisor has to maintain shadow page tables in software, which is much slower. Intel calls it EPT (Extended Page Tables), AMD calls it RVI / NPT (Nested Page Tables); both qualify.

To verify a CPU meets these on existing hardware, run systeminfo from an elevated prompt and check the Hyper-V Requirements section — it explicitly tests for VM Monitor Mode Extensions, Virtualization Enabled in Firmware, Second Level Address Translation, and Data Execution Prevention Available. All four Yes means you are good.

RAM: 512 MB Server Core, 2 GB Desktop Experience

The minimums:

• Server Core: 512 MB minimum.
• Server with Desktop Experience: 2 GB minimum.

The Desktop Experience version pulls in the GUI, IE / Edge, the Windows Shell, and other components that would otherwise be absent — hence the 4× RAM floor. In practice, run neither at the minimum: even a small AD DC needs 4–8 GB to leave overhead for the directory cache, replication queues, and DNS. A file server hosting moderate I/O wants 16 GB or more. The 512 MB / 2 GB numbers are install-and-boot floors, not workload-running targets.

Microsoft recommends ECC (Error-Correcting Code) memory for physical servers. ECC is RAM with extra parity bits that let the memory controller detect single-bit errors and silently correct them. Without ECC, a cosmic-ray-induced bit flip in a server’s RAM — rare but real — can corrupt data, crash the OS, or worse, silently produce wrong results that look correct. ECC is standard on server-grade DIMMs and on enterprise platforms (Intel Xeon, AMD EPYC, ARM-server). Consumer hardware usually lacks ECC.

Storage: 32 GB Base, +4 GB for GUI

The system disk must have at least 32 GB free for a base install. The Desktop Experience adds another 4 GB on top. Two important caveats:

• RAM > 16 GB requires more disk space. Three Windows files scale with RAM:
  • pagefile.sys — the page file. By default, sized at “system managed” which scales roughly with RAM. On a server with 64 GB RAM, expect 16–64 GB of page file depending on memory pressure profile.
  • hiberfil.sys — the hibernation file. Sized at roughly 75% of RAM by default. Server installs almost never need hibernation, so a common server-config step is to disable it: powercfg -h off reclaims that space.
  • Memory dump files (%SystemRoot%\Memory.dmp, mini-dumps) — produced when the OS crashes. A complete-memory-dump can be the size of physical RAM; mini-dumps are usually a few hundred KB.
• 32 GB is install-floor, not production-floor. Logs, Windows Update download cache, and any installed roles (DNS, AD DS, IIS) push real disk usage well past 32 GB during normal operation. Plan 80–100 GB minimum for a real C: drive on a production DC.

Network: 1 Gbps Ethernet, PCIe-Compliant

The NIC must:

• Be at least 1 Gigabit Ethernet (1 Gbps). 100 Mbps NICs no longer meet the requirement — reasonable, since 1 Gbps has been standard on every motherboard for over a decade.
• Be PCI Express compliant. Built-in NICs always are; add-in cards on a modern server use PCIe slots. Older PCI / PCI-X cards are not supported.

PCI Express (PCIe) is the high-speed serial bus that connects expansion cards to the motherboard. Bandwidth scales with the version (PCIe 3.0, 4.0, 5.0) and the number of lanes (x1, x4, x8, x16). For a 1 Gbps NIC, even PCIe 1.x x1 is more than enough; for 10/25/40/100 Gbps NICs, you want PCIe 3.0 x4 or higher. Server motherboards typically ship with multiple PCIe slots specifically to accommodate add-in NICs and storage controllers.

For redundancy and performance, production deployments usually have at least two NICs — one for management, one for client traffic, or paired in a NIC team / SET (Switch Embedded Teaming) configuration. Single-NIC servers are fine for labs, not for production.

TPM: Required for BitLocker, Optional Otherwise

A TPM (Trusted Platform Module) is a small dedicated chip on the motherboard that securely stores cryptographic keys. It does not store the keys on the system disk — it stores them inside the TPM itself, where they cannot be read by software (only used by the TPM to perform crypto operations). Even physical theft of the disk does not expose the keys.

TPM is optional for installing Windows Server 2022 in general but required for several specific features:

• BitLocker Drive Encryption — the TPM seals the volume encryption key against the boot configuration, so the disk only decrypts on the original machine and only if boot has not been tampered with.
• UEFI Secure Boot measurement — the TPM measures each stage of the boot process and stores the hashes in PCRs (Platform Configuration Registers). Used for boot integrity attestation.
• Credential Guard / Device Guard — the TPM is part of the trusted-boot chain that protects credential isolation from kernel-mode attacks.
• Virtualization-Based Security (VBS) — uses the TPM for key sealing and attestation.

Modern servers ship with a TPM 2.0 by default. Older hardware may have TPM 1.2 (still supported, less feature-rich) or no TPM (BitLocker can run without a TPM but has to fall back to a USB key or password at every boot, which is operationally awful). For new deployments, TPM 2.0 is what to look for.

Other Optional Items

• Internet access. Required to download Windows updates and to activate the OS license over KMS / MAK / Azure Connect. Servers without internet access can be activated via VAMT or pre-shared MAK keys, but it is one more step.
• DVD drive or USB stick. Required if you are installing on a physical server from media. Most modern servers have BMC virtual media (iDRAC, iLO, IPMI) that mounts an ISO over the network, eliminating the need for physical media.
• The official Windows Server 2022 ISO. Download from the Microsoft Evaluation Center for evaluation versions; from the Volume Licensing Service Center for licensed copies. The ISO mounts directly in any hypervisor (Hyper-V, VMware, KVM) for VM installs.

The Practical Reality vs the Documented Minimum

Microsoft’s minimums are install-and-boot floors. The hardware that will actually run a real workload comfortably is several times more expensive on every dimension:

The minimums are useful when judging whether legacy hardware can run the OS at all, or for lab VMs where you are squeezing many guests onto a host. For real production, work backwards from the workload — an AD DC, a file server, a Hyper-V host all have very different sizing recipes — and the minimums become a sanity check rather than a target.

Conclusion

Windows Server 2022 minimums: 64-bit 1.4 GHz CPU with DEP/NX/SLAT, 512 MB or 2 GB RAM (Core / Desktop), 32 GB disk plus 4 GB more for the GUI, 1 Gbps NIC, optional TPM (required for BitLocker). They are install-and-boot floors, not production sizing. The CPU requirements are the strict bar — any chip from the last decade meets them — while RAM and disk minimums are exceeded by every real production workload. Use the minimums to confirm legacy hardware can run the OS at all; use workload-based sizing for real deployments. Pair this with the Install Windows Server 2022 in a VM walkthrough and the post-installation configuration checklist for the practical follow-up.