Forum Discussion
Windows 10 Kiosk with Edge Chromium
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.
Microsoft
Thanks for clarifying that! This option sets up the single-app assigned access configuration listed in http://aka.ms/edgekioskmode .
Unfortunately, this is not yet possible with Edge Chromium, as that option currently supports modern apps only. That said, depending on your use case, there are a bunch of possible workarounds which you could use to setup a Kiosk-like restricted environment with Edge Chromium, listed here: https://docs.microsoft.com/en-us/windows/configuration/kiosk-additional-reference. There are also some articles recently published by independent authors (IT admins mostly) that discuss how they've tried to configure Edge Chromium as a Kiosk FYI.
My colleague will respond in a minute as to why you are seeing the blank blue screen and how you can fix it.
Microsoft
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.
Thank you everyone! I'll give the recommendations a shot. Do you know when Chromium Edge may be available for use in Win10 Kiosk?
- Brian Altman
ShipUPride We are working on this scenario, but we don't have a date to share at this time. Support for the new Microsoft Edge with single-app Assigned Access requires some Windows updates, so it will take some time before we can land the full scenario. In the meantime, Microsoft Edge Legacy kiosk mode and the Microsoft Kiosk browser app remain fully supported.
Any update on this? We are hoping to use the new chromium based Edge in Kiosk mode without having to assign enterprise licenses for third party app support and so we can use the same Edge kiosk mode options from the old version. Any ETA would be helpful, we have active projects that are on pause until (new) Edge is working in native kiosk mode.
Thanks!
