Good day all!
Just took receipt of a known faulty WiiU. I knew that the main console was at fault but everything else was in Grade A condition and at the price, could afford to buy a working console element if it was not able to be repaired and still be about where a complete working 2nd hand unit might cost.
So with the reason why I picked up a broken one out of the way, onto the issue!
Never owned a WiiU or heard of Error 160-0103 before today but done some reading and found that there's a number of reasons for it ranging from faulty flash memory, certain games triggering unstable memory to go wibble, failed modding attempts, powering off during updates... fairly extensive list. Also it seems that when the error presents will determine 'how far gone' the console is, though it's not clear to me what's a good place to have the error and what's bad due to my inexperience with it.
Safe to say, I've no idea about the history of this console so couldn't say why it is doing what it's doing but I can say what the current situation with it is.
Just took receipt of a known faulty WiiU. I knew that the main console was at fault but everything else was in Grade A condition and at the price, could afford to buy a working console element if it was not able to be repaired and still be about where a complete working 2nd hand unit might cost.
So with the reason why I picked up a broken one out of the way, onto the issue!
Never owned a WiiU or heard of Error 160-0103 before today but done some reading and found that there's a number of reasons for it ranging from faulty flash memory, certain games triggering unstable memory to go wibble, failed modding attempts, powering off during updates... fairly extensive list. Also it seems that when the error presents will determine 'how far gone' the console is, though it's not clear to me what's a good place to have the error and what's bad due to my inexperience with it.
Safe to say, I've no idea about the history of this console so couldn't say why it is doing what it's doing but I can say what the current situation with it is.
- On first turn on, I wasn't asked to configure the date/time or networking settings - it went straight into asking me to link a NNID.
- Selecting that I didn't have a NNID, it asked me to create a Mii - at which point the system crashed and the error was displayed.
- Restarting and selecting that I did have a NNID, I was directed to configure network settings.
- Console connected to my network fine and put some random stuff in for NNID just to test and sure enough it said the details were incorrect (I have no NNID to progress this line of testing)
- There appears to be no obvious method to skip this stage or jump into settings and have a poke around.
Last edited by awittyusername,