Running into Issues with homebrew? This page will show you how to troubleshoot errors during the exploit and when using apps.
Browser errors
FSGetMountSource failed: Please insert a FAT32 SD Card:
No SD Card detected. Re-insert the SD and try again. This could also mean that the SD card is locked (Slider is down instead of up) or the SD card label is "wiiu" (casing does not matter), which is stated in the guide causes conflict. If it's not any of these issues, try blowing into the slot (not recommended) or use compressed air. Pins may be dusty inside.
FSOpenFile failed [...] payload.elf:
Missing payload file on SD. Make sure you have payload.elf in the wiiu folder, and the wiiu folder on the root of the SD card.
FSOpenFile failed/-11 after launching Mii Maker:
Missing the Homebrew Launcher on the SD card. Make sure you have homebrew_launcher.elf in the sd:/wiiu/apps/homebrew_launcher folder.
SD Mount Failed:
The console recognizes the SD card but could not mount it. Make sure it is formatted properly. Also, your SD card is more compatible with reputable brands (i.e. SanDisk, Samsung, Lexar, etc.) and less likely to have issues.
PayloadLoader Errors
Failed to load SD:/wiiu/payload.elf. Starting the console without any modifications:
PayloadLoader could not find the payload or it doesn't detect your SD card. Reinsert it properly or try cleaning the slot. If the issue persists, try getting fresh files from the Tiramisu or Aroma site, depending on which you use.
Mocha InitLibrary Failed:
This usually happens when using an outdated mocha setup module (e.g. using an old aroma/tiramisu version). Can be fixed by redownloading the latest Aroma or Tiramisu files.
EnvironmentLoader Errors
Don't run the EnvironmentLoader twice:
Happens when you run Health and Safety or through the exploit a second time. The EnvironmentLoader can only be ran one time per boot. If you autoboot into an environment, you do not need to run Health and Safety. To change environments, hold X on boot (or Start for changing boot titles in the boot selector). If you've launched the EnvironmentLoader already, you must reboot to use it again.
EnvironmentLoader: Failed to load module:
This probably happens because of corrupted module files on the SD card. Re-downloading your files should help.
FAQ
A detailed list of FAQ's can be found on this page.