Whenever I try to launch Woomïnstaller from the Wii U Menu, I receive error 199-9999. A popup screen shows up, but all it says is «An error has occurred. If this error persists, contact Nintendo repairs technician» etc.
In most cases reported on the GBATemp forums, error 199-9999 is related to signature mismatches. Though I do indeed have signature checks disabled, as Woomïnstaller is only present on my redNAND setup (using Mocha btw), and I was able to successfully open the Homebrew Launcher RPX from my menu, not to mention the installation of Woomïnstaller itself succeeded, all within the same boot cycle.
If you’re interested, I installed Woomïnstaller on my console by downloading your Git repo, building it (100 or so warnings, probably related to me compiling it with devkitPPC r28 and all of its changed type declarations. 😜) and then copying the FST contents to my SD Card, which I installed on my console using WUPInstaller Y Mod.
The received error message that I mentioned above was very vague about the problem, though I may have found more valuable information in my system log. (Thanks to VinsCool for showing me this trick). I have attached an exert from said logs (/vol/system_slc/usr/logs/28.log I believe it was), which were extracted from my console by rebooting after the 199-9999 error, booting my redNAND and then launching FTPiiU Everywhere.
The log I have provided begins from the point I launched Mocha redNAND, walks through with me as I launch HBL, launch WUPInstaller, use it to install Woomïnstaller’s FST data, close it and return to HBL, close it and return to the Wii U Menu and finally attempt to launch Woomïnstaller, which results in error 199-9999.
syslog.zip
Whenever I try to launch Woomïnstaller from the Wii U Menu, I receive error 199-9999. A popup screen shows up, but all it says is «An error has occurred. If this error persists, contact Nintendo repairs technician» etc.
In most cases reported on the GBATemp forums, error 199-9999 is related to signature mismatches. Though I do indeed have signature checks disabled, as Woomïnstaller is only present on my redNAND setup (using Mocha btw), and I was able to successfully open the Homebrew Launcher RPX from my menu, not to mention the installation of Woomïnstaller itself succeeded, all within the same boot cycle.
If you’re interested, I installed Woomïnstaller on my console by downloading your Git repo, building it (100 or so warnings, probably related to me compiling it with devkitPPC r28 and all of its changed type declarations. 😜) and then copying the FST contents to my SD Card, which I installed on my console using WUPInstaller Y Mod.
The received error message that I mentioned above was very vague about the problem, though I may have found more valuable information in my system log. (Thanks to VinsCool for showing me this trick). I have attached an exert from said logs (/vol/system_slc/usr/logs/28.log I believe it was), which were extracted from my console by rebooting after the 199-9999 error, booting my redNAND and then launching FTPiiU Everywhere.
The log I have provided begins from the point I launched Mocha redNAND, walks through with me as I launch HBL, launch WUPInstaller, use it to install Woomïnstaller’s FST data, close it and return to HBL, close it and return to the Wii U Menu and finally attempt to launch Woomïnstaller, which results in error 199-9999.
syslog.zip
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
Hacking Installed wup installer gx2 channel, error code 199-9999
-
Thread starterFilo97
-
Start dateMar 9, 2017
-
Views
21,113 -
Replies
13
-
#1
When i boot the channel, it gives me the error code 199-9999, every other app works fine.
I am using CBHC 1.6 on a 5.5.1 EUR wiiu. help?
-
#2
Is it installed to NAND or USB?
If on USB try installing to NAND
-
#3
Is it installed to NAND or USB?
If on USB try installing to NAND
it is installed to NAND.
Deleted User
Guest
-
#5
Try using loadiine.ovh to install it or HBL channel version to install it.
In my case, installing it by launching browserhax [Launching HBL from browser then using Wup Installer Mod Y] fixed my problem.
-
#6
Try using loadiine.ovh to install it or HBL channel version to install it.
In my case, installing it by launching browserhax [Launching HBL from browser then using Wup Installer Mod Y] fixed my problem.
I will try both.
——————— MERGED —————————
installing to USB did the trick. the browserhax one didn’t, but the USB one did, thanks a lot @xtheman166!
-
#7
Sorry to bump this, but why can’t it be installed to the NAND? Does anyone happen to know? I’m getting this error as well and I’m just curious, and I’m also kinda wanting to keep all homebrew on the NAND.
-
#8
Sorry to bump this, but why can’t it be installed to the NAND? Does anyone happen to know? I’m getting this error as well and I’m just curious, and I’m also kinda wanting to keep all homebrew on the NAND.
Try what Felek said. I have mine installed to nand just fine. I used the HBL channel then WUP Installer GX2 to install the channel
-
#9
199-9999 usually means you forgot to run CFW/Sigpatcher first.
- Joined
- Jun 3, 2017
- Messages
- 3
- Trophies
- 0
- Age
- 35
- XP
-
33
- Country
-
-
#10
199-9999 usually means you forgot to run CFW/Sigpatcher first.
got the same error even with CFW (mocha)…any advice?
-
#11
I actually got the same error also. But not a big deal I guess, I just went through the HBL instead.
EDIT…on USB I believe?
- Joined
- Jun 3, 2017
- Messages
- 3
- Trophies
- 0
- Age
- 35
- XP
-
33
- Country
-
-
#12
I actually got the same error also. But not a big deal I guess, I just went through the HBL instead.
EDIT…on USB I believe?
…oh that was a good idea…through HBL it does work…without HBL I only had the option:
1. with USB drive connected —> does not work
2. without USB drive connected —> does work
—> deadlock
-
#13
1. with USB drive connected —> does not work
2. without USB drive connected —> does work
I have exactly the same issue. It’s impossible to launch the channel version from NAND when the HDD is attached. It always results in 199-9999.
Is there really no fix for this aside from installing it to USB or using the .elf version? ..which is not really a fix for the actual problem.
Similar threads
You may also like…
- No one is chatting at the moment.
@
K3N1:
https://youtube.com/shorts/8q-CNsOreKE?feature=share
Today at 6:30 AM
Whenever I try to launch Woomïnstaller from the Wii U Menu, I receive error 199-9999. A popup screen shows up, but all it says is «An error has occurred. If this error persists, contact Nintendo repairs technician» etc.
In most cases reported on the GBATemp forums, error 199-9999 is related to signature mismatches. Though I do indeed have signature checks disabled, as Woomïnstaller is only present on my redNAND setup (using Mocha btw), and I was able to successfully open the Homebrew Launcher RPX from my menu, not to mention the installation of Woomïnstaller itself succeeded, all within the same boot cycle.
If you’re interested, I installed Woomïnstaller on my console by downloading your Git repo, building it (100 or so warnings, probably related to me compiling it with devkitPPC r28 and all of its changed type declarations. 😜) and then copying the FST contents to my SD Card, which I installed on my console using WUPInstaller Y Mod.
The received error message that I mentioned above was very vague about the problem, though I may have found more valuable information in my system log. (Thanks to VinsCool for showing me this trick). I have attached an exert from said logs (/vol/system_slc/usr/logs/28.log I believe it was), which were extracted from my console by rebooting after the 199-9999 error, booting my redNAND and then launching FTPiiU Everywhere.
The log I have provided begins from the point I launched Mocha redNAND, walks through with me as I launch HBL, launch WUPInstaller, use it to install Woomïnstaller’s FST data, close it and return to HBL, close it and return to the Wii U Menu and finally attempt to launch Woomïnstaller, which results in error 199-9999.
syslog.zip
You should upgrade or use an alternative browser.
Hacking Installed wup installer gx2 channel, error code 199-9999
-
Thread starterFilo97
-
Start dateMar 9, 2017
-
Views
21,819 -
Replies
13
-
#1
I am using CBHC 1.6 on a 5.5.1 EUR wiiu. help?
-
#2
If on USB try installing to NAND
-
#3
Is it installed to NAND or USB?
If on USB try installing to NAND
it is installed to NAND.
Deleted User
Guest
-
#5
In my case, installing it by launching browserhax [Launching HBL from browser then using Wup Installer Mod Y] fixed my problem.
-
#6
Try using loadiine.ovh to install it or HBL channel version to install it.
In my case, installing it by launching browserhax [Launching HBL from browser then using Wup Installer Mod Y] fixed my problem.
I will try both.
——————— MERGED —————————
installing to USB did the trick. the browserhax one didn’t, but the USB one did, thanks a lot @xtheman166!
-
#7
-
#8
Sorry to bump this, but why can’t it be installed to the NAND? Does anyone happen to know? I’m getting this error as well and I’m just curious, and I’m also kinda wanting to keep all homebrew on the NAND.
Try what Felek said. I have mine installed to nand just fine. I used the HBL channel then WUP Installer GX2 to install the channel
-
#9
- Joined
- Jun 3, 2017
- Messages
- 3
- Trophies
- 0
- Age
- 36
- XP
-
43
- Country
-
#10
199-9999 usually means you forgot to run CFW/Sigpatcher first.
got the same error even with CFW (mocha)…any advice?
-
#11
EDIT…on USB I believe?
- Joined
- Jun 3, 2017
- Messages
- 3
- Trophies
- 0
- Age
- 36
- XP
-
43
- Country
-
#12
I actually got the same error also. But not a big deal I guess, I just went through the HBL instead.EDIT…on USB I believe?
…oh that was a good idea…through HBL it does work…without HBL I only had the option:
1. with USB drive connected —> does not work
2. without USB drive connected —> does work
—> deadlock
-
#13
1. with USB drive connected —> does not work
2. without USB drive connected —> does work
I have exactly the same issue. It’s impossible to launch the channel version from NAND when the HDD is attached. It always results in 199-9999.
Is there really no fix for this aside from installing it to USB or using the .elf version? ..which is not really a fix for the actual problem.
Similar threads
- No one is chatting at the moment.
tempBOT:
jkyoho has joined the room.
22 minutes ago
I modded my Wii U with Tiramisu 2 days ago and today, the Homebrew Launcher results in a 199-9999 error.
So I modded my Wii U with Tiramisu and I decided to fix some things. But after that, the Homebrew Launcher app doesn’t work and results in a 199-9999 error, forcing me to shut down the console. I know I can just use the Internet Browser and type in wiiuexploit.xyz to access the Homebrew Channel but I want to fix the Launcher to make it simpler.
I need some help please as online source does not help.