01-15-2020 11:23 AM
01-15-2020 11:23 AM
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 Edge App is noted with the old Edge logo.
We are able to select Edge and reboot. Upon reboot, the machine auto-logs in and tries to start Edge Chromium (guessing), however we never move beyond a blank blue screen.
Any idea if this is something that should be working? Or if not, when we might expect it to work?
01-15-2020 11:39 AM
@ShipUPride Thanks for letting us know! Can you please confirm which version of Edge you are using, Stable, Beta, Dev, or Canary? And if you haven't yet, can you please submit feedback through the browser so that our team has a log of the blue screen crash?
Project & Community Manager - Microsoft Edge
01-15-2020 11:57 AM
Thanks for the ping! Could you please clarify what you mean by "Kiosk Attended setup"? Which option are you using to configure Kiosk mode? Is it via the "Setup a kiosk" option in Settings, or via InTune or Windows Configuration Designer or some other method?
01-15-2020 12:04 PM
I would like you to pay attention over the history being injected in new Edge which is from chrome not from Edge. I am not able to understand how my personal data (bookmarks, history etc) injected to my work email.
My work data is lost when I migrated to the new version.
Another small bug is with the icons being bookmarked are transient , sometimes they show up and sometimes not.
When i visited the import setting I am not able to find the Edge setting.
01-15-2020 12:05 PM
01-15-2020 12:18 PM
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.
01-15-2020 12:30 PMSolution
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.
01-15-2020 06:10 PM
@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.