This setting doesn't seem to work if the computer is restarted in between closing and opening Directory Opus. If I manually exit via File > Exit Directory Opus and then re-open Directory Opus the previous session is restored just fine, but this doesn't work at all if I want to restart the system. This has caused me to lose a complex session I had open a couple times now. Windows Explorer's "restore previous session…" setting works just fine.
Also would be nice if this setting was also able to restore crashed sessions in the same way for an example Chrome can (if you just press Ctrl+Shift+T for each window that was open earlier after starting Chrome again). Some sort of persistent caching of the previous session state is very much needed in Directory Opus so that the context isn't just seemingly lost entirely so easily.
The lister windows are still open when I exit Directory Opus, whether explicitly via the File menu, or implicitly by Windows shutting it down upon shutdown. I tested it and the setting works sometimes, regardless of whether I exit Directory Opus explicitly or implicitly as described. The fact is though that if it doesn't work reliably, the setting effectively cannot be trusted so it's not useful at all.
Directory Opus is set to launch on startup in my configuration.
The information is saved to /dopusdata/Layouts/System/default.oll, it might be worth having a look at that file after a shutdown/rerun and a shutdown/restart to see if the file date is changing or the file is being deleted. In the past we've had a weird problem with someone's antivirus that was deleting/modifying Opus data files.
Thanks for the info, that sounds useful. I'll keep it in mind the next time I run into this issue, so that I can hopefully through that recover the previous session. Also I don't have any extra antivirus software (other than Windows' built-in Defender) installed, or any other software like that to my knowledge would mess around with external data like that, nor anything else configured that I can think of that would cause such an issue. (Running on Windows 10 22H2 fwiw).