| title | description | keywords | ms.date | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Boot Parameters to Enable Debugging |
Boot Parameters to Enable Debugging |
|
10/21/2022 |
When a kernel debugging connection is established, the system gives a kernel debugger control over its execution. Also, when a bug check occurs or a kernel-mode program communicates with a debugger, the computer waits for a response from a kernel debugger before it continues.
Important
Setting up a network debugging manually is a complex and error prone process. To set up network debugging automatically, see Setting Up KDNET Network Kernel Debugging Automatically. Using the KDNET utility is strongly recommended for all debugger users.
For information on manual setup of a network connection, see Setting Up Kernel-Mode Debugging over a Network Cable Manually.
Note
Before setting BCDEdit options you might need to disable or suspend BitLocker and Secure Boot on the computer.
Caution
Administrative privileges are required to use BCDEdit to modify BCD. Changing some boot entry options using the BCDEdit command could render your computer inoperable. As an alternative, use the Startup settings to change boot settings.
You can use the bcdedit command to view the current debugger boot entries and to change their settings. For more details, see BCDEdit /debug and BCDEdit /dbgsettings.
To enable boot debugging, use the BCDEdit /bootdebug command and specify the appropriate boot component. If you wish to perform kernel debugging after Windows starts, use the BCDEdit /debug command as well. You must also select a debugging connection, just as in normal kernel debugging. For more details, see BCDEdit /bootdebug.
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 and Setting Up KDNET Network Kernel Debugging Automatically.