Do not disable the Windows firewall as a general playback fix. A prompt should be evaluated for the specific application and network context. Ordinary outbound viewing and features that accept local connections are different behaviours, so use the publisher’s documented requirements.
Read which application is named
An unexpected executable or unfamiliar publisher should not receive access just because you recently installed a player. Confirm that the prompt belongs to the intended package. Keep the file source and installed version available when asking the publisher about it.
Distinguish public and private networks
Network classifications affect which rules apply. A trusted home environment is different from a public hotspot. Do not broadly permit inbound access on every network when the app only needs a narrower documented feature, such as local discovery.
Troubleshoot the actual symptom
If the library loads and streams begin, a blanket firewall change is unlikely to be the first useful step. Report whether the issue concerns login, playback or local-device discovery. Revert temporary diagnostic changes that do not address the problem. If a temporary rule was added for a test, document it and remove it when it proves unrelated.
