Page 1 of 1

Windows 10 IoT Enterprise LTSC 2021 Support

Posted: Fri Nov 17, 2023 2:53 pm
by adthelad
Hi,

I am interested in using Windows 10 IoT Enterprise LTSC 2021 on a machine. This version of windows has long term support out to 2032 and can be configured to not run updates, and only allow a user to run a single program (CNC12). I want to use this version of Windows on a machine to avoid any potential problems with users changing windows settings or using other programs on the CNC machine, and also remove some burden of maintaining Windows on the machine.

I am looking at the Single-app kiosk (UWP) mode here:
https://learn.microsoft.com/en-us/windo ... kiosk-mode

Has this been tried before?

Best,
Adam

Re: Windows 10 IoT Enterprise LTSC 2021 Support

Posted: Fri Nov 17, 2023 5:33 pm
by cnckeith
i've heard of a few others running enterprise, seems to work as long as the PC it is running on is not some embedded low power cpu unit.

Re: Windows 10 IoT Enterprise LTSC 2021 Support

Posted: Fri Nov 17, 2023 6:30 pm
by tblough
In order to run as a UWP app, the program has to be written and compiled to run as a UWP app. I do not believe CNC12 meets those requirements.

Re: Windows 10 IoT Enterprise LTSC 2021 Support

Posted: Fri Nov 17, 2023 9:26 pm
by cncsnw
Would a "single app" environment allow for running VirtualControlPanel.exe, MpgClient.exe, etc. in addition to CNC12?

Re: Windows 10 IoT Enterprise LTSC 2021 Support

Posted: Sat Nov 18, 2023 10:09 pm
by ShawnM
I believe that you can do the same with Windows 10 or 11 by adjusting the restrictions for the user account. All this can be edited using the group policy editor. You can block all apps except CNC12 and block users from accessing the control panel to make any system changes as well. Turning off updates is also very easy. And we know that CNC12 runs fine on plain old Windows 10 and 11. :D

Re: Windows 10 IoT Enterprise LTSC 2021 Support

Posted: Sun Nov 19, 2023 1:10 am
by adthelad
Thanks for all the replies, I didn't realise the UWP app requirements so that option is no longer possible.

I will take a closer look at what is possible in the group policy editor. If I can stop the user from making too many changes and running other programs I think this would do the job.