ThisCalculator

Everyday

EFI System Partition: What It Is & How It Works

Updated · Standard formula, shown below

The EFI System Partition (ESP) is a small, FAT32-formatted partition on a GPT disk that stores the boot loaders, drivers, and data your computer’s UEFI firmware needs to start the operating system. When you press the power button, the UEFI firmware reads the ESP to find and launch the boot loader (like Windows Boot Manager or GRUB), which then loads the OS kernel. Without this partition, a modern UEFI-based computer simply cannot boot.

Background: From BIOS to UEFI

Older computers used a Basic Input/Output System (BIOS) with a Master Boot Record (MBR) disk layout. The BIOS would read the first sector of the disk and execute its code, which then loaded the OS. This worked but had limitations: MBR disks could only address up to 2 TB, and the boot process was rigid and insecure.

Intel introduced the Extensible Firmware Interface (EFI) in the late 1990s, later standardized as UEFI (Unified EFI) by the UEFI Forum. UEFI replaces the BIOS with a more flexible firmware interface. It uses the GUID Partition Table (GPT) instead of MBR, allowing disks larger than 2 TB and up to 128 partitions. The ESP is a core part of this new design—it provides a shared, firmware-accessible storage area for boot loaders and tools, independent of the OS installed on the main partitions.

How the ESP Works

The ESP is formatted with the FAT32 file system (or FAT16 for very small disks, but FAT32 is standard). The UEFI firmware includes drivers for FAT32, so it can read files from the ESP without needing an OS. The partition typically contains a folder named EFI with subfolders for each operating system or vendor, such as EFI\Microsoft\Boot for Windows or EFI\ubuntu for Linux.

When you power on the computer, the UEFI firmware checks the boot order (configured in the firmware settings) and looks for a boot entry that points to a specific file on the ESP, usually \EFI\BOOT\BOOTX64.EFI (the default boot loader) or a vendor-specific path. The firmware loads and executes that file, which then loads the OS kernel. This is why the ESP must be readable by the firmware—if it’s corrupted or missing, the system won’t boot.

How to Identify and Manage the ESP

On Windows, you can see the ESP in Disk Management as a partition labeled “EFI System Partition” with no drive letter (it’s hidden). In Linux, it’s usually mounted at /boot/efi or /efi. You can list it with lsblk or fdisk -l.

Common tasks:

  • Check if you have an ESP: Open Disk Management (Windows) or run sudo parted -l (Linux). Look for a small FAT32 partition (typically 100 MB to 500 MB) with the “EFI System” flag.
  • Mount it (Linux): sudo mount /dev/sda1 /mnt (replace sda1 with your ESP).
  • Back it up: Use dd or a disk imaging tool to copy the entire partition. This can save you if boot files get corrupted.

Never delete or format the ESP unless you are absolutely sure you have a backup and a recovery plan. Doing so will make your system unbootable.

Common Problems and Fixes

“No bootable device found” or “Operating system not found” often indicates the ESP is missing, corrupted, or the firmware can’t find it. This can happen after a failed OS update, accidental deletion, or a disk cloning mistake.

Fixes:

  • Windows: Use the Windows installation media, go to Repair your computer → Troubleshoot → Advanced options → Command Prompt. Then run bootrec /rebuildbcd or use bcdboot C:\Windows to recreate the boot files on the ESP.
  • Linux: Boot from a live USB, mount the ESP and your root partition, then run grub-install or update-grub (depending on your distro).
  • Check firmware settings: Ensure the disk is set to UEFI mode (not Legacy/CSM) and that the ESP is marked as bootable (though GPT doesn’t use the “active” flag like MBR).

If the ESP is corrupted but the data is intact, you can often repair it by copying the boot loader from the OS installation media.

ESP vs. MBR Boot Partition: What’s the Difference?

In MBR/BIOS systems, the boot loader resides in the first sector (boot code) and the first partition (often a small partition for boot files). In UEFI/GPT systems, the ESP replaces both. The ESP is not a “system reserved” partition in the traditional sense—it’s a dedicated, firmware-readable area. The system reserved partition on Windows is actually a separate partition that holds the boot manager and recovery tools, but it’s not the same as the ESP. On a UEFI install, Windows may create both an ESP and a Microsoft Reserved (MSR) partition, but the ESP is the one that matters for booting.

Size and Location: Best Practices

The UEFI specification recommends at least 100 MB, but many systems create 300–500 MB to allow for multiple boot loaders and future updates. For most users, 100 MB is sufficient, but if you plan to dual-boot multiple OSes or use advanced features like BitLocker, a larger ESP (500 MB) is safer. The ESP is usually the first partition on the disk, but it can be anywhere on a GPT disk. It must be a primary partition (not logical) and formatted as FAT32.

If you’re installing Windows on a fresh GPT disk, the installer automatically creates the ESP. For Linux, the installer (like Ubuntu’s) will ask you to create an EFI partition if one doesn’t exist. Always ensure the ESP is at least 100 MB and formatted as FAT32.

Safety: How to Avoid Damaging the ESP

Only modify the ESP when you know what you’re doing. Common mistakes:

  • Deleting the ESP while trying to “clean up” partitions—this instantly makes your system unbootable.
  • Formatting the ESP to NTFS or ext4—the firmware can’t read those, so boot fails.
  • Running out of space—if the ESP is too small, Windows updates may fail to write new boot files. Check free space on the ESP (mount it in Linux or use DiskPart in Windows) and expand it if necessary.

To safely back up the ESP, use a tool like dd in Linux (e.g., sudo dd if=/dev/sda1 of=esp_backup.img) or a Windows utility that can copy the partition. Store the backup on a different disk.

Frequently Asked Questions

Can I delete the EFI System Partition? No. Deleting it will prevent your computer from booting. If you’re trying to reclaim space, look elsewhere; the ESP is usually only 100–500 MB, so deleting it won’t free up much.

Why is my ESP formatted as FAT32? Because UEFI firmware includes a FAT32 driver, making it able to read the boot files without relying on an OS. NTFS and ext4 are not universally supported by firmware.

How can I tell if my system uses UEFI or BIOS? In Windows, open System Information and look at “BIOS Mode.” If it says “UEFI,” you have an ESP. In Linux, check if /sys/firmware/efi exists—if it does, you booted in UEFI mode.

What happens if I install Linux on a UEFI system without an ESP? The installer will usually create one automatically. If you manually partition and forget it, the installation may fail or the system won’t boot.

Can I move the ESP to another disk? Yes, but it’s complex. You’d need to copy the ESP contents, create a new ESP on the target disk, and update the firmware boot entries (using bcdedit on Windows or efibootmgr on Linux). It’s safer to reinstall the boot loader.

Is the ESP the same as the Windows “System Reserved” partition? No. On a UEFI install, Windows creates an ESP (typically 100 MB) and a separate Microsoft Reserved (MSR) partition (16 MB). The System Reserved partition you see in Disk Management is usually the ESP if the disk is GPT, but on MBR disks it’s a different partition that holds boot files. They serve similar purposes but are not identical.

Related

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.