How to Use debugger exe for Common Issues

📌 Introduction

The debugger.exe tool is designed to fix common bot issues such as database errors, corrupted settings, or stuck accounts/devices.

This guide explains how to use it to remove problematic entries, repair the database, and configure Windows Security to avoid conflicts.

⚠️ Many issues come from database problems and Windows security restrictions.

Turning off Real-Time Protection and excluding your bot folder is often required for successful troubleshooting.

⚙️ Core Troubleshooting Steps

🗑 Remove Problematic Accounts/Devices

Use this when certain accounts or devices cause errors or prevent the bot from working properly.

Steps:

1. Open debugger.exe from your bot’s installation folder.
2. Find the list of accounts or devices.
3. Delete the line containing the problematic account or device.
4. Save and close the file/tool.
5. Restart the bot to apply changes.

💡 Tip: Always back up the configuration file before making edits.

🔒 Permanently Disable Real-Time Protection

Windows Security can block the bot from overwriting its database. Turning off protection for the bot’s folder prevents this.

Steps:

1. Open Windows Security → Virus & Threat Protection → Manage Settings.
2. Turn Real-Time Protection → Off.
3. Scroll to Exclusions → Add or Remove Exclusions.
4. Add your bot’s installation folder to the exclusion list.
5. Restart your bot.

📌 Why: This allows the bot to update or repair its database without interference.

📤 Send Debugger Errors to Support

If you encounter a problem with the bot and an error appears in debugger.exe, take a screenshot or copy the error message and send it to support.

This will help the support team fix the issue faster by seeing the exact error details.

✅ Best Practices

• Always run debugger.exe as Administrator.
• Keep backups of your bot folder before making changes.
• Only disable Windows Security for the bot folder, not your whole system.
• Keep your bot updated to the latest version.
• Send debugger errors to support immediately for faster troubleshooting.