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.
mikepickardtubeproc Thank you for the email and feedback.
I have a few questions:
In what Windows configuration are you running kiosk mode? (assigned access or non-assigned access?)
Did you configure the newer version of Edge before moving to Windows 20H2?
Windows 20H2 supports the new Microsoft Edge kiosk mode configuration.
From the details of the problem you shared, I believe you are using assigned access kiosk mode. if that is the case then we will be releasing soon a Windows Update to enable assigned access to configure Microsoft Edge Chromium (Win32 app).
You can test these changes right now with a Windows Insider Preview: https://docs.microsoft.com/en-us/deployedge/microsoft-edge-configure-kiosk-mode#configure-using-windows-settings
Let me know if there is anything else I can help with.
