Transferring boot partitions between drives in Windows 10 and 11 requires careful handling of the EFI System Partition (ESP) to prevent boot failures. The most reliable method involves using the built-in
Bcdboot command-line tool, which copies the necessary boot files directly to the target drive’s partition. This approach ensures that your multi-boot configuration remains stable without relying on third-party software that might corrupt critical registry entries or bootloader signatures.
Understanding the Boot Architecture
Modern versions of Windows, including Windows 10 and 11, use the Unified Extensible Firmware Interface (UEFI) for startup processes. Unlike older Legacy BIOS systems that relied on a single Master Boot Record (MBR), UEFI stores boot configuration data in a small, FAT32-formatted partition known as the EFI System Partition (ESP). This partition is typically 100-500 MB in size and contains the bootloader files for all installed operating systems. When you install a second copy of Windows on a different physical drive, it creates its own entry in the ESP or modifies the existing one. If you move the OS files to a new drive without updating the boot configuration, the system will fail to locate the bootloader, resulting in a "Boot Device Not Found" error. Therefore, transferring the boot partition effectively means synchronizing the ESP with the new location of the operating system files.
Preparation and Backup
Before attempting any low-level disk operations, you must secure your data. While the procedures described below are generally safe, modifying boot sectors carries inherent risks. Create a full system image backup using tools like Macrium Reflect or the built-in Windows Backup utility. Additionally, ensure that you have a Windows Installation Media USB drive ready. This media serves as a recovery environment if the primary boot process fails. You should also identify the drive letters assigned to your current Windows installation and the target drive. In the Windows Recovery Environment (WinRE), drive letters may differ from those in the normal desktop session, so do not rely on them being consistent. Verify that both drives are connected and recognized by the motherboard firmware before proceeding.
Using Bcdboot to Transfer Boot Files
The
Bcdboot utility is the standard Microsoft tool for creating or repairing the boot sector. It is included in the Windows installation media and the WinRE environment. To transfer the boot files, you need to know the drive letter of the Windows folder on the source drive and the drive letter of the EFI partition on the target drive.
First, boot from your Windows Installation Media USB and select "Repair your computer" followed by "Troubleshoot" and "Command Prompt." Once the command prompt opens, type
diskpart and press Enter. Inside Diskpart, type
list volume to display all partitions. Identify the EFI partition; it is usually labeled "SYSTEM" or "EFI" and has a file system of FAT32. Note its volume number. Type
select volume X (replace X with the volume number) and then
assign letter=S to assign the letter S to the EFI partition. Exit Diskpart by typing
exit.
Next, determine the drive letter of the Windows directory on the drive where your OS resides. It might be C:, D:, or another letter depending on the current state. Assume the Windows folder is at
C:\Windows and the EFI partition is now
S:. Run the following command:
bcdboot C:\Windows /s S: /f ALL
This command copies the boot files from the specified Windows directory to the EFI partition (S:) and configures the firmware to use them. The
/f ALL flag ensures compatibility with both UEFI and Legacy BIOS modes, though UEFI is standard for modern systems. After execution, verify that no errors appear. You can check the success by listing the contents of the EFI partition using
dir S:\EFI\Microsoft\Boot to ensure files exist.
Configuring the Boot Order
After copying the files, you must instruct the motherboard to boot from the correct drive. Restart the computer and enter the BIOS/UEFI setup by pressing the designated key (often Del, F2, or F12). Navigate to the Boot section and locate the boot priority list. Move the entry corresponding to the target drive’s Windows Boot Manager to the top position. Save changes and exit. If you have multiple Windows installations, ensure that the desired default is selected. If the system still boots into the old drive, you may need to delete the old boot entries using
bcdedit commands in the command prompt, but only after confirming the new boot works reliably.
For more details on resolving issues where the second Windows installation is not found, see our guide on
Troubleshooting Windows Boot Loader: Second Windows Not Found.
Verifying the Transfer
Once the system boots successfully from the new drive, perform basic checks. Open Command Prompt as Administrator and run
bcdedit to view the current boot configuration. Ensure that the path to the
windows device points to the correct partition on the new drive. Check that all applications and settings are intact. If you notice slow boot times or missing drivers, reinstall the chipset and storage drivers specific to the new hardware configuration. Regularly update the BIOS to ensure optimal compatibility with your storage controllers.
If you encounter issues related to Intel Volume Management Device (VMD) settings affecting boot stability, consider reviewing
Is it okay to turn off Intel VMD after updating Windows 11? for potential hardware-specific adjustments.
Frequently Asked Questions
Can I use third-party software instead of bcdboot?
Yes, tools like EaseUS Todo Backup or AOMEI Backupper offer GUI-based solutions for cloning and migrating boot partitions. However, these tools may modify registry keys differently than manual methods, potentially causing conflicts in dual-boot setups. Manual
bcdboot usage provides greater transparency and control over the exact files being copied.
What if my EFI partition is too small?
A standard EFI partition of 100-500 MB is sufficient for most multi-boot configurations. If you are running many operating systems, you may need to expand the partition using
diskpart commands. Never format or delete the EFI partition while Windows is installed on it, as this will render the system unbootable immediately.
How do I remove the old boot entries?
Use the
bcdedit command in an elevated Command Prompt to list entries with
bcdedit /enum. Identify the GUID of the old Windows installation and delete it using
bcdedit /delete {GUID}. Be cautious not to delete the current working entry, as this will break your boot process until repaired.
Does this work for MBR disks?
The
bcdboot method described here is primarily for UEFI/GPT systems. For legacy MBR disks, you would use
bootrec /fixmbr and
bootrec /rebuildbcd instead. Most modern Windows 10 and 11 installations use GPT, making the EFI partition approach the standard requirement.
Will transferring the boot partition affect BitLocker encryption?
If your drive is encrypted with BitLocker, the boot files must remain accessible to decrypt the volume. Transferring boot files does not disable encryption, but you must ensure the TPM and boot integrity measurements remain consistent. If you change hardware significantly, you may need to provide your BitLocker recovery key during the next boot.