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.
Microsoftedgebrk , what issue(s) are you running into when configuring the new Edge as single app kiosk using PowerShell command line?
Powershell script i am running
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
