Chrome --load-extension / --load-unpacked Arguments Not Working Inside Safe Exam Browser (SEB)

[Baskar5532]

We are launching Google Chrome through Safe Exam Browser (SEB) using the Applications configuration and passing Chrome command-line arguments such as:

--load-extension="C:\Path\To\Extension"
--load-unpacked="C:\Path\To\Extension"

These arguments work correctly when Chrome is launched normally outside SEB, but when launched through SEB, the extensions do not load. There is no error shown; the arguments appear to be silently ignored.

Questions / Clarifications Requested:

Is SEB intentionally blocking --load-extension and --load-unpacked arguments?

If yes, is there any supported or recommended alternative to load Chrome extensions while using SEB?

Are there SEB-approved mechanisms (API / configuration / signed extensions) to achieve similar functionality?

Is this restriction configurable or permanent by design?

[dbuechel]

SEB does not block anything particular to Google Chrome (or its extensions), but the application logs may indicate potential issues. You may also want to try kiosk mode "Disable Explorer Shell" instead of the default "Create New Desktop".