Windows 10: After configuring a Kiosk with Windows Configuration Designer, pc Administrator user and...

Good morning, I created a basic kiosk profile for Windows 11 PRO, with Windows Configuration Designer, on a PC that already has an administrator account.After starting the created script, both the kiosk user and the PC administrator user no longer see the start menu and desktop when they log in, but only a black screen. It is possible to start Task Manager via CTRL+ALT+DEL and trying to start explorer.exe in administrator mode or not, but only explorer appears but no desktop. Tried a system restore but nothing: Windows is unusable without User Interface.Is possible to restore the User Interfac

:)

 

Windows Configuration Designer and Kiosk

I create a provisioning package using the Kiosk icon in WCD. The following parameters are what I specified

Set up device - disabled, the computer is already named

Set up Network - disabled, wired network not wifi

Account Management - disabled

Add applications - none

add certificates - none

Configure Kiosk account and app

User name KioskUser

Password

User name KioskUser

App type Classic Windows App

Full path to app c:\AccuPOS\AccuPOS.exe

configure welcome screen buttons: 2

Turn off screen timeout: Yes

Turn off sleep timeout:Yes

then I create the package, move it to a thumb drive and install it on another computer, the results are less than spectacular. The package installs in seconds and reboots the computer.

The system logs in the user and appears to stop at launching after launching eShell.exe, a black screen. I use ctl/alt/del to get a screen where I can launch task manager, then I have to start explorer from task manager. One time I tried my application
and it started fine. I've reviewed the event logs and it is like nothing is seen about Kiosk, the application that is supposed to get loaded, the type of lockdown on the computer that I expected, etc.

Additional Information: eShell has been assigned to all users instead of the specified user in the xml that goes along with a provisioning package. This causes two problems. First, eShell won't launch a UWP which is the standard replacement shell in shell
launcher v1, in shell launcher v2 a UWP can be launched but to get v2 it appears you have to be on win10 1903 or higher, I was on 1809 and am now on 1909. However, I create the provisioning package on a system with 1809 and it doesn't seem to know anything
about customshellhost.exe which replaces eshell in shell launcher v2.

Does anyone have any suggestions here?

 

Unable to configure Kiosk mode

Hi,

i am struggling to configure Kiosk Mode on Windows 10 which is the 1809 build we use for our users.

I am able to configure a kiosk mode on some machine but on a specific tiny i am using which i have rebuilt as per all our machines are build from the network using SCCM when i look at account settings - other user - i do not see the option for Kiosk Mode
but i can see that option for other machines.

is there a reason why i may not be able to configure Kiosk Mode for some machines but not for others?

i do not seem to understand any change in the build where it will allow me to set up kiosk mode on some machine and not others....

i find it slightly odd, if someone can assist would be appreciated.

Thanks,

***Modified title from: Lenovo M720q - Windows 10 Kiosk Mode***

 

Unable to configure Kiosk mode

Hi,



Thank you for writing to Microsoft Community Forums.



I understand that you are unable to configure Kiosk Mode for some machines. I suggest you to refer the article

Set up a single-app kiosk and see if that helps in resolving the issue.



If the issue persists, I would suggest you to post your query in
TechNet forums, where we have support professionals who are well equipped with the knowledge on using SCCM to be able to assist you with the appropriate details.



Regards,

Nikhar Khare

Microsoft Community - Moderator