spider2MW

Delete data from Aurora/Data/Database is the solution, the only thing to is to add scan paths and other settings in Aurora again 🙂

My problem is that I can‘t boot to aurora cause it scans for title updates at every boot and run into the error and I have no idea how to stop it. It is a fresh aurora and everything is fine but my mistake was to let aurora scan for new tu and that required a reboot. So there is no problem with covers or meta data or anything else. And I don‘t wanna use fsd. I just need a fix to stop the search for tu at every boot, otherwise I can‘t use aurora anymore.

I know that there were some issues with the old Aurora and different regions in the past. Afaik most problems were with the assets, I never read anything about my problem with the issue while booting within the search for new TU's. And FSD was only used to open Dashlauch in this case to set the plugin, for sure I wanna use Aurora. But for now there is no option for me to boot it up cause every time it searched for TUs and run into the issue. Only covers without videos and screenshots and active liveblock and livestrong is fine for me. So anyone here who can help me? Or is it just broken and I have to reset everything?

Hallo everyone, yesterday I've tried to scan for new TUs, but after the required restart every time the well known "Unhandled Exception" appears. Scanning for assets as is the most cases of this error was no problem. I've tried everything I found about it here: - installed the latest AuroraCrashPatcher, set it as first plugin to load with dashlaunch (I can still open dashlauch while going to the normal 360 dash after the error, open FSD3 and dashlauch with data manager from there) - enabled / disabled both liveblock and livestrong So I think the only thing is needed to tell Aurora not to scan for new TUs and boot up normally. Everything was fine including the search for assets, so the only thing is needed to stop this damn scan. Afterwards I even did not need the plugin I think. But I absolutely do not have any idea what to do. This is my second 360 and hopefully not the second one with a very rare issue after my first one had something like this with rare used ram and a crashed nand after some updates...thanks! Edit: Console from EU, I am from Germany, so no US console (not sure whether this still matters) spider2MW