Understanding the Boot Failure
The EFI System Partition (ESP) is critical for modern UEFI-based systems because it stores the bootloader, firmware drivers, and other essential startup files. When you delete this partition during disk management in Linux or another environment, Windows loses its ability to initiate the boot sequence. Additionally, if BitLocker is enabled, the system may automatically trigger a lockout upon detecting changes to the boot configuration or missing partitions, requiring your recovery key to proceed.
Before attempting any repairs, ensure you have your BitLocker recovery key available. This 48-digit number is typically found in your Microsoft account, printed on paper, or saved as a file on a USB drive. Without it, unlocking the volume after repair attempts will be impossible. If you are unsure about the status of your encryption, consult our guide on Recovering Data from BitLocker Encrypted Volume with Decryption Key to locate your credentials safely.
Preparing the Installation Media
To fix the bootloader, you need a bootable Windows USB drive created on a separate working computer. Use the official Media Creation Tool from Microsoft to generate a fresh copy of Windows 10 or 11 that matches your current installation. Ensure the USB drive has at least 8GB of free space, as the tool will format it entirely.
Insert the USB drive into the affected PC and power it on. Enter the BIOS/UEFI settings by pressing the designated key (commonly F2, F12, Del, or Esc) immediately after powering on. Navigate to the Boot menu and set the USB drive as the primary boot device. Save changes and exit. The system should now boot into the Windows Setup interface instead of showing a "No Boot Device" error.
Accessing the Recovery Environment
Once the Windows Setup screen appears, select your language preferences and click Next. Do not click "Install Now." Instead, look for the link labeled "Repair your computer" in the bottom left corner of the window. Clicking this will redirect you to the Windows Recovery Environment (WinRE), which contains the command-line tools necessary for manual partition creation and bootloader restoration.
If the option to repair is grayed out or unavailable, verify that the USB drive was created correctly and that the BIOS recognizes it as a UEFI bootable device. In some cases, legacy BIOS mode may prevent access to advanced repair tools. Switching to UEFI mode in BIOS settings often resolves this limitation.
Creating the EFI Partition Manually
In the WinRE menu, navigate to Troubleshoot > Advanced options > Command Prompt. This opens a black terminal window with administrative privileges. First, identify your drives by typing diskpart and pressing Enter. Then, type list disk to display all storage devices. Identify your main hard drive (usually Disk 0) based on its size.
Select the disk by typing select disk 0. Next, create a new partition for the EFI system. Type create partition efi size=100. This creates a 100MB partition specifically for boot files. Assign a drive letter to this new partition so you can write files to it. Type assign letter=S (or any unused letter). Finally, type exit to leave diskpart, but keep the command prompt open.
Restoring the Boot Files
With the EFI partition created and assigned a letter, you can now copy the necessary boot files from the Windows installation media. Assume your USB drive is assigned the letter D (verify this by typing dir d:). If the USB is different, adjust the letter accordingly. Run the following command to copy the boot files:
bcdboot C:\Windows /s S: /f UEFIThis command tells the system to take the Windows folder from the C: drive (your main OS partition) and install the boot files onto the S: drive (the new EFI partition) using UEFI format. If successful, you will see a message stating "Boot files successfully created."
Type exit to close the command prompt. Remove the USB drive and restart the computer. The system should now detect the newly created EFI partition and load Windows normally. If BitLocker prompts for a recovery key, enter the 48-digit code you secured earlier.
Verifying System Integrity
After logging back into Windows, check the Disk Management utility to ensure the EFI partition is marked as healthy and hidden from the main file explorer. It should appear as a small, unallocated or system-reserved partition. Avoid formatting or modifying this partition further to prevent future boot issues.
If you previously used GRUB for dual-booting, you will need to reinstall it on the remaining Linux partition or configure Windows Boot Manager to handle both operating systems. For users concerned about automatic encryption triggers during such operations, reviewing best practices for Rufus configurations might be helpful, as discussed in Disable BitLocker Automatic Device Encryption in Rufus before Activating BitLocker for Windows 11 24H2 Installation.
Frequently Asked Questions
Can I recover the EFI partition using Linux tools?
While technically possible with advanced tools like testdisk, it is risky and often fails to recreate the exact BCD store Windows requires. Using the Windows installation media ensures compatibility and proper file structure for UEFI booting.
What if my Windows partition is not on C:?
The drive letter in the bcdboot command depends on how WinRE mounts your original OS. Check available drives in the command prompt and replace C:\Windows with the correct path, such as D:\Windows.
Will this process delete my personal files?
No, creating a new EFI partition and copying boot files does not affect the contents of your main Windows partition where your documents and applications reside. Only the boot configuration is modified.
Why does BitLocker ask for a key even after repair?
BitLocker monitors boot integrity. Deleting and recreating the EFI partition changes the boot hash, triggering an automatic lock. Providing the recovery key validates that you own the device and allows decryption.
Can I use a third-party tool instead of command line?
Tools like EasyBCD can manage boot entries, but they require a running Windows installation. Since your system cannot boot, the command-line method using bcdboot is the only reliable offline solution.