-
Notifications
You must be signed in to change notification settings - Fork 82
Troubleshooting
Sven Scharmentke edited this page Oct 11, 2025
·
4 revisions
Error: CDB executable not found
Solutions:
- Check if CDB is in PATH:
where cdb - Install Windows SDK with "Debugging Tools for Windows"
- Set custom path in
mcp.json:"args": ["-m", "mcp_windbg", "--cdb-path", "C:\\Program Files (x86)\\Windows Kits\\10\\Debuggers\\x64\\cdb.exe"]
Error: No module named 'mcp_windbg'
Solutions:
- Verify:
pip list | findstr mcp-windbg - Reinstall:
pip uninstall mcp-windbg && pip install mcp-windbg - Use full Python path in
mcp.jsonfor virtual environments:"command": "${workspaceFolder}/.venv/Scripts/python"
Problem: Tools don't appear in Copilot
Solutions:
- Enable MCP in Copilot settings (
Ctrl+,→ search "MCP") - Verify
.vscode/mcp.jsonexists and has valid JSON - Restart VS Code completely
- Check Output → Model Context Protocol for errors
Problem: "No symbols" or symbol loading fails
Solutions:
- Configure symbol path in
mcp.json:"env": {"_NT_SYMBOL_PATH": "SRV*C:\\Symbols*https://msdl.microsoft.com/download/symbols"}
- Test:
python -m mcp_windbg --symbols-path "SRV*C:\Symbols*https://msdl.microsoft.com/download/symbols" - Check network access to
https://msdl.microsoft.com
Problem: "Command timeout" errors
Solutions:
- Increase timeout:
"args": ["-m", "mcp_windbg", "--timeout", "120"] - Use simpler commands first
- Avoid broad analysis on large dumps
Problem: Out of memory or slow performance
Solutions:
- Close unused sessions: "Close the crash dump session for C:\dumps\large.dmp"
- Analyze specific areas instead of full dumps
- Use 64-bit CDB for large dumps
Problem: "Access denied" or "File not found"
Solutions:
- Check file permissions and use absolute paths
- Run VS Code as administrator if needed
- Copy network files locally for analysis
Problem: Cannot connect to remote target
Solutions:
- Use correct format:
tcp:Port=5005,Server=192.168.0.100 - Test connectivity:
telnet 192.168.0.100 5005 - Check target firewall and debugging settings
| Error | Solution |
|---|---|
| "Failed to load dump file" | Check file integrity and permissions |
| "Symbol loading failed" | Verify symbol path and network connectivity |
| "Remote connection refused" | Check port and firewall settings |
| "Command not recognized" | Verify WinDbg command syntax |
"args": ["-m", "mcp_windbg", "--verbose"]# Check versions
python --version
cdb -version
# Test installation
pip list | findstr mcp-windbg
python -m mcp_windbg --help
# Test connectivity
curl -I https://msdl.microsoft.com/download/symbols- Check VS Code Output → Model Context Protocol
- Enable verbose logging
- Search GitHub Issues
- Create new issue with:
- OS, Python, VS Code versions
- Complete error messages
- Steps to reproduce
- Configuration files