What the sources actually say
The klaymm/zapret-guide README opens with a pre-start checklist and warns that skipping even one item can make the whole guide useless. The Flowseal issue tracker shows why: users regularly report BAT files that will not start, and the cause is often the environment rather than the package itself. This article converts that checklist into an ordered preflight you can run before testing any strategy.
Preflight checklist, step by step
- Browser: close Yandex Browser and similar Russian browsers; test with Chrome, Firefox, Edge or Brave. Per the klaymm guide, since October 2025 these browsers forcibly substitute their own DNS and block third-party DoH, so Zapret can be working perfectly while the browser test still fails.
- Other bypass tools: disable ByeDPI, GoodbyeDPI, Proxifier and similar software before testing, so only one traffic interception layer is active.
- AdGuard Desktop: disable its filtering, or add winws.exe and Discord.exe to its exceptions, per the same checklist.
- Antivirus: the checklist asks for the zapret folder to be added to exclusions in products like Kaspersky or Dr.Web. The Flowseal README explains why: the WinDivert driver is flagged by some antivirus engines, typically under names containing WinDivert or Not-a-virus:RiskTool.Multi.WinDivert.
- Killer Control Center: on PCs with a Killer network card, turn off the Bandwidth Control feature.
- Folder path: place the zapret folder at a simple path such as C:\zapret, without Cyrillic characters or spaces.
What real issues add to the checklist
Issue #7490 (December 2025, now closed) describes a user on a clean Windows install whose console window appeared and immediately vanished for every BAT file in a current release, while version 1.8.2 and below still launched. The report does not establish a single cause, but it shows that "nothing starts" can be version-specific rather than a packing mistake on your side.
Issue #7565 (December 2025, now closed) describes a different failure: double-clicking the .bat files produced an "open with" dialog offering Notepad, browsers and Word, meaning Windows did not treat the files as executable batch scripts at all. The issue body does not record a confirmed fix, so treat it as a symptom pattern: check that the archive was fully extracted and that the .bat file association on your system is intact before assuming the package is broken.
What is source-backed vs community-reported
- Source-backed (klaymm guide): the six checklist items above, including the browser DNS finding and the C:\zapret path recommendation.
- Source-backed (Flowseal README): the WinDivert explanation behind antivirus detections, and the suggestion to use a folder exclusion or adjust PUA detection rather than removing security software.
- Community-reported (Issues #7490 and #7565): the BAT startup failure symptoms. These are single user reports with no confirmed universal fix; they illustrate what to check, not what to change everywhere.
When the reported workaround may not apply
The checklist removes common interference, but it cannot fix a fundamentally blocked network or a broken download. If every item is done and BAT files still misbehave, the issues above suggest comparing with an older or newer release and re-extracting a fresh archive from the official releases page. And per the official documentation, no amount of local preparation helps where blocking is done by IP or DNS answers are falsified without protection; the checklist prepares your system, it does not change your ISP.