{"id":57964,"date":"2026-10-28T17:03:48","date_gmt":"2026-10-28T09:03:48","guid":{"rendered":"https:\/\/www.amagicsoft.com\/?p=57964"},"modified":"2026-10-28T17:03:48","modified_gmt":"2026-10-28T09:03:48","slug":"efi-system-partition","status":"publish","type":"post","link":"https:\/\/www.amagicsoft.com\/de\/kb\/disk-partition\/efi-system-partition.html","title":{"rendered":"Was ist eine EFI-Systempartition? Erl\u00e4uterungen zu Gr\u00f6\u00dfe, BCD und Klonen"},"content":{"rendered":"\t\t
\n\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

The EFI System Partition (ESP)<\/strong> is a small partition that stores startup files used by a UEFI-based computer. On a typical Windows UEFI\/GPT installation, it uses the FAT32 file system<\/a> and normally has no drive letter. It helps the computer start Windows; it is separate from the partition containing your documents and installed applications.<\/p>\n

You may notice it while checking Disk Management or preparing to replace an SSD. Although it occupies little space, leaving it out of a system migration can leave you with a drive that contains Windows but cannot start it independently.<\/p>\n

This guide focuses on Windows UEFI\/GPT systems. Other operating systems can use an ESP too, but their boot files and space requirements may differ.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t

What Does the EFI System Partition Do?<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

On a UEFI Windows PC, the firmware starts Windows Boot Manager from the ESP. Boot Manager then starts the Windows OS loader, which loads the components needed to start the operating system. The OS loader normally resides in the Windows partition.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"What\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Component<\/strong><\/p><\/td>

Typical location<\/strong><\/p><\/td>

Role<\/strong><\/p><\/td><\/tr>

UEFI firmware and firmware boot entries<\/p><\/td>

Motherboard firmware and NVRAM<\/p><\/td>

Select the boot application to launch<\/p><\/td><\/tr>

Windows Boot Manager<\/p><\/td>

ESP: \\EFI\\Microsoft\\Boot\\bootmgfw.efi<\/code><\/p><\/td>

Manage the Windows startup process<\/p><\/td><\/tr>

Boot Configuration Data (BCD) store<\/p><\/td>

ESP: \\EFI\\Microsoft\\Boot\\BCD<\/code><\/p><\/td>

Store Windows boot configuration<\/p><\/td><\/tr>

Windows OS loader<\/p><\/td>

Windows partition: \\Windows\\System32\\winload.efi<\/code><\/p><\/td>

Load Windows startup components<\/p><\/td><\/tr><\/tbody><\/table>\n

The paths above describe a typical Windows UEFI installation. Microsoft documents the boot stages, UEFI boot settings, and ESP BCD location separately.<\/p>\n

An important distinction: firmware boot entries and the BCD store are separate things<\/strong>. Firmware entries identify a boot application; BCD configures the Windows boot environment. A disk can contain valid boot files while the firmware still selects the wrong drive or boot entry.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t

Is the EFI Partition the Same as the Windows or Recovery Partition?<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

No. These partitions serve different purposes:<\/p>\n

Partition<\/strong><\/p><\/td>

Purpose<\/strong><\/p><\/td>

What it means for your files<\/strong><\/p><\/td><\/tr>

EFI System Partition<\/p><\/td>

UEFI startup files<\/p><\/td>

Boot dependency<\/p><\/td><\/tr>

Windows partition, usually C:<\/p><\/td>

Windows, applications, user folders<\/p><\/td>

Main file recovery target<\/p><\/td><\/tr>

Microsoft Reserved Partition (MSR)<\/p><\/td>

GPT management reserve<\/p><\/td>

No user files<\/p><\/td><\/tr>

Windows Recovery partition<\/p><\/td>

Windows Recovery Environment<\/p><\/td>

Recovery tools<\/p><\/td><\/tr><\/tbody><\/table>\n

Microsoft documents these as distinct parts of a Windows GPT disk layout<\/a>. Their order and number can vary on manufacturer and upgraded systems.<\/p>\n

Do not identify an ESP only by its size or position. A small partition could serve another purpose. Likewise, a GPT data disk does not become a bootable Windows system disk simply because it uses GPT.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t

EFI Partition Size: How Large Should It Be?<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

There is no single number that describes every existing Windows installation.<\/p>\n

Microsoft’s current UEFI\/GPT deployment guidance specifies these ESP minimums for new layouts:<\/p>\n

Storage device sector type<\/strong><\/p><\/td>

Minimum ESP size in that guidance<\/strong><\/p><\/td><\/tr>

512-byte native or 512e<\/p><\/td>

200 MB<\/p><\/td><\/tr>

4K native (4Kn)<\/p><\/td>

300 MB<\/p><\/td><\/tr><\/tbody><\/table>\n

Older installations and particular conversion workflows can use smaller partitions. For example, the MBR2GPT conversion workflow<\/a> can create an ESP of 100 MB<\/strong>, or 260 MB on disks with 4K sectors<\/strong>. These are conversion-tool rules, so they should not be substituted for the current custom deployment recommendations.<\/p>\n

A working 100 MB ESP is not automatically a problem.<\/strong> Before changing it, ask:<\/p>\n

  1. Does the computer start normally?<\/li>
  2. Has an update or diagnostic report identified insufficient space in the system partition?<\/li>
  3. Are you preserving an existing installation or planning a new disk layout?<\/li>
  4. Will the ESP need to accommodate additional operating-system boot files?<\/li><\/ol>\n

    Partition capacity and free space are different measurements. A 300 MB partition can still run short of available space. Conversely, seeing a smaller partition in Disk Management does not establish that it caused an unrelated startup error.<\/p>\n

    Treat a size change as a planned maintenance task with a backup, rather than a routine way to improve performance. An upgrade error can have several causes; use its specific error details before deciding to resize a system partition.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

    \n\t\t\t\t
    \n\t\t\t\t\t

    What Is Boot Configuration Data, and How Does It Relate to EFI?<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t

    Boot Configuration Data (BCD)<\/strong> stores configuration for Windows boot applications. It can describe boot entries, the default selection, and the Windows loader’s device and path. Windows can use BCD in both UEFI and legacy BIOS environments; BCD itself is not a partition type.<\/p>\n

    On a typical UEFI installation, the active Windows BCD store resides in the ESP under \\EFI\\Microsoft\\Boot\\BCD<\/code>.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"How\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t

    Think of the ESP as the storage location and BCD as configuration stored there. The two can fail differently:<\/p>\n