You plug the Switch into your PC, switch SysDVR to USB mode, and Windows shrugs: unknown device, or the client simply never connects. The most likely cause is a missing or outdated USB driver — Windows does not ship with the right one for the console’s USB interface, and SysDVR needs it installed exactly once.
The good news: since the USB rewrite in v5.5, the driver installs from inside SysDVR-Client itself. If an old guide sent you to Zadig, close that tab — that method is legacy, and the official Wiki is explicit that anyone who set things up the pre-5.5 way must redo it with the current method.
The current method: install the driver from the client
- On the console, open the SysDVR Settings app and set the streaming mode to USB (with the USB-Only build, USB is already the only mode).
- Connect the console directly to the PC with a USB-A to USB-C cable. USB-C to USB-C cables are known to be unreliable for this — and USB streaming does not work while the console is docked, so plug in undocked.
- Launch SysDVR-Client on the PC, open the USB Driver option in the main menu, and click Install.
- Wait for the install to finish, then unplug the console for a few seconds and reconnect it.
- Start the client in USB mode and connect — the console should now be detected.
Do not be alarmed by how Windows names the device after the driver install: the console shows up as an Android-type device, on some systems listed as “Google Inc. Nexus/Pixel (fastboot)”. That is expected — SysDVR’s USB interface presents itself that way, and it is exactly what the driver is for.
Fallback: install Google’s ADB driver manually
If the built-in installer fails on your system, the official manual fallback is Google’s Android USB driver:
- Download the Android ADB USB driver from Google and extract the archive to a folder.
- Inside it, open the
usb_driverfolder and findandroid_winusb.inf. - Right-click
android_winusb.infand choose Install. - Unplug the console for a few seconds, reconnect, and retry the client.
About Zadig: why old guides are wrong now
Pre-5.5 versions of SysDVR required replacing the driver with WinUSB using the Zadig tool. The USB stack was rewritten in 5.5 and that procedure no longer applies — following it today is a common reason USB stays broken. Everything current is described in the USB streaming setup guide; get the latest client and sysmodule from the download page and use the built-in installer above.
Console charges but never appears? Suspect the cable
A classic trap: the Switch charges happily over the cable, so the cable must be fine — except charge-only USB cables exist, and they carry power with no data lines at all. If the console charges but no device ever shows up, try a different cable before reinstalling anything, ideally a short, known data cable. The same applies in reverse while troubleshooting the driver: a cable that drops data intermittently can make a perfectly installed driver look broken. One known-good USB-A to USB-C data cable, plugged straight into the PC, is the reference setup for every test in this guide.
More than one console? Use –serial
If several Switch consoles are attached, the client can be pointed at a specific one from the command line: SysDVR-Client.exe usb --serial <serial>. Without it, the client may attach to a different console than the one you are troubleshooting.
Before blaming the driver: three quick sanity checks
- Is the console actually in USB mode? On the full build, check the mode in the SysDVR Settings app — a console left in a network mode is invisible to USB no matter how good the driver is. (On the USB-Only build USB is the only mode, so skip this.)
- What does Device Manager say? After the built-in install, the console should appear as an Android-type device. If it shows as an unknown device with a warning icon, the driver install did not take — re-run the client’s USB Driver install, unplug for a few seconds, and reconnect. If the listing appears only while the console is awake at the Home menu with a game running, that is normal stream behaviour, not a driver fault.
- Did it work before an update? If USB detection broke right after updating SysDVR, install the current client and sysmodule as a matched pair from the download page and run the driver install once more — driver state from an old client version is a recurring cause of “suddenly unrecognized”.
Also try a port on the PC itself rather than a front-panel or hub port, and a second cable before you conclude anything: for a problem that looks exactly like a driver failure, the physical layer is guilty surprisingly often.
On Linux it works differently
Linux does not use this driver flow at all: USB mode there relies on libusb plus a udev rule (99-sysdvr.rules), and the client must not be run as root — doing so breaks audio. macOS and Android receivers need no driver setup. Details are in the Linux client setup.
Still stuck?
If the device is still not recognized after the built-in install and the manual fallback, try a different USB-A to USB-C cable and a different port (cable quality genuinely matters here), confirm the console is in USB mode, and make sure console and client versions match. If it persists, ask in the project Discord or open a GitHub issue with your Windows version and what Device Manager shows. Related: Goldleaf and nxmtp conflicts over the same USB interface, and the rest of the troubleshooting hub.