Microsoft: KB: Mouse may become unresponsive after you launch an App-V application
When you launch a process that is virtualized through Microsoft Application Virtualization version 4.5, version 4.6, or version 5.0 (App-V 4.5, App-V 4.6 or App-V 5.0) on a touchscreen-enabled device, the mouse pointer may become unresponsive. If you exit either the App-V application process or the wisptis.exe process, you’ll find that the mouse starts to work again.
Note that this also affects RDS/terminal servers if the Desktop Experience is enabled (that is, if the default server setting is not enabled).
This occurs because in some cases, App-V creates a second instance of the wisptis.exe process as part of the application launch. This may create a conflict between the wisptis.exe process that’s already running (because the system is touchscreen) and the new wisptis.exe process that was triggered by the application launch. By exiting either the App-V application process or the wisptis.exe process, this conflict is removed.
For complete details as well as a couple different…
Read the entire article here, KB: Mouse may become unresponsive after you launch an App-V application
via the fine folks at Microsoft App-V Team Blog