What the sources actually say
The Flowseal build ships a service.bat script whose status check prints three independent lines. Issue #13320 (opened 2026-05-11, version 1.9.8c, closed as stale) quotes the output verbatim:
"zapret" service is NOT running.
"WinDivert" service is RUNNING.
Bypass (winws.exe) is RUNNING.Those three lines answer three different questions. The first is whether the Windows service named zapret is running. The second is whether the WinDivert driver service, which winws.exe uses to intercept packets, is up. The third is whether the bypass process itself, winws.exe, is alive. A service installed but not running only concerns the first line.
The same issue shows why the distinction matters: with the zapret service NOT running but winws.exe RUNNING, the reporter still had working YouTube and working Discord text chats. Only Discord voice channels failed. In other words, winws.exe was running outside the service, most plausibly from a manual BAT launch, and the bypass was partly doing its job.
Issue #10636 (opened 2026-02-24, version 1.9.7, closed) shows the mirror-image case. Its title is the diagnostic message "[ERROR] Windows service zapret is installed": the tests flagged the installed state of the service after a reboot, while the reporter said Discord still did not work. The build diagnostics treat service installation as its own checkable fact, separate from whether anything is actually running.
Step-by-step diagnostic flow
- Run the service.bat status check and copy all three lines before changing anything, as the Issue #13320 reporter did.
- Read the winws.exe line first. If Bypass (winws.exe) is RUNNING, the bypass core is alive; a NOT running zapret service then means the service wrapper failed, not the whole tool.
- Read the WinDivert line. winws.exe depends on this driver, so a stopped WinDivert with a stopped winws.exe points lower than the zapret service itself.
- If the service is installed but not running, try starting it and, if that fails, remove and reinstall it through service.bat. The Issue #13320 reporter reinstalled per instructions; in that case it did not resolve the symptom.
- If diagnostics report the service as installed while apps still fail, as in Issue #10636, note the exact error text, reboot state and build version before experimenting further.
- Match the symptom to the layer: one failing application with a running winws.exe suggests a strategy or app-specific problem rather than a service problem.
What is source-backed vs community-reported
- Community-reported: the verbatim three-line status output in Issue #13320.
- Community-reported: the "[ERROR] Windows service zapret is installed" message in the title of Issue #10636.
- Community-reported: the observation that YouTube and Discord text worked while the zapret service was not running.
- Interpretation, clearly marked as such: reading the three lines as service, driver and process is an inference from the output text, not a quote from official documentation.
When the reported workaround may not apply
A status snapshot from May 2026 on version 1.9.8c describes one machine. The build, its service.bat script and the status wording can change between releases, so treat the exact line text as version-specific.
A service that is installed but not running is a symptom, not a diagnosis. The same three lines can follow from very different causes, and neither cited issue ended with a confirmed root cause. Do not assume that fixing the service line will fix a specific app such as Discord voice.