Making the Switch to UEFI

The most prominent reason for thinking about booting through UEFI instead of BIOS is the availability of large drives. BIOS requires a MBR (Master Boot Record) formatted drive which is inherently limited to 2 TiB. But there are more very good reasons for making the switch. In this article I will provide a brief comparison of BIOS and UEFI before explaining how to create bootable devices for UEFI and install Windows on an UEFI system.

Why the BIOS is Outdated

The Basic Input / Output System (BIOS) has been around since the rise of the Personal Computer (PC). It provides a standardized interface to hardware. Only through those mechanism can modern operating systems be booted from hard disks and removable mediums. The Master Boot Record (MBR) is the partitioning scheme necessary for the BIOS to understand partitions and boot from them.

The Unified Extensible Firmware Interface (UEFI) requires a GUID Partition Table (GPT) to boot from a device. This partitioning scheme is necessary to support large drives beyond the limitation mentioned above.

From a technical point of view, the support for large drives is only one of many advantages offered by UEFI. Instead of using a 512 byte boot sector, UEFI accepts boot loaders in files placed a the FAT formatted boot volume. Also, the CPU is able to run boot loaders in protected mode whereas the BIOS forces the CPU to remain in real mode and requires it to switch into protected mode later which is a time consuming task and slows down the boot process. In protected mode, the CPU is able to address all of the physical memory and thereby raises the 1MB limit on addressable memory which helps on systems with several Option ROMs for hardware devices.

In the following sections, I will demonstrate how to install Windows on a UEFI system and how to build bootable devices that can be accessed through BIOS as well as UEFI.

Support for UEFI

When you are thinking about giving UEFI a spin you can choose any 64 bit Windows since Windows Server 2008 and Windows Vista SP1. Therefore, all current versions will work.

In addition, you need hardware that already has a UEFI firmware installed. In fact many modern hardware does not come with a legacy BIOS but contains a UEFI firmware with a Compatibility Support Module (CSM) for BIOS. The CSM is required to boot from MBR formatted drives and is necessary to boot into 32 bit operating systems.

You may have to enable UEFI and configure it to run before BIOS in your hardware firmware. Some devices can even disable the CSM to force a system to use UEFI exclusively.

How to Make an UEFI Bootable USB Stick

When creating an installation medium for your favorite Windows you will probably have used the Windows 7 USB/DVD Download Tool provided by Microsoft. Unfortunately, this tool creates a NTFS formatted USB device which will not be recognized because UEFI requires FAT to find the boot file.

An UEFI bootable USB device is created in two easy steps:

  1. Prepare the USB device by formatting it using FAT32
  2. Copy the contents of the Windows ISO to the USB device

Now you have a USB device that will boot on UEFI systems and start the Windows installer. Next, we will prepare the drive for UEFI boot.

Creating a GPT Formatted Drive

If a system was previously booted through BIOS it contains a Master Boot Record (MBR) formatted drive. As UEFI does not recognize MBR due to the inherent limitations, you need to convert the drive to the GUID Partition Table (GPT). Unfortunately, the Windows installer does not offer such an function.

  1. Just after you have started the installation of a supported Windows, open a command prompt by pressing shift-F10 and launching diskpart.exe.
  2. Select the appropriate drive (list disk and select disk n) and remove all partitions (clean)
  3. Convert the drive to GPT: convert gpt
  4. Exit diskpart.exe, close the command prompt and follow the installer to the drive selection. From now on, the installer is able to take care of creating the necessary partitions on the GPT formatted drive.

The drive will contain the following partitions:

Update: Microsoft has described the partition layout for MBR-formatted drives and GPT-formatted drives.

From now on, it will be rather hard to recognize a system booting through UEFI because it does not brag about it. But you will probably notice an improvement in boot times.

Windows To Go for UEFI

Instead of making the switch to UEFI on your precious, primary device, you can also prepare a USB device to boot into Windows To Go – your hard drive is never touched.

Note that this guide is only applicable to BIOS systems because it creates a NTFS formatted partition which is not bootable by UEFI.

Unfortunately, using Windows To Go with UEFI gets slightly more complicated because it requires a two paritions. This rules out most USB sticks because they register as removable drives. Only fixed drives can have more than one partition. I also recommend using a USB 3.0 device (on a USB 3.0 port) because it will making booting a lot faster.

This guide explains how to go about creating a UEFI bootable Windows To Go:

(You can also perform the first four steps from the Disk Management.)

Your USB drive will now be able to boot Windows To Go on UEFI systems.


UEFI on Wikipedia (

Intel: Beyond BIOS (

UEFI and Windows (

UEFI Support and Requirements for Windows Operating Systems (

The EFI Boot Process (

Creating a GPT formatted drive (

How to create a UEFI bootable USB device (


<?xml version='1.0' encoding='utf-8' standalone='yes'?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="offlineServicing">
<component name="Microsoft-Windows-PartitionManager" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="" xmlns:xsi="">
<component name="Microsoft-Windows-PartitionManager" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="" xmlns:xsi="">


<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="oobeSystem">
<component name="Microsoft-Windows-WinRE-RecoveryAgent" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="" xmlns:xsi="">
<component name="Microsoft-Windows-WinRE-RecoveryAgent" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="" xmlns:xsi="">
Feedback is always welcome! If you'd like to get in touch with me concerning the contents of this article, please use Twitter.