You've got the gist of it yes, the app I want to block has no user logging capability so I want users to only launch the app through this other app which has custom username and passwords and logs the login and logout time against username

You've got the gist of it yes, the app I want to block has no user logging capability so I want users to only launch the app through this other app which has custom username and passwords and logs the login and logout time against username

You could always have some sort of background app that checks to see if that process is running. If the launcher process isn't running then kill it, otherwise it's good.

@budman
It's a factory system based on windows logins but the terminal at which the users run this program from will always be logged into the same windows account - therefore not actually logging who did what. It's impractical to set all of these users up with their own domain account so I have made my own program that asks for a username and pin then launches the program.

Yes I could set up an icon on desktop to the launcher but it's still not going to stop the 'above average intelligence' user from browsing to c:\program files\xxxi and manually starting it

OK - here is an out of the box idea. Why cant you use a program like Kido'z (which is free) and basically lets you control what they can and cant do, like what what files they can access. Ya I know that Kido'z is a "kids" program but my end users act more like kids then some kids I know. That's how I control who can get to what on my terminals.