What the sources actually say

The klaymm practical guide lists AdGuard Desktop on its preflight checklist: before troubleshooting, either turn off filtering in AdGuard Desktop or add winws.exe and Discord.exe to its exclusions. The guide also links Issue #13149 under the label Discord plus AdGuard, 5000 ms ping, RTC.

Issue #13149 (opened 2026-05-08, closed as stale) is a user-written solution report. The author used zapret 1.9.7b with the ALT 11 strategy when, around 2026-04-29, Discord voice broke: text chats worked, but connecting to any voice channel hung on RTC connecting and ping climbed as high as 5000 ms. Voice in the browser version of Discord worked normally, and newer zapret versions had fixed the problem for some users but not for this author.

The author reports that fully turning off AdGuard immediately restored Discord voice, and attributes the conflict to AdGuard traffic filtering. Notably, the author says AdGuard and zapret had previously run together without conflicts, so this was a change in behavior, not a guaranteed incompatibility.

The workaround the author describes, quoted as steps from that issue:

  1. Open AdGuard, go to Settings, then the Network section.
  2. Under traffic filtering, open the list of filtered applications.
  3. Add winws.exe from the bin folder of the zapret build, and add Discord if it is not listed.
  4. Uncheck both winws.exe and Discord in that list; the unchecked state is what disables filtering for them.
  5. Optionally, the author notes the same approach for Cloudflare WARP, which can appear as warp-svc or Cloudflare WARP, if WARP also stopped working.
This fix is one user report attributed to Issue #13149, not an official recommendation. The pinned Flowseal Discord troubleshooting Discussion #252 also covers conflicting background services as a general Discord symptom area.

Step-by-step diagnostic flow

  1. Confirm the symptom shape: Discord text works but voice hangs on RTC connecting, possibly with extreme ping, as in Issue #13149.
  2. Test voice in browser Discord. In the reported case it worked, which pointed away from zapret itself.
  3. Check whether AdGuard Desktop or another traffic-filtering app is installed, including ones you forgot about; the issue author had forgotten AdGuard was installed.
  4. As a test, fully exit AdGuard and retry a voice channel. The author reports voice recovered immediately.
  5. If the test confirms the conflict, either keep AdGuard filtering off for those apps or apply the exclusion steps from the issue: add winws.exe and Discord to the filtered applications list and uncheck them.
  6. Re-test with AdGuard running to confirm both tools now coexist.

What is source-backed vs community-reported

  • Guide-backed: the preflight checklist item to disable AdGuard Desktop filtering or exclude winws.exe and Discord.exe.
  • Community-reported: the entire Issue #13149 case, including the 5000 ms ping figure, the RTC connecting symptom and the unchecking workaround.
  • Community-reported: the additional Cloudflare WARP remark from the same issue.
  • Community context: Discussion #252 treats conflicting services as part of Discord troubleshooting, without naming AdGuard as a universal cause.

When the reported workaround may not apply

Not every AdGuard installation conflicts with zapret. The Issue #13149 author states the two tools worked together for a long time before the problem appeared on zapret 1.9.7b, and that newer zapret versions fixed it for other users. A conflict can be version-specific on either side.

RTC connecting has other documented causes, so an AdGuard exclusion is worth testing only when the symptom shape matches: desktop Discord voice broken while browser Discord voice works. If both are broken, the cause likely sits elsewhere.

Source notes

Every factual claim in this article is grounded in the sources below. Community reports are attributed and are not official recommendations. Last verified: 2026-09-30.