BCDEDIT Command – Edit Boot Configuration in Windows

The BCDEDIT command is a Windows Command Prompt utility that displays and modifies Boot Configuration Data (BCD), which controls how Windows starts. Use BCDEDIT to view boot entries, BCDEDIT /set to change boot options, and BCDEDIT /copy to create backup boot configurations—essential for dual-boot setups, safe mode configuration, boot troubleshooting, and recovery. Administrator privileges are required for all modifications.

Whether you're a system administrator configuring multi-boot environments, an IT professional troubleshooting boot failures, or a power user customizing boot options and timeouts, BCDEDIT provides low-level control over the Windows boot process. The command replaces the legacy boot.ini and is the primary tool for BCD management on Windows Vista and later.

This comprehensive guide covers BCDEDIT syntax, key operations including /enum, /set, and /copy, practical examples for common scenarios, safety precautions, troubleshooting tips, and frequently asked questions. By the end, you'll understand BCD structure and use BCDEDIT responsibly for boot configuration.

What Is the BCDEDIT Command?

The BCDEDIT command is a built-in Windows utility for editing Boot Configuration Data (BCD). BCD is a database that stores boot configuration and replaces the boot.ini file used in older Windows versions. BCD determines which operating systems are available at startup, default boot order, timeout, and boot parameters (e.g., safe mode, debug mode).

BCDEDIT runs in Command Prompt (CMD) and requires Administrator privileges for any modifications. It is available in Windows Vista and later, including Windows 10, Windows 11, and all Windows Server editions. Incorrect use can prevent the system from booting—always backup and test carefully.

BCDEDIT vs Other Boot Tools

• BCDEDIT: Command-line; full BCD control; advanced users
• System Configuration (msconfig): GUI; boot tab; simpler
• Windows Recovery Environment: Repair and reset options
• Bootrec: Fix boot sector; use when Windows won't start

Syntax

BCDEDIT /command [argument1] [argument2] ...

Common Commands

Command	Description
/enum	Displays boot entries (use /enum all for full)
/set	Sets or modifies a boot entry option
/copy	Copies an existing boot entry
/create	Creates a new boot entry
/delete	Deletes a boot entry
/export	Exports BCD store to file (backup)
/import	Imports BCD store from file (restore)
/default	Sets the default boot entry
/displayorder	Sets the order of boot entries
/timeout	Sets boot menu timeout in seconds
/store	Specifies BCD store (default: system)

Common Options for /set

Option	Description
safeboot minimal	Safe Mode
safeboot network	Safe Mode with Networking
safebootalternateshell yes	Safe Mode with Command Prompt
debug on	Enable kernel debugging
nx OptIn	Data Execution Prevention
truncatememory	Limit memory (troubleshooting)

How to Use BCDEDIT Command

View Boot Configuration

Display current boot entries:

BCDEDIT

Or enumerate all:

BCDEDIT /enum

For full details including all properties:

BCDEDIT /enum all

Backup BCD Store

Export BCD to a file before making changes:

BCDEDIT /export C:\BCD_Backup

Restore if needed:

BCDEDIT /import C:\BCD_Backup

Set Boot Menu Timeout

Change how long the boot menu displays (e.g., 10 seconds):

BCDEDIT /timeout 10

Use 0 for immediate boot to default, or higher values for more time to choose.

Set Default Boot Entry

Make a specific entry the default:

BCDEDIT /default {current}

Or use the GUID of another entry. {current} is the currently running Windows.

Copy Boot Entry (Create Backup Entry)

Create a copy of the current Windows entry for safe mode or testing:

BCDEDIT /copy {current} /d "Windows Safe Mode"

This creates a new entry you can modify without affecting the main one.

Enable Safe Mode for an Entry

Configure an entry to boot in Safe Mode:

BCDEDIT /copy {current} /d "Windows Safe Mode"
BCDEDIT /set {GUID} safeboot minimal

Replace {GUID} with the ID of the new entry from the /copy output.

Disable Safe Mode

If stuck in Safe Mode, disable it:

BCDEDIT /deletevalue {current} safeboot

Run from Safe Mode or Recovery Environment.

Add Custom Boot Option (e.g., Debug)

Enable kernel debugging for an entry:

BCDEDIT /set {current} debug yes

Remove Boot Entry

Delete an entry (use with caution):

BCDEDIT /delete {GUID}

Use /delete {GUID} /f to force delete. Get GUID from BCDEDIT /enum.

Common Use Cases

1. Backup boot configuration – Export BCD before major changes: BCDEDIT /export C:\BCD_Backup.

2. Change boot order – Use /displayorder to reorder entries for dual-boot or multi-OS setups.

3. Create Safe Mode entry – Copy current entry, set safeboot, for easy access to Safe Mode from boot menu.

4. Increase boot menu timeout – Use /timeout 30 to give more time to select OS on dual-boot systems.

5. Troubleshoot boot failure – Enable debug or safe mode, or restore from BCD backup.

6. Dual-boot configuration – Add, remove, or reorder entries for Linux, older Windows, or recovery.

7. Disable Secure Boot temporarily – Some firmware; BCDEDIT can work with boot options when combined with firmware settings.

8. Memory limit for testing – Use truncatememory to simulate low-memory scenarios.

9. Recovery environment – Use BCDEDIT from WinRE to fix corrupted BCD when Windows won't boot.

10. Document boot setup – Export BCD and document for disaster recovery.

Tips and Best Practices

1. Always backup first – Run BCDEDIT /export C:\BCD_Backup before any changes.

2. Run as Administrator – BCDEDIT requires elevated privileges for all modifications.

3. Use {current} carefully – {current} refers to the running OS; verify before /set or /delete.

4. Test in VM first – Practice BCDEDIT in a virtual machine before production systems.

5. Document GUIDs – When creating entries, note the GUID for future reference.

6. Disable BitLocker if needed – Some BCD changes may require BitLocker suspended; check documentation.

7. Have recovery media ready – Keep Windows installation or recovery USB available in case of boot failure.

8. One change at a time – Make one modification, reboot, verify, then proceed.

9. Use msconfig for simple changes – For boot timeout and safe mode, msconfig may be easier and safer.

10. Understand before modifying – Read BCDEDIT /? and /? OPERATIONS for full syntax.

Troubleshooting Common Issues

"The requested system device cannot be found"

Problem: BCDEDIT fails with device not found.

Cause: BCD store may be corrupted, or wrong store specified. Running from incorrect environment.

Solution: Boot to Windows Recovery Environment (WinRE). Use BCDEDIT /store C:\Boot\BCD if BCD is on another drive. Run bootrec /rebuildbcd to repair BCD.

Prevention: Backup BCD regularly; avoid modifying when uncertain.

Windows Won't Boot After BCDEDIT Change

Problem: System fails to start after BCDEDIT modification.

Cause: Incorrect /set, deleted critical entry, or corrupted BCD.

Solution: Boot from Windows installation or recovery media. Open Command Prompt, run BCDEDIT /import C:\BCD_Backup if you have backup. Or use bootrec /fixboot and bootrec /rebuildbcd to repair.

Prevention: Always export before changes; test in non-critical environment first.

"Access is denied"

Problem: BCDEDIT returns access denied.

Cause: Not running as Administrator.

Solution: Right-click Command Prompt → Run as administrator. Ensure your account has Administrator rights.

Prevention: Always use elevated Command Prompt for BCDEDIT.

"The specified entry was not found"

Problem: GUID or identifier not found.

Cause: Typo in GUID, or entry was deleted. GUIDs are in braces like {current} or {bootmgr}.

Solution: Run BCDEDIT /enum to list valid identifiers. Use exact GUID from output. Common: {current}, {bootmgr}, {default}.

Prevention: Copy GUIDs from BCDEDIT output; don't type manually.

Related Commands

BOOTREC – Boot Recovery

BOOTREC repairs boot sector and BCD when Windows won't start. Use from WinRE.

Example:

bootrec /fixmbr
bootrec /fixboot
bootrec /rebuildbcd

When to use: Windows won't boot; BCD corruption.

MSCONFIG – System Configuration

MSCONFIG provides a GUI for boot options, timeout, and safe mode. Simpler for basic changes.

Example:

msconfig

When to use: Boot tab changes without command line.

DISKPART – Disk Management

DISKPART manages partitions. Use when BCD or boot files are on a different partition.

Example:

diskpart
list volume

When to use: Identifying boot partition, disk layout.

SFC – System File Checker

SFC scans and repairs protected system files. Use if boot files are corrupted.

Example:

sfc /scannow

When to use: Suspected system file corruption affecting boot.

Frequently Asked Questions

What does the BCDEDIT command do?

BCDEDIT displays and modifies Boot Configuration Data (BCD), which controls how Windows starts. It can change boot order, timeout, default OS, safe mode, debug options, and create or delete boot entries. Administrator rights required.

Is it safe to use BCDEDIT?

BCDEDIT is powerful and can prevent Windows from booting if used incorrectly. Always backup with BCDEDIT /export before changes. Use msconfig for simpler boot options when possible.

How do I backup my boot configuration?

Use BCDEDIT /export C:\BCD_Backup to save BCD to a file. Restore with BCDEDIT /import C:\BCD_Backup if needed. Store backup on separate drive or media.

How do I enable Safe Mode with BCDEDIT?

Copy current entry: BCDEDIT /copy {current} /d "Safe Mode". Note the new GUID. Then: BCDEDIT /set {GUID} safeboot minimal. Reboot and select "Safe Mode" from boot menu.

How do I change the boot menu timeout?

Use BCDEDIT /timeout seconds. For example, BCDEDIT /timeout 10 shows the menu for 10 seconds. Use 0 for no menu (boot directly to default).

How do I set the default boot entry?

Use BCDEDIT /default {GUID}. Replace {GUID} with the entry ID from BCDEDIT /enum. Use {current} for the running Windows.

What is {current} in BCDEDIT?

{current} is an alias for the boot entry of the currently running Windows installation. Use it to modify the active OS entry without looking up the GUID.

Can I use BCDEDIT to fix a computer that won't boot?

Yes, from Windows Recovery Environment. Boot from installation media, choose Repair, then Command Prompt. Run bootrec /rebuildbcd or BCDEDIT /import if you have a backup. Use bootrec /fixboot for boot sector issues.

How do I delete a boot entry?

Use BCDEDIT /delete {GUID}. Get the GUID from BCDEDIT /enum. Add /f to force: BCDEDIT /delete {GUID} /f. Never delete {current} or {bootmgr} unless you know what you're doing.

What is the difference between BCDEDIT and boot.ini?

boot.ini was used in Windows XP and earlier. BCD replaced it in Windows Vista and later. BCDEDIT edits BCD; boot.ini is no longer used on modern Windows.

How do I view all boot entries?

Run BCDEDIT /enum or BCDEDIT /enum all for full details. Use BCDEDIT with no arguments for a summary.

When should I use msconfig instead of BCDEDIT?

Use msconfig for boot timeout, safe mode, and number of processors—it's safer and easier. Use BCDEDIT for advanced options, custom entries, or when msconfig doesn't expose the setting.

Quick Reference Card

Command	Purpose	Example
BCDEDIT	View boot config	Summary
BCDEDIT /enum all	Full boot details	All properties
BCDEDIT /export path	Backup BCD	Before changes
BCDEDIT /import path	Restore BCD	Recovery
BCDEDIT /timeout 10	Boot menu seconds	10 sec timeout
BCDEDIT /default {id}	Set default OS	Boot order
BCDEDIT /copy {current} /d "Name"	Copy entry	New boot option
BCDEDIT /set {id} safeboot minimal	Enable Safe Mode	Safe boot
BCDEDIT /deletevalue {current} safeboot	Disable Safe Mode	Exit safe mode

Try BCDEDIT Command Now

Explore boot configuration concepts in our Windows Command Simulator. For system repair, see SFC and DISM. Browse the full Commands Reference for more Windows CMD utilities. Warning: BCDEDIT is not typically run in simulators; use on real Windows systems with caution.

Summary

The BCDEDIT command manages Boot Configuration Data (BCD) that controls Windows startup. Use it to view entries, set boot timeout, change default OS, create Safe Mode entries, and backup or restore boot configuration. Always backup with /export before changes, run as Administrator, and use msconfig for simpler boot options when possible. BCDEDIT is powerful—incorrect use can prevent booting. Master it for advanced boot management and recovery scenarios.