A dev might be able to say more, but Exception code: 0xe0434352 is hugely vague, according to a web search. It’s an unhandled exception, but a stack would hugely help.
I think this release tries to make a Duplicati-crashlog.txt file in the serverdatafolder that typically also contains the server and job database. Latter is visible in Database screen.
Possibly the “Direct restore” folder is different though. Do you have “Everything” search?
That’s a nice way to almost instantly search for files, looking on the whole drive via MFT.
If that doesn’t work, it looks like it writes the exception to the terminal if you launch there with the command name and your usual options. More extreme would be to run full CLI, because one can recreate the database there, and that might be what crashes TrayIcon.
I think this DB is recreated only enough to give you the dates, then it does more later.
Normal database recreate recreates a DB with all versions of all files, so takes longer.
Certainly you could test that route with lots of logging, but let’s hope for an easier clue.