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.
Single App = You have to change from Application type: "Add Microsoft Edge Legacy browser" to "Add Microsoft Edge browser". - This is a new feature, so be aware of this change.
Multiapp = Still only support för Edge Legacy to add through Intune interface. Instead you need to "Add Win32 app".
AUMID/PATH = C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe
DesktopApplicationId/AUMID for the Win32 app = MSEdge
And you need your KIOSK to be updated to 20H2 for this solution it seems 🙂
Microsoft
Glad you were able to figure out the cause! 🙂 Yep, the new Edge has a separate entry and the "old" Edge is now shown as the "Edge Legacy" entry in InTune and this change was recently rolled out in InTune.
Multi-app has supported the new Edge ever since new Edge was released - as multi-app supported Win32 apps too.