What the sources actually say
Two practical sources cover the Windows path. The Flowseal/zapret-discord-youtube repository README documents the current usage flow for its Windows build, and the klaymm/zapret-guide README adds a preflight checklist plus a strong warning about fake builds. Neither source promises that a given strategy will work on your network; the Flowseal README explicitly says strategy effectiveness depends on many factors and advises trying different strategies until you find one that works for you.
Quick start, step by step
- Enable Secure DNS first. The Flowseal README makes this step one: in Chrome turn on "Use secure DNS" with a chosen provider; in Firefox enable DNS over HTTPS with a custom provider URL; on Windows 11 it can be enabled in OS settings.
- Download the archive (zip/rar) from the releases page of Flowseal/zapret-discord-youtube. Do not use mirrors, Telegram channels or repacks.
- Open the downloaded archive properties and tick "Unblock" if the checkbox is present. The README notes this step can be skipped if you extract with 7-Zip or PeaZip.
- Extract the contents to a path without Cyrillic or special characters. The klaymm checklist recommends a simple path such as C:\zapret without spaces.
- Find a working strategy: run service.bat and use Run Tests, then Standard tests, then All configs, as documented in the Flowseal README. Alternatively, launch general BAT files one by one to test strategies manually; when a strategy is running, winws.exe should appear in the system tray.
- Verify operation by opening the services you need in a supported test browser, then put the working strategy on autostart via service.bat and Install Service.
Preparing the system before testing
The klaymm guide's preflight checklist exists because other software can make a working setup look broken. Before judging any strategy, it asks you to close Yandex Browser and test in Chrome, Firefox, Edge or Brave, and to disable other bypass tools such as ByeDPI, GoodbyeDPI or Proxifier so they do not interfere. The guide attributes the browser finding to community reports: since October 2025, Russian browsers forcibly substitute their own DNS, so tests in them show a negative result even when Zapret works perfectly.
What is source-backed vs community-reported
- Source-backed (Flowseal README): the Secure DNS step, the releases-page download, the archive Unblock flag, the no-Cyrillic extraction path, and the service.bat Run Tests and Install Service flow.
- Source-backed (klaymm guide): the warning against third-party builds, the browser recommendations, and the advice to disable other bypass tools during testing.
- Community-reported: which general/ALT/FAKE strategy works on a given ISP comes from user reports and changes over time; the README itself frames strategy choice as trial and error.
When the reported workaround may not apply
The Flowseal README warns that strategies can stop working over time as they get detected, so a quick start that worked last month may need a different strategy today. It also lists a network-reset sequence (netsh winsock reset, netsh int ip reset all, netsh winhttp reset proxy, ipconfig /flushdns, then reboot) for cases where no strategy fits at all. If every strategy fails even after that, the cause may be outside Zapret's scope, for example IP-based blocking that no desync strategy can bypass.