Making a Specific Volume Bootable using CMD in Windows 10

To make a specific volume bootable in Windows 10, you must use the bcdboot command to copy boot files from a source Windows installation to the target partition and create new Boot Configuration Data (BCD) store entries. This process is distinct from repairing an existing broken boot sector; it actively provisions a drive to be recognized by the UEFI or BIOS firmware as a valid startup device.

Understanding the Distinction Between Repair and Creation

Many users confuse the tools used for fixing boot issues with those used for creating new bootable volumes. The common misconception involves using bcdboot /rebuildbcd, which attempts to rebuild the BCD store based on existing Windows installations. While useful for recovery scenarios where the boot files are missing but the OS remains intact, this approach does not properly prepare a completely new or cloned volume for independent booting. The correct utility for making a volume bootable is bcdboot. This tool performs three critical actions:

1. It copies the essential boot files (such as winload.efi or bootmgr) from the source Windows directory to the target system partition.
2. It creates a new entry in the BCD store that points to the operating system located on the target volume.
3. It ensures the file system structure matches what the firmware expects, whether you are using Legacy BIOS (MBR) or modern UEFI (GPT).

This distinction is vital because simply copying files manually or using disk cloning software often leaves the target drive without the necessary registry links in the BCD store. Without these links, the computer’s firmware will skip the drive during the Power-On Self-Test (POST), even if the Windows files are present. For more context on handling cloned drives, see Making a Cloned Windows Drive Bootable on a New Location (E:).

Prerequisites and Preparation

Before executing any commands, you must ensure your environment is correctly configured. You need administrative privileges to modify system-level boot configurations. Additionally, you must identify two specific paths: the source of the Windows installation files and the destination volume that will become bootable. Identify the Source Windows Directory The source is typically the root folder of an installed Windows instance, such as C:\Windows. If you are working from a Windows PE environment or a recovery drive, this path might differ. Ensure that the source drive contains a fully functional Windows installation with the Windows folder and Program Files directories. Identify the Target System Partition The target volume depends on your firmware type:

• UEFI Systems: You need a dedicated EFI System Partition (ESP). This is usually a small FAT32-formatted partition (often 100MB–500MB) labeled "System" or "EFI." It must have a drive letter assigned temporarily if it doesn't already have one.
• Legacy BIOS (MBR) Systems: You need the active partition containing the Windows installation. This partition must be marked as "Active" in Disk Management. The boot files will reside directly here rather than in a separate ESP.

To assign a drive letter to the target partition if it lacks one, open Command Prompt as Administrator and run diskpart. Inside DiskPart, select the target volume using select vol X (where X is the volume number) and then assign a letter with assign letter=S. Exit DiskPart with exit.

Executing the bcdboot Command

Once the source and target paths are confirmed, you can execute the primary command. The syntax requires specifying the source Windows directory and the target drive letter. For a standard UEFI-based installation, the command structure is:

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

Here, C:\Windows represents the source location of the OS files. /s S: specifies the target system partition (drive S in this example) where boot files will be copied. The /f UEFI flag explicitly tells the tool to format the BCD store for Unified Extensible Firmware Interface systems. If you omit the /f parameter, bcdboot may auto-detect the firmware type, but being explicit prevents errors on hybrid systems. For Legacy BIOS systems, the command changes slightly:

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

In this scenario, S: should be the main Windows partition itself, not a separate small ESP. The /f BIOS flag ensures the creation of legacy boot files like bootmgr instead of bootmgfw.efi. Verifying the Operation If the command executes successfully, CMD will display the message "Boot files created successfully." You can verify the new BCD entries by running bcdedit /enum. Look for an entry under windowsbootloader that references the target drive. If the output shows errors such as "The specified system device cannot be found," double-check that the target drive letter is correct and that the partition is formatted appropriately (FAT32 for UEFI, NTFS for most BIOS setups).

Common Troubleshooting Steps

Errors during this process usually stem from permission issues or incorrect partition types. If you receive an "Access Denied" error, ensure you are running CMD as an Administrator. If you encounter file copy errors, verify that the target partition is not read-only. You can check this by right-clicking the drive in File Explorer, selecting Properties, and ensuring "Read-only" is unchecked. Another frequent issue arises when the target partition is not recognized as a system partition. In DiskPart, after selecting the volume, run list partition to view details. For UEFI, the partition type GUID should correspond to Microsoft Reserved or EFI System. If the partition is formatted as exFAT or NTFS (for UEFI targets), bcdboot will fail. Reformat the target partition to FAT32 using format S: /fs:fat32 before retrying the command. For users dealing with variable persistence in scripts that automate these steps, refer to Persisting Windows Variables in CMD Files to ensure your batch jobs maintain state across multiple execution contexts.

Frequently Asked Questions

Can I make a USB drive bootable using bcdboot?

Yes, provided the USB drive is formatted correctly and large enough to hold the Windows files. You would point the /s parameter to the USB drive letter. However, for general-purpose bootable media, tools like Rufus or the Media Creation Tool are often easier. bcdboot is best suited for internal drives or specific deployment scenarios.

What happens if I use the wrong firmware flag (/f BIOS vs /f UEFI)?

Using the wrong flag will result in boot files being created in a format incompatible with your motherboard's firmware. A UEFI system expecting .efi files will fail to find a bootloader if only legacy bootmgr files are present. Conversely, a BIOS system will ignore .efi files. Always match the flag to your hardware architecture.

Do I need to mark the partition as Active for UEFI systems?

No. The concept of an "Active" partition applies primarily to Legacy BIOS (MBR) systems. UEFI systems rely on the EFI System Partition (ESP) being identified by its partition type GUID and file system structure, not by an active flag. Marking an ESP as active has no effect on UEFI boot processes.

Why does bcdboot say "Boot files created successfully" but the PC still won't boot?

This indicates that while the files were copied, the firmware may not be set to prioritize that drive. Check your BIOS/UEFI settings to ensure the target drive or the ESP containing the boot files is listed first in the boot order. Additionally, Secure Boot might be blocking unsigned boot loaders if you are using custom modifications.

Can I use bcdboot to clone a Windows installation to a different SSD?

does not clone data; it only copies boot files and creates BCD entries. To move an entire Windows installation, you must first clone the drive using disk imaging software. After cloning, you can use bcdboot to fix the boot configuration on the new drive, especially if the UUIDs have changed due to the cloning process.