When researching Windows Startup shortcuts not working it appears that Windows 10 security features now prohibit any application requiring elevated permissions or shortcut to said application to run on boot. So the Shortcut we put into the Windows Start folder is ignored when Windows restarts/boots. Applications and Shortcuts Windows finds that need elevated permissions is adds the Shield symbol to the lower right corner of the application ICON.
Since InteractX needs elevated Admin rights to run, it is banned from running on boot by the Windows 10 OS. I found lots of chatter about it on-line in Microsoft forums etc... so there might be a concise developer documentation of this somewhere but I was unable to find it.
Taking a page from some of the solutions in Microsoft forums.
1) Move the HMIRun shortcut to the Desktop
2) Create a batch file called RunIXapp.bat in the startup folder that when run, changes directory to the desktop and starts the runtime lnk file with a "1" parameter to close the Command Window that opens when you run a batch file and exits.
(See the attached image for what needs to be in the batch file to create
Since the batch file does not need elevated privileges to run, Windows happily runs it and is able to execute the shortcut without triggering the security lockout.
We do not ship any hardware with Windows 10 so this has not come up as an issue for us. I entered it into our Engineering Queue and it will have to be changed in a future release.
For the time being, this batch file will need to be the work around for the Windows 10 security issue.
An additional solution was sent in by a user but has not been tested in enough units to know that is will work in all cases. It requires IT support or a comfort level using Regedit to modify the Windows Registry . If you do not know EXACTLY how to accomplish the registry edit based on the information below -DO NOT- attempt this. It is better to use the method with the batch file above since modifying the registry has a potential to break your Windows OS ability to boot and need to have Windows re-installed.
The registry entry in Windows 10 that controls UA User Policy needs to have its branch :EnableLUA" set to 0 to disable (Create a new key and set to 0 if it does not exist)
Details for EnableLUA can be found at this Microsoft Developer page.