What the sources actually say
The klaymm practical guide puts antivirus on its preflight checklist: it asks users to add zapret to the exclusions of antivirus products, naming Kaspersky and Dr.Web as examples, before troubleshooting anything else.
The same guide dedicates a page to VirusTotal results. It explains that some antivirus engines flag WinDivert.dll and WinDivert64.sys, and that this is a false positive: WinDivert is a legitimate open-source packet capture driver that is also used by some malware, so certain engines mark it preventively. According to the guide, quoting the official Flowseal README, such detections are named WinDivert or Not-a-virus:RiskTool.Multi.WinDivert.
- Treated as expected by the guide: detections named WinDivert or Not-a-virus:RiskTool.Multi.WinDivert, touching only WinDivert.dll or WinDivert64.sys.
- Treated as suspicious by the guide: any other detection name, or detections touching .bat files, winws.exe or .txt files. In that case the guide says to download the build again from the official repository.
For resolutions the guide lists adding the C:\zapret folder to antivirus exclusions, a Windows Defender path through Windows Security, Virus and threat protection, Manage settings, Exclusions, and a Kaspersky setting about detecting legal applications that can be misused.
On the community side, the pinned Flowseal Discord troubleshooting Discussion #252 includes the hypothesis that antivirus software removes or blocks winws.exe, which is why the process can be missing. And Issue #16543 (opened 2026-08-06, still open, versions 1.10.0 and 1.9.9d) reports winws.exe absent from Task Manager and closing immediately when launched manually, with diagnostics closing WinDivert. Importantly, that reporter states Windows Defender found nothing and removed nothing, so antivirus was not confirmed as the cause in that case.
Step-by-step diagnostic flow
- Check whether winws.exe exists in the build folder and whether it appears in Task Manager after launch, the exact symptom in Issue #16543.
- Open your antivirus quarantine and protection history and look for entries touching WinDivert.dll, WinDivert64.sys or winws.exe.
- Compare any detection name against the guide: WinDivert or Not-a-virus:RiskTool.Multi.WinDivert on the driver files is described as a false positive; anything else means re-download the build.
- If the detections match the false-positive pattern, add the zapret folder to exclusions using the paths the guide lists for Windows Defender or Kaspersky, then extract a fresh copy of the build.
- Re-run the build and confirm winws.exe stays alive in Task Manager.
- If winws.exe still vanishes with no antivirus entries, as the Issue #16543 reporter describes, record your Windows edition and build version before looking for other causes.
What is source-backed vs community-reported
- Guide-backed: the antivirus exclusion checklist item naming Kaspersky and Dr.Web.
- Guide-backed: the WinDivert false-positive explanation, the two accepted detection names and the exclusion steps for Windows Defender and Kaspersky.
- Community-reported: the hypothesis in Discussion #252 that antivirus removes winws.exe.
- Community-reported: Issue #16543, where winws.exe disappeared while Windows Defender reportedly detected and removed nothing.
When the reported workaround may not apply
An exclusion only helps if antivirus is actually the cause. Issue #16543 shows a case with the classic symptom and, per the reporter, a clean Windows Defender, on Windows 10 IoT LTSC. Exclusions would not address whatever happened there.
Detection behavior changes with antivirus signature updates, and the guide warning cuts both ways: third-party zapret builds circulated in Telegram or YouTube have contained malicious code, so a detection that does not match the WinDivert pattern should be taken seriously rather than excluded.