Logfile "2024-11-08_13h43m45s_Runtime.log" is created at 13h43m45s, but I started SEB at 13h43m01s.

This most likely indicates an issue with your system capabilities or configuration; the startup information written to the runtime log is one of the very first operations SEB performs during startup:

# Application started at 2024-11-08 13:43:45.629

So you'd need to find out what might cause this delay on your system (e.g. an issue with the .NET Framework installation, or (overly) restrictive security software or configuration etc.).

Another real possibility could be an issue with Windows itself, as you stated above that 3.8 works perfectly fine under Windows 11 version 23H2...

Maybe this helps to find the problem
When I install SEB Build 3.8.0.742 on 24H2 the start is delayed for 40+ seconds
When I install SEB Build 3.8.0.711 (BETA) it almost starts immediately

Thank you both for your quick response! It's clear that it is due to a combination of our 24H2-installation and SEB 3.8.742. Because in the meantime we tested on an older Latitude 3310 and on both clean 24H2-install and Intune enroll, we were thinking new incompatibility between the two. Also because the SEB-process starts immediately but the logging 43 seconds later.
But, I just read you referring to .NET while beside me Widows shows me an update for .NET 3.5/4.8.1 (KB5045934). I will try the update at first and will try the 711-Beta after that for sure! Thanks! I'll keep you posted!

Maybe this helps to find the problem
When I install SEB Build 3.8.0.742 on 24H2 the start is delayed for 40+ seconds
When I install SEB Build 3.8.0.711 (BETA) it almost starts immediately

If you would happen to be able to find a particular commit resp. build where the issue starts to arise (e.g. from 711 to 712), then we could have a closer look at those particular changes and whether they could have negatively impacted the startup procedure.

Until then, the symptoms point to a local issue with the system capabilities and/or configuration as explained above (otherwise we would have a lot of issue reports regarding this problem).

Does anybody know how many builds there are between 3.8.0.711 and 3.8.0.742 or/and where to find them?

They can be found on our build server, see https://sebdev.ethz.ch/project/appveyor/seb-win-refactoring/history.

SEB starts after 6 Seconds in 3.8.0.719 and after 40+ Seconds in 3.8.0.720
Tested multiple times on a HP Probook 440 G11 with a clean W11 install
Windows 11 Education 24H2
Build 26100.2033
Windows Feature Experience Pack 1000.26100.23.0

Update .NET didn't fix the issue unfortunately, but SEB 3.8.711 starts up a lot faster then 742, but looks very unstable. As version 3.9.941 has the same delay, I will test several versions between 711 and 742, and I'm also curious what versions 3.8.0.683 (first 3.8-version) and 3.7.634 (first 3.7-version) have to offer me. Thank you all for your time, I'll keep you informed.

SEB starts after 6 Seconds in 3.8.0.719 and after 40+ Seconds in 3.8.0.720 Tested multiple times on a clean W11 install Windows 11 Education 24H2 Build 26100.2033 Windows Feature Experience Pack 1000.26100.23.0

I just read your results, @AerisEverlast ! I'll take a look at both!!!

SEB starts after 6 Seconds in 3.8.0.719 and after 40+ Seconds in 3.8.0.720 Tested multiple times on a clean W11 install Windows 11 Education 24H2 Build 26100.2033 Windows Feature Experience Pack 1000.26100.23.0

I just read your results, @AerisEverlast ! I'll take a look at both!!!

Well that's clear: 719 starts after 5-6 seconds or so, 720 takes more than 40 seconds as you mentioned. I will compare these two next monday, so no progress in the next two days, sorry.

Version 3.8.0.720 until 3.8.0.742 starts after +40 seconds
Version 3.8.0.743 until 3.8.0.762 start after 6 seconds
Which version is our best option? (most stable release?)
Or do I wait for the official release of 3.9?

Version 3.8.0.720 until 3.8.0.742 starts after +40 seconds
Version 3.8.0.743 until 3.8.0.762 start after 6 seconds

Versions 3.8.0.742 and 3.8.0.743 have literally the exact same code base, the latter is merely another build due to the release branches we create. So there is definitely something else involved here, none of this appears to make sense to me thus far...

Which version is our best option? (most stable release?)

None, these are all potentially unstable development builds which shouldn't be used in a production environment.

Are any of you by chance using ARM devices? I have encountered a startup delay when testing SEB on a Windows ARM machine (see #1024) which however can be worked around by using the 32-bit (x86) build of SEB, at least for the time being.

We have X64 devices No ARM
Can we Use 3.8.0.743 if it's the exact same code?

The .msi from 3.8.0.743 is 1Mb smaller than 3.8.0.742....

Can we Use 3.8.0.743 if it's the exact same code?

Yes, that should be okay, but still at your own risk.

Isn't it all on own risk? ;-)
Thx Damian
Our Exams start 1st of december
We're looking forward to version 3.9

The .msi from 3.8.0.743 is 1Mb smaller than 3.8.0.742....

The difference on disk appears to be a few hundred kilobytes:

I thought maybe 390Kb of textcode could make the difference...

Anyway Once again thank you for your quick reply's

Again, the code is exactly the same. From where the difference stems is unclear to me, may be (one of the many) peculiarities of Windows Installer...

Hi all, thanks for your time again. I'm still testing, reinstalling and analyzing different installs and behaviour, but did not find any clue what makes the delay. (is that proper English?) No ARM over here, btw. To be contunued...

Could all of you please verify whether the issue persists with the 32-bit (x86) build of version 3.8.0? To do so, manually uninstall SEB via the system control panel and then install the 32-bit MSI setup: https://github.com/SafeExamBrowser/seb-win-refactoring/releases/download/v3.8.0/SEB_3.8.0.742_x86_Setup.msi.

After uninstalling 3.8.749x64 and installing 742x86, SEB starts up with a small delay (could be 5-7 seconds) on the first time, but can't start a client-session. Client-log says, after line "INFO: [BrowserApplication] starting initialization...": "ERROR: Caught unexpected exception while performing operation 'LazyInitializationOperation'". The second time SEB starts almost immediately, but with the same error.
Because I used this Windows-install already to test 743 to 749, I'll re-install Windows again to be sure there's nothing left from other installs.

After a clean install of Windows unfortunately same result: start-up in 5-9 seconds followed by an error. See logfiles for more details. Sorry.
2024-11-21_08h59m37s_Client.log
2024-11-21_08h59m37s_Runtime.log

For your information: install of 743 to 749 in new Windows-environment (without uninstall): normal startup with 743 to 748, delayed startup with 749. Besides that I noticed in Taskmanager the SafeExamBrowser-process lists under "Background processes" during the delay and appears under "Apps" when the splash-screen pops up.

I am wondering @dbuechel, do all verions of SEB startup normal on your systems using 24H2? Which version(s) do you use of Windows and other software that SEB uses or SEB depends on?

Installed a new (clean) Win11 24H2.
First installed the x64 bit .exe 3.8.0.742 version --> 2min 5 sec every time
manually uninstalled via control panel
and installed 32bit 3.8.0.742.msi --> 3 sec
HP Probook 440 G9
12th gen i5-1235u 8Gb Ram
Type x64 processor
Hope this helps to find the issue.

I will test the (x86).EXE for 3.8.0.742

Thanks both for the testing, that is actually good news, as now we know that it is an issue with the 64-bit build of SEB. We are following up on this internally and will let you know as soon as we know more.

For the meantime, you should thus be able to use the 32-bit (x86) build of the official release version as a workaround.

@CompaenVMBO The MSI setups do not automatically install all the required runtime dependencies (as does the setup bundle [.exe]). You'll thus need to make sure that all the runtime dependencies listed in the release notes are installed for the 32-bit platform. In your case particularly, I assume the issue is a missing / incorrect version of the 32-bit Visual C++ Redistributable.

I am wondering @dbuechel, do all verions of SEB startup normal on your systems using 24H2? Which version(s) do you use of Windows and other software that SEB uses or SEB depends on?

We could only reproduce the issue on our ARM testing device with Windows 24H2. I myself am still running on Windows 10, but every release undergoes our internal end testing on various different machines running Windows 10 and 11 (as far as I know).

Can't we use the .exe from x86

Can't we use the .exe from x86

No, that is the setup bundle and will install the matching build depending on your platform, i.e. SEB (x86) for 32-bit systems and SEB (x64) for 64-bit systems respectively.

My uni have been on Win 11 23H2 and SEB 3.5 x64 for a while. Upgraded a test machine to 24H2 with SEB3.8.742 x64. SEB takes about 1-2min to start within Edge.

23H2 with SEB 3.8.742 x64 no issues when starting within Edge.

Describe the Bug
SEB 3.8.0.742 x64 when starting within Edge (Inspera exam) it takes 2min.

Steps to Reproduce
Steps to reproduce the behavior:

Go to Start-Menu
Start Edge
Go to Inspera login -> login
Start Exam -> SEB launches -> takes 2min to start

Expected Behavior
SEB should start within a couple of secs.

Screenshots
If applicable, add screenshots to help explain your problem.

Version Information

OS: Windows 11 Education 24H2
SEB-Version 3.8.0.742 x64
HP EliteOne 840 G9 AiO

Additional Context
2024-12-06_14h23m04s_Browser.log
2024-12-06_14h23m04s_Client.log
2024-12-06_14h23m04s_Runtime.log

The issue does not exist with SEB 3.5.0.544 and Win 11 Edu 23H2
The issue does not exist with SEB 3.8.0.742 and Win 11 Edu 23H2
The issue does not exist with SEB 3.9.0.765 x64 BETA and Win 11 Edu 24H2
The issues does not exist with SEB 3.8.0.742 x64, Win 11 24H2 Edu on HP EliteOne 800 G6 AiO

@CompaenVMBO @AerisEverlast @ryeshack @AndreasB-MAU Could you please provide us with an e-mail-address where we can contact you directly? You may send us an e-mail under info (at) safeexambrowser (dot) org or any other way you see fit.

Mail sent

I have just sent an e-mail to all, please do let me know in case you haven't received it or alike.

We are experiencing the same issue with SEB 3.8.742 x64 and Windows 11 24H2 (Home, Pro, and Education). The startup time for SEB sometimes exceeds one minute. Is there already a solution or a working version for this combination? Thanks

@ITNKSA Please provide us with an e-mail-address as specified above.