One rule prevents almost every SysDVR update problem: the sysmodule on the console and SysDVR-Client on your computer must be exactly the same version, and the console must reboot after you change the files. The official troubleshooting guide puts it bluntly — version 6.x on the console with a different version of the client simply won’t connect. Update both sides, reboot, verify: five minutes, done.
Before you start
- The current release is SysDVR v6.3 — see the version history for what changed in each release.
- Download everything from the SysDVR download page, which links each file to its official GitHub release.
- You only replace the program files. Your settings in
/config/sysdvr/stay in place — don’t delete that folder. - Updating is also the fix for most “worked yesterday” problems, especially right after a console firmware update or an Atmosphère update.
Step 1 — Download the new release (both halves)
Grab SysDVR.zip (the full console build) — or SysDVR-USB-Only.zip if that’s the build you run — and the SysDVR-Client build for your operating system, both from the same release. Downloading only one half is the classic mistake; the versions have to match on the number, not just be “recent”.
Step 2 — Replace the sysmodule on the SD card
- Delete the old folder
/atmosphere/contents/00FF0000A53BB665from the SD card. Deleting first guarantees no stale files from the old version linger. - Extract the new SysDVR.zip to the root of the SD card, merging folders. This restores the sysmodule folder, the
/config/sysdvr/files and the Settings app (switch/SysDVR-conf.nro) in one pass. - USB-Only users: extract the USB-Only zip instead. Never mix the two builds — pick the one you run and use only its files.
Step 3 — Update the client to the same version
On your PC or Mac, extract the new client build into a fresh folder (or over the old one) so the whole client is the new version, not a blend. On Android, install the new APK over the existing app. The rule is symmetric: console v6.3 wants client v6.3, on every device you stream to.
Step 4 — Reboot the console
Sysmodules load only when the console boots. Until you reboot, the old version is still the one running, no matter what files are on the card — this is why the Settings app reports a freshly updated install as “outdated”. Reboot, then give the full build its usual ~20 seconds to start.
Step 5 — Verify both sides
- Open the SysDVR Settings app on the console: it should display the new version with no “outdated” warning. (What every item in that app means is covered in SysDVR Settings app explained.)
- Connect with the updated client in your usual mode and confirm the picture and audio arrive.
- If the client can’t find the console, check discovery and network basics in our client can’t find your console fixes before changing anything else.
The three mistakes that cause “version mismatch”
| Mistake | What happens |
|---|---|
| Updated the console only | The old client and new sysmodule refuse to talk — update the client too. |
| Updated the client only | Same mismatch in reverse. Both sides, every time. |
| Copied files but never rebooted | Settings says “outdated”, and the old sysmodule keeps running. Reboot loads the new one. |
| Mixed full and USB-Only files | Unpredictable behaviour. Delete the folder and extract one build, cleanly. |
What about dvr-patches?
Separate project, separate schedule. dvr-patches is keyed to your console firmware, not to the SysDVR version — updating SysDVR never requires new patches, and a firmware update is what triggers a fresh, matching dvr-patches download. The full pairing logic is in our dvr-patches install guide.
Rolling back
Changed your mind? The process is identical in reverse: download the older release from the version history links, replace the console folder, replace the client with the same older version, reboot. Version-matched is version-matched, whichever direction you’re going.
Updating alongside firmware or Atmosphère
SysDVR updates often happen in a pile: Nintendo ships a firmware, Atmosphère follows, and everything homebrew gets shuffled at once. A sane order keeps the pile manageable — firmware and Atmosphère first, SysDVR second, dvr-patches last. Get the console booting cleanly on the new CFW, then do the both-sides SysDVR update from this page, then check whether your firmware jump needs a newly matched dvr-patches build.
One version-history detail worth knowing: from firmware 20.0 onwards, the system reduced the memory available to sysmodules. The full SysDVR build still fits in slightly under 1 MB, but a console crowded with other sysmodules is more likely to hit the ceiling after a big firmware jump — if Atmosphère stops booting after an update pile-up, the Atmosphère won’t boot fixes (including the lighter USB-Only build) are the way back.
How often should you update?
There’s no schedule to keep. Update when a release fixes something you actually hit, when you change firmware or Atmosphère, or when the client and console have drifted onto different versions — and skim the version history first so you know what you’re getting. A matched, working pair beats a newer, mismatched one every time.
Still says “outdated” after the reboot? Then the running sysmodule genuinely isn’t the one you think you installed — usually because the new files landed somewhere other than /atmosphere/contents/00FF0000A53BB665, or the old folder was never actually replaced. Power the console down, pull the card, and check the folder contents against the fresh zip side by side. Nine times out of ten the mismatch is visible the moment you look. The dedicated fix guide covers the remaining cases.
Next steps
- SysDVR version history — what each release changed.
- “Not running / outdated” fixes — if the app still complains after updating.
- The setup guide hub — everything else about running SysDVR well.