What the sources actually say
Flowseal issue reports show that a zapret service problem on Windows is not one single failure. The service entry, the WinDivert driver and the winws.exe bypass process are three separate things, and the build diagnostics report them separately.
Issue #13320 (opened 2026-05-11, version 1.9.8c, now closed as stale) is the clearest example. The reporter ran the service check and saw the zapret service not running while everything else was alive:
"zapret" service is NOT running.
"WinDivert" service is RUNNING.
Bypass (winws.exe) is RUNNING.In that same report YouTube worked normally and Discord text chats worked; only Discord voice channels failed. The reporter had reinstalled strictly following the instructions and removed the service through service.bat, without change. This is the key separation: the bypass process can run and partly work while the Windows service itself is not running.
Issue #11452 (opened 2026-03-23, version 1.9.7b, Windows 11, closed as stale) shows a different service-level failure. The user could not open the properties of the zapret service in the Windows services console and got the error "The stub received bad data". Notably, the reporter states zapret itself worked fine; the goal was only to configure automatic start. The same reporter used Kaspersky with zapret added to exclusions.
Issue #10636 (opened 2026-02-24, version 1.9.7, closed) carries the title "[ERROR] Windows service zapret is installed". The reporter says Discord did not work, and after a computer restart the tests began showing that error. Discord remained broken.
Service behavior also appears repeatedly in Flowseal Discussion #251, a long community troubleshooting thread that includes reports about how the service mode behaves compared with manual BAT launches.
Step-by-step diagnostic flow
Based on the checks the issue reporters actually ran, a reasonable order is:
- Run the status check from service.bat in the Flowseal build and write down all three lines: the zapret service, the WinDivert service and the winws.exe bypass process.
- If winws.exe shows RUNNING, the bypass itself is active. Treat the problem as service-level or app-specific, not as a total zapret failure.
- If the zapret service shows NOT running, remove and reinstall the service through service.bat, as the Issue #13320 reporter describes doing.
- Open the Windows services console and inspect the zapret entry. Issue #11452 shows the properties dialog itself can fail with "The stub received bad data" on Windows 11 while zapret still works, so a broken dialog alone does not prove the bypass is broken.
- If diagnostics show an error such as "[ERROR] Windows service zapret is installed" after a reboot, record the exact message and your build version before changing anything (Issue #10636).
- If only one application fails while the process runs, suspect the strategy or that application rather than the service; in Issue #13320 only Discord voice failed.
What is source-backed vs community-reported
- Community-reported: the exact three-line check-status output in Issue #13320 and the fact that winws.exe ran while the zapret service did not.
- Community-reported: the "The stub received bad data" properties error on Windows 11 in Issue #11452, with zapret otherwise working.
- Community-reported: the post-reboot "[ERROR] Windows service zapret is installed" message in Issue #10636.
- Community-reported: service behavior remarks in Discussion #251.
- Source-backed in a limited sense: the issue template confirms reporters downloaded builds from the official Flowseal releases page, so the reports concern the official build.
When the reported workaround may not apply
These reports span versions 1.9.7 through 1.9.8c, and none of them documents a confirmed universal fix. The Issue #13320 reporter reinstalled exactly per instructions and the service still did not run, so reinstalling is a diagnostic step, not a guaranteed cure.
Service behavior can differ between Windows builds, antivirus setups and zapret versions. A symptom that matched one reporter in early 2026 may have a different cause on your machine, and none of these issues proves that the service failing means the bypass cannot work at all.