Solutions to the most common issues. If your problem isn't here, please open an issue.

Symptom: Double-clicking the EXE shows a UAC prompt, then the app closes or does nothing.

Cause: The app must run with administrator privileges — it needs to modify network packets at a low level.

Fix:

1. Right-click the EXE
2. Choose Run as administrator
3. Accept the UAC prompt

Permanent fix:

1. Right-click EXE → Properties
2. Compatibility tab → check Run this program as an administrator
3. Click Apply

Symptom: Windows Defender or your antivirus marks WinDivert.dll / WinDivert64.sys as suspicious.

Cause: This is a false positive. WinDivert is a legitimate packet-filtering library used by many network tools.

Fix:

1. Open your antivirus Exclusions settings
2. Add the entire folder where GoodByeDPI.GUI.exe lives
3. Restore the file if it was quarantined

📖 WinDivert is used by tools like Simplewall, clumsy, and many others.

Symptom: You click Start, status shows Running, but sites still don't load.

Try these steps in order:

• From ⚡ Fast → 🛡 Compatible
• If that fails → 🔧 Custom

-f 2 -e 40 --native-frag --reverse-frag --max-payload

VPNs and GoodbyeDPI conflict. Turn off the VPN, restart GoodByeDPI, and try again.

Some browsers use QUIC/HTTP3 (UDP-based) which GoodbyeDPI doesn't touch by default. Try:

• Firefox (uses TLS by default)
• Chrome with chrome://flags → disable QUIC

Open CMD as admin:

ipconfig /flushdns

netsh winsock reset
netsh int ip reset

Then reboot.

Some ISPs (especially in certain countries) use advanced filtering beyond DPI. In this case:

• Try Cloudflare WARP
• Or a VPN — GoodbyeDPI isn't always enough

Symptom: You enabled "Run on Windows startup" but the app doesn't launch at login.

Steps to fix:

1. Open Task Scheduler (taskschd.msc)
2. Find the task named GoodbyeDPIManager
3. Right-click → Properties
4. Under General:
   • ✅ Check Run with highest privileges
   • ✅ Check Run whether user is logged on or not
5. Under Triggers: verify it says At log on
6. Click OK

If the task doesn't exist:

• In the GUI, untick then re-tick the option

If you moved the EXE:

• Same fix — re-toggle the setting so the task points to the new path

Symptom: You click "Check for updates" but nothing happens.

Cause: The check runs silently. If you're up to date, you'll see a toast (not a dialog).

Fix: Look at the bottom-right corner of the window — a toast should appear:

• 🟢 "You're on the latest version" — you're up to date
• ⚠ "Couldn't check for updates" — offline or GitHub is blocked

Symptom: You run python main.py from source and it crashes immediately.

Cause: You're running from the wrong directory.

Fix: Always run from the project root:

cd GoodByeDPI-GUI
python main.py

Not from inside app/ or any subfolder.

Symptom: Start fails with an error about ports.

Cause: Another instance of GoodbyeDPI or a similar tool is running.

Fix:

1. Open Task Manager (Ctrl+Shift+Esc)
2. Find and End Task on goodbyedpi.exe
3. Also close any other DPI-bypassing tools
4. Restart GoodByeDPI GUI

Symptom: The window title bar is white/light instead of dark.

Cause: Older Windows 10 builds (< 1809) don't support the DWMWA_USE_IMMERSIVE_DARK_MODE attribute.

Fix: Update Windows. This feature works on:

• Windows 10 v1809+
• Windows 11 (all versions)

Symptom: Websites eventually load, but take 10-30 seconds.

Cause: Fast mode's aggressive fragmentation is being filtered.

Fix:

1. Stop GoodByeDPI
2. Switch to 🛡 Compatible
3. Start again

If still slow, try a Custom combo:

-f 2 -e 40 --native-frag

(without --reverse-frag)

Symptom: The window opens briefly then closes.

Steps:

1. Run the EXE from CMD (as admin) to see the error output:

   "GoodByeDPI.GUI.exe"

2. Copy the error message
3. Open an issue with:
   • Windows version (winver)
   • The error message
   • Steps you took before the crash

Try these in order:

1. Search existing issues — someone may have hit it already:
   👉 github.com/ZvanTors/GoodByeDPI-GUI/issues
2. Ask in Discussions:
   👉 github.com/ZvanTors/GoodByeDPI-GUI/discussions
3. Open a new issue with:
   • ✅ Windows version
   • ✅ App version
   • ✅ Selected mode
   • ✅ Custom args (if any)
   • ✅ The log output (use the Copy button)
   • ✅ What you tried