Windows 10 Enterprise Start Menu in KIOSK mode show the expected tiles but they are not working

Occasional Contributor

Hi ,


I am deploying Windows 10 Enterprise devices with an Azure AD account into Azure AD and intune. Users are enrolled as normal users (no admin). After enrolment we deploy an UWP app to the device and apply a KIOSK mode profile with Intune. On the device where I extracted the orginal custom start Menu Layout xml from , this works perfectly. Device runs in kiosk mode and only the selected apps in the custom start menu can be started. When I configure another device (same formfactor) with the same Azure AD account everything is configured as expected but the tiles of the selected application does not start when clicked , double clicked or touched. The Tiles are there , move when clicked , but start nothing. No errors whatsoever. Very difficult to troubleshoot because I have no access to other applications and when I remove the kiosk profile the issue is gone. Any ideas or help would be appreciated. Thanks P

5 Replies
best response confirmed by Peter Wuytack (Occasional Contributor)

I know what you are dealing with, and this one is documented poorly. It is not terribly hard to fix however. I learned all of this while working with a really helpful field engineer out of Australia. Actually he was Customer Experience driver, and put all the field engineers (who know nothing it seems) to shame. :

When you export the start layout that you want, crack it open in your favorite XML editor , and change the  URL for the application. You see, with that profile the AMUID is generated based on the Provisioned account. The Azure account does not pre-exist on the computer so it has to be provisioned, This means hard links like that will not work because all applications are consumed on a user base for the most part, in Windows 10. One way to get around this is to place the start menu shortcuts in "%AllUsersProfile%\Microsoft\Windows\Start Menu\Programs\<appName>.lnk" ; then they will always work.I recently learned, that is not the best way either. I had the links showing up just like you , but not working. Here is how you fix that:
The Start Menu XML, the app tile will use DesktopApplicationLinkPath for the reference to the app, which will fail when using MDM to provision the tile.   You need to use DesktopApplicationID. In order to get the DesktopApplicationID,follow this link.  


The trick that NO ONE I KNOW knew about was this cmdlet: Get-StartApps. This allows you to work like you normally do and design a start menu, and then harvest the correct AppID GUID/URL thingy after you Export-StartLayout, and replace the Path, with the ID.


Sorry im so verbose. It is an easy fix though.




I can confirm using DesktopApplicationID`s solves strange issues when publishing a startmenu using Intune and also with GPO`s.
Definitely worth trying!

Thanks , I will give it a GO.


Regards ,



You can also use the -UseDesktopApplicationID switch when exporting the layout. For example:


Export-StartLayout -Path 'C:\StartLayout.xml' -UseDesktopApplicationID

Hi Frank , will try now that kiosk mode was released.