Error Dbg Control Break 696 (0x2B8): How to Fix it

ERROR_DBG_CONTROL_BREAK is a developer error, and in most cases, you won’t encounter it as a regular user. If you encounter this issue, today’s guide is going to show you how to fix it.

How can I fix ERROR_DBG_CONTROL_BREAK?

Before we start, try to stop the debugging session and restart it again. Ensure that your drivers are up to date.

1. Close any debuggers that might be running

1. Press Ctrl + Shift + Esc to open Task Manager.
2. Next, look for debugger tools such as windbg.exe, and vsjitdebugger.exe.
3. Select them and click on End Task.
   

2. Detach the debugger from the process

1. Open your debugging tool of choice.
2. If you’re using Visual Studio, go to Debug and choose Detach All.
   
3. For WinDbg, go to Debug and select Detach Debuggee.

3. Disable Debugging mode in Windows

1. Press the Windows key + S and type cmd. Select Run as administrator.
   
2. Run the following command: bcdedit /debug off
   
3. Restart your PC.

4. Scan your system files

1. Open Command Prompt as administrator once again.
2. Run sfc /scannow
   
3. Wait for the scan to finish.
4. Restart your PC and check if the problem is gone.

Often you can recognize ERROR_DBG_CONTROL_BREAK by the following message: 696 (0x2B8) Debugger received control break. If you ever encounter this problem, you should be able to fix it by restarting your debugging sessions or with our other solutions.

This isn’t the only debugging error you can encounter, we wrote about ERROR_DBG_PRINTEXCEPTION_C and ERROR_DBG_CONTROL_C in our previous guides, so don’t miss them.