1) Some portion of our customers are running POSReady 2009. This is basically Windows XP SP3.
2) As a general rule, we cannot reboot these systems. Nor is our software (or updates) allowed to reboot the system.
3) We strive to make our system zero configuration and zero touch. A tech should be able to install our software and never have to touch the PC again. This includes software updates which we preform via a command from our server to execute AI's supplied UPDATE.EXE.
4) We place our APP.EXE in the startup folder.
5) At the end of our AI setup. Our APP.EXE is launched.
We have a situation where our installed product cannot be updated on POSReady 2009. UPDATE.EXE just sits forever in the Task Manager. We have pinpointed this issue to be with MSIEXEC.EXE. Using Process Monitor we noticed that our APP.EXE is hanging off of MSIEXEC.EXE. If we manually restart our application it will be hanging off of EXPLORER.EXE and can update just fine.
A) In Windows XP SP3: After our application is launched from SETUP.EXE its parent process is WINLOGON.EXE.
B) In POSReady 2009: After our application is launched from SETUP.EXE its parent process is MSIEXEC.EXE.
C) In Windows XP SP3 or POSReady 2009: After quitting and launching our APP.EXE it is running off of EXPLORER.EXE.
D) In Windows XP SP3 or POSReady 2009: After a reboot our APP.EXE is running off of EXPLORER.EXE.
MSIEXEC v3.1.4001.5512 on XP
MSIEXEC v4.5.6001.22159 on POSReady 2009