Our setup is a win32 desktop app running on all-in-one PC's with touchscreen initiallt running windows 8, now running windows 10. After updating windows 8 to windows 10 we had problems that the on-screen keyboard activation/de-activation didn't work anymore from within our application, but we managed to solve that, the application runs fine now on those systems with windows 10.
However, when these systems get locked down using Inteset Secure Lockdown and the PCs do not start in tablet mode, the on-screen keyboard doesn't work. I found a few posts on this forum that to the solution would be to force the device to start in tablet mode, and to have the restriction "no desktop" unticked.
We tried that, but what then happens is a blank screen is only shown; when using a few time CTRL-ALT-DEL together with Escape and/or cancel suddenly the application becomes visible.
From one post on this forum I understood that occacionally this can happen when starting in tablet mode; the table app gets in front of inteset or something like that. Our problem is this is not happening occacionally, it is happening all the time.
So we're are left with crippled systems; when starting the computers in desktop mode the auto-start of the app works ok, but the on-screen keyboard is unusable. When starting the computers in tablet mode only a black screen becomes visible and the application is never started (or is running behind the tablet screen?).
We're desperate for a possible solution, does anybody know one ?
However, when these systems get locked down using Inteset Secure Lockdown and the PCs do not start in tablet mode, the on-screen keyboard doesn't work. I found a few posts on this forum that to the solution would be to force the device to start in tablet mode, and to have the restriction "no desktop" unticked.
We tried that, but what then happens is a blank screen is only shown; when using a few time CTRL-ALT-DEL together with Escape and/or cancel suddenly the application becomes visible.
From one post on this forum I understood that occacionally this can happen when starting in tablet mode; the table app gets in front of inteset or something like that. Our problem is this is not happening occacionally, it is happening all the time.
So we're are left with crippled systems; when starting the computers in desktop mode the auto-start of the app works ok, but the on-screen keyboard is unusable. When starting the computers in tablet mode only a black screen becomes visible and the application is never started (or is running behind the tablet screen?).
We're desperate for a possible solution, does anybody know one ?
0
