What the sources actually say
This is one of the most precisely described symptoms in the Flowseal community. Issue #15626 (opened 2026-06-30, closed as stale on 2026-09-09) reports: on zapret-discord-youtube 1.9.9c under Windows with the Opera browser, YouTube opens, comments load, but the video itself never starts playing — endless loading — while Discord works at the same time. The reporter removed the previous version, installed the ALT11 strategy, rebooted, has no antivirus, and tried cycling strategies through Run Tests; none of it helped.
Discussion #251, the maintainer-hosted YouTube troubleshooting thread, contains matching reports in which page content loads while playback fails. That pattern matters diagnostically: if the page, comments and even Discord all work, Zapret is running and at least some strategies are being applied — the failure is specific to the path that delivers the actual video stream, which YouTube serves separately from its pages.
One more detail from the issue is worth holding onto: the reporter had already removed the old version, reinstalled, switched strategies and rebooted. That means the usual first-line advice — reinstall, restart, change strategy — was exhausted before the report was even filed, which is exactly why this symptom deserves its own isolation procedure rather than generic reinstall tips.
Step-by-step diagnostic flow
- Confirm the exact symptom: the watch page renders, comments appear, but the player shows a loading spinner or black screen indefinitely.
- Check whether other targets work. In Issue #15626 Discord worked fine, which rules out a completely dead installation and points at a YouTube-playback-specific layer.
- Verify the basics anyway: winws.exe present in Task Manager and a sane service check-status output, so you are not debugging a stopped process.
- Test the same video in a second browser. Discussion #251 documents behavior differences between Firefox and Chromium-based browsers, so a browser-specific failure tells a different story than a universal one.
- Check ad blockers and content-filtering extensions. In Discussion #251 the maintainer attributes certain playback symptoms to ad-blocking interference and recommends testing with blockers disabled.
- Try the alternative strategies shipped with the build. Keep expectations realistic: the Issue #15626 reporter already cycled strategies through Run Tests without success, so record what you tried rather than assuming this step resolves it.
- If nothing helps, report the issue with your build version, browser, ISP and the exact symptom — that is the information both cited sources show maintainers asking for.
What is source-backed vs community-reported
- Source-backed (Issue #15626, dated 2026-06-30, version 1.9.9c): the documented symptom combination — page and comments load, playback never starts, Discord unaffected — plus the steps the reporter already tried.
- Source-backed (Discussion #251): the maintainer-level recommendation to test without ad blockers for playback symptoms.
- Community-reported: thread participants describing their own playback-only failures and the strategies that happened to help them individually.
- Not established: a proven universal cause. Neither cited source closes the question with a confirmed fix.
When the reported workaround may not apply
Issue #15626 concerns version 1.9.9c and Opera, and it was closed as stale with no confirmed resolution — copying its context only helps if your setup is comparable. Strategy changes that helped individual commenters in Discussion #251 are tied to their ISP and point in time, and blocking methods change. If your page does not load at all, or videos stop at a specific timestamp instead of never starting, those are different symptoms covered by separate articles, and the steps here may not transfer.