Wii Update 4.2 Is Killing Wiis Dead

Wii Update 4.2 Is Killing Wiis Dead

The Nintendo support forums and our tips email alike are packed with reports that Wii system update 4.2 is doing horrible things to Wii consoles, and not just the modded ones.

A quick scan of the Nintendo tech support forum tells the tale of a system update gone slightly awry. The update is freezing halfway through. The update is giving system errors informing customers that their Wii has been modified and then failing to start. There are even reports of random disk read errors following the update. While some of the problems can be attributed to modified systems, customers are reporting issues with units right out of the box.

Kotakuite Crazy Weavile submitted a possible explanation for the problems on the Nintendo forums, suggesting that the latest update irresponsibly updated the system’s bootloader, only to find himself banned shortly thereafter.

While no help is on the horizon for modded console owners, Nintendo tech Jane posted a message in the forums yesterday instructing owners of unmodded Wiis to send their units in for a free repair.

Some of you have reported problems with your Wii console after updating to the Wii System Menu 4.2. The symptoms most people are describing usually occur when the Wii has been modified. However, some of you also mention your system has never been modified.

We’d like to help get your system working properly again. If you’re experiencing problems with your Wii console after downloading Wii System Menu 4.2, and you believe your system has not been modified, please give us a call. If we find that you have a normal system and the update caused your system to not work, we’ll repair it at no charge.


  • to make it 100% clear, the possibility of the update bricking your wii has absolutely NO relation to whether your wii is modded or not. The update carries out the same steps in same reckless fashion on every console no matter what, it doesn’t matter what is previously installed on it.

    Nintendo administration is just bringing up ‘modified consoles’ as possible cause just as a scapegoat, and any chance to try and make homebrew look dangerous is going to be taken by them. It’s the easiest thing to try and blame it on, considering their militant stance against homebrew.

    It’s unfortunate for legitimate homebrew users who have had their wii destroyed by Nintendo, only to find they aren’t getting it fixed for free. Extremely underhanded on their part, would’ve been nice if they took responsibility for this.

  • I use homebrew purely for, you know, homebrew and i’ve learnt an important lesson. NEVER EVER UPDATE. if you have to check and double check the safest way to do so on the internet, there are many helpful people who police these updates.

    • Don’t people have the right to modify their Wii as they see fit? If you buy the product, it’s yours, you can do whatever you want to it. Kind of unfair that Nintendo can sendin updates that will maliciously destroy it.

      Isn’t that against law?

      • You seem to be a bit confused here.

        Yes, you have the right to modify your Wii, but you also sever your Warranty and break the EULA in doing so. Thereafter, you’re responsible for the console’s care because Nintendo is no longer obliged to repair it for free when it breaks from manufacturing faults.

        It’s not so much a matter of targeting homebrew users as it is Nintendo using them as a scapegoat to cover up their own half-assed programming.

        This is where the new bootloader problem comes in, because it’s Nintendo who done fucked up. However, since homebrewers broke the EULA/warranty they now have the pleasure of buying a new Wii or paying for the repairs (to which they will receive a new, homebrew-proof, console).

  • does this include consoles that have used the soft-mod method to install the Homebrew channel. My console is rarely conneced to the internet so i wont update until nintendo fix their mess.

  • According to a particular homebrew development group, Nintendo’s code for the installer for the system menu and other software was very buggy, which was why it led to the bricking of hundreds of wiis

  • I can understand firmware updates locking out homebrew and all of that jazz, but what is the legality of one the not only locks it out, but Breaks the console and then Ninty refusing to honor repairs?

    You may have broken the warranty and the Eula with the Homebrew, but if that didn’t break the Nintendo, and their update did, could it be argued that the Code is malicious and destructive. (In a Legal sense, which I have no creditentials in)

    That being said, it just looks like they’ve borked the whole thing and are killing everyones

    • If you broke the warranty, Nintendo considers everything thereafter your fault and your problem.
      If the break was their fault and you haven’t modded your Wii, THEN it’s their problem to deal with.

      Also, they can’t refuse to repair it even if it is running homebrew.
      It wont be free, but they will repair it.

  • I’m sorry, but the homebrew is beside the point and so is the voided warranty. If my Wii breaks down because of a mistake that Nintendo made then they are obligated to fix my machine whether I’ve been inside it with a screw driver or whether I’ve attacked it with a hackMii installer.

    If, however, this update bricks my Wii because the new firmware doesn’t know how to treat the WiiKey that I could potentially have installed, then I take a bricked machine in my stride and buy a new one.

    (For those playing at home, I removed my WiiKey because it was stopping me from playing a legitimately purchased Brawl. I, too, appreciate this irony).

  • My Wii is now getting dump errors and know of a few more friends that say the same but have not updated, all are using 4.0u. Is this the main symptom after updating?

  • My Wii was only partailly or “quartely” updated to Wii Menu 4.2E because the update stopped 1/4 of the way because I have a 31.2kbps dial-up connection.

Show more comments

Log in to comment on this story!