So last Monday I finally decided to upgrade my 3.2U (which was downgraded from either 3.3U or 3.4U quite sometime ago). I did run into an initial problem during the 4.1 upgrade (following the guide here and using wanin's 4.1 upgrader) with a -1036 error which after searching, I found out was caused because I did not have an ISO60 installed. I believe this is part of the 4.0 system menu update, but really not an issue here. Anyway, late last week I ran into a problem after existing Wii Fit (channel/not the disc) back to the Wii System Menu with the "System Files Corrupt..." message. I power cycled a few times and it started working fine again. But it happened again this weekend and now it pretty much happens all of the time (only seems to be after exiting the Wii Fit channel). So a little more about my system. HBC 1.03 installed, Bootmii (boot2) installed, preloader 0.29 installed. Other various apps, etc. but nothing that should come into play at this point. The only hacks I have enabled in preloader are the disable update disc check and remove no copy flag. Otherwise everything else is disabled. My SD that I have been using does not work with Bootmii, so I changed the preloader setting to boot to the system menu. Again, otherwise everything is at it's default. After being stuck in this state for a while I decided to change preloader to use IOS249 for the system menu (running r14) and it seems to be working fine now. At least all the tests, apps, etc. work as expected and I have not seen the "SystemFiles Corrupt..." message with IOS249 (although it didn't happen until a few days after my initial upgrade to 4.1 and I do use the Wii Fit channel every day). I did try re-running dop-ios to reinstall ISO60 with the sig hash check and reinstalling preloader again, but the problem still persists (when using IOS60 for the system menu). So a couple of questions: 1) Has anyone run into this before and know why IOS60 is causing this problem? 2) Is it ok to use IOS249 (through preloader for the system menu)? 3) Is there anything else I can check or any tools to verify the IOS is fine? To me, it would appear something is wrong with IOS60, but I have to admit I am no expert, just coming to that conclusion since that seems to be the only way I run into this problem. If anyone has any advice or suggestions, as well as being able to answer my questions, it would be much appreciated!