zapret-discord-youtube from GitHub: download, install and fix common errors
A step-by-step guide to zapret for Discord and YouTube on Windows — where to download it on GitHub, how to run it, what to do if it doesn't work or your antivirus complains, and when a VPN is the better choice.
zapret is a free open-source tool that bypasses ISP-level blocking by altering the first packets of a connection so the filter doesn't recognise them — no server abroad involved. Ready-made Windows builds tuned for Discord and YouTube are published on GitHub. The principle and comparison with a VPN: zapret or a VPN.
Download safely: only from the project's GitHub page, Releases section. Not from file hosts, Telegram channels or "free download" sites.
Install on Windows:
1. Download the latest release archive.
2. Unpack to a path without Cyrillic letters or spaces, e.g. C:\zapret.
3. Run a strategy file as administrator.
4. Check Discord and YouTube.
5. If they don't work, try another strategy — each ISP blocks differently.
6. Use the included service installer to start it automatically with Windows.
Antivirus alerts: they're triggered by the low-level packet-capture driver — a false positive for official GitHub archives, no guarantees for anything else.
If it doesn't help: try every strategy, update the build, disable other VPNs/proxies, check the antivirus didn't block the driver. It can't bypass mobile whitelists.
Limits: desktop only, admin rights, breaks after ISP changes, no help with services that block Russian IPs (ChatGPT), no encryption. For phones and zero maintenance use a VPN — Surok is on the download page.
Common errors
- "The path where zapret is installed contains cyrillic characters" — the folder path has non-Latin letters or spaces (e.g. a Russian user name). Move the folder to the drive root,
C:\zapret, and run it from there. - The window opens and closes at once — run the file as administrator.
- Antivirus removed files — restore them from quarantine, add the folder to exclusions and unpack the archive again.
- Nothing changed — the ISP updated its filters; try other launch options in the build and update to the latest release.
