What the sources actually say

The klaymm practical guide opens with a preflight checklist it says must be completed in order before anything else: use a suitable test browser, disable other bypass tools, handle AdGuard Desktop filtering, add antivirus exclusions, disable Killer bandwidth features, and place the folder at C:\zapret without Cyrillic or spaces.

The guide also warns that, since October 2025, Russian browsers such as Yandex.Browser forcibly substitute their own DNS servers (77.88.8.8) and block third-party DNS-over-HTTPS, crediting the discovery to community members in Issue #6083. In such a browser, tests fail even when zapret itself works perfectly; the guide recommends testing with Firefox, Brave, Chrome or Edge.

The build includes its own status check through service.bat. Issue #13320 (2026-05-11, closed, marked stale; version 1.9.8c) quotes real output:

"zapret" service is NOT running.
"WinDivert" service is RUNNING.
Bypass (winws.exe) is RUNNING.

In that same issue, YouTube worked normally and Discord text chats loaded, but voice channels failed. Issue #16543 (2026-08-06, open; builds 1.10.0 and 1.9.9d) adds another data point: winws.exe was absent from Task Manager, and the reporter observed that running the built-in diagnostic closes the WinDivert driver, so status should be re-checked after running diagnostics.

The three status lines are observable facts on your machine. What they mean for a specific failure, such as Discord voice, is interpretation; keep the two separate when comparing your case with issue reports.

Step-by-step diagnostic flow

  1. Browser check: close Yandex.Browser and similar RU browsers; run all tests in Firefox, Brave, Chrome or Edge (guide warning, tied to Issue #6083).
  2. Disable other bypass tools such as ByeDPI, GoodbyeDPI and Proxifier so only one traffic filter is active.
  3. AdGuard Desktop: turn filtering off during setup, or add winws.exe and Discord.exe to its network exclusions; the guide notes the browser extension does not conflict.
  4. Antivirus: confirm the zapret folder is in the exclusion list and check quarantine for removed files, since some products delete WinDivert from the bin folder.
  5. Killer Control Center: on systems with Intel Killer network adapters, disable Bandwidth Control and Advanced Stream Detect.
  6. Folder path: confirm the build sits at a short path such as C:\zapret with no Cyrillic characters or spaces.
  7. Run service.bat and use check status; record the three states: zapret service, WinDivert service and the winws.exe bypass process.
  8. Open Task Manager and confirm winws.exe is actually present, then re-check after any built-in diagnostic run.
  9. If everything reports running but a target still fails, use the built-in tests (service.bat, Run tests, HTTP/HTTPS check) to compare strategies, as the guide describes.

What is source-backed vs community-reported

  • Observable checks (your machine): the three check-status lines, winws.exe presence in Task Manager, whether the target loads in a recommended browser.
  • Source-backed (practical guide): the six preflight items, the browser DNS-substitution warning with its October 2025 date, and the built-in strategy testing flow.
  • Current issue evidence: the quoted check-status output with working YouTube and broken Discord voice (Issue #13320, 2026-05-11, version 1.9.8c).
  • Current issue evidence: missing winws.exe and the diagnostic closing WinDivert (Issue #16543, 2026-08-06, open).
  • Community interpretation: reading service NOT running but winws RUNNING as the cause of a Discord voice failure is the reporter interpretation, not a proven causal chain.

When the reported workaround may not apply

The checklist targets the Flowseal Windows build described by the guide, and menu names or behaviors can change across releases. Both cited issues are version- and date-specific: 1.9.8c in May 2026 and 1.10.0/1.9.9d in August 2026, so re-check details against your own build.

A fully green checklist does not guarantee a working bypass for every ISP, region or target service. Issue #13320 shows the opposite: winws.exe was running and YouTube worked while Discord voice still failed. Strategy choice is environment-specific, and status checks tell you the tool is running, not that it will work everywhere.