Windows 10: Kiosk mode causes all user account to be black screen after applying provisioning package...

Not a question but I'm attempting to Answer the previous issue from January. I've been running into the same issue but what ended up working for me was I built the provisioning package using Microsoft Configuration Design from the Microsoft store. I was able to build, test, and launch my Cricut Kiosk. I'm currently typing up a guide for my job but when that's done I'll post it here. :

:)

 

Kiosk mode causes all user account to be black screen after applying provisioning package

hi I'm trying to configure kiosk mode in windows 10 pro and also I want to use a custom application as the kiosk app.

The custom application is an "indusoft HMI applications" which as a RunStartup.exe in its bin folders, which will open & run the application

build using the indusoft HMI software.

Indusoft is a software use to create human machine interface application. once a HMI is created, it can be made

to run by executing the "RunStartup.exe" application found in the \BIN folders of the indusoft software.

So by using windows configuration designer I add the "RunStartup.exe" as the kiosk app and created the login account accordingly

following the windows configurations designer. For the kiosk application, it is selected as "windows classic app" and

the full path of the "RunStartup.exe" application is provided as requested by the windows configuration designer as to select it as the kiosk app.

so in kiosk mode I expect that ,it will execute the "RunStartup.exe" and the HMI will be running in kiosk mode.

so then finally I created the provisioning package and added the provisioning package to the windows PC. it will create 2 new accounts,

a local admin account and the kiosk account which have the path to the "RunStartup.exe".

The problem is after adding the package, it created the the 2 new accounts correctly, 1 local admin account and the other kiosk account

and also the windows already have another 2 accounts before, so total 4 accounts now.

so after adding the package and restart my PC, the PC straights becomes black screen with mouse pointer only but I can press CTRL ALT DEL

to switch to between the 4 accounts, but all the account after login will be black screens only. the kiosk mode not running the "RunStartup.exe" application

at all. the task manager only shows 1 app running which is the task manager itself and the background processes, but the screen is just black.

all account is same after login, becomes black screen.

so my question will be:

1. what the basic qualifications for an app to be used in kiosk mode, anyway indusoft is a Microsoft partner software.. I just believed that it can be
   
   run in kiosk mode. (I'm checking with the software supplier and waiting reply)
   
2. what's the common issue of black screen where windows OS is running but no any apps is running except for background processes
   
3. can we just use any application to run in kiosk mode or the application must be designed to run in kiosk mode before using the application in kiosk mode.
   
4. what we can do in a event of black screen?? as now all my windows account become black screen, how do I revert back to normal, reformat and install windows again.. for now only task manager can run on top of the black screen.
   

 

Windows 10 1809 LTSC Multi-App Kiosk Provisioning Package unexpected context menu

I have logged a premier support call with Microsoft (2+weeks old now) about this unexpected behaviour but wanted to know if the community have seen this..

Background

1. I have created an advanced provisioning package via the Image and Configuration Designer tool for a multi app kiosk, built the machine and installed the package via SCCM, and deployed the computers to site. All work great.
2. The service desk gets a call advising that users cant print on these devices via citrix. I review the logs, find the problem, create a new provisioning package and begin to test deploying it out in my lab vms and physical machines.
3. This is where the unexpected behaviour begins. When i go and remove the existing prov package and then install the new prov package, i reboot and the kiosk account signs in, the printing problem in citrix is resolved,
   however i can now right click the start menu and the context menu appears. There are no other problems except for this.

If i build the computer from scratch with this new prov package everything works fine with no context menu.

I need to find a fix so i can reapply provisioning packages without having end users able to have access to the context menu.

 

Windows 10 kiosk mode: screen locks after login

Hi Matthias,



Thank you for writing to Microsoft Community Forums.



I understand that you are facing issues while using Kiosk Mode on Windows 10.



Since you are being logged out of Kiosk Mode after every login, I suggest you to refer the article

Troubleshoot kiosk mode issues.



Also, you can try removing and creating the Kiosk account again, follow the steps mentioned below to remove the Kiosk account:

1. Go to Settings >
   Accounts > Family & other people.
   
2. Under Setup a kiosk option click on
   Assigned access.
   
3. Now under Kiosk info click on the
   account name and click on Remove kiosk.
   
4. Now click on Remove.
   

Once the account is removed, refer the article to
Set up a single-app kiosk.



Hope it helps.



Regards,

Prakhar Khare

Microsoft Community – Moderator