Bcdedit /enum All Versus Bcdedit /enum Firmware

This command creates a new empty kick configuration information store. The created store is not a system store.

bcdedit /createstore <file name>

<file name> specifies the
file name
of the boot configuration data shop. If the file name contains spaces, it must be enclosed in
quotation marks
(“”).

Example:

The following command creates the specified store file:

bcdedit /createstore C:\Data\BCD

This control
exports
the contents of the system shop into a file. This file can be used later to restore the state of the system store. This command is only valid for the organisation store.

<file name> is the file name to exist used as the destination for the export. If the file proper name contains spaces, it must exist enclosed in quotation marks (“”).

Instance:

The following command exports the organization store to the specified file:

bcdedit /export "C:\Information\BCD Backup"

This command restores the state of the organization store using a backup data file previously generated using the /consign command. Whatsoever existing entries in the system shop are deleted before the import takes identify. This command is merely valid for the system shop.

bcdedit /import <file name> [/make clean]

<file name> the proper noun of the file that is imported into the system store.

If the file name contains spaces, it must be enclosed in quotation marks (“”).

/clean specifies that all existing firmware boot entries should be deleted (just affects EFI systems).

Case:

The following control imports the specified file into the organisation store.

bcdedit /import "C:\Information\BCD Backup" /clean

This command sets the organisation shop device. This command is but valid for EFI systems in cases where the system store device is ambiguous. This setting does not persist across reboots.

bcdedit /sysstore <devicename>

<devicename> the name of a arrangement segmentation to set as the system store device. The device must be a system partition.

Example:

The following control sets the system store device as specified:

bcdedit /sysstore C:

This command creates a copy of the specified boot entry.

bcdedit [/store <file name>] /copy {<id>} /d <description>

<file name> specifies the store to be used. If this option is non specified, the arrangement shop is used. For more information, run “bcdedit /? shop”.

<id> specifies the identifier of the entry to be copied. For more than information about identifiers, run”bcdedit /? ID”.

<description> specifies the clarification to exist applied to the new entry.

Case:

The following command creates a copy of the specified operating arrangement kicking entry:

bcdedit /copy {cbd971bf-b7b8-4885-951a-fa03044f5d71} /d "Copy of entry"

The following command creates an NTLDR based Os loader entry (Ntldr):

bcdedit /create {ntldr} /d "Before Windows Os Loader"

The post-obit command creates a RAM disk additional options entry:

bcdedit /create {ramdiskoptions}

The post-obit command creates a new operating system boot entry:

bcdedit /create /d "Windows Vista" /awarding osloader

The following control creates a new debugger settings entry:

bcdedit /create {dbgsettings}

This command deletes an entry from the kick configuration data store.

bcdedit [/store <file name>] /delete <id> [/f] [/cleanup | /nocleanup]

<file proper name> specifies the shop to be used. If this option is non specified, the organization store is used. For more information, run “bcdedit /? store”.

<id> specifies the identifier of the boot entry that you lot want to delete. For more data nigh identifiers, run “bcdedit /? ID”.

/f – Deletes the specified entry. Without this option, bcdedit volition not delete any entries that have a well-known identifier.

/cleanup – Deletes the specified entry and removes the entry from the display order. Any other references to the entry being deleted are removed from the store. When deleting an Bone loader entry, the associated resume from hibernation entry is likewise deleted if it is not referenced by whatever other OS loaders. This option is assumed unless /nocleanup is specified.

/nocleanup – Deletes the specified entry without removing the entry from the display order.

Examples:

The following command deletes the specified operating system entry from the store and removes the entry from the brandish society:

bcdedit /delete {cbd971bf-b7b8-4885-951a-fa03044f5d71}

The following control deletes the specified operating system entry from the store and removes the entry from the brandish lodge:

bcdedit /delete {cbd971bf-b7b8-4885-951a-fa03044f5d71} /cleanup

The following command deletes the specified operating arrangement entry from the store without removing the entry from the display order:

bcdedit /delete {cbd971bf-b7b8-4885-951a-fa03044f5d71} /nocleanup

The post-obit command deletes the NTLDR based Os loader entry from the store:

bcdedit /delete {ntldr} /f

This command creates a mirror of the specified boot entry.

bcdedit [/store <file name>] /mirror {<id>}

<file proper name> specifies the store to exist used. If this option is non specified, the organization shop is used. For more information, run “bcdedit /? store”.

<id> specifies the identifier of the entry to be mirrored. For more information about identifiers, run “bcdedit /? ID”.

Instance:

The post-obit control creates a mirror of the specified operating system kick entry:

bcdedit /mirror {cbd971bf-b7b8-4885-951a-fa03044f5d71}

This command deletes a data element from an entry in the kick configuration data store.

bcdedit [/store <file name>] /deletevalue [<id>] <datatype>

<file name> specifies the store to be used. If this choice is non specified, the organisation store is used. For more than information, run “bcdedit /? store”.

<id> specifies the identifier of the entry that will exist modified. If not specified, {current} is used. For more data about identifiers, run “bcdedit /? ID”.

<datatype> specifies the option that volition be removed from the specified entry. Run “bcdedit /? TYPES” for more information nigh data types.

Examples:

The following command deletes the bootsequence option from the boot managing director entry:

bcdedit /deletevalue {bootmgr} bootsequence

The following command deletes the Windows Pre-installation Environs (WinPE) value from the current operating system kicking entry:

bcdedit /deletevalue winpe

The following command deletes the Windows PE value from the specified operating arrangement boot entry:

bcdedit /deletevalue {cbd971bf-b7b8-4885-951a-fa03044f5d71} winpe

This command sets an entry pick value in the boot configuration data shop.

bcdedit [/shop <file name>] /set [{<id>}] <datatype> <value> [ /addfirst | /addl ast | /remove ]

<file proper name> specifies the shop to be used. If this pick is not specified, the system store is used. For more information, run “bcdedit /? store”.

<id> specifies the identifier of the entry to be modified. If not specified, {current} is used. For more information about identifiers, run “bcdedit /? ID”.

<datatype> specifies the option data blazon that will be created or modified. Run “bcdedit /? TYPES” for more information about data types.

<value> specifies the value that should exist assigned to the option. The format of <value> depends on the data type specified. Run “bcdedit /? FORMATS” for more information almost data formats.

/addfirst – This switch can simply exist used if datatype is an object list. Adds the specified entry identifier to the tiptop of the list. If this switch is specified, simply a single entry identifier may be specified. If the specified identifier is already in the listing, it is moved to the height of the list.

/addlast – This switch can only exist used if datatype is an object listing. Adds the specified entry identifier to the finish of the list. If this switch is specified, only a single entry identifier may be specified. If the specified identifier is already in the listing, it is moved to the end of the list.

/remove – This switch can but be used if datatype is an object list. Removes the specified entry identifier from the listing. If this switch is specified, simply a single entry identifier may be specified. If the identifier is not in the listing, so the functioning has no effect. If the final entry is being removed, so the datatype value is deleted.

Examples:

The post-obit command sets the awarding device to the partition C: for the specified operating system entry:

bcdedit /gear up {cbd971bf-b7b8-4885-951a-fa03044f5d71} device partition=C:

Notation: Employ ‘hd_partiton=’ syntax to explicitly disable automatic VHD detection, and create entries that are compatible for booting a virtual car, for case:

bcdedit /store F:\boot\bcd /fix {default} device hd_partition=F:

The post-obit command sets the OS device to a VHD file (C:\vdisks\vdisk01.vhd) for the specified operating organisation entry:

bcdedit /set {cbd971bf-b7b8-4885-951a-fa03044f5d71} osdevice vhd=[C:]\vdisks\disk01.vhd

The following control sets the application path to \windows\system32\winload.exe for the specified operating system entry:

bcdedit /fix {cbd971bf-b7b8-4885-951a-fa03044f5d71} path \windows\system32\winload.exe

The post-obit command sets the NX policy to OptIn for the current operating organisation kicking entry.

bcdedit /ready nx optin

This control lists entries in a store. The /enum control is the default, then running “bcdedit” without parameters is equivalent to running “bcdedit /enum ACTIVE”.

bcdedit [/store <file name>] /enum [<type> | <id>] [/five]

<file name> specifies the store to be used. If this choice is not specified, the system store is used. For more information, run “bcdedit /? shop”.

<type> specifies the type of entries to be listed. <type> tin can be one of the following:

Active – All entries in the kick director display lodge by default.

FIRMWARE – All firmware applications.

BOOTAPP – All boot surroundings applications.

BOOTMGR – The kicking manager.

OSLOADER – All operating system entries.

RESUME – All resume from hibernation entries.

INHERIT – All inherit entries.

ALL – Practice all entries.

<id> specifies the identifier of the entry to exist listed. If an identifier is provided, and then just the specified object will be listed. For information about identifiers, run “bcdedit /? ID”.

/v Displays entry identifiers in total, rather than using names for well-known identifiers.

Examples:

The following command lists all operating organisation loader boot entries:

bcdedit /enum OSLOADER

The following command lists all boot managing director entries:

bcdedit /enum BOOTMGR

The post-obit command lists only the default kick entry:

bcdedit /enum {default}

The following command lists just the specified operating system boot entry:

bcdedit /enum {b38a9fc1-5690-11da-b795-e9ad3c5e0e3a}

Command line option that displays entry identifiers in full, rather than using names for well-known identifiers.

Use /five past itself as a command to display entry identifiers in full for the Agile blazon.

Usually, any well-known entry identifiers are replaced by their friendly autograph form. Specifying /five as a command line switch prevents this replacement and displays all identifiers in total. Running “bcdedit /v” past itself is equivalent to running “bcdedit /enum Active /five”.

bcdedit /5

Example:

The post-obit control lists the active entries in the system store with all entry identifiers displayed in full.

bcdedit /enum Active /5

This command sets the one-fourth dimension boot sequence to be used by the kicking director.

bcdedit /bootsequence <id> [...] [ /addfirst | /addlast | /remove ]

<id> […] specifies a listing of identifiers that make up the boot sequence. You must specify at least one identifier and must separate identifiers by spaces. For more information about identifiers, run “bcdedit /? ID”.

/addfirst – Adds the specified entry identifier to the top of the kicking sequence. If this switch is specified, merely a unmarried identifier may be specified. If the identifier is already in the list, information technology is moved to the height of the listing.

/addlast – Adds the specified entry identifier to the end of the boot sequence. If this switch is specified, only a unmarried identifier may exist specified. If the identifier is already in the listing, it is moved to the finish of the list.

/remove – Removes the specified entry identifier from the boot sequence. If this switch is specified, only a single entry identifier may be specified. If the identifier is not in the list, and then the performance has no issue. If the terminal entry is being removed, then the kicking sequence value is deleted from the boot managing director entry.

Examples:

The following command sets two Os entries and the NTLDR based Os loader in the kick manager one-fourth dimension kick sequence:

bcdedit /bootsequence {802d5e32-0784-11da-bd33-000476eba25f} {cbd971bf-b7b8-4885-951a-fa03044f5d71} {ntldr}

The following command adds the specified Os entry to the cease of the boot manager i-time boot sequence:

bcdedit /bootsequence {802d5e32-0784-11da-bd33-000476eba25f} /addlast

This command sets the default entry that the kicking manager will use when the timeout expires.

bcdedit /default <id>

<id> specifies the identifier of the boot entry to exist used as the default when the time-out expires. For information most identifiers, run “bcdedit /? ID”.

Examples:

The post-obit command sets the specified entry as the default boot manager entry:

bcdedit /default {cbd971bf-b7b8-4885-951a-fa03044f5d71}

The following control sets the NTLDR based OS loader equally the default entry:

bcdedit /default {ntldr}

This control sets the display order to exist used by the boot manager.

bcdedit /displayorder <id> [...] [ /addfirst | /addlast | /remove ]

<id> […] specifies a listing of identifiers that make upwards the display order. At to the lowest degree 1 identifier must be specified and they must be separated past spaces. For more than information near identifiers, run “bcdedit /? ID”.

/addfirst – Adds the specified entry identifier to the peak of the display order. If this switch is specified, but a single entry identifier may be specified. If the specified identifier is already in the list, information technology is moved to the top of the list.

/addlast – Adds the specified entry identifier to the end of the display club. If this switch is specified, just a unmarried entry identifier may exist specified. If the specified identifier is already in the listing, it is moved to the stop of the list.

/remove – Removes the specified entry identifier from the brandish gild. If this switch is specified, but a single entry identifier may exist specified. If the identifier is not in the listing, and so the operation has no effect. If the terminal entry is being removed, so the display gild value is deleted from the kick director entry.

Examples:

The following command sets two Bone entries and the NTLDR based OS loader in the boot director brandish order:

bcdedit /displayorder {802d5e32-0784-11da-bd33-000476eba25f} {cbd971bf-b7b8-4885-951a-fa03044f5d71} {ntldr}

The post-obit command adds the specified Bone entry to the finish of the boot manager display order:

bcdedit /displayorder {802d5e32-0784-11da-bd33-000476eba25f} /addlast

This command sets the time to wait, in seconds, before the boot manager selects a default entry. For data about setting the default entry, run “bcdedit /? default”.

bcdedit /timeout <timeout>

<timeout> specifies the fourth dimension to wait, in seconds, before the kicking manager selects a default entry.

Example:

The following control sets the boot manager <timeout> to 30 seconds:

bcdedit /timeout 30

This control will set the display order to be used past the boot manager when displaying the tools card.

bcdedit /toolsdisplayorder <id> [...] [ /addfirst | /addlast | /remove ]

<id> […] specifies a list of identifiers that make up the tools brandish order. At least one identifier must be specified and they must be separated past spaces. For more information near identifiers, run “bcdedit /? ID”.

/addfirst – Adds the specified entry identifier to the pinnacle of the tools display society. If this switch is specified, only a unmarried entry identifier may exist specified. If the specified identifier is already in the list, it is moved to the top of the list.

/addlast – Adds the specified entry identifier to the end of the tools display lodge. If this switch is specified, only a unmarried entry identifier may exist specified. If the specified identifier is already in the listing, information technology is moved to the end of the listing.

/remove – Removes the specified entry identifier from the tools display order. If this switch is specified, only a single entry identifier may exist specified. If the identifier is not in the listing, then the functioning has no issue. If the last entry is existence removed, and so the tools display lodge value is deleted from the boot manager entry.

Examples:

The following command sets 2 tools entries and the memory diagnostic in the boot manager’s tools display order:

bcdedit /toolsdisplayorder {802d5e32-0784-11da-bd33-000476eba25f} {cbd971bf-b7b8-4885-951a-fa03044f5d71} {memdiag}

The following command adds the specified tool entry to the end of the kick director’south tools display order:

bcdedit /toolsdisplayorder {802d5e32-0784-11da-bd33-000476eba25f} /addlast

This command enables or disables Emergency Management Services for the specified entry.

bcdedit /bootems [<id>] { ON | OFF }

<id> specifies the identifier of the entry to be modified. Although this command volition work for any entry, it is but constructive for kicking applications.

Instance:

The post-obit command enables Emergency Management Services for the boot director:

bcdedit /bootems {bootmgr} ON

This control enables or disables Emergency Direction Services for the specified operating organization boot entry.

bcdedit /ems [<id>] { ON | OFF }

<id> specifies the identifier of the entry to be modified. Only “Windows boot loader” entries tin be specified. If non specified, {current} is used. For more information well-nigh identifiers, run “bcdedit /? ID”.

Example:

The following control enables Emergency Direction Services for the current operating organisation boot entry:

bcdedit /ems ON

This control sets the global Emergency Management Services settings for the system. Emssettings does not enable or disable Emergency Direction Services for whatsoever particular boot entry.

bcdedit /emssettings [ BIOS ] | [ EMSPORT:<port> | [EMSBAUDRATE:<baudrate>] ]

BIOS specifies that the system will use BIOS settings for the Emergency Management Services configuration. This switch merely works on systems that take Emergency Direction Services support provided by the BIOS.

<port> specifies the series port to use as the Emergency Management Services port. This selection should non be specified with the BIOS option.

<baudrate> specifies the serial baud rate to use for Emergency Direction Services. This command should not be specified with the BIOS selection. <baudrate> is optional, and the default is 9,600 baud.

Examples:

The post-obit command sets the Emergency Management Services parameters to use BIOS settings:

bcdedit /emssettings BIOS

The following control sets the Emergency Management Services parameters to use com2: at 115,200 baud.

bcdedit /emssettings EMSPORT:2 EMSBAUDRATE:115200

This command enables or disables the kick debugger for the specified kicking entry. Although this control works for whatever entry, information technology is only effective for kick applications.

bcdedit /bootdebug [<id>] { ON | OFF }

<id> specifies the identifier of the entry to be modified. For information about identifiers, run “bcdedit /? ID”.

Examples:

The post-obit command enables kick debugging for the Windows operating system loader of the current operating arrangement kick entry:

bcdedit /bootdebug ON

The following control disables boot debugging for the Windows kick managing director:

bcdedit /bootdebug {bootmgr} OFF

Sets the global debugger parameters.

This control enables or disables the kernel debugger for the specified boot entry.

bcdedit /debug [<id>] { ON | OFF }

<id> specifies the identifier of the entry to be modified. Only Windows kicking loader entries may be specified. If not specified, {current} is used. For more information about identifiers, run “bcdedit /? ID”.

Examples:

The following control enables kernel debugging for the current Windows operating system boot entry:

bcdedit /debug ON

The following control disables kernel debugging for the specified operating system entry:

bcdedit /debug {cbd971bf-b7b8-4885-951a-fa03044f5d71} OFF

This command sets or displays the hypervisor settings for the system.

This control does not enable or disable the hypervisor debugger for whatsoever item OS loader entry. To enable or disable the hypervisor debugger for a item Bone loader entry, apply “bcdedit /ready <identifier> HYPERVISORDEBUG ON”. For information about identifiers, run “bcdedit /? ID”.

To ready an individual hypervisor debugger setting, use “bcdedit /set {hypervisorsettings} <blazon> <value>”. For information nigh valid types, run “bcdedit /? TYPES”.

bcdedit /hypervisorsettings [ <debugtype> [DEBUGPORT:<port>] [BAUDRATE:<baud>] [CHANNEL:<aqueduct>] [HOSTIP:<ip>] [PORT:<port>] ]

<debugtype> specifies the blazon of debugger. <debugtype> can be one of
SERIAL,
1394, or NET.

<port> for Series debugging, specifies the serial port to use every bit the debugging port.

<baud> for SERIAL debugging, specifies the baud rate to be used for debugging.

<channel> for 1394 debugging, specifies the 1394 channel to exist used for debugging.

<ip> for network debugging, specifies the IPv4 address of the host debugger.

<port> for network debugging, specifies the port to communicate with on the host debugger. Should be 49152 or higher.

Examples:

The following control displays the current hypervisor settings:

bcdedit /hypervisorsettings

The following command sets the hypervisor debugger settings to series debugging over COM1 at 115,200 baud:

bcdedit /hypervisorsettings SERIAL DEBUGPORT:1 BAUDRATE:115200

The following command sets the hypervisor debugger settings to 1394 debugging using channel 23:

bcdedit /hypervisorsettings 1394 CHANNEL:23

The following command sets the hypervisor debugger settings to network debugging with a debugger host at 192.168.one.two communicating on port 50000:

bcdedit /hypervisorsettings Cyberspace HOSTIP:192.168.one.two PORT:50000