What the sources actually say

There is no single "Zapret not working" failure. Recent reports on the Flowseal zapret-discord-youtube issue tracker show completely different layers breaking. In Issue #15626 (opened 2026-06-30, later closed as stale), YouTube pages and comments loaded but videos would not play on version 1.9.9c, while Discord kept working. In Issue #13320 (opened 2026-05-11, closed as stale), the service check showed the "zapret" service NOT running while WinDivert and the winws.exe bypass were both running — YouTube worked, but Discord voice channels did not. In the still-open Issue #16543 (opened 2026-08-06), winws.exe disappeared from Task Manager entirely on Windows 10 IoT LTSC with versions 1.10.0 and 1.9.9d.

The klaymm community guide adds a preflight checklist that explains many apparent failures before Zapret itself is even involved: test in Chrome, Firefox or Edge rather than Yandex.Browser; disable other bypass tools such as ByeDPI, GoodbyeDPI and Proxifier; check AdGuard Desktop filtering; add antivirus exclusions for zapret; turn off Killer Control Center bandwidth control on Killer NICs; and keep the folder at a simple path like C:\zapret without Cyrillic characters or spaces.

The same guide warns that third-party "Zapret builds" circulated via Telegram or YouTube have contained malicious code, and recommends downloading only from the official Flowseal repository releases. An untrusted package is itself a possible cause of "not working".

Step-by-step diagnostic flow

Work through the layers in order. Stop at the first layer that fails — that is where your problem lives.

  1. Package and build: confirm you downloaded zapret-discord-youtube from the official Flowseal releases and that the extracted folder is intact, at a simple path without Cyrillic or spaces.
  2. Process: open Task Manager and check whether winws.exe is running. Issue #16543 describes a case where it was missing entirely or closed immediately after a manual start.
  3. Service: run the service check-status option from the build. Interpret the output carefully — Issue #13320 shows the zapret service can report NOT running while WinDivert and the winws.exe bypass are running, with partial functionality.
  4. Browser: retest in Firefox, Chrome or Edge. The klaymm guide notes that, starting around October 2025, Russian browsers such as Yandex.Browser force their own DNS and block third-party DoH, so tests in them can fail even when Zapret works.
  5. DNS: if the browser substitutes its own DNS resolver, a working Zapret can look broken. Test with a browser whose DNS behavior you control before changing strategies.
  6. Strategy: try the alternative strategy presets shipped with the build. Note that the reporter in Issue #15626 already tried cycling strategies via Run Tests without success, so this step is not a guaranteed fix.
  7. Antivirus and security software: check whether winws.exe is being removed or blocked. Treat this as a hypothesis — the Issue #16543 reporter stated Windows Defender found and removed nothing, yet the process still died.
  8. Target-specific behavior: if one service works and another fails (Discord works, YouTube playback does not, as in Issue #15626), the tool is running and the cause is likely strategy- or hostlist-related rather than a dead installation.

What is source-backed vs community-reported

  • Source-backed (klaymm practical guide): the preflight checklist items — browser choice, disabling other bypass tools, AdGuard and antivirus exclusions, Killer Control Center, and the C:\zapret folder recommendation.
  • Source-backed (klaymm practical guide): the warning against third-party builds and the pointer to official Flowseal releases.
  • Community-reported (Flowseal issues): every specific symptom above — the 1.9.9c YouTube playback failure, the 1.9.8c service-status combination, and the winws.exe disappearance on Windows 10 IoT LTSC.
  • Community-reported: individual outcomes such as "Run Tests did not help" are single-user reports, not general rules.

When the reported workaround may not apply

Every issue cited here is tied to a specific build version, Windows edition, ISP and browser. Two of the three issues were closed automatically as stale, which means no confirmed resolution is attached to them. A strategy or exclusion that helped one reporter may do nothing on a different network, and Zapret does not guarantee access for every ISP, browser or region.

Because blocking methods and builds change over time, recheck the current Flowseal issue index before assuming an old workaround still applies. If your symptom matches an open issue, following that thread is usually more reliable than copying a closed one.