The general problem is that Windows is a messy operating system where developers cannot rely on even basic frameworks to work correctly. Ask professional system administrators and they will confirm this. We are nevertheless working constantly to improve SEB. As this software is free and our resources limited, feel free to contribute to its development by joining the SEB Alliance (or convincing your exam organizing body to do so).

I totally understand and do not envy you. I do appreciate the work you do and, from what i can tell so far, I do like the working product after a fresh windows install. I just hope this to be helpful at some point. So thank you!

Thank you for your understanding. It definitely is disappointing (also for us) that such issues happen depending on the state of the Windows installation and that there doesn't seem to be a reliable way to install the software so everything works without manual fixes. I assume that this happens more often to .NET applications (less to Win32, UWP, WinRT ?) and maybe because we're using not so common frameworks, but that's just a speculation and what some system administrators told us. @dbuechel might know more about that. We will definitely investigate issues further if we have some leads how to fix those and any feedback is welcome.

I also think it is very much likely an issue with privileges. But I have not found a way to check or change any privilege directly connected to these "named pipes". If you know where to change those I could try that. And report my findings.
Otherwise I currently have no resources or desire to dig deep into the windows docs. 😬

@dbuechel might have more information about this, he can contact you in February when he's back from his leave. I remember a case when actually a very old SEB version had a generic name for the named pipe it's using, which then interfered with another application which was also using named pipes. That issue was then solved in SEB, but it showed that the named pipes system can be broken by some app which doesn't use it properly.

The issue with the name conflict for the pipes definitely has been resolved with SEB 3.x, see https://github.com/SafeExamBrowser/seb-win-refactoring/blob/master/SafeExamBrowser.Configuration.Contracts/AppConfig.cs#L27 (unless there is another software using "safeexambrowser" in their pipe address...).

However, as already correctly mentioned above, Windows is a huge ecosystem with myriads of different possible hardware and software configurations. Given the extremely limited resources we have, we simply cannot guarantee that SEB works without issues on all of them. There may be software (e.g. anti-virus software, screen recording or meeting software, mods etc.) which interferes with SEB, there may be system-wide configuration options which interfere with SEB, there may be system management software on managed devices which interfere with SEB and so on. And, if I may hazard a guess, sometimes if not often there are end users wrecking their system or its configuration by not really knowing what they are doing when e.g. changing a system configuration parameter, installing or uninstalling software and what not.

Attempting to solve an issue like this one remotely is pretty hard, and any success in doing so is completely depending on the information we get provided. The more accurate and complete an issue report, the more likely we're able to actually reproduce and then attempt to fix the problem. However, there really are issues which simply cannot be resolved without being physically in front of the system where the problem occurs, and I'm afraid this might just be one of these rare issues.

I'd happily try to investigate the issue further, but therefor I'd at least need the following information to do so meaningfully:

1. A screen recording showing the entire boot procedure up and until starting SEB and encountering the error message.
2. A list of all installed software on the system with the issue.
3. A list of all actually running software and utilities when SEB is attempted to be started.
4. All Windows event logs.
5. All SEB logs.

Closed due to lack of feedback.

We do have the same issue on a computer with windows 11. Is there a possibility to get a more detailed log?

2024-04-05_13h35m25s_Client.log
2024-04-05_13h35m25s_Runtime.log

@JA-HTL There might be additional information in the system event logs (using the Event Viewer application), specifically under "Windows Logs" > "Application").

We most unfortunately have thus far not received any meaningful event log entries nor were we able to determine what the underlying cause might be.

The problem ist on a students laptop, I try to get the logs from him. In the meantime I have a video of the starting process, maybe that helps a little

@JA-HTL Thanks for the video, though it would be great if you could record the entire startup procedure (from where and how SEB itself is being started etc.).

Please use issue #824 for all further discussion.