Multi-app kiosk mode now available in Windows 11!

Finally, has been waiting Windows 11 support for Kiosk´s for so long... Great to see some progress, hopefully Intune support will be coming fast as then could update our Win 10 Multi-app Kiosks finally to Win 11

Is there an ETA when this is coming to MS Intune? We really really need this mode in our environment!

Unfortunately with the current kiosk template a lot of functionality is missing/or just not working (you cant import a .json startlayout for example, microsoft edge wont start because of permission problems, etc.)

Hi sydbruck, Heather_Poulsen,

is there an official release date for Intune support for multi-app kiosk mode in Windows 11?

Kindest regards

Leon Pavesic

The Kiosk Mode in Windows 11 is broken, tested on 24H2

a) File Explorer and Edge Icon are generated on the Taskbar, even if they are not configured
b) File Explorer and Edge can be startet, even if not in the list of <AllowedApps>
You can navigate where ever you want, and start some .exe e.g.: "C:\Program Files\Windows Photo Viewer\ImagingDevices.exe", but cmd.exe is not allowed. You can find a lot of blocked Applications in the Applocker Eventlog, e.g. SoundDevice Executables
c) FileExplorerNamespaceRestrictions, show only Downloads is no longer working
d) Because of the default setting "NoViewContextMenu", you can not "Unpin" the unwanted Apps on Taskbar.

MaxMorsia 
You can simply create a PPKG with the WICD ands install it silently by powershell. As a alternativ, you can write the XML directly into die WMI Store (root\cimv2\mdm\dmmap -> MDM_AssignedAccess).

What is your usecase, that you need psexec?

太好了，多应用的展台模式终于可在Windows 11上运行。

但目前 Windows 11 配置 Multi-app Kiosk 的文档实在太稀缺了，主要是 XML 的引用格式和规范介绍的太过于模糊，导致在实践中不断的发生错误。希望相关的技术文档能够更全面和完善。

Wondering if an Intune Support ETA has been established? Actually, just testing it with Windows 11 anyway and it slightly works ;), but Taskbar manipulation is a no-go :(.

I would assume not very far from Intune Support, also tested today to create multiapp windows 11 machine. Seems like the auto logon doesnt yet work. When the KioskUser0 tries to log in it just kicks it out. Was able to overcome this by creating new user KioskUser00 and setupped autologon for that.  Auto Logon would also work for KioskUser0 account if that would have been moved to Administrators group but that also disables the blocks so that account would have full access to everything which i would recommend not to do.

Edit: newest Windows 11 update seems to fix the autologon issue, now its working as intented.

Please share the XML for the sample above

I was able to get an autologon KIOSK to autolauch Edge and pin it to the Start menu. Now I just have to figure out the behavior of all the Edge arguments. I applied this XML through a custom configuration profile in Intune.

<?xml version="1.0" encoding="utf-8" ?>
<AssignedAccessConfiguration xmlns="http://schemas.microsoft.com/AssignedAccess/2017/config" xmlns:rs5="http://schemas.microsoft.com/AssignedAccess/201810/config" xmlns:win11="http://schemas.microsoft.com/AssignedAccess/2022/config">
<Profiles>
<Profile Id="{9A2A490F-10F6-4764-974A-43B19E722C23}">
<AllAppsList>
<AllowedApps>
<App DesktopAppPath="%ProgramFiles(x86)%\Microsoft\Edge\Application\msedge.exe" rs5:AutoLaunch="true"/>
<App AppUserModelId="Microsoft.Windows.Photos_8wekyb3d8bbwe!App"/>
<App AppUserModelId="Microsoft.BingWeather_8wekyb3d8bbwe!App"/>
<App AppUserModelId="Microsoft.WindowsCalculator_8wekyb3d8bbwe!App"/>
</AllowedApps>
</AllAppsList>
<win11:StartPins>
<![CDATA[
{ "pinnedList":[
{"desktopAppLink":"%ALLUSERSPROFILE%\\Microsoft\\Windows\\Start Menu\\Programs\\Microsoft Edge.lnk"},
{"packagedAppId":"Microsoft.Windows.Photos_8wekyb3d8bbwe!App"},
{"packagedAppId":"Microsoft.BingWeather_8wekyb3d8bbwe!App"},
{"packagedAppId":"Microsoft.WindowsCalculator_8wekyb3d8bbwe!App"}
] }
]]></win11:StartPins>
<Taskbar ShowTaskbar="true"/>
</Profile>
</Profiles>
<Configs>
<Config>
<AutoLogonAccount/>
<DefaultProfile Id="{9A2A490F-10F6-4764-974A-43B19E722C23}"/>
</Config>
</Configs>
</AssignedAccessConfiguration>