Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources or documents need attention: 257/260 feeds/APIs · 416/439 docs · checked 21:54 UTC Customize Public modeDiscuss ChangeIntel on Discord

Windows Server hardware requirements

This page's changes and edits · All guidance changes

Microsoft's edit ·

Minor edit

Microsoft's commit message in MicrosoftDocs/windowsserverdocs · commit a399ffa · +9 −7 lines · also on GitHub

⋯ 3 unchanged lines
44 ms.topic: article
55 author: xelu86
66 ms.author: alalve
7 −ms.date: 06/13/2025
7 +ms.date: 06/12/2025
88 ms.assetid: 4a8b42d7-9fe5-4efe-9ea1-ace2131fe068
99 zone_pivot_groups: windows-os-version
1010 ---
⋯ 50 unchanged lines
6161 - ECC (Error Correcting Code) type or similar technology for physical host deployments
6262
6363 > [!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.
64 +> Attempting to install Windows Server in a virtual machine configured with the minimum supported hardware parameters (1 processor core and 1024 MB RAM) results in a failed installation.
6565 >
6666 > To prevent this issue, perform one of the following actions:
6767 >
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.
68 +> - Allocate 1280 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 1024 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 1280 MB RAM in order to complete the installation.
69 +>
6970 > - 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.
7071
7172 ::: zone-end
⋯ 12 unchanged lines
8485 > To prevent this issue, perform one of the following actions:
8586 >
8687 > - 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.
88 +>
8789 > - 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.
8890
8991 ::: zone-end
⋯ 13 unchanged lines
103105 >
104106 > The system partition needs extra space for any of the following circumstances:
105107 >
106 −> - If you install the system over a network.
107 −> - Computers with more than 16 GB of RAM requires more disk space for paging, hibernation, and dump files.
108 +> - If you install the system over a network
109 +> - Computers with more than 16 GB of RAM requires more disk space for paging, hibernation, and dump files
108110
109111 # [Network](#tab/network)
110112
⋯ 11 unchanged lines
122124
123125 ---
124126
125 −## Secured-Core server requirements
127 +## Secured-core server requirements
126128
127129 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 2022 and later. To deploy a Secured-core server, your device must meet these additional requirements:
128130
⋯ 34 unchanged lines
163165 > A TPM chip is required in order to use certain features such as **BitLocker Drive Encryption**. If your computer has a TPM, it must meet these requirements:
164166 >
165167 > - Hardware-based TPMs must implement version 2.0 of the TPM specification.
166 −> - 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.
168 +> - 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.
167169 > - 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.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 20 Oct 21:54 UTC · 257 of 260 readable · 255 fully read · documentation 416/439 current