{
	"id": "aa24f2df-74cf-4ed4-aafe-8baf9b2cc8d2",
	"created_at": "2026-04-06T00:09:47.349891Z",
	"updated_at": "2026-04-10T03:20:43.734328Z",
	"deleted_at": null,
	"sha1_hash": "14abf32dad665e62bb5d4e122af1b84b8c20e837",
	"title": "bcdedit",
	"llm_title": "",
	"authors": "",
	"file_creation_date": "0001-01-01T00:00:00Z",
	"file_modification_date": "0001-01-01T00:00:00Z",
	"file_size": 47028,
	"plain_text": "bcdedit\r\nBy robinharwood\r\nArchived: 2026-04-05 18:30:40 UTC\r\nBoot Configuration Data (BCD) files provide a store that is used to describe boot applications and boot\r\napplication settings. The objects and elements in the store effectively replace Boot.ini.\r\nBCDEdit is a command-line tool for managing BCD stores. It can be used for a variety of purposes, including\r\ncreating new stores, modifying existing stores, adding boot menu parameters, and so on. BCDEdit serves\r\nessentially the same purpose as Bootcfg.exe on earlier versions of Windows, but with two major improvements:\r\nExposes a wider range of boot parameters than Bootcfg.exe.\r\nHas improved scripting support.\r\nNote\r\nAdministrative privileges are required to use BCDEdit to modify BCD.\r\nBCDEdit is the primary tool for editing the boot configuration of Windows Vista and later versions of Windows. It\r\nis included with the Windows Vista distribution in the %WINDIR%\\System32 folder.\r\nBCDEdit is limited to the standard data types and is designed primarily to perform single common changes to\r\nBCD. For more complex operations or nonstandard data types, consider using the BCD Windows Management\r\nInstrumentation (WMI) application programming interface (API) to create more powerful and flexible custom\r\ntools.\r\nSyntax\r\nbcdedit /command [\u003cargument1\u003e] [\u003cargument2\u003e] ...\r\nParameters\r\nGeneral BCDEdit Command-Line Options\r\nOption Description\r\n/?\r\nDisplays a list of BCDEdit commands. Running this command without an argument displays a\r\nsummary of the available commands. To display detailed help for a particular command, run\r\nbcdedit /? \u003ccommand\u003e , where \u003ccommand\u003e is the name of the command you are searching for\r\nmore information about. For example, bcdedit /? createstore displays detailed help for the\r\nCreatestore command.\r\nhttps://docs.microsoft.com/en-us/windows-server/administration/windows-commands/bcdedit\r\nPage 1 of 4\n\nParameters that Operate on a Store\r\nOption Description\r\n/createstore Creates a new empty boot configuration data store. The created store is not a system store.\r\n/export\r\nExports the contents of the system store into a file. This file can be used later to restore the\r\nstate of the system store. This command is valid only for the system store.\r\n/import\r\nRestores the state of the system store by using a backup data file previously generated by using\r\nthe /export option. This command deletes any existing entries in the system store before the\r\nimport takes place. This command is valid only for the system store.\r\n/store\r\nThis option can be used with most BCDedit commands to specify the store to be used. If this\r\noption is not specified, then BCDEdit operates on the system store. Running the bcdedit /store\r\ncommand by itself is equivalent to running the bcdedit /enum active command.\r\nParameters that Operate on Entries in a Store\r\nParameter Description\r\n/copy Makes a copy of a specified boot entry in the same system store.\r\n/create\r\nCreates a new entry in the boot configuration data store. If a well-known identifier is specified,\r\nthen the /application, /inherit, and /device parameters cannot be specified. If an identifier is\r\nnot specified or not well known, an /application, /inherit, or /device option must be specified.\r\n/delete Deletes an element from a specified entry.\r\nParameters that Operate on Entry Options\r\nParameter Description\r\n/deletevalue Deletes a specified element from a boot entry.\r\n/set Sets an entry option value.\r\nParameters that Control Output\r\nParameter Description\r\n/enum\r\nLists entries in a store. The /enum option is the default value for BCEdit, so running the\r\nbcdedit command without parameters is equivalent to running the bcdedit /enum active\r\ncommand.\r\nhttps://docs.microsoft.com/en-us/windows-server/administration/windows-commands/bcdedit\r\nPage 2 of 4\n\nParameter Description\r\n/v\r\nVerbose mode. Usually, any well-known entry identifiers are represented by their friendly\r\nshorthand form. Specifying /v as a command-line option displays all identifiers in full. Running\r\nthe bcdedit /v command by itself is equivalent to running the bcdedit /enum active /v\r\ncommand.\r\nParameters that Control the Boot Manager\r\nParameter Description\r\n/bootsequence\r\nSpecifies a one-time display order to be used for the next boot. This command is similar\r\nto the /displayorder option, except that it is used only the next time the computer starts.\r\nAfterwards, the computer reverts to the original display order.\r\n/default Specifies the default entry that the boot manager selects when the timeout expires.\r\n/displayorder\r\nSpecifies the display order that the boot manager uses when displaying boot parameters\r\nto a user.\r\n/timeout Specifies the time to wait, in seconds, before the boot manager selects the default entry.\r\n/toolsdisplayorder Specifies the display order for the boot manager to use when displaying the Tools menu.\r\nParameters that Control Emergency Management Services\r\nParameter Description\r\n/bootems Enables or disables Emergency Management Services (EMS) for the specified entry.\r\n/ems Enables or disables EMS for the specified operating system boot entry.\r\n/emssettings\r\nSets the global EMS settings for the computer. /emssettings does not enable or disable EMS\r\nfor any particular boot entry.\r\nParameters that Control Debugging\r\nParameter Description\r\n/bootdebug\r\nEnables or disables the boot debugger for a specified boot entry. Although this command\r\nworks for any boot entry, it is effective only for boot applications.\r\nhttps://docs.microsoft.com/en-us/windows-server/administration/windows-commands/bcdedit\r\nPage 3 of 4\n\nParameter Description\r\n/dbgsettings\r\nSpecifies or displays the global debugger settings for the system. This command does not\r\nenable or disable the kernel debugger; use the /debug option for that purpose. To set an\r\nindividual global debugger setting, use the bcdedit /set \u003cdbgsettings\u003e \u003ctype\u003e \u003cvalue\u003e\r\ncommand.\r\n/debug Enables or disables the kernel debugger for a specified boot entry.\r\nFor examples of how to use BCDEdit, see the BCDEdit Options Reference article.\r\nTo see the notation used to indicate command-line syntax, see Command-Line Syntax Key.\r\nSource: https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/bcdedit\r\nhttps://docs.microsoft.com/en-us/windows-server/administration/windows-commands/bcdedit\r\nPage 4 of 4",
	"extraction_quality": 1,
	"language": "EN",
	"sources": [
		"MITRE"
	],
	"references": [
		"https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/bcdedit"
	],
	"report_names": [
		"bcdedit"
	],
	"threat_actors": [],
	"ts_created_at": 1775434187,
	"ts_updated_at": 1775791243,
	"ts_creation_date": 0,
	"ts_modification_date": 0,
	"files": {
		"pdf": "https://archive.orkl.eu/14abf32dad665e62bb5d4e122af1b84b8c20e837.pdf",
		"text": "https://archive.orkl.eu/14abf32dad665e62bb5d4e122af1b84b8c20e837.txt",
		"img": "https://archive.orkl.eu/14abf32dad665e62bb5d4e122af1b84b8c20e837.jpg"
	}
}