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.
I'd like to give my 2 cents.
We have several PC's in KIOSK mode that are no longer working because of both the 20h2 update and the latest Edge update. It gives me a blue screen indicating that the application (New edge) is not supported under Kiosk mode.
I have had to uninstall 20h2 and the newer version of Edge to get these to work again. Unfortunately, the Payroll website that we have these setup for, is telling me that their site will no longer support Legacy Edge starting March 11th, 2021.
So I do hope you come up with a fix so I can run the latest Windows 10 feature, with the latest Edge version in KIOSK mode. Seems silly that this wasn't tested ahead of time.
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.
- Help appreciated configuring edge chromium as single app kiosk mode using PowerShell command line other than Manual configuration
Raj_GSMicrosoft
edgebrk , 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
Thank you for the explanation. I'm a little confused on Assigned vs. Non-Assigned comment. I don't see an option to setup a KIOSK using "Non-Assigned" access. Even a Google search doesn't show anything.
I did a fresh install, so I have to think the H
As of now, I will just wait for the update so that I can be fully protected.
- Raj_GSmikepickardtubeproc, hope you had a chance to evaluate our new kiosk offering based on the articles shared by Adrian and Nicolò. Let us know in case you still have questions!
mikepickardtubeproc thank you for the email.
Our recommended approach is using assigned access: https://docs.microsoft.com/en-us/deployedge/microsoft-edge-configure-kiosk-mode#configure-using-windows-settings
The assigned access changes will be available with the Windows update 2c February release, that was previously shared.
I am not sure if there is more information to share on this sentence: "I did a fresh install, so I have to think the H..."
Non-assigned access, refers to other ways to locking down the OS, like shell launcher or custom shells. For e.g. shell launcher: https://docs.microsoft.com/en-us/windows/configuration/kiosk-shelllauncher
