SOLVED (see EDIT at the bottom for solution)
I’m having this error occurring when I attempt starting two particular games after updated of FW and AMS. The games were working fine before the update. The issue started with another error message and the "The software was closed..."error message is the last and the lasting result after a chain of events that I’m going to explain below. But first let me explain my setup, because I somehow feel that this might be related or part of the issue.
I’m using the earliest possible version of Switch, with installed SX OS. After the downfall of SX OS I started using Atmosphere, but I’m still booting via the SX OS menu with the following steps:
SX OS –> options -> payloads -> launch payload.bin -> Hekate -> payloads -> launch fusee.bin
Every time I do the boot process on the last step after launching the fusee.bin I get a black screen with message for “fatal error” (in the upper left corner) and request to push the “power button” and when I do this AMS launches without any issue. It was not like this always, but it is for the last few updates of FW and AMS – in the last couple of years or so.
I’m using DBI to install games.
Now here is how my issue started. When I updated the FW to 18.1.0 and AMS to 1.7.1 (including updated of fusee.bin and sig patches) about half a year ago, I tried launching Minecraft and I got a message “Corrupted data has been detected. Please run a check for corrupted data.”. The issue happened ONLY for this game. Everything else was working fine. So I clicked the “Check” button and after the check was completed I got a message “Corrupted data found. The data can be restored by redownloading it.”. So I deleted the game and tried reinstalling with DBI. It didn’t help.
Fast forward to today I updated AMS to 1.8.0, again updating sigpatches too. That didn’t help with the Minecraft issue and it brought the same issue to another game “Shift Happens”. As a remedy I tried:
- Deleting the games and installing them again.
- Downloading and installing different versions of the games (all NSP) from different sources.
- Downloading and installing new and latest update files for the games.
- Deleting the save data for the game from the Switch menu.
- Installing Sys-Patch Sysmodule 1.55 (which actually fixed an issue with another older game that didn’t want to start with the latest AMS - LEGO Harry Potter).
At some point (I believe after reinstalling the games or after installing new version of the games from different source) I started getting the “The software was closed because an error occurred.” error instead and now whatever I do I get only this message and not the original “corrupted data” message.
Now I’m out of ideas. I feel like the bloody corrupted data check I did is coded somewhere and because of it whatever I do is futile.
Any advice will be highly appreciated.
EDIT (01.02.2026):
I finally managed to resolve the issue. I’m writing this to help any other users who might have the same or similar issues. Here is what I did.
- I did a clean install of Atmosphere (1.10.2) deleting the old folder on the SD card and placing the new from the downloaded pack.
- I did a clean install of Hekate (6.5.1) deleting the old bootloader folder and placing the new from the downloaded pack.
- I added only Sys-Patch Sysmodule (latest from https://gbatemp.net/)
- I didn’t add Sig Patches.
- I deleted all other single files (not folders) from the root of the SD card which were remnants from previous installs and SXSO usage.
- I updated DBI to the latest version (863 in Russian).
- I used DBI function to clean orphaned files (under Tools menu). I believe this was the most important step that fixed the issue, because before that they were still giving errors.
- Then I deleted the games (including their save data after making backup with JKSV).
- Then I reinstalled them again. And they were finally working.
- Then I restored their saves with JKSV.
I also:
- updated the FW of the switch to 21.0.0
- started booting Hekate directly with payload from TegraRCM instead of going through the SXSO menu (this resolved the fatal error I was getting every time I launch AMS)
but I think these two actions were not related with the fix of the issue.
I’m having this error occurring when I attempt starting two particular games after updated of FW and AMS. The games were working fine before the update. The issue started with another error message and the "The software was closed..."error message is the last and the lasting result after a chain of events that I’m going to explain below. But first let me explain my setup, because I somehow feel that this might be related or part of the issue.
I’m using the earliest possible version of Switch, with installed SX OS. After the downfall of SX OS I started using Atmosphere, but I’m still booting via the SX OS menu with the following steps:
SX OS –> options -> payloads -> launch payload.bin -> Hekate -> payloads -> launch fusee.bin
Every time I do the boot process on the last step after launching the fusee.bin I get a black screen with message for “fatal error” (in the upper left corner) and request to push the “power button” and when I do this AMS launches without any issue. It was not like this always, but it is for the last few updates of FW and AMS – in the last couple of years or so.
I’m using DBI to install games.
Now here is how my issue started. When I updated the FW to 18.1.0 and AMS to 1.7.1 (including updated of fusee.bin and sig patches) about half a year ago, I tried launching Minecraft and I got a message “Corrupted data has been detected. Please run a check for corrupted data.”. The issue happened ONLY for this game. Everything else was working fine. So I clicked the “Check” button and after the check was completed I got a message “Corrupted data found. The data can be restored by redownloading it.”. So I deleted the game and tried reinstalling with DBI. It didn’t help.
Fast forward to today I updated AMS to 1.8.0, again updating sigpatches too. That didn’t help with the Minecraft issue and it brought the same issue to another game “Shift Happens”. As a remedy I tried:
- Deleting the games and installing them again.
- Downloading and installing different versions of the games (all NSP) from different sources.
- Downloading and installing new and latest update files for the games.
- Deleting the save data for the game from the Switch menu.
- Installing Sys-Patch Sysmodule 1.55 (which actually fixed an issue with another older game that didn’t want to start with the latest AMS - LEGO Harry Potter).
At some point (I believe after reinstalling the games or after installing new version of the games from different source) I started getting the “The software was closed because an error occurred.” error instead and now whatever I do I get only this message and not the original “corrupted data” message.
Now I’m out of ideas. I feel like the bloody corrupted data check I did is coded somewhere and because of it whatever I do is futile.
Any advice will be highly appreciated.
EDIT (01.02.2026):
I finally managed to resolve the issue. I’m writing this to help any other users who might have the same or similar issues. Here is what I did.
- I did a clean install of Atmosphere (1.10.2) deleting the old folder on the SD card and placing the new from the downloaded pack.
- I did a clean install of Hekate (6.5.1) deleting the old bootloader folder and placing the new from the downloaded pack.
- I added only Sys-Patch Sysmodule (latest from https://gbatemp.net/)
- I didn’t add Sig Patches.
- I deleted all other single files (not folders) from the root of the SD card which were remnants from previous installs and SXSO usage.
- I updated DBI to the latest version (863 in Russian).
- I used DBI function to clean orphaned files (under Tools menu). I believe this was the most important step that fixed the issue, because before that they were still giving errors.
- Then I deleted the games (including their save data after making backup with JKSV).
- Then I reinstalled them again. And they were finally working.
- Then I restored their saves with JKSV.
I also:
- updated the FW of the switch to 21.0.0
- started booting Hekate directly with payload from TegraRCM instead of going through the SXSO menu (this resolved the fatal error I was getting every time I launch AMS)
but I think these two actions were not related with the fix of the issue.
Last edited by KillaKnightBG,
