Windows OS Hub
  • Windows Server
    • Windows Server 2022
    • Windows Server 2019
    • Windows Server 2016
    • Windows Server 2012 R2
    • Windows Server 2012
    • Windows Server 2008 R2
    • SCCM
  • Active Directory
    • Active Directory Domain Services (AD DS)
    • Group Policies
  • Windows Clients
    • Windows 11
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows XP
    • MS Office
    • Outlook
  • Virtualization
    • VMWare
    • Hyper-V
    • KVM
  • PowerShell
  • Exchange
  • Cloud
    • Azure
    • Microsoft 365
    • Office 365
  • Linux
    • CentOS
    • RHEL
    • Ubuntu
  • Home
  • About

Windows OS Hub

  • Windows Server
    • Windows Server 2022
    • Windows Server 2019
    • Windows Server 2016
    • Windows Server 2012 R2
    • Windows Server 2012
    • Windows Server 2008 R2
    • SCCM
  • Active Directory
    • Active Directory Domain Services (AD DS)
    • Group Policies
  • Windows Clients
    • Windows 11
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows XP
    • MS Office
    • Outlook
  • Virtualization
    • VMWare
    • Hyper-V
    • KVM
  • PowerShell
  • Exchange
  • Cloud
    • Azure
    • Microsoft 365
    • Office 365
  • Linux
    • CentOS
    • RHEL
    • Ubuntu

 Windows OS Hub / Windows Server 2016 / Create a Bootable USB Flash Drive for Installation Windows Server 2016

March 21, 2017 Windows Server 2016

Create a Bootable USB Flash Drive for Installation Windows Server 2016

The easiest and the most intuitive way to create a bootable USB Flash Drive to install Windows Server 2016 on a physical server is to use Windows USB/DVD Download Tool. This tool allows to write the existing *.iso image of Windows to a USB drive or stick and make it bootable. However, it formats a drive to NTFS, which is only suitable to install Windows on BIOS systems and is not supported on computers with UEFI. In this article we’ll show how to create a bootable USB Flash Drive  with Windows Server 2016 image without any third party tools.

Note. Unlike BIOS systems that can boot from FAT, FAT32, exFAT or NTFS boot partitions, EFI systems can boot only from FAT32 boot partition.

Depending on the UEFI / BIOS server architecture, you will use one of the following methods of creating an installation USB flash drive.

Contents:
  • UEFI Bootable USB Flash Drive
  • Bootable USB Flash Drive with MBR Partition Table for BIOS and UEFI Architectures
  • The Size of Install.wim is Over 4 GB

Important. Be attentive when following these instructions, check disk paths and disk numbers. Otherwise, you can accidentally format a disk containing some data. A USB flash drive will be formatted in any case and all data will be deleted.

UEFI Bootable USB Flash Drive

If you use a USB flash drive to boot and install Windows Server 2016 on a EFI server, there are the following requirements to the USB flash drive:

  1. Minimum size of the USB stick is 8 GB
  2. Partition table type is GPT
  3. File system type is FAT32

So plug your USB flash drive to your computer (in our example, it is a PC running Windows 10), start the command prompt with the administrator privileges and run DISKPART with the following commands:

list disk

Display the list of the disks. In my case, the USB flash drive has the number 1. Select it:

select disk 1

Clean up its contents:

clean

Transform the partition table to GPT:

convert gpt

Create a new partition (with the size under 16GB):

create partition primary

Tip. If the size of your USB flash drive is over 16GB, create a partition less than 16 GB in size:

create partition primary size=16000

Format this partition to FAT32:

format fs=FAT32 quick
Assign a drive letter to the new partition:

assign letter=M

diskpart convert gpt and format fat32

Exit the diskpart:

exit

Copy the distribution files from the mounted ISO image of Windows Server 2016 to the USB flash drive (suppose that the ISO image is mounted as drive E:\).

xcopy e:\* m:\ /H /F /E

Bootable USB Flash Drive with MBR Partition Table for BIOS and UEFI Architectures

You can create a Windows Server 2016 bootable USB flash drive with the MBR partition table for both BIOS and UEFI systems. There are the following requirements to the USB flash drive:

  • Minimum size of the USB flash drive is 8 GB
  • Partition table type is MBR
  • File system type is FAT32

Also, start a diskpart session and run these commands one by one:

The list of disks in the system:

list disk

Select your USB disk (in my example, it is Disk 1):

select disk 1

Clean it:

clean

Create a new partition. If the flash drive size is under 16 GB:

create partition primary

If it is over:

create partition primary size=16000

Format the flash drive to FAT32:

format fs=FAT32 quick

Make the partition active and assign it the drive letter M:

active
assign letter=M

diskpart mbr fat32 bootable usb stick with windows server 2016

Exit diskpart by running exit command and copy the distribution files to the flash drive:

xcopy e:\* m:\ /H /F /E

The Size of Install.wim is Over 4 GB

If the size of Install.wim is over 4 GB, you won’t be able to copy it to your flash drive since the maximum file size in the file system is limited to 4 GB. In this case, you will have to split the WIM file into several smaller files using DISM:

dism /Split-Image /ImageFile:e:\sources\install.wim /SWMFile:m:\sources\install.swm /FileSize:4096

4 comments
0
Facebook Twitter Google + Pinterest
previous post
Activating Windows Server 2016 with KMS Server
next post
Exchange Error “452 4.3.1 Insufficient system resources”

Related Reading

Fix: The Requested Certificate Template is Not Supported...

January 9, 2023

PowerShell: Unable to Resolve Package Source

December 14, 2022

How to Install and Configure Free Hyper-V Server...

November 22, 2022

How to Enable Maintenance Mode on Exchange Server?

November 16, 2022

How to Disable TLS 1.0 and TLS 1.1...

November 10, 2022

4 comments

Domdy March 22, 2019 - 10:20 am

This method also use with Windows 10 entreprise LTSC?

Reply
admin March 27, 2019 - 8:06 am

Yes, this method of creating bootable USB stick is suitable for Windows 10 as well.

Reply
James January 4, 2020 - 6:39 pm

One thing I’d add, is that if you do need to split install.wim you need to re-run robocopy with the /XF switch to ignore install.wim. Otherwise your copy will bomb out and you won’t get all of the other files. Great write up!

Reply
James January 4, 2020 - 9:15 pm

Sorry, meant if you use robocopy to exclude the files.

Reply

Leave a Comment Cancel Reply

Categories

  • Active Directory
  • Group Policies
  • Exchange Server
  • Microsoft 365
  • Azure
  • Windows 11
  • Windows 10
  • Windows Server 2022
  • Windows Server 2019
  • Windows Server 2016
  • PowerShell
  • VMWare
  • Hyper-V
  • Linux
  • MS Office

Recent Posts

  • Using Previous Command History in PowerShell Console

    January 31, 2023
  • How to Install the PowerShell Active Directory Module and Manage AD?

    January 31, 2023
  • Finding Duplicate E-mail (SMTP) Addresses in Exchange

    January 27, 2023
  • How to Delete Old User Profiles in Windows?

    January 25, 2023
  • How to Install Free VMware Hypervisor (ESXi)?

    January 24, 2023
  • How to Enable TLS 1.2 on Windows?

    January 18, 2023
  • Allow or Prevent Non-Admin Users from Reboot/Shutdown Windows

    January 17, 2023
  • Fix: Can’t Extend Volume in Windows

    January 12, 2023
  • Wi-Fi (Internet) Disconnects After Sleep or Hibernation on Windows 10/11

    January 11, 2023
  • Adding Trusted Root Certificates on Linux

    January 9, 2023

Follow us

woshub.com
  • Facebook
  • Twitter
  • RSS
Popular Posts
  • User Profile Disks on Windows Server 2012 R2 / 2016 RDS
  • “Downloading updates 0%” Issue on Windows Server 2016 and Windows 10
  • Configure Storage Spaces Direct (S2D) on Windows Server 2016
  • Windows XP Can’t RDP to Windows 10 / Server 2012R2/2016 RDS
  • How to See Number of Active User Sessions on IIS site?
  • Windows Server 2016: Workgroup Failover Cluster without Active Directory
  • WSUS Group Policy Settings to Deploy Updates
Footer Logo

@2014 - 2023 - Windows OS Hub. All about operating systems for sysadmins


Back To Top