What the sources actually say
Four issues in the Flowseal tracker describe screen-sharing failures, and their symptoms differ. Issue #7921 (opened 2025-12-27, zapret 1.9.1, general(ALT 6).bat, closed as stale): starting screen share showed a plain gray screen, and after a restart Discord produced a stream loading error. The only suggestion in the thread was from another user — change the voice channel region to Rotterdam — with no confirmation it resolved the case.
Issue #8511 (opened 2026-01-01, zapret 1.9.2, general alt11, reporter also tried alt6): screen sharing simply would not load. Here the maintainer, Flowseal, replied directly with a concrete suggestion: remove the --dpi-desync-fake-discord and --dpi-desync-fake-stun parameters (both pointing at the quic_initial_www_google_com.bin file) from the BAT in use and restart zapret. The thread does not record whether the reporter confirmed the fix.
Issue #8773 (opened 2026-01-07, zapret 1.9.2, general (ALT11), provider AVK-WELCOME near Moscow) is the most detailed: Discord opened, but watching someone's stream or sharing the reporter's own screen produced a black screen, while some other participants could see the stream. Changing voice regions — including automatic selection — did not help, and having participants reconnect the stream worked roughly once in 150–200 attempts. The reporter had tried nearly every bundled strategy. Two commenters offered workarounds: start the stream at 480p 15 FPS and raise quality after viewers join, or run service.bat diagnostics and accept the Discord cache reset. The reporter replied that neither helped in their case.
Issue #12495 (opened 2026-04-29, zapret 1.9.7b, closed) describes a one-way failure: the reporter could watch other people's streams, but nobody could see theirs. A commenter in Yekaterinburg on the dom.ru provider reported the identical pattern — no strategy helped, and sometimes viewers heard audio without video. A different commenter wrote that closing Radmin VPN in Task Manager made everything work immediately. Others, including a group in Novosibirsk, reported endless loading with no resolution in the thread.
Step-by-step diagnostic flow
Because the four issues share no single resolution, this flow orders the steps that actually appear in them, from least to most invasive:
- Identify your exact symptom first: gray screen, black screen in both directions, endless loading, or a one-way stream where you see others but they do not see you. The issues show these are not interchangeable.
- Run service.bat → Run Diagnostics and accept the Discord cache reset when offered — one commenter reported this fixed streaming for them, though the Issue #8773 reporter saw no change.
- Try other strategy BAT files; every reporter in these issues ended up testing multiple strategies.
- Change the voice channel region — suggested in Issue #7921 — and, for streams that connect but show nothing, try starting the stream at 480p 15 FPS and raising quality after viewers join, as one Issue #8773 commenter reported.
- On versions around 1.9.2, the maintainer's suggestion in Issue #8511 was to remove the --dpi-desync-fake-discord and --dpi-desync-fake-stun parameters from the BAT and restart zapret.
- Check for other network software running alongside zapret: in Issue #12495, one user's screen sharing recovered the moment Radmin VPN was closed in Task Manager.
What is source-backed vs community-reported
- Community-reported (Issue #7921): gray screen symptom on 1.9.1 / ALT6; region-change suggestion without confirmation.
- Community-reported with maintainer reply (Issue #8511): the fake-discord/fake-stun parameter removal suggested by Flowseal on 1.9.2.
- Community-reported (Issue #8773): black screen in both directions on 1.9.2 across all strategies; low-quality stream start and cache reset reported as working for some, not for the reporter.
- Current issue evidence (Issue #12495, opened 2026-04-29, closed): one-way streaming failure on 1.9.7b; Radmin VPN shutdown reported as an immediate fix by one commenter.
When the reported workaround may not apply
None of the four threads ends with a confirmed universal resolution, and within Issue #8773 the workarounds that helped commenters explicitly failed for the original reporter. The maintainer's parameter-removal suggestion in Issue #8511 was aimed at a specific 1.9.2-era BAT; applying it to a different version means editing a strategy you have not verified. The Radmin VPN observation is a single comment. Providers, zapret versions and strategies differ across all four reports, so treat each step as an experiment to test in order — not as a fix this article can promise.