| 0x01001000 | Unknown entry type (%1!08x!)----------------------------- |
Unknown entry type (%1!08x!)----------------------------- |
| 0x01001001 | Firmware Boot Manager--------------------- |
Firmware Boot Manager--------------------- |
| 0x01001002 | Windows Boot Manager-------------------- |
Windows Boot Manager-------------------- |
| 0x01001003 | Windows Boot Loader------------------- |
Windows Boot Loader------------------- |
| 0x01001004 | Resume from Hibernate--------------------- |
Resume from Hibernate--------------------- |
| 0x01001005 | Windows Memory Tester--------------------- |
Windows Memory Tester--------------------- |
| 0x01001006 | Windows Legacy OS Loader------------------------ |
Windows Legacy OS Loader------------------------ |
| 0x01001007 | Windows Legacy Setup Loader--------------------------- |
Windows Legacy Setup Loader--------------------------- |
| 0x01001008 | Real-mode Boot Sector--------------------- |
Real-mode Boot Sector--------------------- |
| 0x01001009 | Windows Setup------------- |
Windows Setup------------- |
| 0x0100100A | OS Target Template------------------ |
OS Target Template------------------ |
| 0x0100100B | Setup Ramdisk Options--------------------- |
Setup Ramdisk Options--------------------- |
| 0x0100100C | Windows Boot Application (%1!08x!)----------------------------------- |
Windows Boot Application (%1!08x!)----------------------------------- |
| 0x0100100D | Firmware Application (%1!08x!)------------------------------- |
Firmware Application (%1!08x!)------------------------------- |
| 0x0100100E | Legacy Loader Application (%1!08x!)------------------------------------ |
Legacy Loader Application (%1!08x!)------------------------------------ |
| 0x0100100F | Real-mode Application (%1!08x!)-------------------------------- |
Real-mode Application (%1!08x!)-------------------------------- |
| 0x01001020 | EMS Settings------------ |
EMS Settings------------ |
| 0x01001021 | Debugger Settings----------------- |
Debugger Settings----------------- |
| 0x01001022 | Inherited Settings (%1!08x!)----------------------------- |
Inherited Settings (%1!08x!)----------------------------- |
| 0x01001023 | Device options-------------- |
Device options-------------- |
| 0x01001024 | identifier %1 |
identifier %1 |
| 0x01001025 | RAM Defects----------- |
RAM Defects----------- |
| 0x01001026 | Global Settings--------------- |
Global Settings--------------- |
| 0x01001027 | Boot Loader Settings-------------------- |
Boot Loader Settings-------------------- |
| 0x01001028 | Resume Loader Settings---------------------- |
Resume Loader Settings---------------------- |
| 0x01001029 | Hypervisor Settings------------------- |
Hypervisor Settings------------------- |
| 0x01001030 | - secondary plex %0 |
- secondary plex %0 |
| 0x01001031 | Kernel Debugger Settings------------------------ |
Kernel Debugger Settings------------------------ |
| 0x01002001 | %1!-24s!%2 |
%1!-24s!%2 |
| 0x01002002 | %1!-24s!%2!I64u! |
%1!-24s!%2!I64u! |
| 0x01002003 | %1!-24s!0x%2!I64x! |
%1!-24s!0x%2!I64x! |
| 0x01007001 | The entry was successfully copied to %1. |
The entry was successfully copied to %1. |
| 0x01007002 | The entry %1 was successfully created. |
The entry %1 was successfully created. |
| 0x01007003 | The entry was successfully mirrored to %1. |
The entry was successfully mirrored to %1. |
| 0x4100803B | There are no matching objects or the store is empty. |
There are no matching objects or the store is empty. |
| 0xC1008001 | The specified store parameter is not valid.Run bcdedit /? for command line assistance. |
The specified store parameter is not valid.Run bcdedit /? for command line assistance. |
| 0xC1008002 | The verbose command line parameter is not valid.Run \"bcdedit /?\" for command line assistance. |
The verbose command line parameter is not valid.Run \"bcdedit /?\" for command line assistance. |
| 0xC1008003 | The specified entry type is invalid.Run \"bcdedit /?\" for command line assistance. |
The specified entry type is invalid.Run \"bcdedit /?\" for command line assistance. |
| 0xC1008004 | The specified format option is invalid.Run \"bcdedit /?\" for command line assistance. |
The specified format option is invalid.Run \"bcdedit /?\" for command line assistance. |
| 0xC1008005 | The boot configuration data store could not be opened. |
The boot configuration data store could not be opened. |
| 0xC1008006 | There was an error enumerating the boot configuration data entries. |
There was an error enumerating the boot configuration data entries. |
| 0xC1008007 | The copy command specified is not valid.Run \"bcdedit /?\" for command line assistance. |
The copy command specified is not valid.Run \"bcdedit /?\" for command line assistance. |
| 0xC1008008 | A description for the new entry must be specified.Run \"bcdedit /?\" for command line assistance. |
A description for the new entry must be specified.Run \"bcdedit /?\" for command line assistance. |
| 0xC1008009 | The specified entry identifier is not valid. |
The specified entry identifier is not valid. |
| 0xC100800A | An error occurred while attempting the specified copy operation. |
An error occurred while attempting the specified copy operation. |
| 0xC100800B | An error occurred while attempting to set the entry description. |
An error occurred while attempting to set the entry description. |
| 0xC100800C | An error occurred while attempting to obtain the target entry's identifier. |
An error occurred while attempting to obtain the target entry's identifier. |
| 0xC100800D | The delete command specified is not valid.Run \"bcdedit /?\" for command line assistance. |
The delete command specified is not valid.Run \"bcdedit /?\" for command line assistance. |
| 0xC100800E | An error occurred while attempting to reference the specified entry. |
An error occurred while attempting to reference the specified entry. |
| 0xC100800F | This entry cannot be deleted unless the /f switch is specified on the commandline. Run bcdedit /? for more information. |
This entry cannot be deleted unless the /f switch is specified on the commandline. Run bcdedit /? for more information. |
| 0xC1008010 | An error occurred while attempting to delete the specified entry. |
An error occurred while attempting to delete the specified entry. |
| 0xC1008011 | The create command specified is not valid.Run \"bcdedit /?\" for command line assistance. |
The create command specified is not valid.Run \"bcdedit /?\" for command line assistance. |
| 0xC1008012 | You may not use the current boot entry ID for this operation.Run \"bcdedit /?\" for command line assistance. |
You may not use the current boot entry ID for this operation.Run \"bcdedit /?\" for command line assistance. |
| 0xC1008013 | This command line is invalid for a well-known identifier.Run \"bcdedit /?\" for command line assistance. |
This command line is invalid for a well-known identifier.Run \"bcdedit /?\" for command line assistance. |
| 0xC1008014 | The application type switch specified is not valid.Run \"bcdedit /?\" for command line assistance. |
The application type switch specified is not valid.Run \"bcdedit /?\" for command line assistance. |
| 0xC1008015 | The inherited entry type specified is not valid.Run \"bcdedit /?\" for command line assistance. |
The inherited entry type specified is not valid.Run \"bcdedit /?\" for command line assistance. |
| 0xC1008016 | The device entry type specified is not valid.Run \"bcdedit /?\" for command line assistance. |
The device entry type specified is not valid.Run \"bcdedit /?\" for command line assistance. |
| 0xC1008017 | An error occurred while attempting the specified create operation. |
An error occurred while attempting the specified create operation. |
| 0xC1008018 | An error occurred while attempting to delete the specified data element. |
An error occurred while attempting to delete the specified data element. |
| 0xC1008019 | The set command specified is not valid.Run \"bcdedit /?\" for command line assistance. |
The set command specified is not valid.Run \"bcdedit /?\" for command line assistance. |
| 0xC100801A | The element data type specified is not recognized, or does not apply to thespecified entry.Run \"bcdedit /?\" for command line assistance. |
The element data type specified is not recognized, or does not apply to thespecified entry.Run \"bcdedit /?\" for command line assistance. |
| 0xC100801B | The device is not valid as specified.Run \"bcdedit /?\" for command line assistance. |
The device is not valid as specified.Run \"bcdedit /?\" for command line assistance. |
| 0xC100801C | The entry data is not valid as specified.Run \"bcdedit /?\" for command line assistance. |
The entry data is not valid as specified.Run \"bcdedit /?\" for command line assistance. |
| 0xC100801D | The entry list data is not valid as specified.Run \"bcdedit /?\" for command line assistance. |
The entry list data is not valid as specified.Run \"bcdedit /?\" for command line assistance. |
| 0xC100801E | The integer data is not valid as specified.Run \"bcdedit /?\" for command line assistance. |
The integer data is not valid as specified.Run \"bcdedit /?\" for command line assistance. |
| 0xC100801F | The boolean data is not valid as specified.Run \"bcdedit /?\" for command line assistance. |
The boolean data is not valid as specified.Run \"bcdedit /?\" for command line assistance. |
| 0xC1008020 | An error has occurred setting the element data. |
An error has occurred setting the element data. |
| 0xC1008021 | The timeout value is not valid as specified.Run \"bcdedit /?\" for command line assistance. |
The timeout value is not valid as specified.Run \"bcdedit /?\" for command line assistance. |
| 0xC1008022 | The default entry is not valid as specified.Run \"bcdedit /?\" for command line assistance. |
The default entry is not valid as specified.Run \"bcdedit /?\" for command line assistance. |
| 0xC1008023 | The debugger type specified is not valid.Run \"bcdedit /?\" for command line assistance. |
The debugger type specified is not valid.Run \"bcdedit /?\" for command line assistance. |
| 0xC1008024 | The settings are not valid for the debugger type specified.Run \"bcdedit /?\" for command line assistance. |
The settings are not valid for the debugger type specified.Run \"bcdedit /?\" for command line assistance. |
| 0xC1008025 | An error occurred while attempting to access the boot configuration data. |
An error occurred while attempting to access the boot configuration data. |
| 0xC1008026 | An error occurred while attempting to modify the debugger settings. |
An error occurred while attempting to modify the debugger settings. |
| 0xC1008027 | The parameters are not valid.Run \"bcdedit /?\" for command line assistance. |
The parameters are not valid.Run \"bcdedit /?\" for command line assistance. |
| 0xC1008028 | An error occurred while attempting to access the specified entry. |
An error occurred while attempting to access the specified entry. |
| 0xC1008029 | This command can only modify a Windows Boot Loader entry. |
This command can only modify a Windows Boot Loader entry. |
| 0xC100802A | An unknown command was specified.Run \"bcdedit /?\" for command line assistance. |
An unknown command was specified.Run \"bcdedit /?\" for command line assistance. |
| 0xC100802B | The specified EMS settings are not valid.Run \"bcdedit /?\" for command line assistance. |
The specified EMS settings are not valid.Run \"bcdedit /?\" for command line assistance. |
| 0xC100802D | An error occurred while attempting to modify the EMS settings. |
An error occurred while attempting to modify the EMS settings. |
| 0xC100802E | The specified data type is unknown or invalid.Run \"bcdedit /?\" for command line assistance. |
The specified data type is unknown or invalid.Run \"bcdedit /?\" for command line assistance. |
| 0xC100802F | The specified create store command is invalid.Run \"bcdedit /?\" for command line assistance. |
The specified create store command is invalid.Run \"bcdedit /?\" for command line assistance. |
| 0xC1008030 | The store creation operation has failed. |
The store creation operation has failed. |
| 0xC1008031 | The store import command is invalid.Run \"bcdedit /?\" for command line assistance. |
The store import command is invalid.Run \"bcdedit /?\" for command line assistance. |
| 0xC1008032 | The store import operation has failed. |
The store import operation has failed. |
| 0xC1008033 | An invalid combination of switches has been specified.Run \"bcdedit /?\" for command line assistance. |
An invalid combination of switches has been specified.Run \"bcdedit /?\" for command line assistance. |
| 0xC1008034 | An error has occurred reading the existing display order. |
An error has occurred reading the existing display order. |
| 0xC1008035 | The specified command line is not valid.Run \"bcdedit /?\" for command line assistance. |
The specified command line is not valid.Run \"bcdedit /?\" for command line assistance. |
| 0xC1008036 | The baud rate must be one of 9600, 19200, 38400, 57600 or 115200.Run \"bcdedit /?\" for command line assistance. |
The baud rate must be one of 9600, 19200, 38400, 57600 or 115200.Run \"bcdedit /?\" for command line assistance. |
| 0xC1008037 | Valid channel numbers are any integer between 0 and 62, inclusive.Run \"bcdedit /?\" for command line assistance. |
Valid channel numbers are any integer between 0 and 62, inclusive.Run \"bcdedit /?\" for command line assistance. |
| 0xC1008038 | The store export command is invalid.Run \"bcdedit /?\" for command line assistance. |
The store export command is invalid.Run \"bcdedit /?\" for command line assistance. |
| 0xC1008039 | The store export operation has failed. |
The store export operation has failed. |
| 0xC100803A | Invalid command line switch: /%1Run \"bcdedit /?\" for command line assistance. |
Invalid command line switch: /%1Run \"bcdedit /?\" for command line assistance. |
| 0xC100803C | An error has occurred attempting to modify the display order. |
An error has occurred attempting to modify the display order. |
| 0xC100803D | There are no debugger settings present. |
There are no debugger settings present. |
| 0xC100803E | An error occurred while attempting the specified create operation.The specified entry already exists. |
An error occurred while attempting the specified create operation.The specified entry already exists. |
| 0xC100803F | An error occurred while attempting to modify the hypervisor settings. |
An error occurred while attempting to modify the hypervisor settings. |
| 0xC1008041 | There are no hypervisor settings present. |
There are no hypervisor settings present. |
| 0xC1008042 | The set system store device command is invalid.Run \"bcdedit /?\" for command line assistance. |
The set system store device command is invalid.Run \"bcdedit /?\" for command line assistance. |
| 0xC1008043 | The set system store device command has failed. |
The set system store device command has failed. |
| 0xC1008044 | An error occurred while attempting the specified mirror operation. |
An error occurred while attempting the specified mirror operation. |
| 0xC1008045 | The mirror command specified is not valid.Run \"bcdedit /?\" for command line assistance. |
The mirror command specified is not valid.Run \"bcdedit /?\" for command line assistance. |
| 0xC1008046 | The port must be greater than 49151 and less than 65536.Run \"bcdedit -dbgsettings /?\" for command line assistance. |
The port must be greater than 49151 and less than 65536.Run \"bcdedit -dbgsettings /?\" for command line assistance. |
| 0xC1008047 | The key must be specified in base 36. Only digits 0-9 and letters a-z can beused when specifying the key. Each of the four 64 bit key chunks may bespecified with up to 13 characters and must be separated by a period. None ofthe key chunks can be zero. 1.1.1.1, 1.2.3.4, theprevious.keys.arenot.secure,automatically.generated.keysare.safer4you are all examples of valid keys.Run \"bcdedit -dbgsettings /?\" for command line assistance. |
The key must be specified in base 36. Only digits 0-9 and letters a-z can beused when specifying the key. Each of the four 64 bit key chunks may bespecified with up to 13 characters and must be separated by a period. None ofthe key chunks can be zero. 1.1.1.1, 1.2.3.4, theprevious.keys.arenot.secure,automatically.generated.keysare.safer4you are all examples of valid keys.Run \"bcdedit -dbgsettings /?\" for command line assistance. |
| 0xC1008048 | Failed to open a cryptographic service provider. Automatic encryption keygeneration failed. |
Failed to open a cryptographic service provider. Automatic encryption keygeneration failed. |
| 0xC1008049 | Failed to generate an encryption key. |
Failed to generate an encryption key. |
| 0xC100804A | Failed to convert the encryption key to a string. |
Failed to convert the encryption key to a string. |
| 0xC100804B | This platform does not support the cryptographic functions required toautomatically generate a key. Please specify the key directly on thecommand line.Run \"bcdedit -dbgsettings /?\" for command line assistance. |
This platform does not support the cryptographic functions required toautomatically generate a key. Please specify the key directly on thecommand line.Run \"bcdedit -dbgsettings /?\" for command line assistance. |
| 0xC100804C | There are no kernel debugger settings present. |
There are no kernel debugger settings present. |
| 0xC100804D | An error occurred while attempting to modify the kernel debugger settings. |
An error occurred while attempting to modify the kernel debugger settings. |
| 0xC100804F | The remote event logging parameters are not valid.Run \"bcdedit /?\" for command line assistance. |
The remote event logging parameters are not valid.Run \"bcdedit /?\" for command line assistance. |
| 0xC1008050 | An error occurred while attempting to modify the remote event logging settings. |
An error occurred while attempting to modify the remote event logging settings. |
| 0xC1008051 | An error occurred while attempting to modify the remote event logging settings.The debugger settings must be disabled to enable the remote event logging settings. |
An error occurred while attempting to modify the remote event logging settings.The debugger settings must be disabled to enable the remote event logging settings. |
| 0xC1008052 | An error occurred while attempting to modify the debugger settings. The remote event logging settings must be disabled to enable the debugger settings. |
An error occurred while attempting to modify the debugger settings. The remote event logging settings must be disabled to enable the debugger settings. |
| 0xC1008053 | 1394 debugging is no longer supported. Please select another transport. |
1394 debugging is no longer supported. Please select another transport. |
| 0xC100F001 | BCDEDIT - Boot Configuration Data Store EditorThe Bcdedit.exe command-line tool modifies the boot configuration data store.The boot configuration data store contains boot configuration parameters andcontrols how the operating system is booted. These parameters were previouslyin the Boot.ini file (in BIOS-based operating systems) or in the nonvolatileRAM entries (in Extensible Firmware Interface-based operating systems). You canuse Bcdedit.exe to add, delete, edit, and append entries in the bootconfiguration data store.For detailed command and option information, type bcdedit.exe /? . Forexample, to display detailed information about the /createstore command, type: bcdedit.exe /? /createstoreFor an alphabetical list of topics in this help file, run \"bcdedit /? TOPICS\".Commands that operate on a store================================/store Used to specify a BCD store other than the current system default./createstore Creates a new and empty boot configuration data store./export Exports the contents of the system store to a file. This file can be used later to restore the state of the system store./import Restores the state of the system store using a backup file created with the /export command./sysstore Sets the system store device (only affects EFI systems, does not persist across reboots, and is only used in cases where the system store device is ambiguous).Commands that operate on entries in a store===========================================/copy Makes copies of entries in the store./create Creates new entries in the store./delete Deletes entries from the store./mirror Creates mirror of entries in the store.Run bcdedit /? ID for information about identifiers used by these commands.Commands that operate on entry options======================================/deletevalue Deletes entry options from the store./set Sets entry option values in the store.Run bcdedit /? TYPES for a list of datatypes used by these commands.Run bcdedit /? FORMATS for a list of valid data formats.Commands that control output============================/enum Lists entries in the store./v Command-line option that displays entry identifiers in full, rather than using names for well-known identifiers. Use /v by itself as a command to display entry identifiers in full for the ACTIVE type.Running \"bcdedit\" by itself is equivalent to running \"bcdedit /enum ACTIVE\".Commands that control the boot manager======================================/bootsequence Sets the one-time boot sequence for the boot manager./default Sets the default entry that the boot manager will use./displayorder Sets the order in which the boot manager displays the multiboot menu./timeout Sets the boot manager time-out value./toolsdisplayorder Sets the order in which the boot manager displays the tools menu.Commands that control Emergency Management Services for a boot application==========================================================================/bootems Enables or disables Emergency Management Services for a boot application./ems Enables or disables Emergency Management Services for an operating system entry./emssettings Sets the global Emergency Management Services parameters.Command that control debugging==============================/bootdebug Enables or disables boot debugging for a boot application./dbgsettings Sets the global debugger parameters./debug Enables or disables kernel debugging for an operating system entry./hypervisorsettings Sets the hypervisor parameters.Command that control remote event logging=========================================/eventsettings Sets the global remote event logging parameters./event Enables or disables remote event logging for an operating system entry. |
BCDEDIT - Boot Configuration Data Store EditorThe Bcdedit.exe command-line tool modifies the boot configuration data store.The boot configuration data store contains boot configuration parameters andcontrols how the operating system is booted. These parameters were previouslyin the Boot.ini file (in BIOS-based operating systems) or in the nonvolatileRAM entries (in Extensible Firmware Interface-based operating systems). You canuse Bcdedit.exe to add, delete, edit, and append entries in the bootconfiguration data store.For detailed command and option information, type bcdedit.exe /? . Forexample, to display detailed information about the /createstore command, type: bcdedit.exe /? /createstoreFor an alphabetical list of topics in this help file, run \"bcdedit /? TOPICS\".Commands that operate on a store================================/store Used to specify a BCD store other than the current system default./createstore Creates a new and empty boot configuration data store./export Exports the contents of the system store to a file. This file can be used later to restore the state of the system store./import Restores the state of the system store using a backup file created with the /export command./sysstore Sets the system store device (only affects EFI systems, does not persist across reboots, and is only used in cases where the system store device is ambiguous).Commands that operate on entries in a store===========================================/copy Makes copies of entries in the store./create Creates new entries in the store./delete Deletes entries from the store./mirror Creates mirror of entries in the store.Run bcdedit /? ID for information about identifiers used by these commands.Commands that operate on entry options======================================/deletevalue Deletes entry options from the store./set Sets entry option values in the store.Run bcdedit /? TYPES for a list of datatypes used by these commands.Run bcdedit /? FORMATS for a list of valid data formats.Commands that control output============================/enum Lists entries in the store./v Command-line option that displays entry identifiers in full, rather than using names for well-known identifiers. Use /v by itself as a command to display entry identifiers in full for the ACTIVE type.Running \"bcdedit\" by itself is equivalent to running \"bcdedit /enum ACTIVE\".Commands that control the boot manager======================================/bootsequence Sets the one-time boot sequence for the boot manager./default Sets the default entry that the boot manager will use./displayorder Sets the order in which the boot manager displays the multiboot menu./timeout Sets the boot manager time-out value./toolsdisplayorder Sets the order in which the boot manager displays the tools menu.Commands that control Emergency Management Services for a boot application==========================================================================/bootems Enables or disables Emergency Management Services for a boot application./ems Enables or disables Emergency Management Services for an operating system entry./emssettings Sets the global Emergency Management Services parameters.Command that control debugging==============================/bootdebug Enables or disables boot debugging for a boot application./dbgsettings Sets the global debugger parameters./debug Enables or disables kernel debugging for an operating system entry./hypervisorsettings Sets the hypervisor parameters.Command that control remote event logging=========================================/eventsettings Sets the global remote event logging parameters./event Enables or disables remote event logging for an operating system entry. |
| 0xC100F002 | This command lists entries in a store. The /enum command is the default,so running \"bcdedit\" without parameters is equivalent to running\"bcdedit /enum ACTIVE\".bcdedit [/store ] /enum [ | ] [/v] Specifies the store to be used. If this option is not specified, the system store is used. For more information, run \"bcdedit /? store\". Specifies the type of entries to be listed. can be one of the following: ACTIVE All entries in the boot manager display order. This is the default. FIRMWARE All firmware applications. BOOTAPP All boot environment applications. BOOTMGR The boot manager. OSLOADER All operating system entries. RESUME All resume from hibernation entries. INHERIT All inherit entries. ALL All entries. Specifies the identifier of the entry to be listed. If an identifier is provided, then only the specified object will be listed. For information about identifiers, run \"bcdedit /? ID\". /v Displays entry identifiers in full, rather than using names for well-known identifiers.Examples:The following command lists all operating system loader boot entries: bcdedit /enum OSLOADERThe following command lists all boot manager entries: bcdedit /enum BOOTMGRThe following command lists only the default boot entry: bcdedit /enum {default}The following command lists only the specified operating system boot entry: bcdedit /enum {b38a9fc1-5690-11da-b795-e9ad3c5e0e3a} |
This command lists entries in a store. The /enum command is the default,so running \"bcdedit\" without parameters is equivalent to running\"bcdedit /enum ACTIVE\".bcdedit [/store ] /enum [ | ] [/v] Specifies the store to be used. If this option is not specified, the system store is used. For more information, run \"bcdedit /? store\". Specifies the type of entries to be listed. can be one of the following: ACTIVE All entries in the boot manager display order. This is the default. FIRMWARE All firmware applications. BOOTAPP All boot environment applications. BOOTMGR The boot manager. OSLOADER All operating system entries. RESUME All resume from hibernation entries. INHERIT All inherit entries. ALL All entries. Specifies the identifier of the entry to be listed. If an identifier is provided, then only the specified object will be listed. For information about identifiers, run \"bcdedit /? ID\". /v Displays entry identifiers in full, rather than using names for well-known identifiers.Examples:The following command lists all operating system loader boot entries: bcdedit /enum OSLOADERThe following command lists all boot manager entries: bcdedit /enum BOOTMGRThe following command lists only the default boot entry: bcdedit /enum {default}The following command lists only the specified operating system boot entry: bcdedit /enum {b38a9fc1-5690-11da-b795-e9ad3c5e0e3a} |
| 0xC100F003 | This command creates a new entry in the boot configuration data store. Ifa well-known identifier is specified, then the /application, /inherit and/device options cannot be specified. If the is not specified,or if is not well-known, then you must specify an /application, /inheritor /device option.bcdedit /create [{}] [/d ] [/application | /inherit [] | /inherit DEVICE | /device] Specifies the identifier to be used for the new entry. For more information about identifiers, run \"bcdedit /? ID\". Specifies the description to be applied to the new entry. /application Specifies that the new entry must be an application entry. specifies the application type. can be one of the following: BOOTAPP BOOTSECTOR OSLOADER RESUME STARTUP If you use other application types instead of one of these, you must also specify a well-known identifier. /inherit [] Specifies that the new entry must be an inherit entry, and specifies the application type. If is not specified, then the entry can be inherited by any entry. If specified, can be one of the following: BOOTMGR BOOTSECTOR FWBOOTMGR MEMDIAG NTLDR OSLOADER RESUME The modifier prevents the inherit entry from being inherited by an application entry of . /inherit DEVICE Specifies that the new entry must be an inherit entry, and that the entry can only be inherited by a device options entry. /device Specifies that the new entry must be an additional device options entry.Examples:The following command creates a NTLDR based OS loader entry (Ntldr): bcdedit /create {ntldr} /d \"Earlier Windows OS Loader\"The following command creates a RAM disk additional options entry: bcdedit /create {ramdiskoptions}The following command creates a new operating system boot entry: bcdedit /create /d \"Windows Vista\" /application osloaderThe following command creates a new debugger settings entry: bcdedit /create {dbgsettings} |
This command creates a new entry in the boot configuration data store. Ifa well-known identifier is specified, then the /application, /inherit and/device options cannot be specified. If the is not specified,or if is not well-known, then you must specify an /application, /inheritor /device option.bcdedit /create [{}] [/d ] [/application | /inherit [] | /inherit DEVICE | /device] Specifies the identifier to be used for the new entry. For more information about identifiers, run \"bcdedit /? ID\". Specifies the description to be applied to the new entry. /application Specifies that the new entry must be an application entry. specifies the application type. can be one of the following: BOOTAPP BOOTSECTOR OSLOADER RESUME STARTUP If you use other application types instead of one of these, you must also specify a well-known identifier. /inherit [] Specifies that the new entry must be an inherit entry, and specifies the application type. If is not specified, then the entry can be inherited by any entry. If specified, can be one of the following: BOOTMGR BOOTSECTOR FWBOOTMGR MEMDIAG NTLDR OSLOADER RESUME The modifier prevents the inherit entry from being inherited by an application entry of . /inherit DEVICE Specifies that the new entry must be an inherit entry, and that the entry can only be inherited by a device options entry. /device Specifies that the new entry must be an additional device options entry.Examples:The following command creates a NTLDR based OS loader entry (Ntldr): bcdedit /create {ntldr} /d \"Earlier Windows OS Loader\"The following command creates a RAM disk additional options entry: bcdedit /create {ramdiskoptions}The following command creates a new operating system boot entry: bcdedit /create /d \"Windows Vista\" /application osloaderThe following command creates a new debugger settings entry: bcdedit /create {dbgsettings} |
| 0xC100F004 | This command creates a copy of the specified boot entry.bcdedit [/store ] /copy {} /d Specifies the store to be used. If this option is not specified, the system store is used. For more information, run \"bcdedit /? store\". Specifies the identifier of the entry to be copied. For more information about identifiers, run \"bcdedit /? ID\". Specifies the description to be applied to the new entry.Example:The following command creates a copy of the specified operating system bootentry: bcdedit /copy {cbd971bf-b7b8-4885-951a-fa03044f5d71} /d \"Copy of entry\" |
This command creates a copy of the specified boot entry.bcdedit [/store ] /copy {} /d Specifies the store to be used. If this option is not specified, the system store is used. For more information, run \"bcdedit /? store\". Specifies the identifier of the entry to be copied. For more information about identifiers, run \"bcdedit /? ID\". Specifies the description to be applied to the new entry.Example:The following command creates a copy of the specified operating system bootentry: bcdedit /copy {cbd971bf-b7b8-4885-951a-fa03044f5d71} /d \"Copy of entry\" |
| 0xC100F005 | This command deletes an entry from the boot configuration data store.bcdedit [/store ] /delete [/f] [/cleanup | /nocleanup] Specifies the store to be used. If this option is not specified, the system store is used. For more information, run \"bcdedit /? store\". Specifies the identifier of the boot entry that you want to delete. For more information about identifiers, run \"bcdedit /? ID\". /f Deletes the specified entry. Without this option, Bcdedit will 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 will also be removed from the store. When deleting an OS loader entry, the associated resume from hibernation entry is also deleted if it is not referenced by any 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 thestore and removes the entry from the display order: bcdedit /delete {cbd971bf-b7b8-4885-951a-fa03044f5d71}The following command deletes the specified operating system entry from thestore and removes the entry from the display order: bcdedit /delete {cbd971bf-b7b8-4885-951a-fa03044f5d71} /cleanupThe following command deletes the specified operating system entry from thestore without removing the entry from the display order: bcdedit /delete {cbd971bf-b7b8-4885-951a-fa03044f5d71} /nocleanupThe following command deletes the NTLDR based OS loader entry from the store: bcdedit /delete {ntldr} /f |
This command deletes an entry from the boot configuration data store.bcdedit [/store ] /delete [/f] [/cleanup | /nocleanup] Specifies the store to be used. If this option is not specified, the system store is used. For more information, run \"bcdedit /? store\". Specifies the identifier of the boot entry that you want to delete. For more information about identifiers, run \"bcdedit /? ID\". /f Deletes the specified entry. Without this option, Bcdedit will 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 will also be removed from the store. When deleting an OS loader entry, the associated resume from hibernation entry is also deleted if it is not referenced by any 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 thestore and removes the entry from the display order: bcdedit /delete {cbd971bf-b7b8-4885-951a-fa03044f5d71}The following command deletes the specified operating system entry from thestore and removes the entry from the display order: bcdedit /delete {cbd971bf-b7b8-4885-951a-fa03044f5d71} /cleanupThe following command deletes the specified operating system entry from thestore without removing the entry from the display order: bcdedit /delete {cbd971bf-b7b8-4885-951a-fa03044f5d71} /nocleanupThe following command deletes the NTLDR based OS loader entry from the store: bcdedit /delete {ntldr} /f |
| 0xC100F006 | This command sets an entry option value in the boot configuration data store.bcdedit [/store ] /set [{}] [ /addfirst | /addlast | /remove ] Specifies the store to be used. If this option is not specified, the system store is used. For more information, run \"bcdedit /? store\". Specifies the identifier of the entry to be modified. If not specified, {current} is used. For more information about identifiers, run \"bcdedit /? ID\". Specifies the option data type that will be created or modified. Run \"bcdedit /? TYPES\" for more information about data types. Specifies the value that should be assigned to the option. The format of depends on the data type specified. Run \"bcdedit /? FORMATS\" for more information about data formats. /addfirst This switch can only be used if datatype is an object list. Adds the specified entry identifier to the top of the list. If this switch is specified, only a single entry identifier may be specified. If the specified identifier is already in the list, it will be moved to the top of the list. /addlast This switch can only be used if datatype is an object list. Adds the specified entry identifier to the end of the list. If this switch is specified, only a single entry identifier may be specified. If the specified identifier is already in the list, it is moved to the end of the list. /remove This switch can only be used if datatype is an object list. Removes the specified entry identifier from the list. If this switch is specified, only a single entry identifier may be specified. If the identifier is not in the list then the operation has no effect. If the last entry is being removed, then the datatype value is deleted.Examples:The following command sets the application device to the partition C: for thespecified operating system entry: bcdedit /set {cbd971bf-b7b8-4885-951a-fa03044f5d71} device partition=C: NOTE: Use 'hd_partiton=' syntax to explicitly disable automatic VHD detection, and create entries that are compatible for booting a virtual machine, i.e., bcdedit /store F:\\boot\\bcd /set {default} device hd_partition=F:The following command sets the OS device to a VHD file (C:\\vdisks\\vdisk01.vhd)for the specified operating system entry: bcdedit /set {cbd971bf-b7b8-4885-951a-fa03044f5d71} osdevice vhd=[C:]\\vdisks\\disk01.vhdThe following command sets the application path to\\windows\\system32\\winload.exe for the specified operating system entry: bcdedit /set {cbd971bf-b7b8-4885-951a-fa03044f5d71} path \\windows\\system32\\winload.exeThe following command sets the NX policy to OptIn for the current operatingsystem boot entry. bcdedit /set nx optin |
This command sets an entry option value in the boot configuration data store.bcdedit [/store ] /set [{}] [ /addfirst | /addlast | /remove ] Specifies the store to be used. If this option is not specified, the system store is used. For more information, run \"bcdedit /? store\". Specifies the identifier of the entry to be modified. If not specified, {current} is used. For more information about identifiers, run \"bcdedit /? ID\". Specifies the option data type that will be created or modified. Run \"bcdedit /? TYPES\" for more information about data types. Specifies the value that should be assigned to the option. The format of depends on the data type specified. Run \"bcdedit /? FORMATS\" for more information about data formats. /addfirst This switch can only be used if datatype is an object list. Adds the specified entry identifier to the top of the list. If this switch is specified, only a single entry identifier may be specified. If the specified identifier is already in the list, it will be moved to the top of the list. /addlast This switch can only be used if datatype is an object list. Adds the specified entry identifier to the end of the list. If this switch is specified, only a single entry identifier may be specified. If the specified identifier is already in the list, it is moved to the end of the list. /remove This switch can only be used if datatype is an object list. Removes the specified entry identifier from the list. If this switch is specified, only a single entry identifier may be specified. If the identifier is not in the list then the operation has no effect. If the last entry is being removed, then the datatype value is deleted.Examples:The following command sets the application device to the partition C: for thespecified operating system entry: bcdedit /set {cbd971bf-b7b8-4885-951a-fa03044f5d71} device partition=C: NOTE: Use 'hd_partiton=' syntax to explicitly disable automatic VHD detection, and create entries that are compatible for booting a virtual machine, i.e., bcdedit /store F:\\boot\\bcd /set {default} device hd_partition=F:The following command sets the OS device to a VHD file (C:\\vdisks\\vdisk01.vhd)for the specified operating system entry: bcdedit /set {cbd971bf-b7b8-4885-951a-fa03044f5d71} osdevice vhd=[C:]\\vdisks\\disk01.vhdThe following command sets the application path to\\windows\\system32\\winload.exe for the specified operating system entry: bcdedit /set {cbd971bf-b7b8-4885-951a-fa03044f5d71} path \\windows\\system32\\winload.exeThe following command sets the NX policy to OptIn for the current operatingsystem boot entry. bcdedit /set nx optin |
| 0xC100F007 | This command deletes a data element from an entry in the boot configurationdata store.bcdedit [/store ] /deletevalue [] Specifies the store to be used. If this option is not specified, the system store is used. For more information, run \"bcdedit /? store\". Specifies the identifier of the entry that will be modified. If not specified, {current} is used. For more information about identifiers, run \"bcdedit /? ID\". Specifies the option that will be removed from the specified entry. Run \"bcdedit /? TYPES\" for more information about data types.Examples:The following command deletes the bootsequence option from the boot managerentry: bcdedit /deletevalue {bootmgr} bootsequenceThe following command deletes the Windows Preinstallation Environment (WinPE)value from the current operating system boot entry: bcdedit /deletevalue winpeThe following command deletes the Windows PE value from the specified operatingsystem boot entry: bcdedit /deletevalue {cbd971bf-b7b8-4885-951a-fa03044f5d71} winpe |
This command deletes a data element from an entry in the boot configurationdata store.bcdedit [/store ] /deletevalue [] Specifies the store to be used. If this option is not specified, the system store is used. For more information, run \"bcdedit /? store\". Specifies the identifier of the entry that will be modified. If not specified, {current} is used. For more information about identifiers, run \"bcdedit /? ID\". Specifies the option that will be removed from the specified entry. Run \"bcdedit /? TYPES\" for more information about data types.Examples:The following command deletes the bootsequence option from the boot managerentry: bcdedit /deletevalue {bootmgr} bootsequenceThe following command deletes the Windows Preinstallation Environment (WinPE)value from the current operating system boot entry: bcdedit /deletevalue winpeThe following command deletes the Windows PE value from the specified operatingsystem boot entry: bcdedit /deletevalue {cbd971bf-b7b8-4885-951a-fa03044f5d71} winpe |
| 0xC100F008 | This command sets the time to wait, in seconds, before the boot manager selectsa default entry. For information about setting the default entry, run\"bcdedit /? default\".bcdedit /timeout Specifies the time to wait, in seconds, before the boot manager selects a default entry.Example:The following command sets the boot manager to 30 seconds: bcdedit /timeout 30 |
This command sets the time to wait, in seconds, before the boot manager selectsa default entry. For information about setting the default entry, run\"bcdedit /? default\".bcdedit /timeout Specifies the time to wait, in seconds, before the boot manager selects a default entry.Example:The following command sets the boot manager to 30 seconds: bcdedit /timeout 30 |
| 0xC100F009 | This command sets the default entry that the boot manager will use when thetimeout expires.bcdedit /default Specifies the identifier of the boot entry to be used as the default when the time-out expires. For information about identifiers, run \"bcdedit /? ID\".Examples:The following command sets the specified entry as the default boot managerentry: bcdedit /default {cbd971bf-b7b8-4885-951a-fa03044f5d71}The following command sets the NTLDR based OS loader as the defaultentry: bcdedit /default {ntldr} |
This command sets the default entry that the boot manager will use when thetimeout expires.bcdedit /default Specifies the identifier of the boot entry to be used as the default when the time-out expires. For information about identifiers, run \"bcdedit /? ID\".Examples:The following command sets the specified entry as the default boot managerentry: bcdedit /default {cbd971bf-b7b8-4885-951a-fa03044f5d71}The following command sets the NTLDR based OS loader as the defaultentry: bcdedit /default {ntldr} |
| 0xC100F00A | This command sets the display order to be used by the boot manager.bcdedit /displayorder [...] [ /addfirst | /addlast | /remove ] [...] Specifies a list of identifiers that make up the display order. At least one identifier must be specified and they must be separated by spaces. For more information about identifiers, run \"bcdedit /? ID\". /addfirst Adds the specified entry identifier to the top of the display order. If this switch is specified, only a single entry identifier may be specified. If the specified identifier is already in the list, it will be moved to the top of the list. /addlast Adds the specified entry identifier to the end of the display order. If this switch is specified, only a single entry identifier may be specified. If the specified identifier is already in the list, it is moved to the end of the list. /remove Removes the specified entry identifier from the display order. If this switch is specified, only a single entry identifier may be specified. If the identifier is not in the list then the operation has no effect. If the last entry is being removed, then the display order value is deleted from the boot manager entry.Examples:The following command sets two OS entries and the NTLDR based OS loader inthe boot manager display order: bcdedit /displayorder {802d5e32-0784-11da-bd33-000476eba25f} {cbd971bf-b7b8-4885-951a-fa03044f5d71} {ntldr}The following command adds the specified OS entry to the end of the bootmanager display order: bcdedit /displayorder {802d5e32-0784-11da-bd33-000476eba25f} /addlast |
This command sets the display order to be used by the boot manager.bcdedit /displayorder [...] [ /addfirst | /addlast | /remove ] [...] Specifies a list of identifiers that make up the display order. At least one identifier must be specified and they must be separated by spaces. For more information about identifiers, run \"bcdedit /? ID\". /addfirst Adds the specified entry identifier to the top of the display order. If this switch is specified, only a single entry identifier may be specified. If the specified identifier is already in the list, it will be moved to the top of the list. /addlast Adds the specified entry identifier to the end of the display order. If this switch is specified, only a single entry identifier may be specified. If the specified identifier is already in the list, it is moved to the end of the list. /remove Removes the specified entry identifier from the display order. If this switch is specified, only a single entry identifier may be specified. If the identifier is not in the list then the operation has no effect. If the last entry is being removed, then the display order value is deleted from the boot manager entry.Examples:The following command sets two OS entries and the NTLDR based OS loader inthe boot manager display order: bcdedit /displayorder {802d5e32-0784-11da-bd33-000476eba25f} {cbd971bf-b7b8-4885-951a-fa03044f5d71} {ntldr}The following command adds the specified OS entry to the end of the bootmanager display order: bcdedit /displayorder {802d5e32-0784-11da-bd33-000476eba25f} /addlast |
| 0xC100F00B | This command sets the one-time boot sequence to be used by the bootmanager.bcdedit /bootsequence [...] [ /addfirst | /addlast | /remove ] [...] Specifies a list 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 boot sequence. If this switch is specified, only a single identifier may be specified. If the 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 boot sequence. If this switch is specified, only a single identifier may be specified. If the identifier is already in the list, it is moved to the end 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 then the operation has no effect. If the last entry is being removed, then the boot sequence value is deleted from the boot manager entry.Examples:The following command sets two OS entries and the NTLDR based OS loader in theboot manager one-time boot sequence: bcdedit /bootsequence {802d5e32-0784-11da-bd33-000476eba25f} {cbd971bf-b7b8-4885-951a-fa03044f5d71} {ntldr}The following command adds the specified OS entry to the end of the bootmanager one-time boot sequence: bcdedit /bootsequence {802d5e32-0784-11da-bd33-000476eba25f} /addlast |
This command sets the one-time boot sequence to be used by the bootmanager.bcdedit /bootsequence [...] [ /addfirst | /addlast | /remove ] [...] Specifies a list 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 boot sequence. If this switch is specified, only a single identifier may be specified. If the 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 boot sequence. If this switch is specified, only a single identifier may be specified. If the identifier is already in the list, it is moved to the end 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 then the operation has no effect. If the last entry is being removed, then the boot sequence value is deleted from the boot manager entry.Examples:The following command sets two OS entries and the NTLDR based OS loader in theboot manager one-time boot sequence: bcdedit /bootsequence {802d5e32-0784-11da-bd33-000476eba25f} {cbd971bf-b7b8-4885-951a-fa03044f5d71} {ntldr}The following command adds the specified OS entry to the end of the bootmanager one-time boot sequence: bcdedit /bootsequence {802d5e32-0784-11da-bd33-000476eba25f} /addlast |
| 0xC100F00C | This command sets or displays the global debugger settings for the system.This command does not enable or disable the debugger for any particular bootentry. To enable or disable the debugger for a particular boot entry, use\"bcdedit /debug ON\". For information about identifiers, run\"bcdedit /? ID\".To set an individual global debugger setting, use\"bcdedit /set {dbgsettings} \". For information about validtypes, run \"bcdedit /? TYPES\".bcdedit /dbgsettings [ [DEBUGPORT:] [BAUDRATE:] [CHANNEL:] [TARGETNAME:] [HOSTIP:] [PORT:] [KEY:] [nodhcp] [newkey] /start /noumex ] Specifies the type of debugger. can be one of SERIAL, 1394, USB, NET or LOCAL. For SERIAL debugging, specifies the serial port to use as the debugging port. This is an optional setting. For SERIAL debugging, specifies the baud rate to be used for debugging. This is an optional setting. For 1394 debugging, specifies the 1394 channel to be used for debugging. For universal serial bus (USB) debugging, specifies the USB target name to be used for debugging. For network debugging, specifies the IPv4 address of the host debugger. For network debugging, specifies the port to communicate with on the host debugger. Should be 49152 or higher. For network debugging, specifies the key with which to encrypt the connection. [0-9] and [a-z] allowed only. nodhcp For network debugging prevents use of DHCP to obtain the target IP address. newkey For network debugging specifies that a new encryption key should be generated for the connection. /start For all debugger types, this specifies the debugger start policy. can be one of the following: ACTIVE AUTOENABLE DISABLE. If not specified, ACTIVE is the default. /noumex If specified, this causes the kernel debugger to ignore any user-mode exceptions.Examples:The following command displays the current global debugger settings: bcdedit /dbgsettingsThe following command sets the global debugger settings to serial debuggingover com1 at 115,200 baud: bcdedit /dbgsettings SERIAL DEBUGPORT:1 BAUDRATE:115200The following command sets the global debugger settings to 1394 debuggingusing channel 23: bcdedit /dbgsettings 1394 CHANNEL:23The following command sets the global debugger settings to USB debuggingusing target name DEBUGGING: bcdedit /dbgsettings USB TARGETNAME:DEBUGGINGThe following command sets the global debugger settings to network debuggingwith a debugger host at 192.168.1.2 communicating on port 50000: bcdedit /dbgsettings NET HOSTIP:192.168.1.2 PORT:50000The following command sets the global debugger settings to local debugging: bcdedit /dbgsettings LOCAL |
This command sets or displays the global debugger settings for the system.This command does not enable or disable the debugger for any particular bootentry. To enable or disable the debugger for a particular boot entry, use\"bcdedit /debug ON\". For information about identifiers, run\"bcdedit /? ID\".To set an individual global debugger setting, use\"bcdedit /set {dbgsettings} \". For information about validtypes, run \"bcdedit /? TYPES\".bcdedit /dbgsettings [ [DEBUGPORT:] [BAUDRATE:] [CHANNEL:] [TARGETNAME:] [HOSTIP:] [PORT:] [KEY:] [nodhcp] [newkey] /start /noumex ] Specifies the type of debugger. can be one of SERIAL, 1394, USB, NET or LOCAL. For SERIAL debugging, specifies the serial port to use as the debugging port. This is an optional setting. For SERIAL debugging, specifies the baud rate to be used for debugging. This is an optional setting. For 1394 debugging, specifies the 1394 channel to be used for debugging. For universal serial bus (USB) debugging, specifies the USB target name to be used for debugging. For network debugging, specifies the IPv4 address of the host debugger. For network debugging, specifies the port to communicate with on the host debugger. Should be 49152 or higher. For network debugging, specifies the key with which to encrypt the connection. [0-9] and [a-z] allowed only. nodhcp For network debugging prevents use of DHCP to obtain the target IP address. newkey For network debugging specifies that a new encryption key should be generated for the connection. /start For all debugger types, this specifies the debugger start policy. can be one of the following: ACTIVE AUTOENABLE DISABLE. If not specified, ACTIVE is the default. /noumex If specified, this causes the kernel debugger to ignore any user-mode exceptions.Examples:The following command displays the current global debugger settings: bcdedit /dbgsettingsThe following command sets the global debugger settings to serial debuggingover com1 at 115,200 baud: bcdedit /dbgsettings SERIAL DEBUGPORT:1 BAUDRATE:115200The following command sets the global debugger settings to 1394 debuggingusing channel 23: bcdedit /dbgsettings 1394 CHANNEL:23The following command sets the global debugger settings to USB debuggingusing target name DEBUGGING: bcdedit /dbgsettings USB TARGETNAME:DEBUGGINGThe following command sets the global debugger settings to network debuggingwith a debugger host at 192.168.1.2 communicating on port 50000: bcdedit /dbgsettings NET HOSTIP:192.168.1.2 PORT:50000The following command sets the global debugger settings to local debugging: bcdedit /dbgsettings LOCAL |
| 0xC100F00D | This command enables or disables the kernel debugger for the specified bootentry.bcdedit /debug [] { ON | OFF } Specifies the identifier of the entry to be modified. Only Windows boot loader entries may be specified. If not specified, {current} is used. For more information about identifiers, run \"bcdedit /? ID\".Examples:The following command enables kernel debugging for the current Windowsoperating system boot entry: bcdedit /debug ONThe following command disables kernel debugging for the specified operatingsystem entry: bcdedit /debug {cbd971bf-b7b8-4885-951a-fa03044f5d71} OFF |
This command enables or disables the kernel debugger for the specified bootentry.bcdedit /debug [] { ON | OFF } Specifies the identifier of the entry to be modified. Only Windows boot loader entries may be specified. If not specified, {current} is used. For more information about identifiers, run \"bcdedit /? ID\".Examples:The following command enables kernel debugging for the current Windowsoperating system boot entry: bcdedit /debug ONThe following command disables kernel debugging for the specified operatingsystem entry: bcdedit /debug {cbd971bf-b7b8-4885-951a-fa03044f5d71} OFF |
| 0xC100F00E | This command enables or disables the boot debugger for the specified bootentry. Although this command works for any entry, it is only effective for bootapplications.bcdedit /bootdebug [] { ON | OFF } Specifies the identifier of the entry to be modified. For information about identifiers, run \"bcdedit /? ID\".Examples:The following command enables boot debugging for the Windows operating systemloader of the current operating system boot entry: bcdedit /bootdebug ONThe following command disables boot debugging for the Windows boot manager: bcdedit /bootdebug {bootmgr} OFF |
This command enables or disables the boot debugger for the specified bootentry. Although this command works for any entry, it is only effective for bootapplications.bcdedit /bootdebug [] { ON | OFF } Specifies the identifier of the entry to be modified. For information about identifiers, run \"bcdedit /? ID\".Examples:The following command enables boot debugging for the Windows operating systemloader of the current operating system boot entry: bcdedit /bootdebug ONThe following command disables boot debugging for the Windows boot manager: bcdedit /bootdebug {bootmgr} OFF |
| 0xC100F00F | This command sets the global Emergency Management Services settings for thesystem. Emssettings does not enable or disable Emergency Management Servicesfor any particular boot entry.bcdedit /emssettings [ BIOS ] | [ EMSPORT: | [EMSBAUDRATE:] ] BIOS Specifies that the system will use BIOS settings for the Emergency Management Services configuration. This works only on systems that have Emergency Management Services support provided by the BIOS. Specifies the serial port to use as the Emergency Management Services port. This should not be specified with the BIOS option. Specifies the serial baud rate to use for Emergency Management Services. This command should not be specified with the BIOS option. is optional, and the default is 9,600 baud.Examples:The following command sets the Emergency Management Services parameters to useBIOS settings: bcdedit /emssettings BIOSThe following command sets the Emergency Management Services parameters to usecom2: at 115,200 baud. bcdedit /emssettings EMSPORT:2 EMSBAUDRATE:115200 |
This command sets the global Emergency Management Services settings for thesystem. Emssettings does not enable or disable Emergency Management Servicesfor any particular boot entry.bcdedit /emssettings [ BIOS ] | [ EMSPORT: | [EMSBAUDRATE:] ] BIOS Specifies that the system will use BIOS settings for the Emergency Management Services configuration. This works only on systems that have Emergency Management Services support provided by the BIOS. Specifies the serial port to use as the Emergency Management Services port. This should not be specified with the BIOS option. Specifies the serial baud rate to use for Emergency Management Services. This command should not be specified with the BIOS option. is optional, and the default is 9,600 baud.Examples:The following command sets the Emergency Management Services parameters to useBIOS settings: bcdedit /emssettings BIOSThe following command sets the Emergency Management Services parameters to usecom2: at 115,200 baud. bcdedit /emssettings EMSPORT:2 EMSBAUDRATE:115200 |
| 0xC100F010 | This command enables or disables Emergency Management Services for thespecified operating system boot entry.bcdedit /ems [] { ON | OFF } Specifies the identifier of the entry to be modified. Only \"Windows boot loader\" entries can be specified. If not specified, {current} is used. For more information about identifiers, run \"bcdedit /? ID\".Example:The following command enables Emergency Management Services for the currentoperating system boot entry: bcdedit /ems ON |
This command enables or disables Emergency Management Services for thespecified operating system boot entry.bcdedit /ems [] { ON | OFF } Specifies the identifier of the entry to be modified. Only \"Windows boot loader\" entries can be specified. If not specified, {current} is used. For more information about identifiers, run \"bcdedit /? ID\".Example:The following command enables Emergency Management Services for the currentoperating system boot entry: bcdedit /ems ON |
| 0xC100F011 | This command enables or disables Emergency Management Services for thespecified entry.bcdedit /bootems [] { ON | OFF } Specifies the identifier of the entry to be modified. Although this command will work for any entry, it is only effective for boot applications.Example:The following command enables Emergency Management Services for the bootmanager: bcdedit /bootems {bootmgr} ON |
This command enables or disables Emergency Management Services for thespecified entry.bcdedit /bootems [] { ON | OFF } Specifies the identifier of the entry to be modified. Although this command will work for any entry, it is only effective for boot applications.Example:The following command enables Emergency Management Services for the bootmanager: bcdedit /bootems {bootmgr} ON |
| 0xC100F012 | This command-line option can be used with most Bcdedit commands to specify thestore to be used. If this option is not specified, then the system store isused.This option may not be used with the /createstore, /import and /exportcommands.bcdedit /store Specifies the file name of the boot configuration data store. If the file name contains spaces, it must be enclosed in quotation marks (\"\").Example:The following commands list the active entries in the specified data storefile: bcdedit /store C:\\DATA\\BCD /enum ACTIVE bcdedit /store \"C:\\DATA\\My BCD\" /enum ACTIVE |
This command-line option can be used with most Bcdedit commands to specify thestore to be used. If this option is not specified, then the system store isused.This option may not be used with the /createstore, /import and /exportcommands.bcdedit /store Specifies the file name of the boot configuration data store. If the file name contains spaces, it must be enclosed in quotation marks (\"\").Example:The following commands list the active entries in the specified data storefile: bcdedit /store C:\\DATA\\BCD /enum ACTIVE bcdedit /store \"C:\\DATA\\My BCD\" /enum ACTIVE |
| 0xC100F013 | bcdedit /createstore This command created a new empty boot configuration data store. The created store is not a system store. Specifies the filename of the boot configuration data store. If the filename contains spaces, it must be enclosed in quotation marks (\"\").Example:The following command creates the specified store file: bcdedit /createstore C:\\DATA\\BCD |
bcdedit /createstore This command created a new empty boot configuration data store. The created store is not a system store. Specifies the filename of the boot configuration data store. If the filename contains spaces, it must be enclosed in quotation marks (\"\").Example:The following command creates the specified store file: bcdedit /createstore C:\\DATA\\BCD |
| 0xC100F014 | bcdedit /import [/clean]This command restores the state of the system store using a backup data filepreviously generated using the /export command. Any existing entries in thesystem store are deleted before the import takes place. This command is onlyvalid for the system store. The name of the file that is imported into the system store. If the filename contains spaces, it must be enclosed in quotation marks (\"\"). /clean Specifies that all existing firmware boot entries should be deleted (only affects EFI systems).Example:The following command imports the specified file into the system store. bcdedit /import \"C:\\Data\\BCD Backup\" /clean |
bcdedit /import [/clean]This command restores the state of the system store using a backup data filepreviously generated using the /export command. Any existing entries in thesystem store are deleted before the import takes place. This command is onlyvalid for the system store. The name of the file that is imported into the system store. If the filename contains spaces, it must be enclosed in quotation marks (\"\"). /clean Specifies that all existing firmware boot entries should be deleted (only affects EFI systems).Example:The following command imports the specified file into the system store. bcdedit /import \"C:\\Data\\BCD Backup\" /clean |
| 0xC100F015 | bcdedit /export This command exports the contents of the system store into a file. This filecan be used later to restore the state of the system store. This command isonly valid for the system store. The filename to be used as the destination for the export. If the filename contains spaces, it must be enclosed in quotation marks (\"\").Example:The following command exports the system store to the specified file: bcdedit /export \"C:\\Data\\BCD Backup\" |
bcdedit /export This command exports the contents of the system store into a file. This filecan be used later to restore the state of the system store. This command isonly valid for the system store. The filename to be used as the destination for the export. If the filename contains spaces, it must be enclosed in quotation marks (\"\").Example:The following command exports the system store to the specified file: bcdedit /export \"C:\\Data\\BCD Backup\" |
| 0xC100F016 | Usually, any well-known entry identifiers are replaced by their friendlyshorthand form. Specifying /v as a command-line switch prevents thisreplacement and displays all identifiers in full. Running \"bcdedit /v\" byitself is equivalent to running \"bcdedit /enum ACTIVE /v\".bcdedit /vExample:The following command lists the active entries in the system store with allentry identifiers displayed in full. bcdedit /enum ACTIVE /v |
Usually, any well-known entry identifiers are replaced by their friendlyshorthand form. Specifying /v as a command-line switch prevents thisreplacement and displays all identifiers in full. Running \"bcdedit /v\" byitself is equivalent to running \"bcdedit /enum ACTIVE /v\".bcdedit /vExample:The following command lists the active entries in the system store with allentry identifiers displayed in full. bcdedit /enum ACTIVE /v |
| 0xC100F017 | bcdedit /toolsdisplayorder [...] [ /addfirst | /addlast | /remove ]This command will set the display order to be used by the boot manager whendisplaying the tools menu. [...] Specifies a list of identifiers that make up the tools display order. At least one identifier must be specified and they must be separated by spaces. For more information about identifiers, run \"bcdedit /? ID\". /addfirst Adds the specified entry identifier to the top of the tools display order. If this switch is specified, only a single entry identifier may be 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 order. If this switch is specified, only a single entry identifier may be specified. If the specified identifier is already in the list, it is moved to the end of the list. /remove Removes the specified entry identifier from the tools display order. If this switch is specified, only a single entry identifier may be specified. If the identifier is not in the list, then the operation will have no effect. If the last entry is being removed, then the tools display order value is deleted from the boot manager entry.Examples:The following command sets two tools entries and the memory diagnostic in theboot 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 bootmanager's tools display order: bcdedit /toolsdisplayorder {802d5e32-0784-11da-bd33-000476eba25f} /addlast |
bcdedit /toolsdisplayorder [...] [ /addfirst | /addlast | /remove ]This command will set the display order to be used by the boot manager whendisplaying the tools menu. [...] Specifies a list of identifiers that make up the tools display order. At least one identifier must be specified and they must be separated by spaces. For more information about identifiers, run \"bcdedit /? ID\". /addfirst Adds the specified entry identifier to the top of the tools display order. If this switch is specified, only a single entry identifier may be 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 order. If this switch is specified, only a single entry identifier may be specified. If the specified identifier is already in the list, it is moved to the end of the list. /remove Removes the specified entry identifier from the tools display order. If this switch is specified, only a single entry identifier may be specified. If the identifier is not in the list, then the operation will have no effect. If the last entry is being removed, then the tools display order value is deleted from the boot manager entry.Examples:The following command sets two tools entries and the memory diagnostic in theboot 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 bootmanager's tools display order: bcdedit /toolsdisplayorder {802d5e32-0784-11da-bd33-000476eba25f} /addlast |
| 0xC100F018 | bcdedit /sysstore This command sets the system store device. This command is only valid for EFIsystems in cases where the system store device is ambiguous. This setting doesnot persist across reboots. The name of a system partition to set as the the system store device. The device must be a system partition.Example:The following command sets the system store device as specified: bcdedit /sysstore C: |
bcdedit /sysstore This command sets the system store device. This command is only valid for EFIsystems in cases where the system store device is ambiguous. This setting doesnot persist across reboots. The name of a system partition to set as the the system store device. The device must be a system partition.Example:The following command sets the system store device as specified: bcdedit /sysstore C: |
| 0xC100F021 | IDENTIFIERSMany of the Bcdedit commands require identifiers. An identifieruniquely identifies entries contained in the store. An identifier takes theform of a globally unique identifier, or GUID. A GUID has the following format,where each \"x\" represents a hexadecimal digit. {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}For example: {d2b69192-8f14-11da-a31f-ea816ab185e9}The position of the dashes (-) and the braces at the beginning and end of theGUID are required.Several entries can be identified by well-known identifiers. If an entry has awell-known identifier, BCDedit displays it in output unless the /v command-lineswitch is used. For more information, run \"bcdedit /? /v\".The well-known identifiers are as follows: {bootmgr} Specifies the Windows boot manager entry. {fwbootmgr} Specifies the firmware boot manager entry, specifically on systems that implement the Extensible Firmware Interface (EFI) specification. {memdiag} Specifies the memory diagnostic application entry. {ntldr} Specifies a OS loader (Ntldr) that can be used to start operating systems earlier than Windows Vista. {current} Specifies a virtual identifier that corresponds to the operating system boot entry for the operating system that is currently running. {default} Specifies a virtual identifier that corresponds to the boot manager default application entry. {ramdiskoptions} Contains the additional options required by the boot manager for RAM disk devices. {dbgsettings} Contains the global debugger settings that can be inherited by any boot application entry. {emssettings} Contains the global Emergency Management Services settings that can be inherited by any boot application entry. {badmemory} Contains the global RAM defect list that can be inherited by any boot application entry. {globalsettings} Contains the collection of global settings that should be inherited by all boot application entries. {bootloadersettings} Contains the collection of global settings that should be inherited by all Windows boot loader application entries. {resumeloadersettings} Contains the collection of global settings that should be inherited by all Windows resume from hibernation application entries. {hypervisorsettings} Contains the hypervisor settings that can be inherited by any OS loader entry. |
IDENTIFIERSMany of the Bcdedit commands require identifiers. An identifieruniquely identifies entries contained in the store. An identifier takes theform of a globally unique identifier, or GUID. A GUID has the following format,where each \"x\" represents a hexadecimal digit. {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}For example: {d2b69192-8f14-11da-a31f-ea816ab185e9}The position of the dashes (-) and the braces at the beginning and end of theGUID are required.Several entries can be identified by well-known identifiers. If an entry has awell-known identifier, BCDedit displays it in output unless the /v command-lineswitch is used. For more information, run \"bcdedit /? /v\".The well-known identifiers are as follows: {bootmgr} Specifies the Windows boot manager entry. {fwbootmgr} Specifies the firmware boot manager entry, specifically on systems that implement the Extensible Firmware Interface (EFI) specification. {memdiag} Specifies the memory diagnostic application entry. {ntldr} Specifies a OS loader (Ntldr) that can be used to start operating systems earlier than Windows Vista. {current} Specifies a virtual identifier that corresponds to the operating system boot entry for the operating system that is currently running. {default} Specifies a virtual identifier that corresponds to the boot manager default application entry. {ramdiskoptions} Contains the additional options required by the boot manager for RAM disk devices. {dbgsettings} Contains the global debugger settings that can be inherited by any boot application entry. {emssettings} Contains the global Emergency Management Services settings that can be inherited by any boot application entry. {badmemory} Contains the global RAM defect list that can be inherited by any boot application entry. {globalsettings} Contains the collection of global settings that should be inherited by all boot application entries. {bootloadersettings} Contains the collection of global settings that should be inherited by all Windows boot loader application entries. {resumeloadersettings} Contains the collection of global settings that should be inherited by all Windows resume from hibernation application entries. {hypervisorsettings} Contains the hypervisor settings that can be inherited by any OS loader entry. |
| 0xC100F022 | TYPESThe /set and /deletevalue commands require a as a parameter. uniquely identifies both the data format and meaning of the value.Data types are identified using either a name or a custom type. The names arelisted below, along with their data formats (in parentheses) and a shortdescription of the custom type. If a format is not specified, then thedescription lists the literal values that you can use for that type. Forinformation about data formats, run \"bcdedit /? formats\".The following types are valid for any entry. For information about types thatare specific to a particular entry, such as boot manager entries or the WindowsOS Loader entries, see the end of this help topic.Entries======= DESCRIPTION (string) Defines the description of the entry. PATH (string) Defines the path to the application. DEVICE (device) Defines the device that the application resides on. INHERIT (list) Defines the list of entries to be inherited.For information about additional types for device objects, run\"bcdedit /? TYPES DEVOBJECT\".For information about additional types for particular applications,run \"bcdedit /? TYPES \", where is one of the following:BOOTAPP Boot applications. These types also apply to the boot manager, memory diagnostic application, Windows OS loader, and the resume application.BOOTMGR Boot manager.BOOTSECTOR Boot sector application.CUSTOMTYPES Custom types.DEVOBJECT Device object additional options.FWBOOTMGR Firmware boot managerMEMDIAG Memory diagnostic applicationNTLDR OS loader that shipped with earlier Windows OSOSLOADER Windows Vista OS loaderRESUME Resume application |
TYPESThe /set and /deletevalue commands require a as a parameter. uniquely identifies both the data format and meaning of the value.Data types are identified using either a name or a custom type. The names arelisted below, along with their data formats (in parentheses) and a shortdescription of the custom type. If a format is not specified, then thedescription lists the literal values that you can use for that type. Forinformation about data formats, run \"bcdedit /? formats\".The following types are valid for any entry. For information about types thatare specific to a particular entry, such as boot manager entries or the WindowsOS Loader entries, see the end of this help topic.Entries======= DESCRIPTION (string) Defines the description of the entry. PATH (string) Defines the path to the application. DEVICE (device) Defines the device that the application resides on. INHERIT (list) Defines the list of entries to be inherited.For information about additional types for device objects, run\"bcdedit /? TYPES DEVOBJECT\".For information about additional types for particular applications,run \"bcdedit /? TYPES \", where is one of the following:BOOTAPP Boot applications. These types also apply to the boot manager, memory diagnostic application, Windows OS loader, and the resume application.BOOTMGR Boot manager.BOOTSECTOR Boot sector application.CUSTOMTYPES Custom types.DEVOBJECT Device object additional options.FWBOOTMGR Firmware boot managerMEMDIAG Memory diagnostic applicationNTLDR OS loader that shipped with earlier Windows OSOSLOADER Windows Vista OS loaderRESUME Resume application |
| 0xC100F026 | The following describes the formats of the data that are required for used with the /set command. The format that is required depends onthe that you specify with the /set command. For more informationabout the formats associated with each , run \"bcdedit /? TYPES\".bool A boolean value. The following values correspond to TRUE: 1, ON, YES, TRUE The following values correspond to FALSE: 0, OFF, NO, FALSEdevice A device can be one of the following types: BOOT PARTITION= HD_PARTITION= FILE=[] RAMDISK=[], VHD=[], LOCATE[=] The options for these types are: A drive letter with a colon and no trailing backslashes. (Required) Can be either BOOT, LOCATE, or a drive letter with colon. The square brackets do not indicate that this is optional, but are a literal part of the syntax. A path to the file (or .wim file) from the root of the parent device. The identifier to the device options entry that contains the system deployment image (SDI) options for the RAM disk. This is usually {ramdisksdioptions}. Supplies an optional element used to locate a device by looking for a specified path. The default locate element for a device is its application path (systemroot for an osdevice). Custom values must be specified using custom element syntax (see -help types customtypes), for example: locate=custom:22000002.id An entry identifier, which refers to an entry in the boot configuration data store. Run \"bcdedit /? ID\" for more information about identifiers.integer A 64-bit integer type. Some integer types can be set using enumerated values.integerlist A list of one or more 64-bit integers, separated by spaces. This list should not be enclosed in quotation marks.list An entry identifier list. It contains one or more entry identifiers separated by spaces. The list should not be enclosed in quotation marks.string A literal string. If it contains spaces, it should be surrounded by quotation marks (\"\"). |
The following describes the formats of the data that are required for used with the /set command. The format that is required depends onthe that you specify with the /set command. For more informationabout the formats associated with each , run \"bcdedit /? TYPES\".bool A boolean value. The following values correspond to TRUE: 1, ON, YES, TRUE The following values correspond to FALSE: 0, OFF, NO, FALSEdevice A device can be one of the following types: BOOT PARTITION= HD_PARTITION= FILE=[] RAMDISK=[], VHD=[], LOCATE[=] The options for these types are: A drive letter with a colon and no trailing backslashes. (Required) Can be either BOOT, LOCATE, or a drive letter with colon. The square brackets do not indicate that this is optional, but are a literal part of the syntax. A path to the file (or .wim file) from the root of the parent device. The identifier to the device options entry that contains the system deployment image (SDI) options for the RAM disk. This is usually {ramdisksdioptions}. Supplies an optional element used to locate a device by looking for a specified path. The default locate element for a device is its application path (systemroot for an osdevice). Custom values must be specified using custom element syntax (see -help types customtypes), for example: locate=custom:22000002.id An entry identifier, which refers to an entry in the boot configuration data store. Run \"bcdedit /? ID\" for more information about identifiers.integer A 64-bit integer type. Some integer types can be set using enumerated values.integerlist A list of one or more 64-bit integers, separated by spaces. This list should not be enclosed in quotation marks.list An entry identifier list. It contains one or more entry identifiers separated by spaces. The list should not be enclosed in quotation marks.string A literal string. If it contains spaces, it should be surrounded by quotation marks (\"\"). |
| 0xC100F027 | BOOT APPLICATIONThe following types apply to entries for boot applications. These types alsoapply to the boot manager, memory diagnostic application, Windows OS loader,and the resume application. For information about data formats for these types,run \"bcdedit /? FORMATS\".Display======= GRAPHICSRESOLUTION Defines the graphics resolution, 1024x768, 800x600, 1024x600, etc. HIGHESTMODE (bool) Enables boot applications to use the highest graphical mode exposed by the firmware. GRAPHICSMODEDISABLED (bool) Disables graphics mode. HIGHESTMODE (bool) Forces the highest resolution supported by the firmware. NOVESA (bool) Disables the use of Video Electronics Standards Association (VESA) display modes. (Defunct.) NOVGA (bool) Disables the use of VGA modes entirely. BOOTUXDISABLED (bool) Disables boot graphics.Debugging========= BAUDRATE (integer) Defines the baud rate for the serial debugger. BOOTDEBUG (bool) Enables the boot debugger. CHANNEL (integer) Defines the channel for the 1394 debugger. BUSPARAMS (string) Defines the PCI bus, device, and function numbers of the debugging device. For example, 1.5.0 describes the debugging device on bus 1, device 5, function 0. DEBUGADDRESS (integer) Defines the address of a serial port for the debugger. DEBUGPORT (integer) Defines the serial port number for the serial debugger. DEBUGSTART Can be ACTIVE, AUTOENABLE or DISABLE. DEBUGTYPE Can be SERIAL, 1394, USB, NET or LOCAL. DHCP (bool) Controls use of DHCP by the network debugger. DHCP set to false forces local link only address. HOSTIP Defines the host IP address for the network debugger. KEY Holds the key used to encrypt the network debug connection. NOUMEX (bool) Causes user-mode exceptions to be ignored. PORT (integer) Defines the network port for the network debugger. TARGETNAME (string) Defines the target name for the USB debugger.Memory====== BADMEMORYACCESS (bool) Allows an application to use the memory described by the bad memory list. BADMEMORYLIST (integerlist) Defines the list of Page Frame Numbers describing faulty memory in the system. TRUNCATEMEMORY (integer) Disregard all memory at or above the specified physical address. AVOIDLOWMEMORY (integer) Avoid using memory below the specified physical address in the boot loader as much as possible.Emergency Management Services============================= BOOTEMS (bool) Enables Emergency Management Services. EMSBAUDRATE (integer) Defines the baud rate for Emergency Management Services. EMSPORT (integer) Defines the serial port number for Emergency Management Services.Devices and Hardware=========================== CONFIGACCESSPOLICY Can be DEFAULT or DISALLOWMMCONFIG. FIRSTMEGABYTEPOLICY Can be USENONE, USEALL or USEPRIVATE. EXTENDEDINPUT (bool) Enables extended console input functionality.Applications============ LOCALE (string) Defines the locale of the boot application. NOUMEX (bool) Causes user-mode exceptions to be ignored.Recovery======== RECOVERYENABLED (bool) Enables the recovery sequence. RECOVERYSEQUENCE (list) Defines the recovery sequence.Verification============ TESTSIGNING (bool) Allows pre-release test code signing certificates. FLIGHTSIGNING (bool) Allows flight-signed code signing certificates.Error Screens============= BOOTSHUTDOWNDISABLED (bool) Indicates that the machine should not shutdown after displaying an error screen for 1 minute. The default is to attempt the shutdown. This does not work on legacy firmware. BOOTERRORUX (integer) Defines the graphics experience for boot errors. Can be Legacy, Standard or Simple. Valid only on keyboard-less devices.For additional types that apply to the boot manager, memory diagnosticapplication, windows OS loader, or the resume application, run\"bcdedit /? TYPES \", where is one of the following: BOOTMGR The boot manager. MEMDIAG The memory diagnostic application. OSLOADER The Windows OS loader. RESUME The resume application. |
BOOT APPLICATIONThe following types apply to entries for boot applications. These types alsoapply to the boot manager, memory diagnostic application, Windows OS loader,and the resume application. For information about data formats for these types,run \"bcdedit /? FORMATS\".Display======= GRAPHICSRESOLUTION Defines the graphics resolution, 1024x768, 800x600, 1024x600, etc. HIGHESTMODE (bool) Enables boot applications to use the highest graphical mode exposed by the firmware. GRAPHICSMODEDISABLED (bool) Disables graphics mode. HIGHESTMODE (bool) Forces the highest resolution supported by the firmware. NOVESA (bool) Disables the use of Video Electronics Standards Association (VESA) display modes. (Defunct.) NOVGA (bool) Disables the use of VGA modes entirely. BOOTUXDISABLED (bool) Disables boot graphics.Debugging========= BAUDRATE (integer) Defines the baud rate for the serial debugger. BOOTDEBUG (bool) Enables the boot debugger. CHANNEL (integer) Defines the channel for the 1394 debugger. BUSPARAMS (string) Defines the PCI bus, device, and function numbers of the debugging device. For example, 1.5.0 describes the debugging device on bus 1, device 5, function 0. DEBUGADDRESS (integer) Defines the address of a serial port for the debugger. DEBUGPORT (integer) Defines the serial port number for the serial debugger. DEBUGSTART Can be ACTIVE, AUTOENABLE or DISABLE. DEBUGTYPE Can be SERIAL, 1394, USB, NET or LOCAL. DHCP (bool) Controls use of DHCP by the network debugger. DHCP set to false forces local link only address. HOSTIP Defines the host IP address for the network debugger. KEY Holds the key used to encrypt the network debug connection. NOUMEX (bool) Causes user-mode exceptions to be ignored. PORT (integer) Defines the network port for the network debugger. TARGETNAME (string) Defines the target name for the USB debugger.Memory====== BADMEMORYACCESS (bool) Allows an application to use the memory described by the bad memory list. BADMEMORYLIST (integerlist) Defines the list of Page Frame Numbers describing faulty memory in the system. TRUNCATEMEMORY (integer) Disregard all memory at or above the specified physical address. AVOIDLOWMEMORY (integer) Avoid using memory below the specified physical address in the boot loader as much as possible.Emergency Management Services============================= BOOTEMS (bool) Enables Emergency Management Services. EMSBAUDRATE (integer) Defines the baud rate for Emergency Management Services. EMSPORT (integer) Defines the serial port number for Emergency Management Services.Devices and Hardware=========================== CONFIGACCESSPOLICY Can be DEFAULT or DISALLOWMMCONFIG. FIRSTMEGABYTEPOLICY Can be USENONE, USEALL or USEPRIVATE. EXTENDEDINPUT (bool) Enables extended console input functionality.Applications============ LOCALE (string) Defines the locale of the boot application. NOUMEX (bool) Causes user-mode exceptions to be ignored.Recovery======== RECOVERYENABLED (bool) Enables the recovery sequence. RECOVERYSEQUENCE (list) Defines the recovery sequence.Verification============ TESTSIGNING (bool) Allows pre-release test code signing certificates. FLIGHTSIGNING (bool) Allows flight-signed code signing certificates.Error Screens============= BOOTSHUTDOWNDISABLED (bool) Indicates that the machine should not shutdown after displaying an error screen for 1 minute. The default is to attempt the shutdown. This does not work on legacy firmware. BOOTERRORUX (integer) Defines the graphics experience for boot errors. Can be Legacy, Standard or Simple. Valid only on keyboard-less devices.For additional types that apply to the boot manager, memory diagnosticapplication, windows OS loader, or the resume application, run\"bcdedit /? TYPES \", where is one of the following: BOOTMGR The boot manager. MEMDIAG The memory diagnostic application. OSLOADER The Windows OS loader. RESUME The resume application. |
| 0xC100F028 | FIRMWARE BOOT MANAGERThe following types apply only to entries for the firmware boot manager. Forinformation about data formats for these types, run \"bcdedit /? FORMATS\".Boot==== BOOTSEQUENCE (list) Defines the one-time boot sequence. DEFAULT (id) Defines the default boot entry. TIMEOUT (integer) Defines the boot manager time to wait, in seconds.Display======= DISPLAYORDER (list) Defines the boot manager display order list. |
FIRMWARE BOOT MANAGERThe following types apply only to entries for the firmware boot manager. Forinformation about data formats for these types, run \"bcdedit /? FORMATS\".Boot==== BOOTSEQUENCE (list) Defines the one-time boot sequence. DEFAULT (id) Defines the default boot entry. TIMEOUT (integer) Defines the boot manager time to wait, in seconds.Display======= DISPLAYORDER (list) Defines the boot manager display order list. |
| 0xC100F029 | BOOT MANAGERThe following types apply only to entries for the boot manager. For informationabout data formats for these types, run \"bcdedit /? FORMATS\".Boot==== BOOTSEQUENCE (list) Defines the one-time boot sequence. PERSISTBOOTSEQUENCE (bool) Enables persisting a boot sequence across multiple boots. DEFAULT (id) Defines the default boot entry. TIMEOUT (integer) Defines the boot manager time to wait, in seconds, before the boot manager selects a default entry.Resume====== RESUME (bool) Indicates that a resume operation should be attempted. RESUMEOBJECT (id) Provides the identifier of the resume application object. HIBERBOOT (bool) Indicates that a hiberboot resume should be attempted. This is used along with the RESUME setting and should not be modified.Display======= DISPLAYBOOTMENU (bool) Enables the boot menu display. DISPLAYORDER (list) Defines the boot manager display order list. TOOLSDISPLAYORDER (list) Defines the boot manager tools display order list.For additional types that apply to the boot manager, run\"bcdedit /? TYPES BOOTAPP\". |
BOOT MANAGERThe following types apply only to entries for the boot manager. For informationabout data formats for these types, run \"bcdedit /? FORMATS\".Boot==== BOOTSEQUENCE (list) Defines the one-time boot sequence. PERSISTBOOTSEQUENCE (bool) Enables persisting a boot sequence across multiple boots. DEFAULT (id) Defines the default boot entry. TIMEOUT (integer) Defines the boot manager time to wait, in seconds, before the boot manager selects a default entry.Resume====== RESUME (bool) Indicates that a resume operation should be attempted. RESUMEOBJECT (id) Provides the identifier of the resume application object. HIBERBOOT (bool) Indicates that a hiberboot resume should be attempted. This is used along with the RESUME setting and should not be modified.Display======= DISPLAYBOOTMENU (bool) Enables the boot menu display. DISPLAYORDER (list) Defines the boot manager display order list. TOOLSDISPLAYORDER (list) Defines the boot manager tools display order list.For additional types that apply to the boot manager, run\"bcdedit /? TYPES BOOTAPP\". |
| 0xC100F02A | WINDOWS OS LOADERThe following types can be used only for Windows OS Loader entries. Forinformation about data formats for these types, run \"bcdedit /? FORMATS\".Boot==== BOOTLOG (bool) Enables the system initialization log. BOOTSTATUSPOLICY Can be DisplayAllFailures, IgnoreAllFailures, IgnoreShutdownFailures, IgnoreBootFailures, IgnoreCheckpointFailures, DisplayShutdownFailures, DisplayBootFailures, or DisplayCheckpointFailures. LASTKNOWNGOOD (bool) Enables boot to last known good configuration. NOCRASHAUTOREBOOT (bool) Disables automatic restart on crash. RESUMEOBJECT (id) Defines the identifier of the resume object that is associated with this operating system object. SAFEBOOT Can be Minimal, Network or DsRepair SAFEBOOTALTERNATESHELL (bool) Uses the alternate shell when booted into Safe mode. SOS (bool) Displays additional boot information. WINPE (bool) Enables the computer to boot to Windows PE.Display======= BOOTUX Defines the graphics experience during boot. Can be Disabled, Basic or Standard. (Defunct.) BOOTMENUPOLICY Defines the type of boot menus the system will use. Can be Legacy or Standard.Options======= ADVANCEDOPTIONS (bool) Enables advanced options. LOADOPTIONS (string) Defines any additional options that are not covered by other types. OPTIONSEDIT (bool) Enables the options editor.Processors and APICs==================== CLUSTERMODEADDRESSING (integer) Defines the maximum number of processors to include in a single Advanced Programmable Interrupt Controller (APIC) cluster. CONFIGFLAGS (integer) Specifies processor-specific configuration flags. MAXPROC (bool) Reports the maximum number of processors in the system. NUMPROC (integer) Uses only the specified number of processors. ONECPU (bool) Forces only the boot CPU to be used. RESTRICTAPICCLUSTER (integer) Defines the largest APIC cluster number to be used by the system. USEPHYSICALDESTINATION (bool) Forces the use of the physical APIC. USELEGACYAPICMODE (bool) Forces the use of legacy APIC mode even if the processors and chipset support extended APIC mode. X2APICPOLICY (integer) Enables the use of extended APIC mode if the processors and chipset support extended APIC mode. Can be Enabled, Disabled or Default. MAXGROUP (bool) Maximizes the number of groups created in group configuration. GROUPAWARE (bool) Forces drivers to be aware of multiple groups in a multi-group environment. GROUPSIZE (integer) Specifies the size of all processor groups. Must be an integer of power of 2.Hardware Abstraction Layer (HAL) & KERNEL========================================= HAL (string) Defines the file name for a private HAL. HALBREAKPOINT (bool) Enables the special hardware abstraction layer (HAL) breakpoint. KERNEL (string) Defines the file name for a private kernel. USEPLATFORMCLOCK (bool) Forces the use of a platform clock source for the system's performance counter. FORCELEGACYPLATFORM(bool) Forces the OS to assume the presence of legacy PC devices like CMOS, keyboard controller etc. TSCSYNCPOLICY Controls the TSC synchronization policy. Can be Default, Legacy or Enhanced. |
WINDOWS OS LOADERThe following types can be used only for Windows OS Loader entries. Forinformation about data formats for these types, run \"bcdedit /? FORMATS\".Boot==== BOOTLOG (bool) Enables the system initialization log. BOOTSTATUSPOLICY Can be DisplayAllFailures, IgnoreAllFailures, IgnoreShutdownFailures, IgnoreBootFailures, IgnoreCheckpointFailures, DisplayShutdownFailures, DisplayBootFailures, or DisplayCheckpointFailures. LASTKNOWNGOOD (bool) Enables boot to last known good configuration. NOCRASHAUTOREBOOT (bool) Disables automatic restart on crash. RESUMEOBJECT (id) Defines the identifier of the resume object that is associated with this operating system object. SAFEBOOT Can be Minimal, Network or DsRepair SAFEBOOTALTERNATESHELL (bool) Uses the alternate shell when booted into Safe mode. SOS (bool) Displays additional boot information. WINPE (bool) Enables the computer to boot to Windows PE.Display======= BOOTUX Defines the graphics experience during boot. Can be Disabled, Basic or Standard. (Defunct.) BOOTMENUPOLICY Defines the type of boot menus the system will use. Can be Legacy or Standard.Options======= ADVANCEDOPTIONS (bool) Enables advanced options. LOADOPTIONS (string) Defines any additional options that are not covered by other types. OPTIONSEDIT (bool) Enables the options editor.Processors and APICs==================== CLUSTERMODEADDRESSING (integer) Defines the maximum number of processors to include in a single Advanced Programmable Interrupt Controller (APIC) cluster. CONFIGFLAGS (integer) Specifies processor-specific configuration flags. MAXPROC (bool) Reports the maximum number of processors in the system. NUMPROC (integer) Uses only the specified number of processors. ONECPU (bool) Forces only the boot CPU to be used. RESTRICTAPICCLUSTER (integer) Defines the largest APIC cluster number to be used by the system. USEPHYSICALDESTINATION (bool) Forces the use of the physical APIC. USELEGACYAPICMODE (bool) Forces the use of legacy APIC mode even if the processors and chipset support extended APIC mode. X2APICPOLICY (integer) Enables the use of extended APIC mode if the processors and chipset support extended APIC mode. Can be Enabled, Disabled or Default. MAXGROUP (bool) Maximizes the number of groups created in group configuration. GROUPAWARE (bool) Forces drivers to be aware of multiple groups in a multi-group environment. GROUPSIZE (integer) Specifies the size of all processor groups. Must be an integer of power of 2.Hardware Abstraction Layer (HAL) & KERNEL========================================= HAL (string) Defines the file name for a private HAL. HALBREAKPOINT (bool) Enables the special hardware abstraction layer (HAL) breakpoint. KERNEL (string) Defines the file name for a private kernel. USEPLATFORMCLOCK (bool) Forces the use of a platform clock source for the system's performance counter. FORCELEGACYPLATFORM(bool) Forces the OS to assume the presence of legacy PC devices like CMOS, keyboard controller etc. TSCSYNCPOLICY Controls the TSC synchronization policy. Can be Default, Legacy or Enhanced. |
| 0xC100F02B | RESUME LOADERThe following types apply to entries for the resume loader. For informationabout data formats for these types, run \"bcdedit /? FORMATS\".Display======= BOOTUX Defines the graphics experience during resume. Can be Disabled, Basic, or Standard. (Defunct.) BOOTMENUPOLICY Defines the type of boot menus the system will use. Can be Legacy or Standard.Hibernation file================ FILEDEVICE (Device) Specifies the device containing the hibernation file. FILEPATH (String) Specifies the path of the hibernation file.Other===== ASSOCIATEDOSDEVICE (Device) Names the OS device associated with the hibernated OS. This is only useful in cases where the hibernation file is not stored on the OS device. CUSTOMSETTINGS (Boolean) Allows resume loader to use custom settings. PAE (Boolean) Indicates whether the hibernated OS was running with PAE enabled.For additional types that apply to the resume application, run\"bcdedit /? TYPES BOOTAPP\". |
RESUME LOADERThe following types apply to entries for the resume loader. For informationabout data formats for these types, run \"bcdedit /? FORMATS\".Display======= BOOTUX Defines the graphics experience during resume. Can be Disabled, Basic, or Standard. (Defunct.) BOOTMENUPOLICY Defines the type of boot menus the system will use. Can be Legacy or Standard.Hibernation file================ FILEDEVICE (Device) Specifies the device containing the hibernation file. FILEPATH (String) Specifies the path of the hibernation file.Other===== ASSOCIATEDOSDEVICE (Device) Names the OS device associated with the hibernated OS. This is only useful in cases where the hibernation file is not stored on the OS device. CUSTOMSETTINGS (Boolean) Allows resume loader to use custom settings. PAE (Boolean) Indicates whether the hibernated OS was running with PAE enabled.For additional types that apply to the resume application, run\"bcdedit /? TYPES BOOTAPP\". |
| 0xC100F02C | MEMORY DIAGNOSTIC APPLICATIONThe following types apply only to entries for memory diagnostic applicationentries. For information about data formats for these types, run\"bcdedit /? FORMATS\".Test==== PASSCOUNT (integer) The number of iterations that will be run. TESTMIX Can be BASIC or EXTENDED. CACHEENABLE (boolean) Overrides the default cache settings of the testmix.For additional types that apply to the memory diagnostic application, run\"bcdedit /? TYPES BOOTAPP\". |
MEMORY DIAGNOSTIC APPLICATIONThe following types apply only to entries for memory diagnostic applicationentries. For information about data formats for these types, run\"bcdedit /? FORMATS\".Test==== PASSCOUNT (integer) The number of iterations that will be run. TESTMIX Can be BASIC or EXTENDED. CACHEENABLE (boolean) Overrides the default cache settings of the testmix.For additional types that apply to the memory diagnostic application, run\"bcdedit /? TYPES BOOTAPP\". |
| 0xC100F02D | DEVICE ADDITIONAL OPTIONSThe following types apply to device additional options entries. For informationabout data formats for these types, run \"bcdedit /? FORMATS\".The following options are valid for the device additional options entry:Ramdisk======= EXPORTASCD (bool) Enables exporting the RAM disk as a CD. RAMDISKIMAGELENGTH (integer) Defines the image length for the RAM disk. RAMDISKIMAGEOFFSET (integer) Defines the image offset for the RAM disk. RAMDISKSDIDEVICE (device) Defines the device on which the SDI file is located. RAMDISKSDIPATH (string) Defines the path to the SDI file. RAMDISKTFTPCLIENTPORT (integer) Defines the Trivial File Transfer Protocol (TFTP) client port for the RAM disk Windows Imaging (WIM) file. RAMDISKTFTPBLOCKSIZE (integer) Defines the Trivial File Transfer Protocol (TFTP) block size for the RAM disk Windows Imaging (WIM) file. RAMDISKTFTPWINDOWSIZE (integer) Defines the Trivial File Transfer Protocol (TFTP) window size for RAM disk Windows imaging (WIM) file. RAMDISKMCENABLED (bool) Enables or disables Multicast for RAM disk Windows Imaging (WIM) file. RAMDISKMCTFTPFALLBACK (bool) Enables fallback to TFTP if Multicast fails. RAMDISKTFTPVARWINDOW (bool) Enables or disables Trivial File Transfer Protocol (TFTP) Variable window size extension. |
DEVICE ADDITIONAL OPTIONSThe following types apply to device additional options entries. For informationabout data formats for these types, run \"bcdedit /? FORMATS\".The following options are valid for the device additional options entry:Ramdisk======= EXPORTASCD (bool) Enables exporting the RAM disk as a CD. RAMDISKIMAGELENGTH (integer) Defines the image length for the RAM disk. RAMDISKIMAGEOFFSET (integer) Defines the image offset for the RAM disk. RAMDISKSDIDEVICE (device) Defines the device on which the SDI file is located. RAMDISKSDIPATH (string) Defines the path to the SDI file. RAMDISKTFTPCLIENTPORT (integer) Defines the Trivial File Transfer Protocol (TFTP) client port for the RAM disk Windows Imaging (WIM) file. RAMDISKTFTPBLOCKSIZE (integer) Defines the Trivial File Transfer Protocol (TFTP) block size for the RAM disk Windows Imaging (WIM) file. RAMDISKTFTPWINDOWSIZE (integer) Defines the Trivial File Transfer Protocol (TFTP) window size for RAM disk Windows imaging (WIM) file. RAMDISKMCENABLED (bool) Enables or disables Multicast for RAM disk Windows Imaging (WIM) file. RAMDISKMCTFTPFALLBACK (bool) Enables fallback to TFTP if Multicast fails. RAMDISKTFTPVARWINDOW (bool) Enables or disables Trivial File Transfer Protocol (TFTP) Variable window size extension. |
| 0xC100F02E | BOOT SECTORBoot Sector type applies to entries that contain bootsector in the form of afile. Currently there are no additional options for this type. |
BOOT SECTORBoot Sector type applies to entries that contain bootsector in the form of afile. Currently there are no additional options for this type. |
| 0xC100F02F | CUSTOM TYPESA custom type identifies the data format and meaning of a value that is notrepresented by a friendly type name built in to BCDedit. Custom types aretypically used to extend the functionality of BCD.A custom type has the following format: custom:0xXXXXXXXX The literal string \"custom:\" followed by an 8-digit hexadecimal number that encodes the format and meaning of the type.A custom type appears in the same parameter position as a friendly type name ina /set or /deletevalue command. For example: bcdedit /set {} custom:0xXXXXXXXX For information about custom types that can be used with this version ofBCDedit, search the Microsoft Knowledge Base for these keywords: BCD, BCDedit,custom types |
CUSTOM TYPESA custom type identifies the data format and meaning of a value that is notrepresented by a friendly type name built in to BCDedit. Custom types aretypically used to extend the functionality of BCD.A custom type has the following format: custom:0xXXXXXXXX The literal string \"custom:\" followed by an 8-digit hexadecimal number that encodes the format and meaning of the type.A custom type appears in the same parameter position as a friendly type name ina /set or /deletevalue command. For example: bcdedit /set {} custom:0xXXXXXXXX For information about custom types that can be used with this version ofBCDedit, search the Microsoft Knowledge Base for these keywords: BCD, BCDedit,custom types |
| 0xC100F030 | NTLDR based OS LOADERCurrently there are no additional options for this type. |
NTLDR based OS LOADERCurrently there are no additional options for this type. |
| 0xC100F031 | TOPICS IN THIS HELP FILETo display help for a topic, run \"bcdedit /? \" where is one ofthe following:bootdebug /bootdebug command.bootems /bootems command.bootsequence /bootsequence command.copy /copy command.create /create command.createstore /createstore command.dbgsettings /dbgsettings command.debug /debug command.default /default command.delete /delete command.deletevalue /deletevalue command.displayorder /displayorder command.eventsettings /eventsettings command.event /event command.ems /ems command.emssettings /emssettings command.enum /enum command.export /export command.FORMATS Formats for types.hypervisorsettings /hypervisorsettings command.ID Identifiers for entries..import /import command.mirror /mirror command.set /set command.store /store command-line option.timeout /timeout command.toolsdisplayorder /toolsdisplayorder command.TYPES Types that apply to any entry.TYPES BOOTAPP Types that apply to boot applications. These include the boot manager, memory diagnostic application, Windows OS loader, and the resume application.TYPES BOOTMGR Types that apply to the boot manager.TYPES BOOTSECTOR Types that apply to the boot sector application.TYPES CUSTOMTYPES Custom types.TYPES FWBOOTMGR Types that apply to the firmware boot managerTYPES MEMDIAG Types that apply to the memory diagnostic applicationTYPES NTLDR Types that apply to the NTLDR based OS loaderTYPES OSLOADER Types that apply to the Windows OS loaderTYPES RESUME Types that apply to the resume applicationv /v command-line option |
TOPICS IN THIS HELP FILETo display help for a topic, run \"bcdedit /? \" where is one ofthe following:bootdebug /bootdebug command.bootems /bootems command.bootsequence /bootsequence command.copy /copy command.create /create command.createstore /createstore command.dbgsettings /dbgsettings command.debug /debug command.default /default command.delete /delete command.deletevalue /deletevalue command.displayorder /displayorder command.eventsettings /eventsettings command.event /event command.ems /ems command.emssettings /emssettings command.enum /enum command.export /export command.FORMATS Formats for types.hypervisorsettings /hypervisorsettings command.ID Identifiers for entries..import /import command.mirror /mirror command.set /set command.store /store command-line option.timeout /timeout command.toolsdisplayorder /toolsdisplayorder command.TYPES Types that apply to any entry.TYPES BOOTAPP Types that apply to boot applications. These include the boot manager, memory diagnostic application, Windows OS loader, and the resume application.TYPES BOOTMGR Types that apply to the boot manager.TYPES BOOTSECTOR Types that apply to the boot sector application.TYPES CUSTOMTYPES Custom types.TYPES FWBOOTMGR Types that apply to the firmware boot managerTYPES MEMDIAG Types that apply to the memory diagnostic applicationTYPES NTLDR Types that apply to the NTLDR based OS loaderTYPES OSLOADER Types that apply to the Windows OS loaderTYPES RESUME Types that apply to the resume applicationv /v command-line option |
| 0xC100F032 | This command sets or displays the hypervisor settings for the system.This command does not enable or disable the hypervisor debugger for anyparticular OS loader entry. To enable or disable the hypervisor debugger for aparticular OS loader entry, use \"bcdedit /set HYPERVISORDEBUG ON\".For information about identifiers, run \"bcdedit /? ID\".To set an individual hypervisor debugger setting, use\"bcdedit /set {hypervisorsettings} \". For information aboutvalid types, run \"bcdedit /? TYPES\".bcdedit /hypervisorsettings [ [DEBUGPORT:] [BAUDRATE:] [CHANNEL:] [HOSTIP:] [PORT:] ] Specifies the type of debugger. can be one of SERIAL, 1394, or NET. For SERIAL debugging, specifies the serial port to use as the debugging port. For SERIAL debugging, specifies the baud rate to be used for debugging. For 1394 debugging, specifies the 1394 channel to be used for debugging. For network debugging, specifies the IPv4 address of the host debugger. For network debugging, specifies the port to communicate with on the host debugger. Should be 49152 or higher.Examples:The following command displays the current hypervisor settings: bcdedit /hypervisorsettingsThe following command sets the hypervisor debugger settings to serial debuggingover COM1 at 115,200 baud: bcdedit /hypervisorsettings SERIAL DEBUGPORT:1 BAUDRATE:115200The following command sets the hypervisor debugger settings to 1394 debuggingusing channel 23: bcdedit /hypervisorsettings 1394 CHANNEL:23The following command sets the hypervisor debugger settings to networkdebugging with a debugger host at 192.168.1.2 communicating on port 50000: bcdedit /hypervisorsettings NET HOSTIP:192.168.1.2 PORT:50000 |
This command sets or displays the hypervisor settings for the system.This command does not enable or disable the hypervisor debugger for anyparticular OS loader entry. To enable or disable the hypervisor debugger for aparticular OS loader entry, use \"bcdedit /set HYPERVISORDEBUG ON\".For information about identifiers, run \"bcdedit /? ID\".To set an individual hypervisor debugger setting, use\"bcdedit /set {hypervisorsettings} \". For information aboutvalid types, run \"bcdedit /? TYPES\".bcdedit /hypervisorsettings [ [DEBUGPORT:] [BAUDRATE:] [CHANNEL:] [HOSTIP:] [PORT:] ] Specifies the type of debugger. can be one of SERIAL, 1394, or NET. For SERIAL debugging, specifies the serial port to use as the debugging port. For SERIAL debugging, specifies the baud rate to be used for debugging. For 1394 debugging, specifies the 1394 channel to be used for debugging. For network debugging, specifies the IPv4 address of the host debugger. For network debugging, specifies the port to communicate with on the host debugger. Should be 49152 or higher.Examples:The following command displays the current hypervisor settings: bcdedit /hypervisorsettingsThe following command sets the hypervisor debugger settings to serial debuggingover COM1 at 115,200 baud: bcdedit /hypervisorsettings SERIAL DEBUGPORT:1 BAUDRATE:115200The following command sets the hypervisor debugger settings to 1394 debuggingusing channel 23: bcdedit /hypervisorsettings 1394 CHANNEL:23The following command sets the hypervisor debugger settings to networkdebugging with a debugger host at 192.168.1.2 communicating on port 50000: bcdedit /hypervisorsettings NET HOSTIP:192.168.1.2 PORT:50000 |
| 0xC100F033 | This command creates a mirror of the specified boot entry.bcdedit [/store ] /mirror {} Specifies the store to be used. If this option is not specified, the system store is used. For more information, run \"bcdedit /? store\". Specifies the identifier of the entry to be mirrored. For more information about identifiers, run \"bcdedit /? ID\".Example:The following command creates a mirror of the specified operating system bootentry: bcdedit /mirror {cbd971bf-b7b8-4885-951a-fa03044f5d71} |
This command creates a mirror of the specified boot entry.bcdedit [/store ] /mirror {} Specifies the store to be used. If this option is not specified, the system store is used. For more information, run \"bcdedit /? store\". Specifies the identifier of the entry to be mirrored. For more information about identifiers, run \"bcdedit /? ID\".Example:The following command creates a mirror of the specified operating system bootentry: bcdedit /mirror {cbd971bf-b7b8-4885-951a-fa03044f5d71} |
| 0xC100F034 | This command sets or displays the global remote event logging settings for thesystem. Currently this command is an alias of dbgsettings. Please see dbgsettings for more information. |
This command sets or displays the global remote event logging settings for thesystem. Currently this command is an alias of dbgsettings. Please see dbgsettings for more information. |
| 0xC100F035 | This command enables or disables the remote event logging for the specified boot entry.bcdedit /event [] { ON | OFF } Specifies the identifier of the entry to be modified. Only Windows boot loader entries may be specified. If not specified, {current} is used. For more information about identifiers, run \"bcdedit /? ID\".Examples:The following command enables remote event logging for the current Windowsoperating system boot entry: bcdedit /event ONThe following command disables remote event logging for the specified operatingsystem entry: bcdedit /event {cbd971bf-b7b8-4885-951a-fa03044f5d71} OFF |
This command enables or disables the remote event logging for the specified boot entry.bcdedit /event [] { ON | OFF } Specifies the identifier of the entry to be modified. Only Windows boot loader entries may be specified. If not specified, {current} is used. For more information about identifiers, run \"bcdedit /? ID\".Examples:The following command enables remote event logging for the current Windowsoperating system boot entry: bcdedit /event ONThe following command disables remote event logging for the specified operatingsystem entry: bcdedit /event {cbd971bf-b7b8-4885-951a-fa03044f5d71} OFF |
| 0xC100F036 | VESA, PCI, VGA, and TPM======================= USEFIRMWAREPCISETTINGS (bool) Uses BIOS-configured Peripheral Component Interconnect (PCI) resources. MSI Can be Default or ForceDisable. VGA (bool) Forces the use of the VGA display driver. TPMBOOTENTROPY Can be Default, ForceDisable, or ForceEnable.Debugging and Performance========================= DBGTRANSPORT (string) Defines the file name for a private debugger transport. DEBUG (bool) Enables kernel debugging. PERFMEM (integer) Specifies the size (in megabytes) of the buffer to allocate for performance data logging.Memory====== INCREASEUSERVA (integer) Increases the amount of virtual address space that the user-mode processes can use, in MBs. NOLOWMEM (bool) Disables the use of low memory. NX Can be OptIn, OptOut, AlwaysOn or AlwaysOff. PAE Can be Default, ForceEnable, ForceDisable. REMOVEMEMORY (integer) Removes memory, in MBs, from the total available memory that the operating system can use.Drivers and System Root======================= DRIVERLOADFAILUREPOLICY Can be Fatal or UseErrorControl. EMS (bool) Enables kernel Emergency Management Services. OSDEVICE (device) Defines the device that contains the system root. SYSTEMROOT (string) Defines the path to the system root.Hypervisor========== HYPERVISORLAUNCHTYPE Controls the hypervisor launch type. Can be Off or Auto. HYPERVISORDEBUG (bool) Enables hypervisor debugging. HYPERVISORDEBUGTYPE Can be SERIAL, 1394, or NET. HYPERVISORDEBUGPORT (integer) Defines the serial port number for the serial debugger. HYPERVISORBAUDRATE (integer) Defines the baud rate for the serial debugger. HYPERVISORCHANNEL (integer) Defines the channel for the 1394 debugger. HYPERVISORHOSTIP (integer) Defines the IPv4 address of the debugger host for the network debugger. HYPERVISORHOSTPORT (integer) Defines the UDP port to communicate with on the debugger host for the network debugger. HYPERVISORBUSPARAMS (string) Defines the PCI bus, device, and function numbers of the debugging device. For example, 1.5.0 describes the debugging device on bus 1, device 5, function 0. HYPERVISORUSELARGEVTLB (bool) Increases virtual TLB size. HYPERVISORIOMMUPOLICY Controls the hypervisor IOMMU policy. Can be default, enable or disable.Virtual Secure Mode=================== VSMLAUNCHTYPE Controls the Virtual Secure Mode launch type. Can be Off or Auto.For additional types that apply to the Windows OS Loader, run\"bcdedit /? TYPES BOOTAPP\". |
VESA, PCI, VGA, and TPM======================= USEFIRMWAREPCISETTINGS (bool) Uses BIOS-configured Peripheral Component Interconnect (PCI) resources. MSI Can be Default or ForceDisable. VGA (bool) Forces the use of the VGA display driver. TPMBOOTENTROPY Can be Default, ForceDisable, or ForceEnable.Debugging and Performance========================= DBGTRANSPORT (string) Defines the file name for a private debugger transport. DEBUG (bool) Enables kernel debugging. PERFMEM (integer) Specifies the size (in megabytes) of the buffer to allocate for performance data logging.Memory====== INCREASEUSERVA (integer) Increases the amount of virtual address space that the user-mode processes can use, in MBs. NOLOWMEM (bool) Disables the use of low memory. NX Can be OptIn, OptOut, AlwaysOn or AlwaysOff. PAE Can be Default, ForceEnable, ForceDisable. REMOVEMEMORY (integer) Removes memory, in MBs, from the total available memory that the operating system can use.Drivers and System Root======================= DRIVERLOADFAILUREPOLICY Can be Fatal or UseErrorControl. EMS (bool) Enables kernel Emergency Management Services. OSDEVICE (device) Defines the device that contains the system root. SYSTEMROOT (string) Defines the path to the system root.Hypervisor========== HYPERVISORLAUNCHTYPE Controls the hypervisor launch type. Can be Off or Auto. HYPERVISORDEBUG (bool) Enables hypervisor debugging. HYPERVISORDEBUGTYPE Can be SERIAL, 1394, or NET. HYPERVISORDEBUGPORT (integer) Defines the serial port number for the serial debugger. HYPERVISORBAUDRATE (integer) Defines the baud rate for the serial debugger. HYPERVISORCHANNEL (integer) Defines the channel for the 1394 debugger. HYPERVISORHOSTIP (integer) Defines the IPv4 address of the debugger host for the network debugger. HYPERVISORHOSTPORT (integer) Defines the UDP port to communicate with on the debugger host for the network debugger. HYPERVISORBUSPARAMS (string) Defines the PCI bus, device, and function numbers of the debugging device. For example, 1.5.0 describes the debugging device on bus 1, device 5, function 0. HYPERVISORUSELARGEVTLB (bool) Increases virtual TLB size. HYPERVISORIOMMUPOLICY Controls the hypervisor IOMMU policy. Can be default, enable or disable.Virtual Secure Mode=================== VSMLAUNCHTYPE Controls the Virtual Secure Mode launch type. Can be Off or Auto.For additional types that apply to the Windows OS Loader, run\"bcdedit /? TYPES BOOTAPP\". |