Windows 10: Win 10 Kiosk mode with photo app network connectivity

We have a kiosk machine set up, with win 10 20H2, it is not connected to any kind of network. It displays a slidshow of pictures, that are stored on the machine. Yet every time we restart the machine Photo app displays an error, that it "cannot connect to the internet". The machine was never connected to the internet after the initial setup, and we wish to not connect it, how can we disable this, or hide this error msg?

:)

 

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

 

Kiosk Mode in Windows 10.

We would just like to clarify some information.

• How many apps do you plan on running on the said mode?

This maybe an option that suits your purpose. Kindly follow the steps provided in this
link.

For more information, you might want to check this article out about:
Configure kiosk and shared devices running Windows desktop editions.

Regards.

 

How to allow Windows 10 multi-app kiosk mode to run program from network drive

I'm experimenting with Windows 10 multi-app kiosk mode as a possible solution for some public kiosk terminals, and I've gotten the XML file written in a way that everything works perfectly after applying the provisioning package.

Almost.

The provisioning works fine if I do not add the paths of our specific software under "AllowedApps" and leave it as simply a list of basic Windows apps like File Explorer, Google Chrome, etc.

As soon as I add the paths to the proprietary apps though, the newly built provisioning file fails to make any changes to the computer at all.

The apps (desktop apps, not UWP) that need to load are located on a server in the same LAN and must be loaded via a network share. They cannot be installed locally on the kiosk computer.

So I've pinpointed the problem being that the kiosk mode doesn't seem to like allowing apps that are located on a network drive.

I'll appreciate any kind of pointers on how to get around this. Is it a known limitation of kiosk mode? And if so, is there an unofficial workaround I can do to "trick" it into allowing specific desktop apps to load from a network drive that are not and cannot be installed on the local kiosk computer?

I'm really liking the kiosk mode, but unfortunately the whole point of using it would be to run apps that can only be loaded from a network drive.

Here's the different ways I tried writing the network paths for the programs, none of which worked:

<App DesktopAppPath="Z:\\[RemotePC]\[ShareName]\[FolderInShare]\[ServerApplication].exe" />

<App DesktopAppPath="\\[RemotePC]\[ShareName]\[FolderInShare]\[ServerApplication].exe" />

<App DesktopAppPath="Z:\[FolderInShare]\[ServerApplication].exe" />