How to fix ERROR_DBG_CONTROL_C 693 (0x2B5)
Repairing system files is the quickest fix
4 min. read
Updated on
Read our disclosure page to find out how can you help Windows Report sustain the editorial team. Read more
The ERROR_DBG_CONTROL_C Win32 system error, with code 693 (0x2B5), indicates issues with the debugger or the debugging process. The message for Error Code 693 reads, Debugger got control C.
The system code usually appears due to corrupted system files, outdated drivers, conflicting applications, and a buggy or incompatible BIOS.
Before you proceed to the solutions, restart the computer, install pending Windows and software updates, and disable any active third-party antivirus solution!
How can I fix the ERROR_DBG_CONTROL_C Windows system error?
1. Repair corrupted system files
- Press Windows + S to open Search, type Command Prompt, and click on Run as administrator.
- Click Yes in the UAC prompt.
- Paste the following DISM commands individually and hit Enter after each:
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
- Execute this command to run the SFC scan:
sfc /scannow
- Finally, restart the computer to apply the changes.
Since corrupted system files are the most common reason behind Error Code 693 (ERROR_DBG_CONTROL_C), you should run the DISM (Deployment Image Servicing and Management) and SFC (System File Checker) scans to replace all problematic files with their cached copies!
2. Update the drivers
- Press Windows + X to open the Power User menu, and select Device Manager.
- Expand all the entries here, individually right-click on each device listed underneath, and select Update driver.
- Click on Search automatically for drivers to let Windows install the best locally available version.
- Similarly, update the other drivers and then restart the PC.
Corrupted or outdated drivers can also trigger issues with the debugging process causing ERROR_DBG_CONTROL_C, and updating the drivers will get things up and running!
If Windows can’t find a better version, go to the manufacturer’s website, find the new releases, and manually install the latest driver.
3. Uninstall conflicting applications
- Press Windows + R to open Run, type appwiz.cpl in the text field, and hit Enter.
- Select any app installed or updated around the same time the issues first appeared, and click Uninstall.
- Follow the on-screen instructions to complete the process and then reboot the PC.
If a quick app removal didn’t work, there may be leftover files or Registry entries still conflicting with Windows. So, I recommend using a top-rated software uninstaller to wipe all traces of the app installation.
4. Perform a system restore
- Press Windows + S to open Search, type Create a restore point, and click on the relevant result.
- Click the System Restore button.
- Select the Choose a different restore point option, if available, and click Next.
- Pick the oldest restore point from the list, and click Next.
- Verify the restore details, click Finish, and confirm the change.
- Wait for the restore to complete. It typically takes 15-45 minutes.
If you can’t figure out what’s triggering ERROR_DBG_CONTROL_C 693 (0x2B5) Debugger got control C, performing a system restore will revert any recent misconfigurations. Make sure you choose a restore point created before the system error first appeared!
5. Update the BIOS
For a few, a bug in the installed BIOS version was responsible for ERROR_DBG_CONTROL_C. So, if a new version is available, update the BIOS. Otherwise, downgrade to an older BIOS version.
Since the BIOS update is tricky and different for each computer, I recommend you check the manufacturer’s official website for the exact steps.
One of these solutions should have ideally fixed Error Code 693 (Debugger got control C). If not, the last option is to reinstall Windows. It will certainly get things running because the problem is almost always caused by software-based issues.
Before you leave, discover common Windows errors and their expert solutions to prevent such issues from reappearing! Also, don’t miss our latest article on ERROR_DBG_CONTROL_BREAK for more information.
For any queries or to share which fix worked for you, drop a comment below.
User forum
0 messages