Windows Server hardware requirements
Microsoft's edit ·
Microsoft's commit message in MicrosoftDocs/windowsserverdocs · commit 1e85a31 · +39 −17 lines · also on GitHub
11
---
22
title: Hardware requirements for Windows Server
3
−description: What are the minimum hardware requirements for storage, CPU, network, and memory (RAM) for Windows Server.
3
+description: Lear about the minimum hardware requirements for storage, CPU, network, and memory (RAM) to run Windows Server.
44
ms.topic: article
55
author: xelu86
66
ms.author: alalve
7
−ms.date: 10/22/2024
7
+ms.date: 06/09/2025
88
ms.assetid: 4a8b42d7-9fe5-4efe-9ea1-ace2131fe068
99
zone_pivot_groups: windows-os-version
1010
---
⋯ 5 unchanged lines
1616
Unless otherwise specified, these minimum hardware requirements apply to all installation options (Server Core and Server with Desktop Experience) for both Windows Server Standard and Windows Server Datacenter editions.
1717
1818
> [!IMPORTANT]
19
−> The highly diverse scope of potential deployments makes it unrealistic to state recommended hardware requirements that would be generally applicable. Consult documentation for each of the server roles you intend to deploy for more details about the resource needs of particular server roles. For the best results, conduct test deployments to determine appropriate hardware requirements for your particular deployment scenarios.
19
+> The highly diverse scope of potential deployments makes it unrealistic to state recommended hardware requirements that would be applicable. Consult documentation for each of the server roles you intend to deploy to learn more about the resource needs of particular server roles. For the best results, conduct test deployments to determine appropriate hardware requirements for your particular deployment scenarios.
2020
2121
## Components
2222
⋯ 29 unchanged lines
5252
5353
**Minimum**:
5454
55
−- 512 MB for Server Core
56
−
5755
:::zone pivot="windows-server-2025"
5856
57
+- 2 GB for Server Core
58
+
5959
- 2 GB for Server with Desktop Experience, 4 GB recommended
6060
61
+- ECC (Error Correcting Code) type or similar technology for physical host deployments
62
+
63
+> [!IMPORTANT]
64
+> Attempting to install Windows Server in a virtual machine configured with the minimum supported hardware parameters (1 processor core and 512 MB RAM) results in a failed installation.
65
+>
66
+> To prevent this issue, perform one of the following actions:
67
+>
68
+> - Allocate 1,280 MB RAM or more to the virtual machine on which you intend to install this release. Once setup is complete, you can change the allocation as little as 1,024 MB RAM, depending on the actual server configuration. If you've modified the boot image for the setup with addition languages and updates, you might need to allocate more than 1,280 MB RAM in order to complete the installation.
69
+> - Interrupt the boot process of this release on the virtual machine with the keyboard combination `SHIFT+F10`. In the command prompt that opens, use `diskpart.exe` to create and format an installation partition. Run `wpeutil createpagefile /path=C:\pf.sys` (assuming the installation partition you created was C:\\). Then close the command prompt and proceed with the installation.
70
+
6171
::: zone-end
6272
6373
:::zone pivot="windows-server-2022,windows-server-2019,windows-server-2016"
6474
65
−- 2 GB for Server with Desktop Experience
75
+- 1 GB for Server Core
6676
67
−::: zone-end
77
+- 2 GB for Server with Desktop Experience
6878
6979
- ECC (Error Correcting Code) type or similar technology for physical host deployments
7080
7181
> [!IMPORTANT]
72
−> Attempting to install Windows Server in a virtual machine configured with the minimum supported hardware parameters (1 processor core and 512 MB RAM) will result in a failed installation.
82
+> Attempting to install Windows Server in a virtual machine configured with the minimum supported hardware parameters (1 processor core and 512 MB RAM) results in a failed installation.
7383
>
74
−> To prevent this issue, perform one of the following:
84
+> To prevent this issue, perform one of the following actions:
7585
>
76
−> - Allocate more than 800 MB RAM to the virtual machine on which you intend to install this release. Once the setup has completed, you can change the allocation to as little as 512 MB RAM, depending on the actual server configuration. If you've modified the boot image for the setup with addition languages and updates, you may need to allocate more than 800 MB RAM in order to complete the installation.
86
+> - Allocate 800 MB RAM or more to the virtual machine on which you intend to install this release. Once setup is complete, you can change the allocation as little as 800 MB RAM, depending on the actual server configuration. If you've modified the boot image for the setup with addition languages and updates, you might need to allocate more than 800 MB RAM in order to complete the installation.
7787
> - Interrupt the boot process of this release on the virtual machine with the keyboard combination `SHIFT+F10`. In the command prompt that opens, use `diskpart.exe` to create and format an installation partition. Run `wpeutil createpagefile /path=C:\pf.sys` (assuming the installation partition you created was C:\\). Then close the command prompt and proceed with the installation.
7888
89
+::: zone-end
90
+
7991
# [Storage](#tab/storage)
8092
8193
Computers that run Windows Server must include a storage adapter that is compliant with the PCI Express architecture specification. Servers classified as hard disk drives must not use Parallel Advanced Technology Attachment (PATA) for persistent storage devices. Windows Server also doesn't allow PATA, Advanced Technology Attachment (ATA), Integrated Drive Electronics (IDE), and Enhanced Integrated Drive Electronic (EIDE) for boot, page, or data drives.
⋯ 5 unchanged lines
8799
- 32 GB of space
88100
89101
> [!NOTE]
90
−> Be aware that 32 GB should be considered an *absolute minimum* value for successful installation. This minimum should allow you to install Windows Server 2022 or later using the Server Core installation option with the Web Services (IIS) server role. A server in Server Core mode is ~4 GB smaller than the same server using the **Server with Desktop Experience** installation option.
102
+> 32 GB should be considered an *absolute minimum* value for successful installation. This minimum should allow you to install Windows Server 2022 or later using the Server Core installation option with the Web Services (IIS) server role. A server in Server Core mode is ~4 GB smaller than the same server using the **Server with Desktop Experience** installation option.
91103
>
92
−> The system partition will need extra space for any of the following circumstances:
104
+> The system partition needs extra space for any of the following circumstances:
93105
>
94106
> - If you install the system over a network.
95
−> - Computers with more than 16 GB of RAM will require more disk space for paging, hibernation, and dump files.
107
+> - Computers with more than 16 GB of RAM requires more disk space for paging, hibernation, and dump files.
96108
97109
# [Network](#tab/network)
98110
⋯ 11 unchanged lines
110122
111123
---
112124
125
+## Secured-Core server requirements
126
+
127
+Secured-core is a set of integrated hardware, firmware, driver, and operating system (OS) security features that provide enhanced protection against advanced threats. Secured-core systems deliver security that starts before the OS boots and continues throughout system operation. Secured-core server features are available in Windows Server 2019 and later. To deploy a Secured-core server, your device must meet these additional requirements:
128
+
129
+- **DMA Remapping (IOMMU)**: Support for *Intel VT-d* or *AMD-Vi* is required to ensure secure and efficient management of direct memory access (DMA) by devices, safeguarding against unauthorized memory access.
130
+
131
+- **Kernel DMA Protection**: The system must have opt-in capability for Kernel DMA Protection, which helps prevent attacks that exploit external peripherals to gain unauthorized access.
132
+
133
+- **DRTM (Dynamic Root of Trust for Measurement)**: This feature is needed to ensure a secure boot process by verifying the integrity of the system's startup environment, protecting against firmware-based attacks.
134
+
113135
## Other requirements
114136
115137
There are other hardware requirements to consider depending on your scenario:
116138
117
−- DVD drive (if you intend to install the operating system from DVD media)
139
+- DVD drive (if you intend to install the OS from DVD media)
118140
119141
The following items are only required for certain features:
120142
⋯ 1 unchanged line
122144
123145
- Trusted Platform Module (TPM)
124146
125
−- Graphics device and monitor capable of Super VGA (1024 x 768) or higher-resolution
147
+- Integrated or dedicated graphics and monitor capable of Super VGA (1024 x 768) or higher-resolution
126148
127
−- Keyboard and Microsoft mouse (or other compatible pointing device)
149
+- Keyboard and mouse (or other compatible pointing device)
128150
129151
- Internet access (fees might apply)
130152
⋯ 2 unchanged lines
133155
>
134156
> - Hardware-based TPMs must implement version 2.0 of the TPM specification.
135157
> - TPMs that implement version 2.0 must have an EK certificate that is either pre-provisioned to the TPM by the hardware vendor or be capable of being retrieved by the device during the first boot.
136
−> - TPMs that implement version 2.0 must ship with SHA-256 PCR banks and implement PCRs 0 through 23 for SHA-256. It is acceptable to ship TPMs with a single switchable PCR bank that can be used for both SHA-1 and SHA-256 measurements.
158
+> - TPMs that implement version 2.0 must ship with SHA-256 PCR banks and implement PCRs 0 through 23 for SHA-256. It's acceptable to ship TPMs with a single switchable PCR bank that can be used for both SHA-1 and SHA-256 measurements.
Microsoft's Markdown source from MicrosoftDocs/windowsserverdocs, © Microsoft Corporation, under CC BY 4.0. Changed lines with up to 3 unchanged lines around each; ChangeIntel kept this copy 10 Oct 01:29 UTC. The commit date is when the source changed, which can be hours or days before Learn published it.