I am working with creating a Device Configuration Profile for Kiosk Mode. The device is Windows 10 1809 and is Azure AD joined only and is syncing and receiving policies, updates, and software. When the device is restarted the Kiosk policy attempts to force the Auto-login option but fails. It is showing User "kioskUser0" and giving the generic message of "username/password is incorrect". I wait a minute or 2 and the timeout for attempting the login with the kiosk user occurs, then I am able to then login with any azure ad user I attempt. When the policy is applied is it creating kioskUser0 as a local account on the device?Other than restarting, is there any way for the device to attempt to log back into the kiosk section? (logging in and signing out does not seem to trigger this)

Oliver Kieselbach I am working with Premiere support at the moment to dig in and figure this out. I will reply back with my notes for others to benefit from as well. This reply is to let everyone know this is still being investigated.

cbelcher @Oliver Kieselbach Below are the results of what I found with MS Support to be the steps taken to achieve Kiosk Mode. Devices must enrolled to MS Intune. I did this with Set up my School PC's appUsing open Wireless SSID (our MAC addresses were added CISCO ISE to allow them directly on to the network without the need to click our Acceptable Use Policy)Created a Dynamic Group to for the enrolled devices (Using Assigned will also work)Devices were updated from Windows 10 1803 to 1809 using the Software Update Ring policyCreated a device configuration policy to “Enable share usage data” to BasicObtained the Online and Offline version of the Kiosk Browser app from the MS Store for Education***Unable to tell the difference in the apps from the console UI once synced***Assigned the app to the device group***The first app in the list was chosen, which in further investigation is the online app.6.Setup a Device Configuration policy for a Kiosk profileNamed "Kiosk Profile for Library Catalog"Single App = Kiosk BrowserSet up for Auto logon, Windows 1803+URL (for now) bing.comIn further testing, I found the Kiosk Browser app does support intranet sitesAssigned to the device group from Step 2 Notes for the experience:I found I had to restart the devices several times after everything was in place before it would actually take place. (Approx 3-4 times per device) During some further testing I found:In a Device Restriction policy, password section, filling in the preferred tenant name breaks the auto login feature for kiosk mode. I made a single change and once the devices synced, and restarted, they were unable to auto-login. Thank you Oliver for reaching out to help me.

Kiosk device profile not auto logging in There's currently a known issue in Windows Update KB5022303, which applies to both Windows 10 and Windows 11, where Kiosk device profiles that have auto log on enabled won't auto login. After Autopilot completes provisioning, the device stays on the sign-in screen prompting for credentials. To work around this known issue, you can manually enter the kiosk user credentials with the username kioskUser0 and no password. After entering this username with no password, it should take you to the desktop. There's a fix pending, but no estimated date for the release of the fix at this time. https://learn.microsoft.com/en-us/mem/autopilot/known-issuesHave you seen this?best,Oliver

Hi cbelcher, hmm okay understand. I didn't setup kiosk with USB sticks and provisioning packages until now. Anyway after restart the auto logon should work. Did you try to specify .\kioskUser0 and leave the pasword blank? important is the .\ in front to make sure the logon window knows it is a local user logon. Do you have other MDM policies which getting applied to the device as well? maybe they create a kind of conflict. e.g. if you enforce via Compliance policy require passwort it will break auto logon. best, Oliver

Thank you!!! I have spent hours trying to learn the setup. I now understand that I was seing this working if I hadn't fully updated the machine (I have just rebuilt the same machine 5 times to work out why this was not working).Lots of searching later and this comment has answered why I am struggling and that my settings are applying, but the autologin is not working.Thank you so much for posting this!😄

Kiosk Mode not logging in - "kioskUser0 the user name or password is incorrect"

Oliver Kieselbach
MVP
Mar 25, 2019
Hi cbelcher,

the policy is creating the kioskuser0 and confgures the autologon. If you combine this with a Autopilot Self Deploying Mode (SDM) Profile then the OOBE will enable the Enrollment Status Page (ESP) and waits for the receiving of this policy and then when it proceeds the kioskuser0 autologon will instantly take you to the Kiosk. In my tests I found a problem in this mode as the ESP is currently not correctly waiting for the kiosk profile therefore the autologon is not working. This is currently known by Microsoft and they are working on a fix.

best,

Oliver
- cbelcher
  Copper Contributor
  Apr 01, 2019
  Oliver Kieselbach
  To clarify, I am not using Auto-pilot with ESP. This are provisioned with a USB and the the kiosk mode profile is applied when the device is synced. Is the issue you stated still going to affect me?
  - Oliver Kieselbach
    MVP
    Apr 03, 2019
    Hi cbelcher,
    
    hmm okay understand. I didn't setup kiosk with USB sticks and provisioning packages until now. Anyway after restart the auto logon should work. Did you try to specify .\kioskUser0 and leave the pasword blank? important is the .\ in front to make sure the logon window knows it is a local user logon. Do you have other MDM policies which getting applied to the device as well? maybe they create a kind of conflict. e.g. if you enforce via Compliance policy require passwort it will break auto logon.
    
    best,
    
    Oliver
kodyjahody
Copper Contributor
Apr 11, 2024
Hi,
here is my little workaround tip:
assign AAD/Entra account to Intune's Kiosk mode config
set autologon manually (Sysinternals Autologon) or via powershell script
- Nat_Evans
  Copper Contributor
  Apr 11, 2024
  kodyjahody
  
  I actually went away and came back to this with fresh eyes. I managed to get this working WITHOUT any scripts or other setups.
  
  I found that although I did not assign a compliance policy and the default compliance policy that applied did not have any password settings I could see in Intune, as soon as I made a new, empty compliance policy to catch the machine when it enrolled - it worked.
  
  Unfortunately, my experience with Intune has been if it doesn't work today, walk away and try another day and it may work. I can't guarantee this works every time as I only needed to make one kiosk setup.
  
  I have a working Windows 11 kiosk configured by Intune alone.

Forum Discussion

Kiosk Mode not logging in - "kioskUser0 the user name or password is incorrect"

Share

Resources