← Back to Blog

Fix Stremio Starting in Background With No Window

August 5, 2026

If Stremio remains in Task Manager but never displays a usable window, fully close it and check whether Windows has excluded local TCP ports 11470–11474. If that range is excluded, address the software or Windows configuration responsible for the reservation rather than deleting unknown exclusions blindly, then restart Stremio.

This specific failure was reported with Stremio 5.0.24 on Windows 11. The report does not establish that every background-only startup has the same cause, so confirm the port errors before making system changes.

Why Stremio can start without showing its window

The affected Stremio installation launched stremio-shell-ng.exe and stremio-runtime.exe, placed an icon in the system tray, but did not render a responsive application window. Its startup log showed repeated errors for ports 11470 through 11474:

Error: listen EACCES: permission denied 0.0.0.0:11470
Error: listen EACCES: permission denied 0.0.0.0:11471
Error: listen EACCES: permission denied 0.0.0.0:11472
Error: listen EACCES: permission denied 0.0.0.0:11473
Error: listen EACCES: permission denied 0.0.0.0:11474

Windows listed all five ports in an excluded TCP port range. An excluded port is reserved at the operating-system level, so an application can receive an EACCES permission error even when no other process is actively listening on that port.

In the reported case, Stremio's local server kept trying ports within the same unavailable range. Because the local service did not start successfully, the WebView-based interface never became usable.

1. End the incomplete Stremio startup

Before diagnosing the problem, stop the processes left behind by the failed launch:

  1. Press Ctrl+Shift+Esc to open Task Manager.
  2. Find stremio-shell-ng.exe, stremio-runtime.exe, or any entry named Stremio.
  3. Select each remaining Stremio process and choose End task.
  4. Confirm that the Stremio tray icon has disappeared.

Do this before every new test. Otherwise, an earlier incomplete instance can make the results confusing.

2. Check whether Windows excludes the reported ports

Open Windows Terminal or Command Prompt as administrator, then run this read-only command:

netsh interface ipv4 show excludedportrange protocol=tcp

Look for a range that includes any or all of these ports:

  • 11470
  • 11471
  • 11472
  • 11473
  • 11474

The displayed range does not have to begin at 11470. For example, a larger excluded range could contain all five ports.

Result Meaning Next action
11470–11474 fall inside an excluded range The report's failure mechanism is plausible Continue with the reservation steps below
None of the ports are excluded This is probably a different startup problem Check the Stremio log and update or report the issue
The log does not contain EACCES errors Port exclusion is not confirmed Avoid changing Windows port reservations

Also inspect the startup log available from the failed launch. The strongest match is both an excluded range covering these ports and repeated listen EACCES messages for the same ports.

3. Restart Windows and check again

A full Windows restart is a low-risk first attempt. After restarting:

  1. Run the netsh command again.
  2. See whether the excluded range is still present.
  3. Launch Stremio once.

Restarting Stremio alone did not resolve the original report. A Windows restart may help only if the reservation was temporary; persistent exclusions require identifying what created or requires them.

4. Resolve the excluded range safely

Do not immediately use commands that delete an excluded port range. Windows or installed networking software may depend on that reservation, and it may return after a restart.

Instead, review whether the exclusion appeared after a change involving networking, virtualization, containers, VPN software, or device-management configuration. These are possible sources of port reservations, not a confirmed cause in the reported case. Update, reconfigure, or temporarily disable the responsible component only if you can identify it safely.

On a work or school computer, contact the administrator and provide:

  • The output of netsh interface ipv4 show excludedportrange protocol=tcp
  • The Stremio EACCES log lines
  • The affected range, 11470–11474
  • Your Stremio and Windows versions

After the reservation is corrected, restart Windows, verify that the ports are no longer excluded, and launch Stremio again.

5. Check for a newer Stremio build

The GitHub report concerns Stremio 5.0.24. Check the official Stremio application or download source for a newer Windows release, but do not assume that a later build fixes this issue unless its release information says so.

An update may contain improved startup handling or port selection. Reinstalling the same version is less likely to help when Windows still excludes the required ports because reinstalling does not normally explain or remove an operating-system port reservation.

What worked for affected users

The GitHub reporter stated that changing Stremio's local HTTP server range from 11470–11474 to 12460–12464 allowed the application window and WebView to load normally. This is a user-reported workaround from one environment, not a universally verified or documented fix.

The report does not provide a supported, version-independent procedure for changing those ports. Configuration files and internal launch behavior can change between builds, and another port range might also be reserved on a different computer. For those reasons:

  • Prefer resolving the conflicting reservation or installing an officially corrected build.
  • Do not copy an undocumented configuration change without backing up the original file or value.
  • Verify any replacement range against Windows' excluded-port list first.
  • Expect an application update or reinstall to overwrite unsupported internal changes.

If you cannot safely identify the reservation and no official update is available, report the diagnostic details rather than experimenting with Windows' reserved ranges.

What probably will not fix this exact error

  • Disabling Windows Firewall: An excluded TCP range is not the same as a firewall block. Do not turn off firewall protection solely for this symptom.
  • Running Stremio as administrator: Elevation is not established as a way to bypass an excluded port range.
  • Changing community addons: This failure occurs while Stremio's local service and interface are starting, before playback. Community addons are independently operated and are not implicated by the reported EACCES errors.
  • Repeatedly clicking the tray icon: The report says both the window and tray controls were unusable during the failed startup.

If the ports are not excluded

If Windows does not exclude 11470–11474, treat the background process and missing window as a separate issue. End all Stremio processes, restart Windows, check for an application update, and collect the startup log. When requesting support, include the exact errors rather than assuming that the port-range report applies.

Useful diagnostic details include the Stremio version, Windows edition and build, whether the tray icon appears, the names of running Stremio processes, and the complete startup error around the first failure.

Last reviewed: August 5, 2026

Sources and further reading