Windows Server Installation: Step by Step Guide for 2026 Full Setup Tutorial

To install Windows Server in 2026, download the correct Windows Server 2025 ISO or use installation media supplied through your organization’s licensing channel. Back up the target server, confirm that the hardware and storage controller are supported, create a bootable USB drive, and boot the server in the appropriate firmware mode. In Windows Setup, choose the language and keyboard, select Install Windows Server, choose the licensed edition and installation option, accept the terms, select the destination disk, and start the installation. After the automatic restarts, set the local Administrator password, install updates, configure networking, activate Windows Server, and add only the roles the server needs.

Windows Server 2025 is Microsoft’s current Long-Term Servicing Channel (LTSC) release. Microsoft also lists Windows Server, version 23H2 as the latest Annual Channel release, which is aimed more at container and microservice innovation than traditional long-lived infrastructure. For most organizations planning a conventional file server, domain controller, application server, or virtualization host, this guide focuses on Windows Server 2025 LTSC.

Important: A clean installation deletes the selected operating-system partition and can destroy data. Confirm the disk number and backup status before you click Install.

What you should decide before installing

A successful Windows Server deployment starts before the machine boots from the ISO. Decide what the server will do, where it will run, and how it will be managed.

1. Choose the deployment method

You can install Windows Server on physical hardware, in a virtual machine, or through a cloud provider. The installation screens are similar, but the preparation is different.

A physical installation requires compatible firmware, storage and network drivers, and access to the server console. A virtual-machine installation requires enough virtual CPU, RAM and disk capacity for both the guest operating system and its workload. A cloud deployment usually uses a provider image rather than manually booting from a USB drive.

This article covers a local clean installation from USB or DVD. For Azure, use the provider’s Windows Server image and deployment workflow instead of treating the Azure VM like a physical server.

2. Select the edition

Windows Server 2025 has two primary editions:

•Standard: Suitable for physical servers and environments with limited virtualization. Microsoft describes the licensed virtualization entitlement as two virtual machines plus one Hyper-V host per fully licensed server.

•Datacenter: Intended for highly virtualized or data-center environments. It includes unlimited virtualization rights when correctly licensed and provides capabilities intended for larger-scale deployments.

The edition must match your license, product key, subscription, and virtualization plan. Microsoft states that Client Access Licenses (CALs) are required for each user or device accessing a licensed server, subject to the applicable licensing terms. Confirm licensing with Microsoft or your reseller before deploying the server in production.

Do not select an edition simply because it has more features. If you need two or fewer Windows Server virtual machines on a properly licensed host, Standard may be sufficient. Datacenter is generally the better fit when the host will run many Windows Server VMs or when you require Datacenter-specific features.

3. Choose Server Core or Desktop Experience

Windows Server Setup offers two installation options:

•Server Core: A smaller installation with no local graphical desktop. It is managed with PowerShell, Windows Admin Center, Server Configuration tool, or remote administration tools. It normally has a smaller footprint and a reduced local attack surface.

•Server with Desktop Experience: Includes the full graphical interface and local management tools. It is easier for administrators who need a GUI on the server or who are supporting software that requires local graphical components.

Server Core is a strong default for a dedicated infrastructure role that will be managed remotely. Desktop Experience can be more practical for a first deployment, a server that requires local GUI administration, or an application whose vendor specifically requires it. This choice is made during installation and cannot be changed later without reinstalling Windows Server.

Windows Server 2025 requirements and preparation checklist

Microsoft notes that actual requirements depend on the installed roles, applications, storage design, and deployment model. Its published minimums are not performance recommendations. A file server, domain controller, SQL Server host, and Hyper-V host can need very different hardware.

Minimum requirements

For a basic installation, plan for the following Microsoft minimums:

•A 1.4 GHz 64-bit processor compatible with the x64 instruction set and required CPU features such as NX/DEP, CMPXCHG16b, LAHF/SAHF, PrefetchW, and Second Level Address Translation.

•At least 2 GB of RAM for Server Core.

•At least 2 GB of RAM for Server with Desktop Experience, with 4 GB recommended by Microsoft.

•32 GB of system-partition space as an absolute minimum for a successful Server Core installation in the scenarios Microsoft describes. Leave considerably more space for updates, logs, applications, paging files, and recovery tools.

•A PCI Express-compliant storage adapter. Legacy PATA, ATA, IDE, and EIDE devices are not supported for Windows Server boot, page, or data drives.

•An 8 GB or larger USB flash drive for installation media, or a dual-layer DVD and compatible optical drive if using DVD media.

For a virtual machine, do not configure the guest with only the smallest theoretical memory values. Microsoft warns that setup can fail with very low VM memory. Allocate at least 1,280 MB during installation for the affected current configuration, and provide additional memory if the image contains extra languages or updates. In practice, allocate more than the minimum for a stable production VM.

Practical recommendations

For production, use hardware or a VM configuration with enough headroom for the planned role. An SSD or enterprise NVMe device will generally provide a better experience than a small, slow disk. Use ECC memory in physical server deployments where supported, and size RAM for the operating system, file cache, applications, Hyper-V guests, and backup agents.

Check the server manufacturer’s Windows Server 2025 support matrix. Download storage, RAID, network, chipset, and firmware updates before starting. If the server uses a RAID controller or a specialized HBA, store its Windows Server driver on a second USB drive so Setup can load it if the installation disk is not detected.

Secure Boot, TPM 2.0, UEFI, and virtualization extensions are not identical requirements for every basic installation. They are required for certain security features and secured-core configurations. Microsoft’s secured-core requirements include TPM 2.0, Secure Boot, virtualization-based security support, DMA remapping, kernel DMA protection, and DRTM capability. Enable the features required by your security baseline and workload, but do not assume that a missing TPM is the explanation for every installation failure.

What to prepare before booting

Prepare these items before you begin:

1.A supported Windows Server 2025 ISO from Microsoft, your OEM, Visual Studio subscription, or your volume licensing channel.

2.A valid product key, subscription entitlement, or evaluation plan.

3.A verified backup or image of any data on the target disk.

4.The server name, intended IP address, subnet mask or prefix, default gateway, DNS servers, time zone, and domain plan.

5.Storage-controller and network drivers, if the hardware needs them.

6.A bootable USB drive or DVD.

7.A maintenance window if the system is replacing an existing server.

8.A documented rollback plan.

Microsoft’s evaluation ISO provides Standard and Datacenter choices and both Server Core and Desktop Experience options. The evaluation edition expires after 180 days and must be activated over the internet within the first 10 days to avoid automatic shutdown. Do not use an evaluation image as an unplanned production license.

How to create Windows Server installation media

Option A: Use a bootable USB drive

The simplest method is to prepare an empty USB flash drive with at least 8 GB of capacity and copy the mounted ISO contents to it using Microsoft’s documented method or a trusted media-creation utility.

Before writing the drive, verify that you have selected the correct USB device. Media-creation tools can erase the selected drive. After the process finishes, inspect the USB contents and confirm that it contains the Windows setup files, including the boot files. If possible, verify the ISO hash supplied by your licensing or download source before creating the media.

If you are using PowerShell or DiskPart to prepare the media, be deliberate about the disk number. Never run a disk-cleaning command until you have confirmed the USB device by size and model.

Option B: Use a DVD

A dual-layer 8.5 GB DVD is required for the official DVD method. Mount or burn the ISO using a reliable disc-burning tool and select the option to verify the disc after burning. A bad burn can produce confusing errors later, including missing files or an installation that stops while copying files.

Option C: Use virtual media or a remote console

Many physical servers let you mount an ISO through a baseboard-management controller, remote console, or virtual media feature. This avoids physically inserting a USB drive, but it can be slower. Confirm that the remote console is stable and that the server will not lose access to the ISO during the file-copy stage.

Step-by-step Windows Server installation

Step 1: Connect the installation media and open firmware settings

Insert the USB drive, DVD, or virtual ISO, then restart the server. Open the boot menu or BIOS/UEFI setup. Common keys include F2, F10, F12, and Delete, but the correct key depends on the manufacturer.

Select the installation media as the temporary boot device, or move it to the top of the boot order. Use UEFI when your server and deployment standard support it. Keep the firmware mode consistent with the disk layout you intend to use. A UEFI installation normally uses GPT, while a legacy BIOS installation normally uses MBR. Do not switch between modes halfway through troubleshooting without understanding the effect on the disk layout.

If the server contains several disks, disconnect nonessential disks or label them clearly. This reduces the chance of putting the boot files on one disk and the operating system on another.

Step 2: Set language, time, and keyboard options

When Windows Setup starts, choose the language to install, time and currency format, and keyboard layout. Select Next.

These settings affect the initial environment. They do not replace later regional, time-zone, or keyboard configuration, so focus on selecting the values your administrators need during setup.

Step 3: Start Windows Server Setup

On newer Windows Server 2025 media, select Install Windows Server and acknowledge that the selected installation will remove files, apps, and settings. On older or alternate setup media, the screen may say Install now instead.

If Setup asks for a licensing method, select the method that matches your entitlement. A product key is used for OEM, retail, or volume-licensing media. Windows Server 2025 can also present an Azure pay-as-you-go option when its prerequisites are met; use that option only when the server is being deployed under the appropriate Azure licensing arrangement.

Step 4: Select the Windows Server image

Choose the licensed Windows Server 2025 edition and installation option:

•Standard or Datacenter

•Server Core or Server with Desktop Experience

Read the selection carefully. Installing Server Core when you expected the GUI is not a minor display setting; it is a different installation option. Likewise, selecting Datacenter without the correct license can create a licensing problem even if the installation itself completes.

Accept the applicable license terms and continue.

Step 5: Select the destination disk

Choose the disk where Windows Server will be installed. For a new server, select the unallocated space and let Setup create the required partitions, unless your organization has a documented partitioning standard.

For a clean installation on an existing disk, delete only the partitions you have explicitly identified for replacement. Deleting a partition is destructive. If the disk does not appear, choose Load driver and provide the correct storage-controller driver.

Be especially careful when the machine has two or more disks. Microsoft documents a Windows Server 2025 installation issue on some legacy BIOS systems when the operating system is being installed to the second disk as enumerated by BIOS. In that situation, confirm which disk the firmware treats as the primary disk, or use a supported UEFI/GPT design.

Select Next or Install to begin copying the files.

Step 6: Let Setup complete without interruption

Windows Setup will copy files, expand the image, install features, and restart the server several times. This is expected. Do not remove the installation media too early, press keys that boot the process from the beginning, or power off the server while Setup is working.

If the system repeatedly returns to the first Setup screen, remove the USB drive after the first reboot or select the local disk from the boot menu. If it stops at a blank screen or reboots continuously, check firmware settings, storage drivers, memory, and installation-media integrity before trying random partition changes.

Step 7: Set the Administrator password and sign in

At the first-login screen, set a long, unique local Administrator password. Store it in your organization’s approved password vault. Do not reuse a domain password or leave the local Administrator account with a temporary password.

Sign in locally or through the remote console. On Server Core, the command prompt and Server Configuration tool are normal; the absence of a desktop does not mean installation failed.

First configuration after installation

A newly installed operating system is not ready for production simply because the desktop or command prompt appears. Complete the following sequence before placing the server on a live network.

1. Install cumulative updates and reboot

Open Windows Update and install the latest servicing stack, cumulative updates, security updates, and approved driver updates. Reboot when required, then check again. A newly installed ISO can be months behind the current patch level.

Windows Server 2025 includes newer security and hybrid-management capabilities. Features such as Azure Arc-enabled Hotpatch have their own prerequisites and may be preview features, so verify their current support status before promising reboot-free patching in a production design.

2. Rename the server

Use a clear naming standard such as DC01, FILE01, APP01, or HV01. Avoid changing the name after installing a domain controller or binding applications to the old name.

From PowerShell, a basic example is:

Plain Text

Rename-Computer -NewName “FILE01” -Restart

Replace the name with the value approved for your environment.

3. Configure a stable network identity

Servers that provide infrastructure services normally need a stable IP address. Configure the address, prefix or subnet mask, default gateway, DNS servers, and VLAN according to your network plan. Avoid using public DNS servers on a domain controller; internal DNS is central to Active Directory name resolution.

You can inspect the current configuration with:

Plain Text

Get-NetIPConfiguration Get-NetAdapter

Do not assign a static address that is already in use. Test connectivity to the gateway, internal DNS, required management hosts, and the internet if your update or activation design requires it.

4. Set the time zone and verify time synchronization

Correct time matters for logs, certificates, scheduled tasks, Kerberos authentication, and troubleshooting. Set the time zone and verify that the server is synchronizing with the intended time source.

A domain member should normally follow the domain time hierarchy. A domain controller should be configured according to the organization’s Active Directory time design rather than pointed casually at a random time server.

5. Activate Windows Server

Activation depends on how you obtained the software: retail, OEM, volume licensing, subscription, Azure, or evaluation. Confirm activation in Settings, System, or with the appropriate licensing commands for your environment. Do not publish a product key in screenshots, tickets, scripts, or public documentation.

6. Install only the required roles and features

Use Server Manager, PowerShell, or Windows Admin Center to add roles. Common examples include:

•Active Directory Domain Services (AD DS)

•DNS Server

•DHCP Server

•File and Storage Services

•Hyper-V

•Internet Information Services (IIS)

•Failover Clustering

A smaller role footprint is easier to secure and maintain. Do not install every role “just in case.” Document each role, its dependencies, its owner, its backup method, and its patching window.

7. Configure security and management

Enable the security baseline approved for your organization. Restrict inbound firewall rules, disable unnecessary services, use separate administrator accounts, and limit RDP exposure. Prefer management through a private network, VPN, Windows Admin Center, or other controlled administration path rather than exposing RDP directly to the public internet.

Windows Server 2025 introduces security changes including Credential Guard behavior on qualifying devices and additional Active Directory protections. Test security-policy changes with existing applications and legacy systems before applying them across a domain.

8. Back up and test recovery

Configure a supported backup solution for the operating system, application data, system state, and virtual machines as appropriate. A backup is not complete until you have tested restoration. Record where recovery media, encryption keys, credentials, and application-specific recovery instructions are stored.

Optional: Install Active Directory Domain Services

If this server will become a domain controller, plan DNS, domain naming, replication, time synchronization, recovery, and placement before promotion. Do not promote the first domain controller as an experiment on a production network.

Install the role with PowerShell:

Plain Text

Install-WindowsFeature AD-Domain-Services -IncludeManagementTools

Then use Server Manager or the AD DS deployment tools to create a new forest or add the server to an existing domain. In a production environment, confirm the forest and domain functional-level plan, DNS delegation, replication topology, backup strategy, and privileged-access controls before promotion.

Windows Server 2025 includes Active Directory improvements, but newer capabilities may have forest-wide compatibility requirements. For example, Microsoft documents a 32K database-page option and related functional-level considerations. Do not enable a new AD feature without checking the compatibility of every domain controller and forest component.

Common Windows Server installation problems and fixes

“The drive is not detected”

The installer may not include the driver for a RAID controller, HBA, NVMe device, or virtual storage controller. Download the driver from the hardware or hypervisor vendor, extract it to a separate USB drive, and select Load driver in Setup. Also check whether the storage controller is configured in the expected RAID, HBA, or AHCI mode.

“Windows Server installation has failed”

Common causes include corrupted media, a failing USB drive, an unsupported storage controller, a UEFI/GPT and BIOS/MBR mismatch, insufficient VM memory, or selecting the wrong disk. Recreate the media, verify the ISO, update firmware, load the correct driver, and inspect the disk layout. Do not repeatedly wipe the disk before identifying the cause.

Setup stops while copying or expanding files

This often points to bad installation media, an unstable USB connection, faulty RAM, a failing disk, or a hardware-temperature issue. Try a different USB port and known-good media. Run the vendor’s memory and storage diagnostics. If the failure follows the server rather than the USB drive, investigate the hardware.

The server keeps booting back into Setup

The firmware may still be booting from USB. Remove the USB drive after the first restart or select the newly installed disk from the boot menu. If the system cannot boot from the disk, check that the firmware mode matches the disk partition style and that the boot files were created on the intended disk.

Setup reports a GPT or MBR problem

UEFI and legacy BIOS use different boot conventions. If the installation is intended for UEFI, boot the installation media in UEFI mode and use a GPT disk. If the organization requires legacy BIOS, use the corresponding MBR design. Changing firmware mode can make an existing installation unbootable, so decide before partitioning.

The server has no network after installation

Install the correct vendor NIC driver, inspect the adapter in Device Manager or with Get-NetAdapter, and confirm that the cable, switch port, VLAN, and virtual switch are correct. A server can complete OS installation even when its network driver is missing.

A domain join fails

Check DNS first. The client must be able to resolve the domain and locate a domain controller. Verify the server’s time, IP configuration, firewall rules, and credentials. Do not use a public DNS server as the only DNS setting for a domain member.

The evaluation server shuts down

Microsoft states that evaluation versions must be activated over the internet within the first 10 days and expire after 180 days. Convert the evaluation only through a supported licensing path, or reinstall using properly licensed media if conversion is not appropriate.

Windows Server installation best practices

•Use the latest supported Windows Server 2025 media and patch it immediately after installation.

•Prefer UEFI and GPT for new hardware when that matches your organization’s standard.

•Keep the operating system, application data, and backup targets separate where the workload justifies it.

•Use Server Core for roles that can be managed remotely and Desktop Experience only when its GUI or application compatibility is needed.

•Never guess which disk is safe to erase.

•Keep storage and network drivers available offline.

•Use a unique local Administrator password and store it securely.

•Document the server name, IP address, roles, license channel, firmware mode, disk layout, and recovery method.

•Test updates and security policies in a lab or pilot group before applying them to critical servers.

•Monitor CPU, memory, storage latency, disk health, event logs, backup jobs, and certificate expiry after go-live.

Frequently asked questions

Is Windows Server 2025 the latest Windows Server version in 2026?

Microsoft’s release-information page identifies Windows Server 2025 as the current LTSC release. It also identifies Windows Server, version 23H2 as the latest Annual Channel release. Choose the release channel based on the workload and lifecycle you need, not only on the version number.

Can I install Windows Server without a product key?

You can install an evaluation edition or use a supported installation and licensing path that defers key entry, but production use still requires valid licensing and activation. The available licensing screens depend on the media and channel you are using.

Should I choose Server Core or Desktop Experience?

Choose Server Core when the server will be managed remotely and its roles do not require a local GUI. Choose Desktop Experience when local graphical administration or a software vendor’s compatibility requirement justifies it. The choice cannot be switched later without reinstalling.

Does Windows Server 2025 require TPM 2.0 and Secure Boot?

Not every basic installation requires both. TPM 2.0 and Secure Boot are required for certain security capabilities, including secured-core configurations and some features such as BitLocker. Check the requirements for the specific hardware security features you plan to enable.

How much disk space should I allocate?

Microsoft lists 32 GB as an absolute minimum for successful installation in the documented Server Core scenario. That is not a sensible general production allocation. Give the operating system enough space for cumulative updates, logs, paging, dump files, management agents, and role-specific components.

Can I install Windows Server on a virtual machine?

Yes. Provide the guest with compatible virtual hardware, enough memory for Setup and the workload, a supported virtual storage controller, and network connectivity. Hyper-V hosts also need hardware virtualization support and enough memory for the host plus every guest.

What should I do after installing Windows Server?

Install updates, rename the server, configure DNS and a stable IP address, set the time zone, activate the operating system, add only required roles, apply security controls, configure monitoring and backups, and test recovery before production use.

Learn more How to Activate Windows License on a VPS: Full Guide