Implement Edge Chromium support in Kiosk mode ("Assigned Access" in Windows 10)

Copper Contributor

Implement Edge Chromium support in Kiosk mode ("Assigned Access" in Windows 10)

Hi, you can implement Edge Chromium support in Kiosk mode ("Assigned Access" in Windows 10)

We currently have an intranet in which it generates several errors in MicrosoftEdge mode with EdgeHTML in assigned access Kisoco mode and it would be helpful to have compatibility with the new Microsoft Edge Chromium in assigned access kiosk mode.

Thank you.

14 Replies



This will probably be a feature the new browsers can support when we get out of the preview channels,

to more stable releases like Beta or after.


Thanks for your feature request,




Are there any Updates to this feature?

I'm interested in this too. Would be great to be able to use the Chromium features in this build to install the add-ins that we use for digital signage (The Revolver add-in allows us to switch between two web page tabs every 30 seconds / regular Edge in kiosk mode only shows tabs statically)

You can use w32 Applications with assigned access. That should´t be any problem. Only the new edge browser ui isn´t optimized for it. You would need to whitelist your URLs so that users can´t reach out to other sites. For an intranet maybe good enough?

@V-FRROME Any updates on this? Chromium Edge will be rolled out soon and we also want to use Kiosk Mode with new Chromium Edge?

Hi all, our dev team needs the chromium version to be running on Kiosk mode.

Why? Edge doesn't follow the SVG standards and it is a MUST for our app.


Any update? any help on how to run Edge Chromium on W10 kiosk mode?


Thanks in advance.


Need this feature too. We have currently a few devices running the MS Edge legacy with it's crappy engine. On webpages the touch input like drawing is not working.


Looking forward that the MS Edge Chromium in the Assigned Access may fix this issue natively.

Needed also by our organization! Guess what will happen if you have some client with Kiosk mode enable and the browser is automatically updated...
It breaks. I can't imagine the headache this is going to cause as more and more kiosk mode machines auto update to Chromium Edge. This is an enormous problem that Microsoft should have addressed before release.

I successfully authorized MS Edge Chromium Stable in a multiapp kiosk mode on Windows 10 1909.


Here is an example of the configuration I used:

<?xml version="1.0" encoding="utf-8" ?>
xmlns="<a href="" target="_blank"></a>"
xmlns:v2="<a href="" target="_blank"></a>"
xmlns:v3="<a href="" target="_blank"></a>"
<Profile Id="{UUID}">
<App DesktopAppPath="%PROGRAMFILES (X86)%\Microsoft\Edge\Application\msedge.exe" />
<App DesktopAppPath="%PROGRAMFILES (X86)%\Microsoft\EdgeUpdate\MicrosoftEdgeUpdate.exe" />
<App AppUserModelId="Microsoft.Windows.Explorer" />
<v2:AllowedNamespace Name="Downloads"/>
<![CDATA[<LayoutModificationTemplate xmlns:defaultlayout="<a href="" target="_blank"></a>" xmlns:start="<a href="" target="_blank"></a>" Version="1" xmlns="<a href="" target="_blank"></a>">
<LayoutOptions StartTileGroupCellWidth="6" />
<defaultlayout:StartLayout GroupCellWidth="6">
<start:Group Name="Kiosk">
<start:DesktopApplicationTile Size="2x2" Column="2" Row="0" DesktopApplicationLinkPath="%APPDATA%\Microsoft\Windows\Start Menu\Programs\System Tools\File Explorer.lnk" />
<start:DesktopApplicationTile Size="2x2" Column="0" Row="0" DesktopApplicationLinkPath="%ALLUSERSPROFILE%\Microsoft\Windows\Start Menu\Programs\Microsoft Edge.lnk" />
<Taskbar ShowTaskbar="true"/>
<DefaultProfile Id="{UUID}"/>


I'm not certain that "%PROGRAMFILES (X86)%\Microsoft\EdgeUpdate\MicrosoftEdgeUpdate.exe" is needed but I think it may be used to update Edge Chromium since it does not update via Windows Update, like the old Edge.


Note that I did try via AppIDs (MSEdge and Microsoft.MicrosoftEdge_8wekyb3d8bbwe!MicrosoftEdge) but it did not seem to work.


As for the single app Kiosk mode, it should work similarly.



@FrenezOrg thanks for the feedback, at least we have something which probably will make it work.


However, I think that most of us would like to choose Edge Chromium through other set-up methods than a provisioning package. For example, I usually configure Kiosks through the local Settings app, and I would like Edge Chromium to be selectable within the list of apps that can run when the kiosk account signs in. The "old" Edge has been added to the list only with Windows 10 version 1809, with further specific settings; I have not tried yet, but I guess the "new" Edge is currently not available in the list of apps!

Hello @FrenezOrg

Thanks for the XML config! Will surely try it on MultiApp.

I'm currently having fun with SingleApp kiosk and tried default XML config with Edge Chromium and it didn't work. I'm pretty sure because of new Edge is not Windows App, it's just normal exe app - and SingleApp kiosk supposed to run only Windows App.

I wonder what engine Kiosk Browser is based on...


If you want to open a website in kiosk mode from an app simply use the Chrome command


eg Proc = Process.Start(browser, "--kiosk" + Msg)


where browser is the path to Edge Chromium exe

Choosing Edge Chromium while setting up a kiosk on Windows 10 is finally possible with Windows 10 20H2 (Insiders) and Edge 87. Support for older Windows 10 versions (1909 and up) as well as feature parity with Edge legacy for kiosk-related features should come early 2021 (my guess is before March 9, when support for Edge legacy will be over).


Useful resources: