We have found that the DeviceLock settings in the Security Baseline have prevented Kiosks from deploying successfully.
For this reason, we removed all DeviceLock settings from the SB and deploy them instead through a separate Configuration Profile.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Prior to raising this question in this topic, I visited a few technical forums and followed the same instructions, but I'm not sure where I went wrong.
Tried followed the link (as well) as is - https://endpointmanagertips.com/dipping-my-toes-into-windows-autopilot-self-deploying-kiosks/, but single\Multi app & autologon does not function.
I was able to login to the KIOSK machine after manually entering the local account (.\KioskUser0), however single app mode is not functioning. It appears to be a standard desktop.
I tried to reset the testing machine using both ways without success. Please find the screenshot:
Note: Please see the following screenshots.
2. Created deployment profile
3. Added the Group in Compliance
4. Configuration profile:
6. Kiosk Browser (Offline) deployed to specific group
Note: 1 I was running many scenarios on the same testing computer.
I used to wipe the system from intune anytime I applied a new configuration or changed a profile.
Will it be the source of the problem?
Note: 2 - Though security baselines creates a problem but I couldn't find the Security baselines profile in Intune. Created the basic profile and excluded the kiosk group as well.)
We have found that the DeviceLock settings in the Security Baseline have prevented Kiosks from deploying successfully.
For this reason, we removed all DeviceLock settings from the SB and deploy them instead through a separate Configuration Profile.
We are actually having around 30 devices deployed successfully as kiosk devices. By itself the deployment wasn't working, or better, it worked for a very short period of time. What we did is remove every compliance policy from the kiosk devices, except for the built-in that is. Having a compliance policy applied to a kiosk devices seems to break the autologin mechanism somehow. In addition to that, we enforced a script deployed as a Win32 app where we add the autologin registry entries (kioskUser0 as default user, .\ as default domain and AutoAdminLogon = 1).
For info, this doesn't seem to work with Windows 11 devices...
The issue with kiosk mode was solved for us with the Windows 10 CU update April 11, 2023—KB5025221
This update addresses a known issue that affects kiosk device profiles. If you have enabled automatic logon, it might not work. After Autopilot completes provisioning, these devices stay on the credential screen. This issue occurs after you install updates dated January 10, 2023, and later.
Any update on this? We are facing the same issue. When we do a systemreset of a Windows 10 machine through the command prompt. We are facing the same issue with Multi App Kiosk mode Autologon. When we do a fresh installation of Windows through a USB image, it is working as intended.
Having this same issue despite the device being excluded from SBs and compliance.