USB is SysDVR’s lowest-latency streaming mode: gameplay travels over a cable instead of your Wi-Fi, so there’s no network congestion to fight. The setup has three parts — switch the console to USB mode, install the Windows driver once (using the method built into the current client, not Zadig), and connect. Two honest limits before you start: USB does not work while the console is docked, and the cable matters more than you’d expect.
Step 1 — Switch the console to USB mode
On the console, open the Homebrew Menu, launch SysDVR Settings, and set the streaming mode to USB. If you installed the USB-Only build, skip this step — that build is always in USB mode and has no settings app. Remember the sysmodule takes about 20 seconds after boot to start, so give it a moment before troubleshooting a mode change that “didn’t take”.
Step 2 — Install the driver (Windows, one time only)
Since the version 5.5 USB rewrite, the driver is installed from inside the client itself:
- Launch SysDVR-Client on your PC (see the Windows client setup if you haven’t installed it yet).
- In the client’s main menu, open the USB Driver option and click Install.
- Unplug the console for a few seconds after the install finishes.
After installation the console shows up on the PC as an Android-style device — on some systems it appears as a “Google Inc. Nexus/Pixel (fastboot)” device, which is expected and harmless.
About Zadig: older guides tell you to replace the driver with Zadig/WinUSB. That was the pre-5.5 method and it is obsolete. The author is explicit that if you did the Zadig replacement before 5.5, you must redo the driver setup the new way. If the built-in installer fails for some reason, the documented manual fallback is Google’s Android ADB USB driver (the android_winusb.inf from the Android USB driver package).
On other platforms there is less to do: macOS and Android receivers need no driver setup at all. On Linux, USB works through libusb plus a udev rule (99-sysdvr.rules) — and never run the client as root, which breaks audio; details are in the Linux client setup.
Step 3 — Use the right cable
Connect the console directly to the PC with a USB-A to USB-C cable. USB-C-to-USB-C cables are known to cause problems with SysDVR’s USB mode, so if a C-to-C cable is all you have and nothing connects, swap the cable before changing any software. Also connect the console undocked, in handheld form — the dock’s USB path doesn’t carry this mode.
Step 4 — Connect from the client
In the client’s GUI, choose the USB connection and it will attach to the console automatically. From the command line the equivalent is:
SysDVR-Client.exe usbIf more than one console is attached, specify which one with the --serial option alongside the usb command. Video not appearing instantly is normal for the first moments — the stream waits for a keyframe, produced roughly every two seconds, so move the in-game camera and give it a couple of seconds.
One conflict to know about
While SysDVR is using the USB interface, other USB homebrew tools — Goldleaf, nxmtp, Twili and similar — stop working, because they contend for the same interface. Switch the console back to a network mode in Settings when you need them (full build), or disable the sysmodule and reboot (USB-Only). We walk through it in Goldleaf / nxmtp stopped working. And if Windows doesn’t recognize the device at all, start with USB device not recognized on Windows.
This walkthrough assumes the full build on Windows for the driver section, since that’s where most readers are; the console-side and connection steps are identical on every platform, and platform differences are called out where they exist.
What you need
- SysDVR installed on the console — full build (switchable to USB mode) or the USB-Only build.
- SysDVR-Client on the receiving PC, version-matched to the console.
- A USB-A to USB-C cable that carries data, not a charge-only lead.
- On Windows, five minutes for the one-time driver install below. On macOS, nothing extra; on Linux, the libusb/udev setup from the Linux client guide.
When USB is the right choice
Pick USB when latency is the priority — fighting games, rhythm games, speedrun attempts — or when the Wi-Fi where you’re playing is crowded or weak, because a cable removes the network from the equation entirely. Pick a network mode instead when you want to play docked on the TV, sit away from the PC, or receive on a phone without a cable trailing across the room. Plenty of setups keep both configured: the mode is a Settings-app toggle on the console, so switching takes seconds. What USB will never do is work through the dock, and it locks out other USB homebrew while it owns the interface — plan around those two facts and it’s the most reliable mode SysDVR has.
First-connection checks
- Console awake and in a game (the Home menu is never captured — a black screen there is normal).
- Sysmodule given its ~20 seconds after boot to start.
- Cable swapped once if nothing enumerates — C-to-C cables are the classic culprit.
- Client and console on the same SysDVR version.
Next steps
- TCP Bridge mode — when you’d rather stream wirelessly with low latency.
- Lag, stutter & audio desync fixes — if the stream runs but feels wrong.
- Back to the setup guide hub for the full map of SysDVR guides.