A missing EFI System Partition (ESP) can prevent a Windows 10 or Windows 11 computer from starting even when the Windows installation, programs, and personal files are still completely present on the SSD or hard drive.

Typical symptoms include:

• No Bootable Device
• Boot Device Not Found
• Operating System Not Found
• Windows Boot Manager missing from BIOS/UEFI
• Computer repeatedly opening BIOS/UEFI Setup
• Windows Automatic Repair loop
• Windows not starting after cloning an SSD
• Windows not booting after deleting or changing partitions
• A Windows installation visible on the drive but unavailable in the boot menu

On a UEFI/GPT Windows installation, the EFI System Partition contains the boot files required by the firmware to start Windows. Microsoft documents the ESP as the system partition used by UEFI/GPT systems, normally formatted as FAT32.

The good news is that a missing or damaged EFI partition does not automatically mean Windows must be reinstalled. If the Windows partition itself is healthy, it is often possible to create a new EFI System Partition and rebuild the Windows boot files using DiskPart and BCDBoot. Microsoft specifically documents BCDBoot as a tool for setting up or repairing the Windows system partition.

What Is the EFI System Partition?

EFI stands for Extensible Firmware Interface. On modern PCs using UEFI firmware and GPT partitioning, Windows uses a special partition called the:

EFI System Partition (ESP)

The EFI partition is different from your normal C: drive. It does not contain your documents, applications, or most Windows system files.

Instead, it stores boot-related files used by UEFI firmware.

A typical Windows UEFI disk may look approximately like:

Disk 0 – GPT

EFI System Partition      FAT32
Microsoft Reserved (MSR)
Windows Partition (C:)    NTFS
Recovery Partition

Microsoft's recommended UEFI/GPT layout includes the system partition, Microsoft Reserved partition, Windows partition, and recovery tools partition.

The EFI partition normally has no drive letter, which is why you generally do not see it in File Explorer.

What Is Stored Inside the EFI Partition?

A Windows EFI partition normally contains an EFI directory structure such as:

EFI
 └── Microsoft
      └── Boot

It contains files and configuration required to start Windows Boot Manager.

One of the important Windows UEFI boot components is associated with Windows Boot Manager, which eventually loads Windows through the UEFI boot process.

If these boot files or the entire ESP disappear, the Windows partition may remain intact but the firmware may no longer know how to start it.

EFI Partition vs Windows Partition

These partitions serve completely different purposes.

Partition	Typical File System	Purpose
EFI System Partition	FAT32	UEFI boot files
MSR Partition	Reserved	GPT partition management
Windows Partition	NTFS	Windows, programs and user data
Recovery Partition	NTFS	Windows Recovery Environment

Do not confuse the EFI partition with the Windows Recovery partition.

Deleting the Recovery partition may affect Windows recovery features.

Deleting the EFI partition can make the computer completely unbootable.

Why Does the EFI Partition Go Missing?

There are several possible causes.

1. EFI Partition Was Accidentally Deleted

Partition management software, DiskPart, Linux installers, cloning utilities, or manual disk modifications can accidentally delete the ESP.

Because it is small, users sometimes incorrectly assume that it is unnecessary.

2. SSD or HDD Was Cloned Incorrectly

This is extremely common.

A user may clone only the C: partition instead of cloning the complete disk.

For example:

Old SSD:

EFI
MSR
C:
Recovery

but the new SSD contains only:

C:

All Windows files are present, but the new drive cannot independently boot because its EFI System Partition was never copied.

3. Windows Boot Files Are on Another Disk

This frequently happens on systems containing multiple drives.

For example:

Disk 0 – Old SATA SSD
    EFI System Partition

Disk 1 – New NVMe SSD
    Windows C:

Windows may be installed on Disk 1 while its boot files remain on Disk 0.

Everything appears normal until Disk 0 is removed or fails.

The new NVMe then appears to contain a complete Windows installation but cannot boot independently.

4. Partition Table Damage

Disk corruption, interrupted partition operations, failing storage devices, or third-party disk utilities can damage GPT partition information.

5. EFI Partition Was Formatted

The partition may still physically exist but its boot files may have been deleted or the file system damaged.

In this situation, recreating the entire partition might not be necessary. Rebuilding its boot files with BCDBoot may be sufficient.

6. MBR/GPT Conversion Problem

A failed or incomplete MBR-to-GPT conversion can cause boot problems.

Microsoft's MBR2GPT process creates an EFI System Partition when required and installs UEFI boot files as part of conversion.

7. BIOS/UEFI Settings Changed

Sometimes the EFI partition is perfectly healthy, but firmware boot mode has been changed.

For example:

Windows installed as:

GPT + UEFI

but BIOS is changed to:

Legacy / CSM

Windows may stop booting.

Before rebuilding partitions, always verify the firmware boot mode.

Important: Does Every Windows PC Need an EFI Partition?

No.

An EFI System Partition is specifically associated with UEFI/GPT booting.

A traditional BIOS/MBR Windows installation uses a different boot arrangement.

Therefore, do not create an EFI partition simply because you cannot find one.

First determine whether the Windows disk is GPT.

How to Check Whether the Disk Is GPT

If Windows still starts, open:

Disk Management

or run Command Prompt as Administrator:

diskpart
list disk

Look at the GPT column.

Example:

Disk ###   Status     Size     Free     Dyn  GPT
--------   --------   -------  -------  ---  ---
Disk 0     Online     953 GB   0 B           *

The * indicates GPT.

You can also use:

diskpart
select disk 0
list partition

Do not assume Disk 0 is always the Windows disk. Verify carefully, particularly on systems containing multiple SSDs.

How to Check Whether an EFI Partition Already Exists

Open:

Disk Management

Look for a small partition identified as:

EFI System Partition

Alternatively:

diskpart
list disk
select disk 0
list partition

Then:

list volume

An ESP will normally be a small FAT32 system partition.

If one already exists, you may only need to repair the boot files rather than create another partition.

Before Repairing a Missing EFI Partition

This procedure modifies disk partitions and boot configuration.

Before continuing:

1. Back up important files whenever possible.
2. Confirm which physical disk contains Windows.
3. Confirm the Windows disk uses GPT.
4. Confirm the machine is intended to boot using UEFI.
5. Disconnect unnecessary external storage devices.
6. Be especially careful if multiple internal SSDs contain Windows installations.
7. If BitLocker/device encryption is enabled, make sure you have the recovery key before changing boot-related configuration.

Never blindly copy DiskPart commands from another computer. Disk and partition numbers vary between systems.

Method 1: Try Windows Startup Repair First

Before manually modifying partitions, try the built-in recovery environment.

Boot from a Windows installation USB or enter Windows Recovery Environment.

Select:

Troubleshoot → Advanced options → Startup Repair

Allow Windows to attempt automatic repair.

If Windows starts afterward, no manual partition creation is required.

If Startup Repair cannot repair the boot environment, continue with manual diagnosis.

Method 2: Repair an Existing EFI Partition

If an EFI partition already exists but Windows does not boot, rebuilding its boot files may be enough.

Boot from Windows installation media.

At the Windows Setup screen, use the recovery options to open Command Prompt. Depending on the environment, Shift + F10 can also open a command prompt.

Microsoft documents using Windows installation media or Windows PE to access a command line for BCDBoot system-partition repair.

Run:

diskpart
list vol

Identify:

• Windows partition
• EFI FAT32 partition

Remember that drive letters in Windows Recovery Environment may be different from normal Windows drive letters.

Your Windows installation might therefore be:

D:\Windows

instead of:

C:\Windows

Microsoft notes that Windows PE can assign drive letters differently depending on the environment and connected drives.

Test possible Windows partitions:

dir C:\Windows
dir D:\Windows
dir E:\Windows

Once the correct Windows partition has been identified, return to DiskPart.

Example:

diskpart
select disk 0
list partition
select partition <EFI-partition-number>
assign letter=S
exit

Now rebuild the boot files:

bcdboot D:\Windows /s S: /f UEFI

Replace D: with the actual Windows partition.

Microsoft documents that /f UEFI creates the required EFI/Microsoft/Boot structure when used with the /s system-partition parameter.

A successful operation should report:

Boot files successfully created.

Restart the computer.

Method 3: Recreate a Missing EFI System Partition

If the EFI partition has genuinely been deleted, you need unallocated space from which to create another one.

Step 1 – Boot into Windows Recovery Command Prompt

Boot from a Windows 10/11 installation USB.

Open:

Repair your computer → Troubleshoot → Advanced options → Command Prompt

Step 2 – Identify the Correct Disk

Run:

diskpart
list disk

Carefully identify the disk containing Windows.

Example only:

select disk 0
list partition

Do not automatically select Disk 0 unless you have verified that it is the correct disk.

Step 3 – Verify GPT

The target Windows disk should be GPT for this UEFI/EFI procedure.

Use:

list disk

Look for * under GPT.

If the Windows disk is MBR, stop here. The appropriate procedure may involve BIOS/MBR boot repair or a controlled MBR-to-GPT conversion rather than simply creating an ESP.

Step 4 – Create Space for the EFI Partition

If sufficient unallocated space already exists, use it.

If there is no suitable unallocated space, the Windows partition may need to be shrunk.

First identify the correct volume:

list volume

Then select it:

select volume <Windows-volume-number>

Shrink it, for example:

shrink desired=300

This attempts to create approximately 300 MB of unallocated space.

Current Microsoft deployment sample scripts use a 300 MB EFI System Partition for newly prepared UEFI/GPT Windows disks.

Do not shrink a volume unless you are certain you have selected the correct one.

Step 5 – Create the New EFI Partition

With the correct GPT disk selected and suitable unallocated space available:

create partition efi size=300

Format it as FAT32:

format quick fs=fat32 label="System"

Assign a temporary drive letter:

assign letter=S

Check:

list volume

Then exit DiskPart:

exit

At this point, the partition exists, but Windows may still not boot because the boot files have not yet been installed.

Step 6 – Find the Actual Windows Drive Letter

Do not assume Windows is C: while working from recovery media.

Try:

dir C:\Windows

If Windows is not there:

dir D:\Windows

then:

dir E:\Windows

Continue until you locate the genuine Windows installation.

Suppose Windows is found at:

D:\Windows

Then D: is the source you should use for BCDBoot.

Step 7 – Rebuild Windows UEFI Boot Files

Run:

bcdboot D:\Windows /s S: /f UEFI

Replace D: with the actual Windows drive letter.

BCDBoot copies boot-environment files from the Windows installation to the system partition and creates or repairs the BCD store.

If successful, you should see:

Boot files successfully created.

Step 8 – Restart and Check UEFI

Close Command Prompt and restart.

Remove the Windows installation USB when appropriate.

Enter BIOS/UEFI Setup and confirm:

• Boot Mode = UEFI
• Correct SSD/NVMe is detected
• Windows Boot Manager is available
• Windows Boot Manager/correct drive has appropriate boot priority

Then attempt to boot Windows.

Step 9 – Remove the Temporary EFI Drive Letter

The EFI System Partition normally should not appear in File Explorer.

If Windows starts and S: remains assigned, open Command Prompt as Administrator:

diskpart
list volume
select volume <EFI-volume-number>
remove letter=S
exit

Verify the volume number carefully before removing anything.

The EFI partition should normally remain hidden and should not be used for regular file storage.

Example Complete EFI Rebuild Procedure

The following is an example only. Do not paste it blindly.

Assume:

• Windows is on Disk 0
• Disk 0 is GPT
• 300 MB unallocated space is available
• Windows appears as D: in recovery mode

Commands might look like:

diskpart
list disk
select disk 0
list partition
create partition efi size=300
format quick fs=fat32 label="System"
assign letter=S
exit

dir D:\Windows

bcdboot D:\Windows /s S: /f UEFI

Restart afterward.

The critical requirement is that the disk, Windows volume, and EFI partition are correctly identified for the specific computer.

What If BCDBoot Says "Failure When Attempting to Copy Boot Files"?

If you receive:

Failure when attempting to copy boot files.

check the following.

Verify the Windows Directory

Run:

dir D:\Windows

Make sure it is the actual Windows installation.

Verify the EFI Partition Is FAT32

Run:

diskpart
list volume

The EFI partition should be FAT32.

Verify the EFI Partition Has a Drive Letter

For example:

S:

Then retry:

bcdboot D:\Windows /s S: /f UEFI

Verify You Selected the Correct Disk

A common mistake is creating or repairing an EFI partition on the wrong SSD.

This is particularly easy on PCs with:

• SATA SSD + NVMe SSD
• two NVMe drives
• old HDD + new SSD
• cloned drives
• dual Windows installations

What If Windows Is on MBR Instead of GPT?

Do not use the above procedure without understanding the disk's current boot architecture.

Traditional BIOS systems normally use MBR, while UEFI Windows installations normally use GPT. Microsoft documents separate partition requirements for BIOS/MBR and UEFI/GPT systems.

For eligible Windows installations, Microsoft provides:

MBR2GPT.EXE

for converting a system disk from MBR to GPT without deleting data when validation requirements are satisfied.

The conversion workflow includes creating or reusing an EFI System Partition, installing UEFI boot files, applying GPT metadata, and updating BCD.

Do not run MBR2GPT casually on an important production machine. Verify compatibility, backup status, BitLocker state, firmware UEFI support, and disk layout first.

EFI Partition Missing After Cloning SSD

This deserves special attention because it is one of the most common scenarios.

Suppose the original drive contains:

Disk 0
[EFI] [MSR] [Windows C:] [Recovery]

You clone only Windows to a new NVMe:

Disk 1
[Windows C:]

The PC may continue booting because the firmware is still loading the EFI boot files from Disk 0.

You then remove Disk 0.

Suddenly:

No Bootable Device

appears.

The Windows installation on the new SSD may be completely healthy.

The problem is simply that the new disk does not have an independent EFI boot environment.

The solution can be to create an ESP on the new GPT disk and run BCDBoot against the Windows installation.

EFI Partition Exists on the Wrong Drive

Another common configuration is:

Disk 0
EFI System Partition

Disk 1
Windows C:

The PC depends on both disks.

This can happen if Windows Setup was performed while multiple drives were connected.

If Disk 0 later fails or is removed, Windows on Disk 1 cannot boot.

For a system that should boot independently from Disk 1, a properly configured EFI System Partition and boot files need to exist on the intended boot disk.

This type of repair should be performed particularly carefully because multiple EFI partitions and multiple Windows installations can make drive identification confusing.

Can You Copy EFI Files Manually?

It is preferable to use BCDBoot rather than manually copying individual EFI files.

BCDBoot is specifically designed to initialize or repair the system partition using boot files from the Windows installation. It can create the BCD store and configure Windows boot-environment files.

For example:

bcdboot C:\Windows /s S: /f UEFI

is far safer and more complete than attempting to manually copy random EFI files.

Should You Format an Existing EFI Partition?

Not automatically.

If the EFI partition exists but Windows does not boot, first consider rebuilding its boot files.

Formatting an ESP removes existing boot files and may also affect:

• other Windows installations
• dual-boot configurations
• OEM utilities
• Linux boot loaders
• custom recovery environments

Therefore, formatting should only be done when you understand exactly what is stored there and why it is necessary.

EFI Partition and BitLocker

Be particularly careful on BitLocker/device-encrypted systems.

Changing boot partitions, firmware settings, TPM-related configuration, or boot entries can trigger BitLocker recovery.

Before performing EFI repair on an encrypted computer:

• locate the BitLocker recovery key
• verify which Windows partition is encrypted
• avoid clearing TPM unnecessarily
• avoid changing Secure Boot or firmware settings unless required

An EFI boot problem and a BitLocker recovery prompt are different problems, although boot configuration changes can cause BitLocker to request recovery authentication.

EFI Partition and Secure Boot

Secure Boot depends on the UEFI boot environment but is not the same thing as the EFI System Partition.

If Windows Boot Manager has disappeared, simply disabling Secure Boot usually does not recreate the missing ESP or restore deleted Windows boot files.

Repair the actual boot environment rather than treating Secure Boot as the primary cause without evidence.

EFI Partition vs Recovery Partition

These are frequently confused.

EFI System Partition

Used during startup:

UEFI Firmware
       ↓
EFI System Partition
       ↓
Windows Boot Manager
       ↓
Windows Loader
       ↓
Windows

Recovery Partition

Contains Windows Recovery Environment components used for:

• Advanced startup
• Startup Repair
• Reset/repair operations
• troubleshooting

A computer can potentially boot without a functioning Recovery partition.

A UEFI Windows installation cannot boot normally if its required EFI boot environment is unavailable.

How to Prevent EFI Partition Problems

Never Delete Small Partitions Without Identifying Them

Small partitions are not necessarily useless.

They may be:

• EFI System Partition
• Microsoft Reserved Partition
• Recovery Partition
• OEM diagnostics partition

Clone the Entire System Disk

When migrating Windows to a new SSD, preferably clone all required system partitions rather than copying only C:.

A typical migration should preserve:

EFI
MSR
Windows
Recovery

where appropriate.

Test the New SSD Independently

After cloning, a useful validation step is to verify that the new drive can boot without relying on the old drive.

Do this only after confirming your backup and migration are complete.

Keep Recovery Media Available

Maintain a current Windows installation/recovery USB so you can access Command Prompt and recovery tools if boot files become damaged.

Important Warning About DiskPart

DiskPart is extremely powerful.

Commands such as:

clean
delete partition
format

can destroy data or partition structures when used against the wrong disk.

For EFI repair, never use:

clean

unless your intention is actually to erase the disk.

You normally do not need to erase or reinstall Windows merely to recreate a missing EFI partition.

Recommended Troubleshooting Sequence

When a Windows computer appears to have a missing EFI partition, use this order:

1. Confirm the Windows partition still exists
              ↓
2. Check whether disk is GPT or MBR
              ↓
3. Confirm BIOS is configured for UEFI
              ↓
4. Check whether an EFI partition already exists
              ↓
5. Try Startup Repair
              ↓
6. If ESP exists → rebuild boot files with BCDBoot
              ↓
7. If ESP is genuinely missing → create a FAT32 ESP
              ↓
8. Run BCDBoot against the correct Windows installation
              ↓
9. Verify Windows Boot Manager in UEFI
              ↓
10. Boot and test Windows

This approach avoids unnecessarily reinstalling Windows.

Frequently Asked Questions (FAQ)

1. What happens if the EFI partition is missing?

On a UEFI/GPT Windows installation, the firmware may be unable to locate Windows Boot Manager, causing the computer to fail to boot even though Windows itself remains on the drive.

2. Can Windows boot without an EFI partition?

A normal UEFI/GPT Windows installation requires an EFI system boot environment. Traditional BIOS/MBR systems use a different boot architecture and do not use an ESP in the same way.

3. Does a missing EFI partition mean my Windows files are deleted?

No.

The EFI partition and Windows partition are separate. Your C: partition, programs, and personal files may still be intact.

4. Can I recreate the EFI partition without reinstalling Windows?

Yes, in many cases.

If the Windows installation is intact and the disk layout is suitable, you can create an EFI System Partition and use BCDBoot to rebuild the boot files.

5. What file system should the EFI partition use?

For Windows UEFI/GPT systems, the EFI System Partition uses FAT32.

6. How large should the EFI partition be?

Existing systems can have ESP sizes that vary by installation history and hardware. For newly prepared Windows UEFI/GPT layouts, Microsoft's current sample deployment script uses a 300 MB FAT32 system partition.

When repairing an existing machine, do not delete a healthy ESP merely because its size differs from a newer deployment recommendation.

7. What command recreates Windows EFI boot files?

A commonly used BCDBoot command is:

bcdboot C:\Windows /s S: /f UEFI

However, C: must be replaced with the actual Windows drive letter and S: with the temporary drive letter assigned to the correct EFI System Partition.

8. Why does Windows become D: in recovery mode?

Windows PE/Recovery Environment can assign drive letters differently from the installed operating system. Therefore, always locate the Windows folder before running repair commands.

9. Why is my EFI partition not visible in File Explorer?

This is normal.

The EFI System Partition normally has no permanent drive letter and is intentionally hidden from normal users.

10. Can I assign a drive letter to the EFI partition?

Yes, temporarily for troubleshooting.

For example:

assign letter=S

After repair, the temporary letter can be removed.

11. Should I delete an old EFI partition?

Not until you have positively identified which EFI partition the system is using.

Deleting the wrong ESP can immediately make Windows or another operating system unbootable.

12. Why did my cloned SSD stop booting after removing the old SSD?

The old SSD may have contained the EFI System Partition while the new SSD contained only the Windows partition.

The computer was therefore still depending on the old drive for boot files.

13. Can one disk contain Windows while another contains the EFI partition?

Yes, such configurations can occur, especially when Windows is installed with multiple disks connected.

However, it creates a dependency on both drives.

14. Does Startup Repair recreate a missing EFI partition?

Startup Repair can resolve various boot problems, but a completely absent or incorrectly configured ESP may require manual partition and BCDBoot repair.

15. Is the EFI partition the same as System Reserved?

Not exactly.

"System Reserved" is commonly associated with BIOS/MBR Windows installations, whereas an EFI System Partition is used for UEFI/GPT booting.

16. Is the EFI partition the same as the MSR partition?

No.

The EFI System Partition contains UEFI boot files.

The Microsoft Reserved (MSR) partition is a separate reserved partition used as part of GPT disk management.

17. Is the EFI partition the same as the Windows Recovery partition?

No.

The EFI partition is involved in booting the operating system. The Recovery partition contains Windows Recovery Environment components.

18. Will creating a new EFI partition delete my C: drive?

Creating an ESP in existing unallocated space does not inherently delete C:. However, incorrectly shrinking, formatting, deleting, or selecting partitions can cause data loss. Always verify the disk layout first.

19. Can I use NTFS for an EFI System Partition?

For standard Windows UEFI deployment, the ESP should be formatted as FAT32.

20. What does BCDBoot actually do?

BCDBoot copies boot-environment files from a Windows installation to the system partition and creates or repairs the BCD boot configuration. On UEFI systems it can configure the EFI boot environment.

21. What if bcdboot C:\Windows does not work?

First verify that C: really contains the installed Windows environment.

In recovery mode it may instead be:

D:\Windows

or:

E:\Windows

Then verify that the target EFI partition is correct and accessible.

22. Can an EFI partition become corrupted instead of deleted?

Yes.

The partition can still exist while its FAT32 file system, BCD store, or boot files are damaged. In such cases, repair may be possible without creating another ESP.

23. Should I use Bootrec or BCDBoot for a missing EFI partition?

For rebuilding the Windows system partition and EFI boot files, BCDBoot is particularly relevant because Microsoft specifically documents it for setting up and repairing the system partition.

24. Can MBR2GPT create an EFI partition?

Yes. During eligible MBR-to-GPT conversions, Microsoft's MBR2GPT workflow creates or reuses an EFI System Partition and installs UEFI boot files.

25. Do I need to reinstall Windows after accidentally deleting the EFI partition?

Usually not as the first response.

If the Windows partition and its files are intact, rebuilding the EFI System Partition and Windows boot environment may restore the existing installation without reinstalling Windows.

Conclusion

A missing EFI System Partition can make a perfectly healthy Windows installation appear completely unusable. The key is understanding that the Windows partition and the boot partition are separate components.

For a UEFI/GPT Windows installation, the repair process generally involves identifying the correct Windows disk, confirming whether an ESP already exists, creating one only when genuinely necessary, formatting it as FAT32, and rebuilding the Windows boot environment with BCDBoot.

The most important command in many EFI recovery scenarios is:

bcdboot <WindowsDrive>:\Windows /s <EFIDrive>: /f UEFI

However, the correct drive letters and disk numbers must be determined on the affected computer rather than assumed.

Before modifying partitions, always verify whether the machine uses UEFI/GPT or BIOS/MBR, identify every disk carefully, protect BitLocker recovery information, and back up important data whenever possible.

A missing EFI partition is a serious boot problem, but it does not automatically require formatting the computer or reinstalling Windows.

#Tags

#EFIPartition #EFISystemPartition #EFIPartitionMissing #Windows11 #Windows10 #WindowsBootRepair #UEFIBoot #UEFI #GPT #WindowsBootManager #BCDBoot #DiskPart #BootRepair #WindowsRecovery #StartupRepair #BootDeviceNotFound #NoBootableDevice #OperatingSystemNotFound #BCDRepair #EFIRepair #BootloaderRepair #WindowsTroubleshooting #WindowsSupport #WindowsTips #WindowsRecoveryEnvironment #WinRE #WindowsPE #GPTPartition #FAT32 #SystemPartition #WindowsBoot #SSDRepair #SSDCloning #NVMe #SSDUpgrade #WindowsMigration #MBR2GPT #MBR #SecureBoot #BitLocker #BootFiles #BootConfigurationData #WindowsInstallationUSB #WindowsStartupRepair #DiskManagement #WindowsPartition #RecoveryPartition #MicrosoftReservedPartition #UEFIGPT #TechSupport