Forum Discussion
Kiosk Mode not logging in - "kioskUser0 the user name or password is incorrect"
Hi all,
i am suffering the same issue, even if I have some other prerequisites. The aim is the same, i want to deploy an Single app, full-screen kiosk device., which displays a full screen web page, which can be used without any interactive logon.
My configuration is the following:
- Windows 11 Pro (Build 10.0.22621.1265)
- Deployed via Self-Provisioning Autopilot profile
- Intune Kiosk profile configured and assigned to device
- Kiosk Browser (offline app from WSfB) is deployed to device
- Device is configured with an extra ESP, waiting for all required apps (only Kiosk and TeamViewer Quick Support is deployed)
When I deploy my device, autopilot (WLAN or LAN) works like a charm, the device gets provisioned real fast, but then my trouble starts. Instead of displaying the configured website, I get the windows logonpage with no user prefilled. As soon as i enter the username '.\kioskuser0' i am able to sign in without the requirement of a password and the configured website gets displayed as i wish. But i have to logon every time with the user which is configured by the Kiosk Intune Profile. I can't remember, that this is an expected behavior and i haven't seen this in any blog or video.
Here are my Intune configurationprofiles, which get successfully deployed to the device:
Settings Catalog
No the steps I did to find the error:
I have double checked, if the client got the policy and made several reboots, to be sure the configuration is on the client. Well, it is:
Catalog:
App:
Since I know, any password policy or preferred Tenant information will break the experience, I have tripplechecked this and made shure, that no corresponding Policy is in place. I can confirm, there is no device lock policy on the device. To make the things more tricky, the following Eventlogs are empty and can't help me in any way:
- Microsoft-Windows-AssignedAccess/Admin
- Microsoft-Windows-AssignedAccess/Operational
- Microsoft-Windows-Authentication User Interface/Operational
To get around the problem, i played with different settings within the Kiosk Profile, my problem didn't disappear. Regardless if i configure the Kiosk Browser or the Edge Browser with Digital/interactive Signage, i still get the windows 11 sign in screen.
Oliver Kieselbach: Do you have any clue, how to get my configuration out of this mess? Even waiting an entire #membeer, to allow intune replication didn't work :(.
Greetings Michael
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-issues
Have you seen this?
best,
Oliver
- Nat_EvansMar 12, 2024Copper ContributorThank 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!
😄 - Michael MornhinwegFeb 24, 2023Copper ContributorHi Oliver,
thank you very much for the hint! Actually i haven't seen this article, but it explains my experiences on the clientside. As the article is linked to Autopilot, will it still ocure, when i deploy the machine on another way and assign the kiosk-profile afterwards?
Is there any way to get around this issue? Maybe the Autoadminlogon regkeyies or do i have to deal with "just enter kioskuser0 and hit enter"?
greetings,
Michael