Known issue. Apparently it stared sometime when 18.x.x was introduced and now it's even more present on 20.x.x. From what I've gathered, it's caused by console trying to fetch new EULA for your account to accept while constantly being blocked by 90DNS or similar. There are a couple of workarounds for this like staying offline or in airplane mode, removing all real NNIDs from your profiles (not sure if this actually fixes the issue), creating a new emuNAND from an updated sysNAND where EULA has been agreed to, etc.
I personally have no real NNIDs linked to any of my profiles (except from the fake ones linked by linkalho) and I'm yet to run into that issue on my emuNAND.
Update, the problem has been solved:
I'll leave the post up for someone that might need it:
The issue was solved by renaming the "
atmosphere/contents" folder to "
oldcontents", then, by excluding things, I found out that the issue was the "
0000000000534C56" folder which was SaltyNX.
Hi, sorry for bothering, any idea why softwares doesn't start up anymore?
I regularly updated:
- Atmosphere to 1.9.1 + fusee.bin
- Hekate to the v6.3.1
- Changed hekate_ipl.ini (
changed fss0 to pkg3 + removed kip1patch=nosigchk, .ini in the bottom)
- Replaced sigpatches (deleted patches.ini, kip and exfs folders) with sys-patch 1.5.6
I've tested new sigpatches aswell with the modified fusee.bin, no effect whatsoever, same issue...
Sys-patch shows '
noncasigchk_new, nocntchk2, noacidsigchk, es3, ctest2, nim and disablecaverification1/2/3' all
Patched in green, but, only a couple games actually works without giving the error:
"The software was closed because an error occurred".