Installing or updating Microsoft Edge on Windows 10
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I set up loaner devices to just use the browser. I recently updated them to Windows10-2004 and installed the new Edge browser. I just get a blank blue screen when I try to sign in with kiosk mode after setting it up to open with Edge (the Icon that I am able to select still looks like the old one). Does anyone know if I need to go back to the old OS or the old Edge?
Installing or updating Microsoft Edge on Windows 10
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Hi all,
Untill last week (early july 21), on about forty of our clients we ran a edge legacy based kiosk mode that we set up with the powershell command "Set-AssignedAccess -AppUserModelId Microsoft.MicrosoftEdge_8wekyb3d8bbwe!MicrosoftEdge -UserName "kioskuser""
Unfortunately, after patching those clients, CU for Windows removed edge legacy and installed edge chromium instead. The blue screen now appeared when starting those kiosk clients.
We cleared assigned access with "Clear-AssignedAccess" and tried to set up kiosk with the powershell command "Set-AssignedAccess -AppUserModelId MSEdge -UserName "kioskuser"" (we changed the AUMID to the AUMID for Edge Chr. we found with the command Get-StartApps).
Bad news: it fails with error "New-CimInstance : One or more parameter values passed to the method were invalid....."
Our Windows Version is 20H2 (OS Build 19042.985), Edge Version is Edge Stable Ver. 91.0.864.64
Can anyone tell me wether theres a way to set up kiosk with Edge Chromium with Powershell command Set-AssignedAccess? And without Beta or Insider Preview Software, as we den't want to run this kind of software in production environments?
At the moment the only way to set up kiosk mode successfully is to do this manually via settings -> accounts -> other users -> Set up a kiosk, as we don't yet use InTune or whatever.
Thank you in advance
Norbert
I am having the same issue with the updated edge browser. When our kiosk restarts it comes up with a black screen. If I alt tab I can see the browser page and select it to bring it to the foreground. The issue is this is at a remote site and a touch screen and I have to remote into the kiosk whenever I'm notified. Which seems to be more frequent lately.
Does anyone know how to fix the issue?
This kiosk ran for years without any problems before the latest update.
Hi,
What is the current status of the new Edge in Kiosk mode (assigned access)?
I am still experience some problems with the new Edge in Kiosk mode after applying the following steps:
The screens stays black after rebooting Windows and logging into the Kiosk mode. It seems like the browser stays somewhere in the background since the thumbnail is visible when I swipe left on the screen but clicking on it only show a short flash with the browser. I found a complex workaround to make the browser visible.
I'm using a 32 bits Windows version and OS build 19043.906 and Edge version 89.0.774.68
Hey there Andrew,
We're continuing to roll out features for kiosk mode with every major release to the browser, but it is still the preview version. We've added tables to the kiosk mode documentation indicating what features have already rolled out and what features are coming up, as well as what policies are available.
Hi JamesonB87,
No updates on the full release at this time. You can keep an eye on the Roadmap at the bottom of the kiosk documentation for updates when timelines are established, but we're still working on the feature at this time - Configure Microsoft Edge kiosk mode | Microsoft Docs
Hi Alex,
Its now half way through March. Do we have a stable, released version of Windows 10 and the new Edge (both Microsoft products) that will work compatibly in Microsoft's Kiosk mode yet?
The updates of Edge and Windows broke my Kiosks devices last yearand I have had to rebuild to older versions.
I have been waiting for some time now for this issue to be resolved and don't want to be rolling out (even more) beta versions to my clients.