This blog post explains how to create a bootable USB drive for installing Windows Server 2025 on a physical server. The guide utilizes only the built-in tools available in Windows 10, Windows 11, or Windows Server. The installation process varies slightly depending on your system; it can be installed on either a BIOS system, which uses an MBR disk, or a UEFI-based system, which uses GPT disks. Follow these steps to prepare a USB drive for Windows Server 2025 installation.
Getting ready to create a USB Drive for a Windows Server 2025 Installation
First, you will need to have all the prerequisites in place.
- To download the Windows Server 2025 ISO file, you have various sources available. If you wish to test Windows Server 2025 without a license, you can obtain it from the evaluation center.
- Windows Server Evaluation Center offers options to try and download Windows Server 2025 download or to deploy it in Azure.
- Volume Licensing Service Center, where Volume License customers can download Windows Server 2025.
- An USB drive with at least 8GB size
Windows Server 2025 USB Thumb Drive for UEFI (GPT) systems
To create the USB drive to install Windows Server 2025 on a UEFI (GPT system, you do the following steps:
- The at least an 8GB USB drive has to be formatted in FAT32
- The USB needs to be GPT and not MBR
- You will need to split the wim file using dism since it is larger than 4GB
- Copy all files from the ISO to the USB drive
This is it, and here is how you do it. First, plug in your USB drive to your computer.
Open a PowerShell using the Run as Administrator option. You will need to change the path of the Windows Server 2025 ISO, and you will need to replace the disk number in the script before running the third command and make sure C:\Temp exists. From previous experiences with users, run the script line by line.
REMINDER: The following commands will wipe the USB Drive completely. Backup everything before you run through the PowerShell.
# Define Path to the Windows Server 2025 ISO
$ISOFile = "C:\Temp\WindowsServer2025.iso"
# Create temp diectroy for new image
$newImageDir = New-Item -Path 'C:\Temp\newimage' -ItemType Directory
# Mount iso
$ISOMounted = Mount-DiskImage -ImagePath $ISOFile -StorageType ISO -PassThru
# Driver letter
$ISODriveLetter = ($ISOMounted | Get-Volume).DriveLetter
# Copy Files to temporary new image folder
Copy-Item -Path ($ISODriveLetter +":\*") -Destination C:\Temp\newimage -Recurse
# Split and copy install.wim (because of the filesize)
dism /Split-Image /ImageFile:C:\Temp\newimage\sources\install.wim /SWMFile:C:\Temp\newimage\sources\install.swm /FileSize:4096
# Get the USB Drive you want to use, copy the disk number
Get-Disk | Where BusType -eq "USB"
# Get the right USB Drive (You will need to change the number)
$USBDrive = Get-Disk | Where Number -eq 2
# Replace the Friendly Name to clean the USB Drive (THIS WILL REMOVE EVERYTHING)
$USBDrive | Clear-Disk -RemoveData -Confirm:$true -PassThru
# Convert Disk to GPT
$USBDrive | Set-Disk -PartitionStyle GPT
# Create partition primary and format to FAT32
$Volume = $USBDrive | New-Partition -Size 8GB -AssignDriveLetter | Format-Volume -FileSystem FAT32 -NewFileSystemLabel WS2025
# Copy Files to USB (Ignore install.wim)
Copy-Item -Path C:\Temp\newimage\* -Destination ($Volume.DriveLetter + ":\") -Recurse -Exclude install.wim
# Dismount ISO
Dismount-DiskImage -ImagePath $ISOFile
After that, you can safely remove the USB drive and use it to boot your server from.
Windows Server 2025 USB Thumb Drive for BIOS (MBR) systems
To create the USB drive to install Windows Server 2025 on BIOS (MBR) systems, you can follow these steps:
- The at least an 8GB USB drive has to be formatted in NTFS
- USB drive needs to us MBR
- The partition needs to be set active
- Copy all files from the ISO to the USB Drive
This is it, and here is how you do it. First, plug in your USB drive to your computer.
Open a PowerShell using the Run as Administrator option. You will need to change the path of the Windows Server 2025 ISO, and you will need to replace the disk number in the script before running the third command and make sure C:\Temp exists. From previous experiences with users, run the script line by line.
REMINDER: The following commands will wipe the USB Drive completely. Backup everything before you run through the PowerShell.
# Define Path to the Windows Server 2025 ISO
$ISOFile = "C:\Temp\WindowsServer2025.iso"
# Get the USB Drive you want to use, copy the friendly name
Get-Disk | Where BusType -eq "USB"
# Get the right USB Drive (You will need to change the FriendlyName)
$USBDrive = Get-Disk | Where FriendlyName -eq "Kingston DT Workspace"
# Replace the Friendly Name to clean the USB Drive (THIS WILL REMOVE EVERYTHING)
$USBDrive | Clear-Disk -RemoveData -Confirm:$true -PassThru
# Convert Disk to MBR
$USBDrive | Set-Disk -PartitionStyle MBR
# Create partition primary and format to NTFS
$Volume = $USBDrive | New-Partition -UseMaximumSize -AssignDriveLetter | Format-Volume -FileSystem NTFS -NewFileSystemLabel WS2025
# Set Partiton to Active
$Volume | Get-Partition | Set-Partition -IsActive $true
# Mount ISO
$ISOMounted = Mount-DiskImage -ImagePath $ISOFile -StorageType ISO -PassThru
# Driver letter
$ISODriveLetter = ($ISOMounted | Get-Volume).DriveLetter
# Copy Files to USB
Copy-Item -Path ($ISODriveLetter +":\*") -Destination ($Volume.DriveLetter + ":\") -Recurse
# Dismount ISO
Dismount-DiskImage -ImagePath $ISOFile
After completing these steps, you may safely eject the USB drive and use it to boot your server for the installation of Windows Server 2025. For exmaple you can use this media to install it on a phyiscial server or even on an Intel NUC for Windows Server labs.
Conclusion
I trust this post has been informative. Should you have any inquiries, feel free to ask in the comments section.
Tags: Azure, Cloud, Microsoft, USB, USB Drive, USB media, Virtualization, Windows, Windows Server, Windows Server 2025 Last modified: July 3, 2024
Great post as always. Quick note the link to the Volume License Center is out of date it seems.
Thanks! Will have a look
Thanks for this!
Fyi, you can replace:
$USBDrive = Get-Disk | Where FriendlyName -eq “Kingston DT Workspace”
with
$USBDrive = Get-Disk | Where BusType -eq “USB” | OGV -Passthru
to make it more user-friendly and no longer be reliant on hard coded names/numbers
Thank you, yes this is great. I remember thinking about this, the reason I decided I did it the other way, is that if a customer has multiple USB drives in the computer, I don’t want to format the wrong one by running the command :) (Kind of a safety net
But yes your comment is right!
Thanks for this, I was having problems with the usb image I created.