Mouse may become unresponsive after you launch an App-V application


When you launch a process that was virtualized through Microsoft Application Virtualization version 4.5, version 4.6, or version 5 (App-V 4.5, App-V 4.6, App-V 5.0) on a touchscreen-enabled device, the mouse pointer may become unresponsive. When you exit either the App-V application process or the wisptis.exe process, the mouse starts to work again. This also affects RDS/terminal servers if the Desktop Experience is enabled (that is, if the default server setting is not enabled).


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, you remove this conflict.


Option 1: Automated resolution

To fix this problem automatically, install the latest .NET Framework hotfix rollup. When you do this, ObjExclusion registry settings are not required.

Note This is the recommended solution.

Install this hotfix rollup from Hotfix rollup 3026376 (Offline Installer) for the .NET Framework 4.5, 4.5.1, and 4.5.2 on Windows Vista SP2, Windows 7 SP1, Windows 8, Windows 8.1, Windows Server 2008 SP2, Windows Server 2008 R2 SP1, Windows Server 2012, and Windows Server 2012 R2.

Option 2: Manual process

To manually resolve this issue, create the following registry key on the client.

App-V 5.0:


App-V 4.6:

x86 systems


x64 systems

Type: Reg_SZ
Name: WPFMouseAndTouchInput
Value: {773F1B9A-35B9-4E95-83A0-A210F2DE3B37}-running


ID članka: 2987845 - Poslednji pregled: 18.11.2015. - Verzija: 1

Povratne informacije