What the sources actually say
winws.exe is the actual bypass process of the Flowseal Windows build: strategy BAT files and the zapret service both ultimately start it. When winws.exe is absent from Task Manager, no filtering is happening, regardless of what menus or windows appeared during setup.
Issue #16543 (opened 2026-08-06, still open at verification time; builds 1.10.0 and 1.9.9d on Windows 10 IoT LTSC) describes exactly this: after some time everything stops working, and winws.exe is missing from Task Manager. The reporter says the built-in diagnostic closes WinDivert, reinstalling the config does not help, a reboot does not bring winws.exe back, and launching a config manually closes winws.exe immediately. Notably, the reporter states Windows Defender found and removed nothing, and that a manual launch occasionally does work.
Issue #10015 (2026-02-08, closed; version 1.9.5) is a related pattern: after opening the service file, a command line window opens and closes, and then nothing happens. Repeated reinstalls and older versions did not help. The reporter also mentions a Windows prompt asking whether to allow the file to interact with the PC.
Where does the antivirus hypothesis come from? The pinned Discord troubleshooting Discussion #252 is cited in the community as raising the idea that security software removes or blocks zapret components. Independently, the klaymm practical guide states that antivirus products often flag WinDivert as a threat and delete it from the bin folder, and recommends adding the zapret folder to exclusions before installation. Treat this as a plausible, documented failure mode, not a proven cause for every case.
Step-by-step diagnostic flow
- Open Task Manager and check whether winws.exe is present while your BAT or service should be active.
- Run service.bat and use the check-status option; note which of the three lines (zapret service, WinDivert service, winws.exe bypass process) report as running.
- Launch a strategy BAT manually and watch what happens: does winws.exe start and stay, or close immediately, as reported in Issue #16543?
- Open your antivirus quarantine and protection history and look for entries mentioning winws.exe or WinDivert.
- Check the bin folder inside your zapret directory; if executable or driver files are missing, re-extract a fresh copy of the official release into a clean folder.
- Reboot and re-check, because one reporter saw the process missing again after a restart even after a seeming success.
What is source-backed vs community-reported
- Source-backed (practical guide): antivirus software may flag WinDivert and remove files from the bin folder; exclusions are recommended before installation.
- Current issue evidence: winws.exe disappearing from Task Manager and closing instantly on manual launch (Issue #16543, 2026-08-06, open, builds 1.10.0/1.9.9d).
- Current issue evidence: console window opens and closes with no result on version 1.9.5 (Issue #10015, 2026-02-08, closed).
- Community hypothesis: antivirus or security software as the reason winws.exe disappears (Discussion #252), not confirmed in every reported case.
When the reported workaround may not apply
Adding an antivirus exclusion helps only when the antivirus actually removed or blocked something. Where Defender found nothing, as in Issue #16543, other factors come into play: the reporter used a less common Windows edition (10 IoT LTSC), and the builds involved (1.10.0, 1.9.9d) may have their own regressions.
Reinstalling or trying older versions is a frequently repeated community step, but in both cited issues it did not solve the problem by itself. A version that works on one machine is version- and system-specific evidence, not a universal recommendation, and no single issue proves one root cause for all winws.exe failures.