Just following up.. we worked with John again today and the latest version of the component did not resolve the issue. So, for now we'll have to rely on the config file update chosen as the solution to this post.

We're continuing to investigate. This might be related to TouchScreen Windows Devices and this component (it's not the machine's fault). I will keep this thread posted.