We have a shell package that installs with two commands from cmd prompt on the machine with the Select client. When we try to script the installation to run, using either Powershell or cmd interface, we get this error after calling
We're copying the shell package's dll into the Select directory, then running these commands in sequence from the cmd prompt. Works fine when done one at a time.
I have passed this case to our R&D department. They will respond to this forum when they have an answer.
The only information that I found is that this has occurred in automation scripts that are not interactive. This is the link: GetDoubleClickTime returns 0 unexpectedly . The third party tool we use to manage the UI windows does pass the SystemInformation.DoubleClickTime value to an internal timer and I believe this may be the problem.