What the sources actually say

The documented case is Flowseal issue #1826, opened on 2025-03-24 and titled "With Zapret running, Radmin VPN started working poorly". The reporter wrote that starting from that date, while using the general(ALT3).bat strategy, Radmin VPN behaved unstably: it hung on "Connecting..." for a long time, then could drop the connection on its own, forcing another wait. At the moment of the drop, the Radmin VPN log showed the line "Disconnected from server(code:9)".

The same reporter added an important detail: they had previously used general(ALT1).bat with no Radmin problems, but on that day Discord stopped working with ALT1 and only worked with ALT3 — which is when the Radmin VPN instability appeared. In other words, the strategy that restored Discord coincided with the VPN problem in this one case.

In the comments, another user confirmed that Radmin VPN did not work until zapret was disabled, and later added that it had started working again without them understanding why. A separate comment from December 2025 describes a similar picture with the ALT6 strategy: Radmin reported that its own service was not running and would not enable, and after a PC reboot Radmin stayed in a failed state even before zapret was started. A comment from June 2026 states that ALT12 did not work for them while ALT6 did.

Issue #1826 was closed automatically as stale. Neither the issue body nor its comments contain a confirmed general fix — only individual observations tied to specific strategies, dates and setups.

Step-by-step diagnostic flow

The issue itself does not prescribe a procedure, but the observations in it suggest a reasonable order for narrowing down your own case:

  1. Stop zapret completely — remove the installed service through service.bat and make sure winws.exe is not running — then check whether Radmin VPN connects normally. This separates "zapret is running" from everything else.
  2. If Radmin works only while zapret is stopped, note exactly which BAT strategy you were using. In the issue, behavior differed between ALT1, ALT3, ALT6 and ALT12 for different reporters.
  3. Restart the PC and check Radmin before starting zapret. One commenter reported Radmin already failing at that point, which points away from zapret as the direct cause in their case.
  4. Check the Radmin VPN log at the moment of a disconnect. The original reporter saw "Disconnected from server(code:9)"; having your own log line makes any upstream report far more useful.
  5. If you change strategies, retest both Discord and Radmin after each change, because in the reported case the two moved in opposite directions.

If you can reproduce the conflict reliably, the most productive step is to report it in the Flowseal repository with your strategy name, zapret version and the Radmin log excerpt, since the existing issue closed without a diagnosis.

What is source-backed vs community-reported

  • Community-reported (issue body): Radmin VPN instability with general(ALT3).bat starting 2025-03-24, including the "Disconnected from server(code:9)" log line, and the ALT1/ALT3 trade-off with Discord.
  • Community-reported (comments): Radmin failing until zapret is disabled; a later spontaneous recovery; Radmin failing even before zapret starts after reboot; ALT6 working where ALT12 did not.
  • Source-backed by official documentation: nothing in this article. The official zapret documentation does not address Radmin VPN, and the issue offers no maintainer diagnosis.

When the reported workaround may not apply

Every observation here comes from a single user on a single ISP, zapret version and strategy at a particular date. One commenter explicitly said the problem disappeared without them changing anything, which means the cause may sit outside zapret entirely — for example in Radmin VPN servers or ISP behavior that day. Switching strategies helped one commenter and did nothing for the original reporter, so "use ALT6" or any similar tip from the thread should be treated as an individual data point, not a fix.

Do not assume a zapret strategy change is safe to chase blindly: in the reported case, the strategy that fixed Discord was the one that coincided with Radmin VPN breaking.

Source notes

Every factual claim in this article is grounded in the sources below. Community reports are attributed and are not official recommendations. Last verified: 2026-09-30.