Bcdboot Exe Bootsect Exe E Imagex Exe
And also the Retrieve Tools plugin, It also recovers bcdboot.exe, WimMountInstall.exe. And copies them in%tools% folder. Install wimmount v6.1 driver via Win7 Waik WimMountInstall.exe: the driver is. Capture with Imagex.exe 1min 53s. 2WindowsSystem32BootSect.exe' -o'E:Destination Folder'. Bcdboot.exe is a Windows command line utility used to install the bootmgr bootloader and to configure its boot configuration data (BCD). Bcdboot copies the core boot files from a chosen Windows installation on the disk to the system boot partitionand adds that an appropriate entry to the boot configuration data.
bcdboot.exe is a Windows command line utility used to install the bootmgr bootloader and to configure its boot configuration data (BCD). bcdboot copies the core boot files from a chosen Windows installation on the disk to the system boot partition, and adds that an appropriate entry to the boot configuration data.
Contents Belkin usb wifi hackintosh.
Synopsis
Arguments enclosed with bracers { } are necessary, arguments enclosed with bracekts [ ] are optional, stands for “or“.
Description
bcdboot is used to install the bootmgr bootloader to the system partition, creates a new BCD store entry and initializes its contents as-needed. The BCD is a firmware-independent database containing boot-time configuration data. It replaced the old boot.ini previously used by the ntldr bootloader in Windows XP and Windows Server 2003. bcdboot doesn’t affect the bootsector or the master boot record (MBR), which must be configured separately. It can be used to either reinstall the bootloader files overwriting default boot entry, or optionally to add a single entry to the boot menu instead. bcdboot is especially useful when setting up multiple operating systems on a single computer, and can be used to fix boot problems such as an operating system not showing up in the boot menu or an out-dated or corrupted bootloader installation.
The command line arguments to bcdboot are as follows:
source
Instructs bcdboot to copy the critical boot files from the source Windows installation to the system (boot) partition, installs a BCD entry for the source installation, and adds that entry to the displayed boot menu. The typical source format is C:Windows. On UEFI-based systems, boot environment files and the BCD store are stored on a the reserved UEFI system partition, while on BIOS-based systems these files are stored on the primary (active) partition.
/i <locale>
This flag specifies the localization of the boot environment; the locale value for US English is en-us
/s <volumeLetter>
Copies the boot environment files to a partition labeled by volumeLetter and creates a new BCD store on it. As the system partition isn’t labeled, this option is not used in the typical deployment scenarios. The user should use this option when configuring a drive that will be used on another computer i.e. a secondary hard drive, or in case the correct boot partition is not automatically identified. More on the difference of deployment depending on the firmware type can be found in the section regarding the /f option below.
/f <firmwareType>
Specifies the firmware type. Valid values are UEFI, BIOSand ALL. Used with the /s flag. The UEFIvalue copies only the UEFI-compatible boot files and initializes a BCD store on a partition specified by the /s flag making it compatible with UEFI-based systems. The BIOS value does the same for BIOS-based systems. The ALL value installs both the BIOS- and UEFI-compatible versions of the bootloader and also configures each of their BCDs accordingly.
/v
Enables verbose mode. In verbose mode, extra information about the operations being carried out is displayed to the end user.
/m <OSloaderGuid>
Merges an existing BCD entry identified by the GUID OSloaderGuid with the system template to create a bootable entry. By default, this option will merge only global objects.
/addlast
The default behaviour of bcdboot is that the newly-created entry is added as the first in Windows Boot Manager menu. This options specifies that it is added as the last entry in the list instead.
/p
Used to preserve the existing UEFI boot order. The boot entry positions are preserved, and if the entry doesn’t exist it will be added as the first one in the list. It cannot be used together with the /addlast option.
/d
Preserves the existing default windows boot entry.
/c
Specifies that the existing objects (BCD elements) won’t be migrated. In Windows 10, during an upgrade BCD elements such as debugsettings or flightsigning are preserved as well.
Exit Status
bcdboot returns 0 on success and 1 if an error occurs.
Examples
To copy the boot environment files to the system partition and add a Windows installation located on the D: drive to the boot entry:
bcdboot D:Windows
To copy the boot environment files from the C:Windows folder to the system partition on a secondary hard drive. Here, the partition labeled with a D: is the system partition of the secondary hard drive:
bcdboot C:Windows /s D:
To copy the boot environment files on a partition labeled D: that belongs to a secondary hard drive, including boot files to support either a UEFI-based or a BIOS-based computer:
bcdboot c:Windows /s D: /f ALL
Compatibility
bcdboot works on Windows 10, Windows 8.1, WIndows 8, Windows 7, Wndows Vista, Windows Server 2016. Technical Preview, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2, Windows Server 2008.
History
bcdboot was first introduced in Windows 7. The /p, /d, and /c flags were introduced in Windows 10.
See Also
bootsect – tool used to update bootsector and master boot record code.
-->BCDBoot is a command-line tool used to configure the boot files on a PC or device to run the Windows operating system. You can use the tool in the following scenarios:
- Add boot files to a PC after applying a new Windows image. In a typical image-based Windows deployment, use BCDBoot to set up the firmware and system partition to boot to your image. To learn more, see Capture and Apply Windows, System, and Recovery Partitions.
- Set up the PC to boot to a virtual hard disk (VHD) file that includes a Windows image. To learn more, see Boot to VHD (Native Boot): Add a Virtual Hard Disk to the Boot Menu.
- Repair the system partition. If the system partition has been corrupted, you can use BCDBoot to recreate the system partition files by using new copies of these files from the Windows partition.
- Set up or repair the boot menu on a dual-boot PC. If you've installed more than one copy of Windows on a PC, you can use BCDBoot to add or repair the boot menu.
File Locations
In Windows and Windows Preinstallation Environment (WinPE) | %WINDIR%System32BCDBoot.exe |
In the Windows Assessment and Deployment Kit (Windows ADK): | C:Program Files (x86)Windows Kits10Assessment and Deployment KitDeployment Toolsamd64BCDBootBCDBoot.exe |
Supported operating systems
BCDBoot can copy boot environment files from images of Windows 10, Windows 8.1, Windows 8, Windows 7, Windows Vista, Windows Server 2016 Technical Preview, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2, or Windows Server 2008.
How It Works
To configure the system partition, BCDBoot copies a small set of boot-environment files from the installed Windows image to the system partition.
BCDBoot can create a Boot Configuration Data (BCD) store on the system partition using the latest version of the Windows files:
- BCDBoot creates a new BCD store and initialize the BCD boot-environment files on the system partition, including the Windows Boot Manager, using the %WINDIR%System32ConfigBCD-Template file.
- New in Windows 10: During an upgrade, BCDBoot preserves any other existing boot entries, such as debugsettings, when creating the new store. Use the /c option to ignore the old settings and start fresh with a new BCD store.
- If there is already a boot entry for this Windows partition, by default, BCDBoot erases the old boot entry and its values. Use the /m option to retain the values from an existing boot entry when you update the system files.
- By default, BCDBoot moves the boot entry for the selected Windows partition to the top of the Windows Boot Manager boot order. Use the /d option to preserve the existing boot order.
On UEFI PCs, BCDBoot can update the firmware entries in the device’s NVRAM:
- BCDBoot adds a firmware entry in the NVRAM to point to the Windows Boot Manager. By default, this entry is placed as the first item in the boot list. Use the /p option to preserve the existing UEFI boot order. Use /addlast to add it to the bottom of the boot order list.
Command-Line Options
The following command-line options are available for BCDBoot.exe.
BCDBOOT <source> [/l <locale>] [/s <volume-letter> [/f <firmware type>]] [/v] [/m [{OS Loader GUID}]] [/addlast or /p] [/d] [/c]
| Option | Description |
|---|---|
<source> | Required. Specifies the location of the Windows directory to use as the source for copying boot-environment files. The following example initializes the system partition by using BCD files from the C:Windows folder: |
/l <locale> | Optional. Specifies the locale. The default is US English ( The following example sets the default BCD locale to Japanese: |
/s <volume letter> | Optional. Specifies the volume letter of the system partition. This option should not be used in typical deployment scenarios. Use this setting to specify a system partition when you are configuring a drive that will be booted on another computer, such as a USB flash drive or a secondary hard drive. UEFI:
BIOS:
The following example copies BCD files from the C:Windows folder to a system partition on a secondary hard drive that will be booted on another computer. The system partition on the secondary drive was assigned the volume letter S: The following example creates boot entries on a USB flash drive with the volume letter S, including boot files to support either a UEFI-based or a BIOS-based computer: |
/f <firmware type> | Optional. Specifies the firmware type. Valid values include
If you specify the /f option, you must also specify the /s option to identify the volume letter of the system partition. The following example copies BCD files that support booting on either a UEFI-based or a BIOS-based computer from the C:Windows folder to a USB flash drive that was assigned the volume letter S: |
/v | Optional. Enables verbose mode. Example: |
/m [{OS Loader GUID}] | Optional. Merges the values from an existing boot entry into a new boot entry. By default, this option merges only global objects. If you specify an OS Loader GUID, this option merges the loader object in the system template to produce a bootable entry. The following example merges the operating-system loader in the current BCD store that the specified GUID identifies in the new BCD store: |
/addlast | Optional. Specifies that the Windows Boot Manager firmware entry should be added last. The default behavior is to add it first. Cannot be used with /p. |
/p | Optional. Specifies that the existing Windows Boot Manager firmware entry position should be preserved in the UEFI boot order. If entry does not exist, a new entry is added in the first position. Cannot be used with /addlast. By default, during an upgrade BCDBoot moves the Windows Boot Manager to be the first entry in the UEFI boot order. |
/d | Optional. Preserves the existing default operating system entry in the {bootmgr} object in Windows Boot Manager. |
/c | Optional. Specifies that any existing BCD elements should not be migrated. New for Windows 10: By default, during an upgrade, BCD elements such as debugsettings or flightsigning are preserved. |
Repair the system partition
If the system partition has been corrupted, you can use BCDBoot to recreate the system partition files by using new copies of these files from the Windows partition.
Boot your PC to a command line. For example, boot to the Windows installation disk and press Shift+F10, or boot to Windows PE (WinPE: Create USB Bootable drive).
Use Diskpart to determine which drive letter contains your Windows partition and system partition (
diskpart, list vol, exit).Optional: Format your system partition:
format (drive letter of your system partition) /qAdd a boot entry for your Windows partition:
bcdboot D:WindowsReboot the PC. Windows should appear.
Set up or repair the boot menu on a dual-boot PC
When setting up a PC to boot more than one operating system, you may sometimes lose the ability to boot into one of the operating systems. The BCDBoot option allows you to quickly add boot options for a Windows-based operating system. To set up a dual-boot PC:
Install a separate hard drive or prepare a separate partition for each operating system.
Install the operating systems. For example, if your PC has Windows 7, install Windows 10 onto the other hard drive or partition.
Reboot the PC. The boot menus should appear with both operating systems listed.
If both operating systems aren't listed:
Open a command line, either as an administrator from inside Windows, or by booting to a command line using the Windows installation media and pressing Shift+F10, or by booting to Windows PE (WinPE: Create USB Bootable drive).
Add boot options for a Windows operating system.
Reboot the PC. Now, the boot menu will show both menu options.
Troubleshooting
For information about repairing the boot files on a PC with Windows XP and a more recent version of Windows such as Windows 7, see the Microsoft Knowledge Base Article 2277998.