Using windows operating system for automation application with Labview

[rolfk]

---

@bienieck wrote:

How did you disable Ctrl-Alt-Del if it is hidden deep down in the Windows kernel?

---

Frist step was to disable Task Manager in HKCU\Software\Microsoft\Windows\CurrentVersion\Policies\System   DWORD:DisableTaskMgr

But this was Windows XP, so there definitely is room for "improvements" in later Windows versions that can and quite possibly will change this or even make it not work at all.

This still doesn't completely lock out everything. If you want to go all the way you will need to install a kernel driver to hook the specific key. But that is really going to mess with a system in very nasty ways.

Edit: as LLindenbauer points out, Windows 10 seems to come with such a kernel driver that can be enabled and configured in Windows.

[wiebe@CARYA]

You can make your application full screen and make it kill all explorer.exe instances.

Not totally fail proof, as there's an opportunity for the user to kill your application before it starts. 

IIRC, even when starting your application as shell still allows the user to do CTRL+SHIFT+ESC, and CTRL+ALT+DEL and such shortcuts.

In the past I used a key remapper to disable such shortcuts, and that worked.

[constructionworker]

After a long research.... If we make a general research evaluation;

***The application created with Labview cannot be used in kiosk mode on any normal windows version.

-In any Windows version (pro,enterprise,home) if we want to use the application     created  with labview at startup of the computer,

    1-The application is created to run in full screen and the steps in this link are applied.

     2-As an alternative to Kiosk mode, 'shell launcher' can be used.

                    How to change shell initialization is explained in detail here. and here

-What is the difference between starting the application as a start-up and starting it by changing the shell?

   Shell Launcher advantage for app:

• -Shell Launcher enables OEMs to set a classic, non-UWP, app as the system shell. The advantage to using Shell Launcher is the ability to provide custom actions based on the exit code of the OEM application. For example if the OEM application exits with a specific exit code, the system can be configured to automatically restart the application, reboot or shutdown the device, etc.

  -What is the performance difference between starting the application as a start-up and      starting by changing the shell?

           1-I dont know.

-What is the difference between using Windows 10 ioT enterprise and normal windows(pro,home,enterprise) in automation systems?

1- Avoiding unwanted updates.

2- long-term working guarantee

3- Windows 10 IoT Enterprise is the marketing SKU name for the Windows 10           Enterprise LTSB edition that is available through the Industry OEM   channel.  Enterprise LTSB is the same base OS as Windows 10 Enterprise without     the store UX, Cortana, Edge or any of the UWP applications that are serviced   through the store such as News, Sports, Finance, etc.

-What is the performance difference between deploying the application on Windows 10 ioT enterprise or normal windows(pro,home,enterprise)?

 **Probably not much difference