Back to docs
TroubleshootingUpdated: December 5, 2024

Common Issues

Solutions to frequently encountered problems.

Common Issues

If something isn’t working as expected, you’re in the right place. This guide covers the most frequent problems and how to fix them—clear, direct, and jargon-free.

Permission errors

Some features (like service management or deep system inspection) need administrator rights. If you see permission errors:

  • Run WinDEETS as administrator.
  • For event log access, check your Group Policy or local policy settings.

Windows Defender Firewall blocking WinDEETS

When you first install WinDEETS, Windows Defender Firewall may show a security alert. The installer automatically configures firewall rules to allow WinDEETS on both private and public networks.

If you see the firewall dialog:

  • Check both boxes (Private networks AND Public networks) to ensure full functionality.

  • Private networks (home/work) are recommended at minimum for trusted network access.

  • If you accidentally dismissed the dialog, you can manually allow WinDEETS in Windows Defender Firewall settings:

    netsh advfirewall firewall add rule name="WinDEETS" dir=in action=allow program="C:\Program Files\WinDEETS\WinDEETS.exe" enable=yes profile=private,public
    

The installer automatically sets up these rules during installation, and removes them when you uninstall WinDEETS.

Application fails to start

If WinDEETS doesn't launch after install:

  • On a headless server or VM, try launching with --no-gpu:

    "C:\Program Files\WinDEETS\WinDEETS.exe" --no-gpu
    
  • Check logs at %LOCALAPPDATA%\WinDEETS\logs for error details.

  • Make sure all required dependencies are installed (Windows updates, Visual C++ redistributables).

Permission denied when collecting event logs

  • Run WinDEETS as administrator.
  • Check for policies that restrict event log access.

High CPU or memory usage

If WinDEETS uses more resources than expected:

  • Reduce the data collection window or limit the number of channels.
  • Use No-GPU mode if you have GPU driver issues.

Error codes and reporting

If you see an error code:

  • Include the code and a log excerpt when reporting.
  • Use the Contact → Bug report form to send issues, and attach a diagnostic export if possible.

If you’re still stuck, check the Documentation for more guides or Contact us for help. We’re here to get you back on track.