Nintendo offers solution for Wii Fit U transfer hard locks from Wii Fit and Wii Fit Plus

Have you downloaded Wii Fit U yet? You should it’s free for a month after all. If you did then you might have imported your data from Wii Fit or Wii Fit Plus (but only if you transferred your Wii data already). While it might work for most people some people have been running into problems.

The main problem? The Wii U console will lock up when the save data has been attempted to be copied over. Nintendo Australia has posted some instructions for helping you get your transfer back on track if it happens to you and how the error may happen if you’re yet to try.

Conditions that May Produce the Error:

The lock-up error may occur in instances when all of the following conditions are met:

• Two or more sets of user data were created in Wii Fit or Wii Fit Plus and the data created earlier was deleted.
• A Mii character used in Wii Fit or Wii Fit Plus is registered in the Wii U Mii Maker.
• The data from Wii Fit or Wii Fit Plus is transferred to the Wii U.

 

How to Resolve the Error:

If you encounter this error, you will need to delete any Mii characters in the Wii U Mii Maker that were used in Wii Fit or Wii Fit Plus, start Wii Fit U, and then transfer user data.

If the Mii character that needs to be deleted is the user’s Mii character, please follow the steps below to change the user’s Mii character:

Advertisement

1. From the user selection screen, highlight the user.
2. Go to User Settings.
3. Select View/Modify User Information.
4. Tap Next to enter the user’s password.
5. Select Change Mii and choose a new Mii character from Mii Maker.
6. Delete the user’s original Mii from Mii Maker.

Furthermore, if the deleted Mii was being used in other software, the user will have to re-register their new Mii character with each piece of software.

To use the deleted Mii character with Wii Fit U, after transferring all user data, the user must once again go to the Mii Maker and then select Copy from Wii Menu.

Phew! Hopefully Nintendo get to patching this as soon as possible but if not – there’s how to fix it. Has anyone had a problem with the import? Let us know in the comments – our import went just fine here.