D
Deleted User
Guest
It is a little confusing, I agree. If "Don't relaunch OS" is set to ON, the console will not restart after the IOSU exploit happens and the CFW is launched. If "Don't relaunch OS" is set to OFF, the console will restart (and you can use the "Show Launch Image" option as well).it works thank you, but what is "don't relaunch os"? it was set on ON by default. I use the old method to start hbc through php hosting.
Theoretically, when the IOSU exploit happens, some parts of IOSU are supposed to be somewhat messed up, which could cause issues later on. Having IOSU restarted after the CFW is patched in prevents this from happening.
However, nobody has noticed any issues when they set their CFW to not restart IOSU, so really, the choice is up to you. Not relaunching the OS is faster because you're not waiting for it to restart.
However, if you do choose to restart, take note that HBL will have been unloaded, and you will have to reload it using the browser exploit or Haxchi.
I would just leave it as ON, unless you are worried about potential damage.