Show actual error message insted of pointing to obscure log files.

[gitterdude]

When SEB aborts with an error the user sees a text (which IIRC can't even be copied and pasted) suggesting to have a look in AppData\Local\SafeExamBrowser\Logs...
AppData is a hidden folder, so the user can't easily get to it using the Explorer and the log files are usually not that easy to read and understand for the random user.

The error message displayed to the user should be the error which caused the program abort.
It should for instance say "Dual monitors detected and only the internal one is allowed" instead of "If you're lucky you may be able to find the error in a log file that's in the bottom of a locked filing cabinet stuck in a disused lavatory with a sign on the door saying 'Beware of the Leopard'"

[dbuechel]

With respect to the display monitoring and other important aspects, there actually is a specific error message revealing all required details. There are however a wide range of possible causes which could lead to a startup failure, and we unfortunately can't write a custom dialog for each and every one of them.

Thus, please provide a concrete request regarding which error case you'd like to have covered and then we can investigate further. As this particular error (regarding the runtime integrity of version 3.10.2) however pertains to security-related aspects, there is a certain trade-off which we have to make between revealing some but not too much information.

[gitterdude]

Yes, the log file usually explains the error fairly well but it's not that easy for an ordinary user to locate that file and then sort through all the log entries to eventually find the error.

In addition to writing the error to the log I would think it could be written to a program variable as well and then presented in the "Session start error" window instead of or in addition to "Please consult the log files at c:<user>\Appdata...."

You're already telling the user where to find the error, which means that the ones who may be interested in using that info to try and circumvent the program know where to find it. I presume that people interested in those things also know how to click "Show hidden folders" in the Explorer settings.

I had a teacher spending half an hour trying to show the students what an SEB test looked like only to having it constantly crashing.
When she came to me after the class I saw that "Dual monitors not allowed" error in the log file; she had attached a projector to show the students her screen.

So at least that error, the one where SEB can't shut down Windows Update and the one where files are missing from the installation ( #1078 (comment) ) would be nice to see in the "Session start error" window.