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
I've been trying to run KIOSK through Intune, with W10 20H2, but Edge will not run. It says the application cannot be started.
This is a newly installed computer, and I'm running a "Single app" profile.
Nothing fancy..
I've read about tons of ppl having the same issue with 20H2.
What can I do about it?
- Kelly_Y
Hi Everyone! In an effort to ensure that everyone is addressed for their individual needs and questions, please start a new discussion for each separate kiosk mode issue. Thanks!
-Kelly
- Raj_GS
Thanks! The new Edge is Win32-based and so, Set-AssignedAccess cannot be used to configure it as kiosk app, as that command only works with UWP apps.
To configure Edge as single app kiosk with Assigned Access, you'll have to use WMI Bridge solution: https://docs.microsoft.com/en-us/windows/configuration/kiosk-mdm-bridge. Look for the Powershell samples linked from that page too.
Cc: @edgebrk
Set-AssignedAccess -AUMID Microsoft.MicrosoftEdge.Stable_8wekyb3d8bbwe!MSEDGE -UserName $usrname
Application was not found. Enter either a valid AppName or AUMID
At C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules\AssignedAccess\AssignedAccess.psm1:288 char:17
+ throw $SCStringTable.ErrorAppNotFound
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OperationStopped: (Application was...ppName or AUMID:String) [], RuntimeException
+ FullyQualifiedErrorId : Application was not found. Enter either a valid AppName or AUMID- Raj_GS
I have not tried this option myself, so would relay this back to some experts who may know better. But in the meantime, some dumb questions:
1. I hope you are trying "-AppUserModelId" as in the docs and not "-AUMID" as you mentioned in the post?
2. Are you also supplying the user name/SID via the options mentioned in the docs when using the "Set-AssignedAccess" command line?
This is the doc I'm referring to in the above: https://docs.microsoft.com/en-us/windows/configuration/kiosk-single-app#powershell
- Raj_GS
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.
- I am trying to create a single app kiosk mode using PowerShell cmd Set-AssignedAccess -AUMID MSEdge this command not accepting it.
- Solution!
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 🙂
