search

SafeExamBrowser / seb-win-refactoring

Safe Exam Browser for Windows.
https://www.safeexambrowser.org/news_en.html
Mozilla Public License 2.0
188 stars 126 forks source link

Startup SEB v3.8 delayed by 40+ seconds using Windows 24H2 #1023

Open CompaenVMBO opened 1 day ago

CompaenVMBO commented 1 day ago

First of all I'm brandnew on Github, so if I do anything the wrong way, please let me know :-) We upgraded SEB from version 3.6 to 3.8, because laptops are using Windows 24H2. Unfortunately we discoverred unsuspected behaviour starting SEB.

Describe the Bug After starting SEB v3.8, it can take up to 50 seconds before it starts up visibly e.g. the splash-screen appears.

Steps to Reproduce Steps to reproduce the behavior:

  1. Start SEB

Expected Behavior I'm used to a maximum delay of around 5 seconds, before the splash-screen appears.

Screenshots Not applicable.

Version Information

Additional Context Logfile "2024-11-08_13h43m45s_Runtime.log" is created at 13h43m45s, but I started SEB at 13h43m01s. Logging also starts at 45s. The problem occures on systems (Windows + SEB) deployed and controlled by Intune, but also on systems with Windows installed by MS-ISO and Bundle-download of SEB. The SEB-proces starts up immediately after starting SEB, by the way, using 15-25% CPU for the first 5-10 seconds. After that, CPU drops to 11% until splash-screen. It's easy to spot several delays in the Runtime-log, but we cannot explain (and solve) it. Help.

Other situations compared: 3.6/24H2: SEB/24H2-incompatibillity 3.6/23H2: average of 5 seconds startup-delay 3.8/23H2: average of 2 seconds startup-delay

2024-11-08_13h43m45s_Client.log 2024-11-08_13h43m45s_Runtime.log

dbuechel commented 1 day ago

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.).

dbuechel commented 1 day ago

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...

AerisEverlast commented 1 day ago

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

CompaenVMBO commented 11 hours ago

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!

dbuechel commented 8 hours ago

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).

AerisEverlast commented 6 hours ago

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

dbuechel commented 5 hours ago

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

AerisEverlast commented 4 hours ago

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

CompaenVMBO commented 4 hours ago

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.

CompaenVMBO commented 4 hours ago

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!!!

CompaenVMBO commented 4 hours ago

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.