Forum Discussion

Copper Contributor

Jan 15, 2020

Solved

Windows 10 Kiosk with Edge Chromium

We are testing Windows 10 Kiosk Mode with the new Edge Chromium Browser as the app to launch in full screen mode. Edge Chromium is installed and working, however in the Kiosk Attended Setup, the Edg...

Brian Altman
Jan 15, 2020
ShipUPride ,

The Windows 10 Settings, Accounts, Assigned Access sets Microsoft Edge Legacy as the browser for your kiosk device. When the new version of Microsoft Edge (Chromium based) Stable channel is installed, Microsoft Edge Legacy is hidden and all attempts to launch Microsoft Edge Legacy are redirected to the new version. For more details see Access Microsoft Edge Legacy after installing the new version of Microsoft Edge and Windows updates to support the next version of Microsoft Edge.

The reason you’re seeing the blue screen is because Assigned Access is trying to launch the new version of Microsoft Edge, which is not currently supported in this scenario. To continue using Microsoft Edge Legacy kiosk mode deploy the Microsoft Edge Allow Microsoft Edge Side by Side browser experience policy, set it to Disabled. The Configure for Windows article has instructions on downloading the Microsoft Edge policy template and setting a policies.

Let me know if you have any further issues or question.

Cyph3r

Copper Contributor

Nov 02, 2020

We've just upgraded to Windows 10 20H2 last week, then our kiosk machines stopped working. Only showed blue screen (not BSOD). We're running Microsoft Edge browser app on our customer facing Kiosk machines. It's a shame, this should have been fixed before 20H2 was released. Would be great to get more app options when running in kiosk mode.

JSTFL

Copper Contributor

Nov 03, 2020

Cyph3r it is a shame that they did this, but can confirm that we managed to uninstall Chromium Edge and then do the registry changes to block Chromium Edge from downloading in 20H1 (I should imagine still possible in 20H2?) - it's a bit of a pain, why Microsoft did this without having Kiosk Mode support first is beyond me . . .

Adrian_Guta
Former Employee
Nov 06, 2020
As mentioned in my latest post Windows 20H2 doesn't have Legacy Edge and the side by side experience (registry keys) won't work.

"Starting with Windows 10 version 20H2 Microsoft Edge Legacy is no longer included. Starting with this version of Windows 10 the side-by-side experience is not supported."
More details here: https://docs.microsoft.com/en-us/deployedge/microsoft-edge-sysupdate-access-old-edge#before-you-begin
zigat
Copper Contributor
Nov 03, 2020
Hi, does anyone know, why we have problems with implementing any web browser (edge, explorer, google chrome,..) in kiosk mode. We are doing through Windows configuration designer tool, with a provisioning package, and every time when we start a kiosk account we get a blue screen or an error, it's not possible to open your app 0x80070057.

Thank you for your reply.

BR, Z