question

GladdingMark-6551 avatar image
0 Votes"
GladdingMark-6551 asked Sean-Liming commented

Shell Launcher shows black screen before application starts

We have customised our WIndows 10 IoT Enterprise (1607) OS image to boot into the custom Shell Launcher rather than the standard Windows desktop. The Shell Launcher successfully runs our application and there are no UI elements with Windows branding displayed.

However there is a long period of time (~15-20 seconds) during which a black screen is displayed. This time occurs after the BIOS splash screen disappears and prior to our Application being launched (launching our application takes <1sec).

The boot sequence we observe is as follows:

  1. BIOS splash screen is displayed (~5-10 seconds).

  2. Black screen is displayed (~15-20 seconds).

  3. Application UI is displayed

This behaviour is very disconcerting to a first time user of our device as it appears the device has shut itself off during power up.

Is there a way to configure the OS so the BIOS splash screen remains visible until the Application UI is displayed (i.e. eliminate the black screen)?




windows-10-setupwindows-iot-10core
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

I experienced the exact same behavoiur.

The issue occured after switching from
1607 to 1809

Have you found a solution for this?

0 Votes 0 ·
CarlFan-MSFT avatar image
0 Votes"
CarlFan-MSFT answered GladdingMark-6551 commented

Hi,
Did you set up kiosk mode and sign in with the kiosk account (a local standard user account) ? Has the system been activated?
According to your description, you may check the permisson. Just like the information below:
https://stackoverflow.com/questions/39613612/diagnosing-why-a-custom-shell-on-windows-10-iot-gives-black-screen

Hope this helps and please help to accept as Answer if the response is useful.
Best Regards,
Carl

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi Carl,
I don't believe we are using kiosk mode as such.
We have enabled the Shell Launcher to launch our application directly, rather than loading the desktop.
The account we use is a local standard user account.
The system has been activated.

The issue is not that our application fails to launch but that there is a period of time (~15-20 seconds) during which a black screen is displayed prior to the Application starting.

Is there a way to configure the OS so the BIOS splash screen remains visible until the Application UI is displayed (i.e. eliminate the black screen)?

Regards,
Mark.

0 Votes 0 ·
Sean-Liming avatar image
0 Votes"
Sean-Liming answered Sean-Liming commented

Is it safe to assume that you have the embedded-boot and embedded logon components enabled to hide Windows elements and autologon?

  1. If you are using UEFI boot, you can put an image in the firmware that will stay visible through the OS load stage.

  2. Using group policy, you can set the logon background screen to shows something while the system auto logs into the shell application

Computer Configuration > Administrative Templates > Control Panel > Personalization ->"Force specific lock screen and logon image"

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Did you look into my suggestions?

0 Votes 0 ·