{"id":3949,"date":"2016-05-12T04:36:05","date_gmt":"2016-05-12T09:36:05","guid":{"rendered":"http:\/\/neosmart.net\/wiki\/?page_id=3949"},"modified":"2016-06-06T07:25:48","modified_gmt":"2016-06-06T12:25:48","slug":"bcdboot","status":"publish","type":"page","link":"https:\/\/neosmart.net\/wiki\/winman\/bcdboot\/","title":{"rendered":"bcdboot.exe"},"content":{"rendered":"

bcdboot.exe<\/strong> is a Windows command line utility used to install the bootmgr bootloader and to configure its boot configuration data (BCD). bcdboot<\/code>\u00a0copies the core\u00a0boot files from\u00a0a chosen\u00a0Windows installation on the disk to the system boot\u00a0partition,\u00a0\u00a0and adds that an appropriate entry\u00a0to the boot configuration data.<\/p>\n

Synopsis<\/span><\/h2>\n

Arguments enclosed with bracers\u00a0{ \u00a0}<\/strong> are necessary, arguments enclosed with\u00a0bracekts [ \u00a0]<\/strong> are optional, | stands for \u201cor<\/strong>\u201c.\u00a0<\/strong><\/p>\n

bcdboot {source} [\/i <locale>] [\/s <volumeLetter> [\/f <firmwareType>]] [\/v] [\/m <OSloaderGuid>]] [\/addlast | \/p] [\/d] [\/c]<\/strong><\/pre>\n
Description<\/span><\/h2>\n
bcdboot<\/strong>\u00a0is used to install the bootmgr\u00a0bootloader to the system partition, creates a new BCD store entry and initializes its contents as-needed. The BCD is a firmware-independent database containing\u00a0boot-time configuration data. It replaced the old boot.ini previously used by the ntldr\u00a0bootloader in Windows XP and Windows Server 2003. bcdboot<\/code>\u00a0doesn’t affect the bootsector or the master boot record (MBR<\/strong>), which must be configured separately. It can be used to either reinstall the bootloader files overwriting default\u00a0boot entry, or optionally to add a single entry to the boot menu\u00a0instead. bcdboot<\/code>\u00a0is 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.<\/p>\n
The command line arguments to bcdboot<\/code>\u00a0are as follows:<\/p>\n
source<\/code><\/strong>
\nInstructs bcdboot to copy\u00a0the critical boot files from the source<\/code>\u00a0Windows installation to the system (boot) partition, installs a BCD entry for the\u00a0source<\/em> installation, and adds that entry to the displayed boot menu. The typical\u00a0source<\/code>\u00a0format is C:\\Windows<\/code><\/strong>. On UEFI-based systems, boot environment files and the BCD store are stored on a the reserved UEFI system\u00a0partition, while\u00a0on BIOS-based systems\u00a0these\u00a0files are stored on the primary (active) partition.<\/p>\n
\/i <locale><\/code><\/strong>
\nThis flag specifies\u00a0the localization of the boot environment; the\u00a0locale<\/code>\u00a0value for US English is en-us<\/code><\/p>\n
\/s <volumeLetter><\/code><\/strong>
\nCopies the boot environment files to a partition labeled by\u00a0volumeLetter<\/code> and creates\u00a0a 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<\/code> option below.<\/p>\n
\/f <firmwareType><\/code><\/strong>
\nSpecifies the firmware type. Valid values are UEFI<\/code><\/strong>, BIOS<\/code> <\/strong>and ALL<\/code><\/strong>.\u00a0Used with the \/s<\/code> flag. The UEFI<\/code> <\/strong>value copies only<\/em>\u00a0the UEFI-compatible boot files and\u00a0initializes\u00a0a BCD store on a partition specified by the \/s flag making it compatible with UEFI-based systems. The BIOS\u00a0<\/code><\/strong>value\u00a0does the same for BIOS-<\/code>based systems. The ALL<\/code><\/strong> value installs both the BIOS- and UEFI-compatible versions of the bootloader and also configures each of their BCDs accordingly.<\/p>\n
\/v<\/code><\/strong>
\nEnables\u00a0verbose mode. In verbose mode,\u00a0extra information about the operations being carried out is displayed to the end user.<\/p>\n
\/m <OSloaderGuid><\/code><\/strong>
\nMerges an existing BCD entry identified by the GUID OSloaderGuid<\/code>\u00a0with the system template to create a bootable entry. By default, this option will merge only global objects.<\/p>\n
\/addlast<\/code><\/strong>
\nThe default behaviour of bcdboot is that the newly-created entry is added as the first\u00a0in\u00a0Windows Boot Manager menu. This options specifies that it is added as the last entry in the list instead.<\/p>\n
\/p<\/code><\/strong>
\nUsed 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\u00a0in\u00a0the list. It cannot be used together with\u00a0the \/addlast<\/code><\/strong> option.<\/p>\n
\/d<\/code><\/strong>
\nPreserves the existing default windows boot entry.<\/p>\n
\/c<\/code><\/strong>
\nSpecifies 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.<\/p>\n
Exit Status\u00a0<\/span><\/h2>\n
bcdboot<\/strong>\u00a0returns 0\u00a0<\/strong>on success and 1<\/strong> if an error occurs.<\/p>\n
Examples<\/span><\/h2>\n
To copy the boot environment files to the system partition and add a Windows installation located on the D: drive to the boot entry:<\/p>\n
bcdboot D:\\Windows<\/code><\/strong><\/p>\n
To copy the\u00a0boot environment files from the C:\\Windows folder to the system partition on a secondary hard drive. Here, the\u00a0partition labeled with a D: is the system partition of the secondary hard drive:<\/p>\n
bcdboot C:\\Windows \/s D:<\/code><\/strong><\/p>\n
To copy the boot environment files on\u00a0a partition labeled D: that belongs to a secondary hard drive, including boot files to support either a UEFI-based or a BIOS-based computer:<\/p>\n
bcdboot c:\\Windows \/s D: \/f\u00a0ALL<\/code><\/strong><\/p>\n
Compatibility<\/span><\/h2>\n
bcdboot<\/strong>\u00a0works 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.<\/p>\n
History<\/span><\/h2>\n
bcdboot<\/strong>\u00a0was first introduced in Windows 7. The\u00a0\/p<\/code>, \/d<\/code>, and \/c<\/code> flags were introduced in Windows 10.<\/p>\n
See Also<\/span><\/h2>\n
bootsect<\/a>\u00a0– tool used to update bootsector and master boot record code.<\/p>\n","protected":false},"excerpt":{"rendered":"
bcdboot.exe is a Windows command line utility used to install the bootmgr bootloader and to configure its boot configuration data (BCD). bcdboot\u00a0copies the core\u00a0boot files from\u00a0a chosen\u00a0Windows installation on the disk to the system boot\u00a0partition,\u00a0\u00a0and adds that an appropriate entry\u00a0to the boot configuration data. Synopsis Arguments enclosed with bracers\u00a0{ \u00a0} are necessary, arguments enclosed with\u00a0bracekts […]<\/p>\n","protected":false},"author":516,"featured_media":0,"parent":3793,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-3949","page","type-page","status-publish","hentry"],"aioseo_notices":[],"jetpack_shortlink":"https:\/\/wp.me\/P3SlTq-11H","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/neosmart.net\/wiki\/wp-json\/wp\/v2\/pages\/3949","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/neosmart.net\/wiki\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/neosmart.net\/wiki\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/neosmart.net\/wiki\/wp-json\/wp\/v2\/users\/516"}],"replies":[{"embeddable":true,"href":"https:\/\/neosmart.net\/wiki\/wp-json\/wp\/v2\/comments?post=3949"}],"version-history":[{"count":49,"href":"https:\/\/neosmart.net\/wiki\/wp-json\/wp\/v2\/pages\/3949\/revisions"}],"predecessor-version":[{"id":4294,"href":"https:\/\/neosmart.net\/wiki\/wp-json\/wp\/v2\/pages\/3949\/revisions\/4294"}],"up":[{"embeddable":true,"href":"https:\/\/neosmart.net\/wiki\/wp-json\/wp\/v2\/pages\/3793"}],"wp:attachment":[{"href":"https:\/\/neosmart.net\/wiki\/wp-json\/wp\/v2\/media?parent=3949"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}