When an application that uses a .NET Framework(WPF, silverlight, SCOM / SCCM console, App-V UI etc) 4.5.2 is virtualized on any version of the App-V 5 client there is severe mouse-lag or hang.
Reproduce the issue
Connect a device which uses the Tablet Input service – most commonly Wacom-devices. Any WPF application based on .NET Framework 4.5.2 can cause the issue – for example using Chrome to access Outlook Web Access and then pressing “New message” (will use Silverlight) to generate a new email will spawn the wisptis.exe. The mouse freezes. If the process (wisptis.exe) is terminated mouse responsive will return to normal. The below is the process start of wisptis.exe
Process 5836 starting at 000000013F5AD9C8 C:\Windows\System32\wisptis.exe 11:24:08.939: [6388/6532] NtTerminateProcess( ProcessHandle=0x4f8, ExitStatus=0xc000042c ) => 0
The attempt to start this process fails with an STATUS_ELEVATION_REQUIRED code.
(credits to Paul Richards for the above info)
It seems that reverting back to .NET 4.5.1 has resolved the issue for quite a few people. If your application actually requires the .NET Framework 4.5.2 version that is of no use as a workaround. Installing the below hotfix may improve the issue aswell, however the successrate so far is low;
(while you are at it – apply this one aswell: Tablet PC Input Panel cannot be moved after you install update 2973201 in Windows 7 or Windows Vista )
WISPTIS.exe is a process to handle the pen input, and therefore we can reduce our impact by completely disabling the the functionality. The policy can be find under;
I haven’t personally confirmed this and so far this seems extremely intrusive as it completely disables the functionality for all applications.
Community discussed workarounds
This obviously breaks the input functionality, however only for the virtualized application.
(Thanks Paul Richards for the above suggestion – brilliant in so many ways)
Microsoft Support Solution – 2014-10-15
This is the Microsoft suggested solution. Apparently App-V makes an attempt to start a second process, and therefore the lag is experienced. Create the following registry key on the App-V client machine. Location:“HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AppV\Subsystem\ObjExclusions” Type: Reg_SZ
The number 93 is used in this because 93 is the first available number in a default installation. This might be higher if your installation has more object exclusions.
Thanks Paul Richards for the update
Report it to Microsoft. There is a bug file on Connect that seems to have an open discussion, and there is a pending support case with Microsoft that is awaiting the long term solution.
If you are a heavy user of Wacom hardware – see this guide of Vizibler that hopefully can improve your situation.