When SysDVR-Client opens and your console never appears in the list, the stream itself is usually fine — the client and the console simply are not discovering each other. Discovery in TCP Bridge mode works by the console advertising itself over your local network with a UDP broadcast, and several common things can block that broadcast or make the two sides refuse to talk.
The most likely cause is a version mismatch between the SysDVR sysmodule on the console and SysDVR-Client on your PC — the two must be exactly the same version or the connection fails. Close behind are a firewall blocking the client, a no_adv file silently disabling discovery, and routers that isolate devices from each other. Work through the fixes below in order; most people are streaming again within the first three.
Before you start: the 60-second checklist
- The console is powered on, connected to the same network as the PC, and a game is running (SysDVR only streams gameplay).
- You rebooted the console after installing or updating SysDVR — sysmodules only load at boot.
- SysDVR-Client was allowed through Windows Firewall when it asked (this matters for network discovery).
- No VPN is active on the PC — VPNs routinely swallow local broadcast traffic.
Fix 1: Reboot the console after any install or update
Sysmodules are loaded when Atmosphère boots, not when you copy files to the SD card. If you installed or updated SysDVR and never restarted, the old version (or nothing) is what is actually running, and the client will not pair with it. Reboot the console, wait about 20 seconds for the sysmodule to start, then relaunch the client.
Fix 2: Make the console and client versions match
Open the SysDVR Settings app on the console to see the sysmodule version, and compare it with the client release on your PC. If they differ, update both sides from the same release — grab the current version from our download page and follow the steps in how to update SysDVR. Remember to reboot the console after replacing the files.
Fix 3: Confirm both devices are really on the same network
Auto-discovery only works on the same local network segment. Check the console’s IP address in its internet settings and make sure the PC is on the same router and the same network — not a guest Wi-Fi network, which typically blocks device-to-device traffic. Public hotspots and some routers enable AP/client isolation, which makes discovery impossible no matter what you change on either device; if you suspect isolation, test on a different network or use manual IP entry (Fix 5).
Fix 4: Let the client through the firewall and drop the VPN
On Windows, the firewall prompt when you first launch SysDVR-Client is not a formality — denying it can block the discovery broadcast. Allow the client on private networks, or add it as an exception manually. If you run a VPN on the PC, disconnect it while streaming: local traffic routed into the tunnel never reaches the console. Third-party security suites can block it too; whitelist the client there as well.
Fix 5: Enter the console’s IP address manually
If discovery keeps failing, skip it: the client supports manual connections, and since v6.3 it remembers the last manually entered IP, so you only type it once. Find the console’s IP in its internet settings, enter it in the client’s manual connection option, and connect. This bypasses broadcast problems, no_adv files and most router quirks in one move.
Fix 6: Check for a no_adv file
Auto-discovery can be deliberately switched off by placing an empty file at /config/sysdvr/no_adv on the SD card. If you (or a pre-made SD setup) created that file, the console never advertises itself and will never appear in the client list — you can still connect by manual IP. Delete the file and reboot if you want discovery back. The advanced tips post covers this flag in more detail.
Fix 7: Isolate the problem with a different mode
Still nothing? Test another path to learn where the failure lives. Try Simple Network (RTSP) mode with a player such as mpv pointing at the console’s IP, or connect over USB following the USB streaming setup. If RTSP works, your network path is fine and the issue is specific to discovery; if USB works, the sysmodule is healthy and the problem is definitely on the network side.
Know which discovery you are actually using
One distinction saves a lot of confusion: only TCP Bridge mode has discovery at all. In that mode the console advertises itself and the client lists what it hears. Simple Network (RTSP) mode has no list and nothing to “find” — you always connect directly to the console’s IP address, so a failure there means a wrong IP or a blocked path, not a discovery problem. And if the console is set to USB mode in its Settings app, it will never appear on the network: the mode on the console and the mode in the client have to match. Check that first whenever a previously working setup suddenly goes quiet — a mode left on USB after a wired session is a classic.
Still stuck?
If the client still cannot see the console after all of the above, note down both version numbers, the mode you are using and your network setup, then ask in the project Discord or open a GitHub issue — the official support channels linked from the project Wiki. Reports with exact versions get answers much faster. More fixes live on our SysDVR troubleshooting hub, including the Settings app showing “not running” and black screen guides.