Format the EFI system partition when you want to completely wipe all previous boot data — for example, after a dual-boot installation (e.g., Windows + Linux). This will delete all bootloaders.
I don't use Linux, so I checked this with ChatGPT.
ChatGPT: "Formatting the ESP wipes all bootloaders and boot managers."
If anyone is interested: ChatGPT: "If you’d like, I can also help you draft a unified glossary (Boot Manager vs. bootloader vs. OS loader), so you don’t have to rethink the wording every time you write about UEFI/boot flow."
UEFI Boot Terminology
UEFI Boot Manager (firmware component)
- Built into the UEFI firmware.
- Maintains the boot order (BootOrder, Boot#### variables in NVRAM).
- Decides which EFI executable to run first from the EFI System Partition (ESP).
- Example: When you press F12 or Esc at startup to pick a device, you’re using the UEFI Boot Manager.
Bootloader (generic EFI program)
- An EFI application stored on the ESP.
- Launched by the UEFI Boot Manager.
- Its job is to prepare and transfer control to the operating system kernel.
- Examples:
- GRUB (grubx64.efi) for Linux
- systemd-boot (systemd-bootx64.efi)
- shim (shimx64.efi, used in Secure Boot)
OS-specific Boot Manager
- Some operating systems provide their own boot manager, which acts as a middle layer between UEFI and the OS loader.
- Example:
- Windows Boot Manager (bootmgfw.efi)
- Reads the Boot Configuration Data (BCD).
- Presents boot choices (Safe Mode, Recovery, multiple Windows installations).
- Chooses and launches the OS loader (winload.efi).
OS Loader (OS-specific bootloader stage)
- Responsible for loading the OS kernel and essential drivers.
- Examples:
- Windows: winload.efi (loads ntoskrnl.exe).
- Linux: GRUB can directly load the Linux kernel (vmlinuz) or hand off to another loader.
EFI System Partition (ESP)
- FAT32 partition where bootloaders and boot managers reside.
- Typical layout:
/EFI/Boot/bootx64.efi (fallback bootloader)
/EFI/Microsoft/Boot/bootmgfw.efi (Windows Boot Manager)
/EFI/ubuntu/grubx64.efi (GRUB for Ubuntu)
/EFI/fedora/shimx64.efi (shim loader for Secure Boot)
- Formatting the ESP wipes all bootloaders and boot managers.
In short:
- UEFI Boot Manager = firmware’s built-in selector.
- Bootloader = EFI program launched from the ESP.
- Windows Boot Manager (bootmgfw.efi) = OS-specific manager, not just a loader.
- OS Loader = loads the kernel (e.g., winload.efi on Windows).
If anyone is interested:
MBR Disk Boot Process (BIOS-based booting):
1. BIOS firmware performs the POST (Power-On Self-Test).
2. BIOS reads the Master Boot Record (MBR) from the first sector of the boot disk — in other words, from the boot sector of that disk.
3. The MBR boot code identifies the active (bootable) partition and transfers control to its Volume Boot Record (VBR) — in other words, to the boot sector of that partition.
4. The VBR boot code loads the Windows Boot Manager — bootmgr (a file in the root of the boot partition, typically C:\bootmgr).
5. bootmgr reads the BCD store from the \Boot\BCD path on the system partition.
6. Based on BCD settings, it launches winload.exe, the OS loader for BIOS-based systems, to start Windows.
GPT Disk Boot Process (UEFI-based booting):
1. UEFI firmware performs the POST (Power-On Self-Test).
2. UEFI checks the system's NVRAM for boot entries.
3. A boot entry (e.g., "Windows Boot Manager") points to \EFI\Microsoft\Boot\bootmgfw.efi on the EFI system partition.
4. bootmgfw.efi is the Windows Boot Manager, which loads and reads the BCD (Boot Configuration Data) store from the same EFI system partition.
5. Based on BCD settings, it launches winload.efi, the OS loader for UEFI-based systems, to start Windows.
In short:
- MBR disks rely on boot sectors and an active partition to eventually reach bootmgr.
- GPT disks rely on the UEFI firmware to directly load EFI files from the EFI system partition, so no MBR/VBR/active partition concept exists.
Windows will not boot on BIOS systems unless the boot device is configured as the primary boot option in the BIOS settings. UEFI systems do not have this specific limitation because they function differently.
