Once you hit that magical 16 thousand file mark the switch becomes incapable of accessing that folder without crashing, in Software mode you get "The software was closed because of an error" in Applet mode you just get BSOD. Once they pile up removing the SD is the only way since Windows and Linux aren't effected by the Switch's file limit.you don't even need to remove the card from console, use FTP to clear from computer, DBI or NX-Explorer to delete from console.
on latest versions of Atmosphère that folder get purged from time to time.
But can't files and folders of the same name exist at the same time? Also that wouldn't remove the sysmodule just prevent it from writing. When erpt is inhibited from writing it crashes (nasty little bugger isn't it) so this wouldn't actually solve it just cause the crashes without having files in the folder.Put SD to PC. Delete erpt_report folder, create file with the same name and set RO attribute to it.
That's just a clean up tool, doesn't actually help with the problem since the moment you forget they'll pile up and once that happens you're back to the PC.DBI now can clean that folder with the "clean orphan files" option.
Like I mentioned, maybe try to find out why so many are generated, it doesn't look normal to have over 10k error reports generated in a few months, I have a few hundret after over a year.That's just a clean up tool, doesn't actually help with the problem since the moment you forget they'll pile up and once that happens you're back to the PC.
Report the issue on Atmosphere Githubdon't wanna necro this but my chipmodded switch oled kept being stuck at the nintendo switch logo when booting CFW...
the only fix (other than constantly replacing the atmosfere folder) was to delete this cursed "erpt_report" folder and then create a empty file with the same name. i had no more boot hangs issues ever since.
the internet is full of reports of this boot problem but no one mention this fked folder. logging should be optional...
there is a issue already (github/Atmosphere-NX/Atmosphere/issues/1987) but the dev closed it with no fix. there are people saying this is intended but its beyond me how something that prevents booting the CFW is intended.Report the issue on Atmosphere Github
you are right.. the proper fix is in the KefirOS who compiled atmosphere with logging disabled. so there are no more logs crashing the system and also no crashes when checking for updates/random games trying to phone home. simply download Kefir OS and only get the atmosphere folder from that zip.. copy that to your sd card and enjoy!For what it's worth don't do that trick replacing the folder with a file. I don't know why it happens but for example accidentally enabling the network features in Pokemon Sword/Shield with Y while in air plane mode leads to a crash when erpt_reports isn't a folder. No other crash issues so far.
This is like treating cancer by taking strong painkillers. You don't feel the pain anymore, but something was causing those reports to be constantly generated. And it seems you don't want to know what was that.you are right.. the proper fix is in the KefirOS who compiled atmosphere with logging disabled. so there are no more logs crashing the system and also no crashes when checking for updates/random games trying to phone home. simply download Kefir OS and only get the atmosphere folder from that zip.. copy that to your sd card and enjoy!
i'm 100% is not a bug, never said it was a bug. its just a feature without a "off" toggle preventing my switch from booting.This is like treating cancer by taking strong painkillers. You don't feel the pain anymore, but something was causing those reports to be constantly generated. And it seems you don't want to know what was that.
Tip: It's not bug in Atmosphere.
There's already an issue for this on github by the way, Link to it here.Report the issue on Atmosphere Github
This argument only works if we don't know what's causing the errors, but we know exactly what's causing them, and that is blocking of Nintendo services. In this case the error reporting feature is causing a problem due to an error that is intentional, because it is being done to prevent having your Switch Banned (That's the point of blocking online).This is like treating cancer by taking strong painkillers. You don't feel the pain anymore, but something was causing those reports to be constantly generated. And it seems you don't want to know what was that.
Tip: It's not bug in Atmosphere.
Thank you for sharing this with us, I'm sure it'll help a lot of people. Too bad we couldn't have gotten an official solution from Atmosphere themselves but honestly something is better than nothing.i'm 100% is not a bug, never said it was a bug. its just a feature without a "off" toggle preventing my switch from booting.
i found a way to get my setup working as expected and shared it here, maybe others don't want to waste hours as I did
this was my problem as well. the logs are filled because i block nintendo crap. which ofc i block...This argument only works if we don't know what's causing the errors, but we know exactly what's causing them, and that is blocking of Nintendo services. In this case the error reporting feature is causing a problem due to an error that is intentional, because it is being done to prevent having your Switch Banned (That's the point of blocking online).