Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/WiiLink24/WiiLink24-Patcher/llms.txt

Use this file to discover all available pages before exploring further.

When something goes wrong with WiiLink Patcher, the two best first steps are to run the patcher in debug mode to capture extended logs, and — if that does not resolve the problem — to open a report on the GitHub Issues page. Most issues fall into a small set of known categories, all covered below.
Always try debug mode first before filing a bug report. The extra output often pinpoints the problem immediately and makes any report you do file far easier to act on.

​
Debug Mode

Pass the --debug flag when launching the patcher to enable extended logging. In this mode the patcher prints every file it downloads, including the source URL and the local destination path — giving you a detailed trace of what happened before an error. 
# Windows
.\WiiLinkPatcher_Windows_v213.exe --debug

# macOS / Linux
./WiiLinkPatcher_Linux-x64_v213 --debug
Copy the terminal output in full when you open a GitHub issue; it contains all the context a maintainer needs to reproduce and fix the problem.

​
Common Issues

The patcher pings https://patcher.wiilink24.com/connectiontest.txt at startup. If that request fails, you will see a connection error.Steps to resolve:
  1. Check that your device has a working internet connection by opening a browser and visiting any website.
  2. If your internet is fine, the WiiLink server may be temporarily down for maintenance or experiencing an outage.
  3. Join the WiiLink Discord server and check the #server-status or announcements channels to see if an outage has been reported.
The patcher will report the HTTP status code it received (or the network error message) — include that in your Discord or GitHub report so the team can investigate quickly.
Some antivirus products flag WiiLink Patcher as malware. This is a false positive. The patcher is fully open source and contains no malicious code.Options to work around this:
  • Add the patcher executable (or its containing folder) as an exception / exclusion in your antivirus software.
  • Temporarily disable real-time protection while downloading and running the patcher, then re-enable it.
  • Build the patcher from source yourself — see the Building from Source guide — so you can verify every line of code before running it.
If you are unsure whether a detection is a false positive, inspect the source code on GitHub before proceeding.
The patcher tries to auto-detect any connected SD card at startup and again when navigating the main menu.Steps to resolve:
  1. Make sure your SD card is inserted and mounted before launching the patcher.
  2. At the main menu, press R to retry auto-detection without restarting.
  3. If auto-detection still fails, press M to manually enter the path to your SD card (e.g. D:\ on Windows or /Volumes/NO NAME on macOS).
The patcher only needs write access to the apps/ and wad/ directories on the SD card, so ensure those locations are not write-protected.
If a WiiLink/WAD folder from a previous patcher run is already present in the current directory, the patcher will prompt you before proceeding.
  • Delete the existing folder to start a completely fresh download and patch cycle.
  • Keep the existing folder to reuse any WAD files that were already successfully downloaded, which can save time if a previous run was interrupted.
If you are troubleshooting a bad installation, deleting the folder and starting fresh is generally the safest choice.
When a patcher operation fails, an error screen is displayed showing:
  • Task — the operation that was running when the error occurred.
  • Command or Message — either the internal command that was invoked, or the error text returned by the system (whichever is applicable to the failure).
  • Exit code — the non-zero exit code from the failed process.
To report this issue:
  1. Run the patcher again with --debug and reproduce the error to capture the full log.
  2. Open a new issue at https://github.com/WiiLink24/WiiLink24-Patcher/issues.
  3. Include the task, command or message, exit code, and the full debug log output.
The more detail you provide, the faster the team can identify and fix the root cause.
Pre-built x64 macOS binaries require Rosetta 2 to run on Apple Silicon (M1 or newer) Macs. If Rosetta is not installed, the OS will refuse to execute the binary.Option 1 — Install Rosetta:
/usr/sbin/softwareupdate --install-rosetta --agree-to-license
After Rosetta is installed, the osx-x64 build will run transparently.Option 2 — Use the native ARM64 build:Download the osx-arm64 release from the Releases Page. Note that arm64 binaries must be code-signed on Mac hardware — if you are building from source, perform that step on a real Mac.
If patched channels install successfully but do not connect or function on your Wii, the most common cause is that WiiConnect24 is not enabled.Steps to resolve:
  1. On your Wii, go to Wii Settings → Internet → Connection Settings → Standby Connection and make sure it is set to On.
  2. Ensure your Wii’s internet connection is active and can reach WiiLink servers.
  3. Follow the full post-installation guide on the WiiLink website: https://wiilink.ca/guide/wads
If channels still do not work after following the guide, ask for help in the WiiLink Discord server.
WiiLink Patcher is designed for Windows 10 and 11. If you run it on an older version of Windows, the patcher will display a compatibility warning.For the best visual experience on any Windows version:
  • Set your console font to Consolas, size 16.
  • Set the window and buffer size to 120 columns × 30 rows.
These settings can be adjusted by right-clicking the console window title bar and selecting Properties → Font and Layout.

​
Getting Help

If you have worked through the steps above and the problem persists, reach out through one of the official support channels:

GitHub Issues

Open a bug report or feature request. Include your OS, patcher version, and the full debug log output.

WiiLink Discord

Get real-time help from the WiiLink community and team. Check server-status announcements for any active outages.

Build docs developers (and LLMs) love

Get started for freeTalk to us