Hi lately I've had the problem where windows 10 would not recognize that the axe-fx II was connected, and certainly not connect to the axe-fx II from axe-edit. I found a temporary solution where I start windows in advanced mode where forced driver authorization is turned off, but today I found a permanent fix.
Ok i have this Wii, it was at version 3.2E and had BackupLaucher and Homebrew Channel. But couldnt install wad's. So i thought maybe if i updated to 4.0 then it would fix the problem. So i followed a Guide(found from Google) on how to update. All went well but i still cant install wads. (ret -1022) Anyone knw how to fix? Press J to jump to the feed. Press question mark to learn the rest of the keyboard shortcuts. The inclusion the 116 error code in the troubleshooter is only coincidence and holds no specific meaning (other than driver caused bluescreens do occur with some frequency). Look in the Event Viewer to see if anything is reported about those.
- Hi lately I've had the problem where windows 10 would not recognize that the axe-fx II was connected, and certainly not connect to the axe-fx II from axe-edit. I found a temporary solution where I start windows in advanced mode where forced driver authorization is turned off, but today I found a permanent fix.
- I'm attempting to mod the Wii Console, not the vWii for the Wii U. I'm using version 3.1 of d2x cIOS installer as well. When I load d2x cIOS installer and get into changing the version, it only goes as high as v6. I have d2x v10 beta r52 in the folder, so shouldn't I be seeing v10? Any suggestions or anything I'm doing wrong?
'Driver install error code: 116
Driver could not be updated.
Run installer again and accept
installation of unsigned drivers.'
and this message is pretty frustrating, but the way I did it was this:
Update drivers in Windows 10
- Select Start , in Search , type Device Manager, and select it from the list of results.
- Expand a category (like Monitors or Network Adapters) to find the name of your device, in this case the axe-fx II right, then right-click (or tap and hold) it, and select Update Driver. ...
- S̶e̶l̶e̶c̶t̶ ̶S̶e̶a̶r̶c̶h̶ ̶a̶u̶t̶o̶m̶a̶t̶i̶c̶a̶l̶l̶y̶ ̶f̶o̶r̶ ̶u̶p̶d̶a̶t̶e̶d̶ ̶d̶r̶i̶v̶e̶r̶ ̶s̶o̶f̶t̶w̶a̶r̶e̶.̶
And Voilà! Windows 10 now accepts the Fractal Audio USB driver so you can run axe-edit/cab-lab normally instead of having to use advanced startup / safe-mode or whatever
Pretty basic stuff, but it's been frustrating me from time to time when I forget about the specific way of doing it for various reasons like uninstall/install, new drive, whatever Cios Installer Error 116 Hp
This is based off of my offline guide to upgrade any console (that has NOT been region hacked) to v4.2 safely. This is a modification of the Shop Channel and IOS61 Installer by tona. It has been rigorously tested and should not brick anyone, but as usual, use it at your own risk. Source included of course.
It will detect your region, download and install all of the NECESSARY IOSes, your specific system menu, and the shopping channel update from v4.2 It will NOT touch your cIOSes, stub anything, or touch your boot2. It also will NOT trucha sign any of the IOSes it downloads and installs. If you want to pirate, you'll have to go ahead and use DOP-IOS or similar to trucha patch your IOS70 after the upgrade is complete smile.gif
It is almost completely automated. Answer a question in the beginning, sit back and relax, and wait for the update to be completed. When finished, you'll be on v4.2 with everything functional (no upside down HBC, no 'vulnerable IOS not found' errors). This should hopefully eliminate all of the goofy issues people have been having with the upgrade.