BCDEdit /debug

The /debug boot option enables or disables kernel debugging of the Windows operating system associated with the specified boot entry or the current boot entry.


Before setting BCDEdit options you might need to disable or suspend BitLocker and Secure Boot on the computer.

    bcdedit /debug [{ID}] { on | off } 



The {ID} is the GUID that is associated with the boot entry. If you do not specify an {ID}, the command modifies the operating system that is currently active. If a boot entry is specified, the GUID associated with the boot entry must be enclosed in braces { }.

Enables kernel debugging of the specified boot entry. If a boot entry is not specified, kernel debugging is enabled for the current operating system.

Disables kernel debugger of the specified boot entry. If a boot entry is not specified, kernel debugging is disabled for the current operating system.


The /debug boot option enables kernel debugging for a specific boot entry. Use the /dbgsettings option to configure the type of debugging connection to use and the connection parameters. If no /dbgsettings are specified for the boot entry, the global debug settings are used. The default values for the global settings are shown in the following table.

dbgsetting parameter Default value

Connection type


Debug port


Baud rate


For information about Windows debugging tools, see Windows Debugging. For information about setting up and configuring a kernel-mode debugging session, see Setting Up Kernel-Mode Debugging Manually.

The following example enables kernel debugging of the boot entry with the GUID of 49916baf-0e08-11db-9af4-000bdbd316a0.

bcdedit /debug {49916baf-0e08-11db-9af4-000bdbd316a0} on 

In the following example, the first command sets the global debugger settings for USB 2.0 and names the target myVistaTarget. The second command enables the debugger for the current session.

bcdedit /dbgsettings usb targetname:myVistaTarget 
bcdedit /debug ON