Answered by:

WTClient.exe

Question

Since I installed my Trust TB-5300 Slimline Design Tablet in Windows 7, I quite often get a high CPU usage of the WTClient.exe process, even when the tablet is not attached. The processor usage is then around 50%. However, this only happens when my laptop (Acer Aspire 7520) restarts after hibernation. After a 'normal' startup, the processor usage is just low, as it should be when doing nothing. Installing the tablet doesn't help, en to quit the process all the times isn't a pleasure too. I also tried to force not to start WTClient.exe at startup (using Ccleaner), but that didn't work, everytime WTClient.exe is one of the processes, even when the tablet is not used. How can I fix the problem of the 50% processor usage? Thanks in advance!

Unfortunately your solution didn't help. I have Genius G-PEN 4500 tablet and on the official website there aredrivers specifically to Windows 7, and still the SAME behavior as tomgreep has. Still WMClient.exe consumes constantly about 50% of CPU usage after resuming from Hibernation. I didn't notice that on my desktop computer, but it's very crucial on the netbook, where I could actually discover this problem...

Maybe I'll try to contact Genius, however it seems like it's not exactly driver issue - now there are two of us - Trust and Genius. And maybe those, who were too lazy to register here and respond :)

Same situation here. I have a Genius MousePen 8x6 tablet and this situation occurs exactly as described both in my laptop (Dell Vostro 1500, C2D T5470, 2GB) and in my desktop (C2D E6600, 2GB) PCs, both of them have Windows 7 installed. And both of them use the drivers provided by Genius specifically for Windows 7. WTClient.exe has 45-55% of CPU usage after returning from hibernation. I can kill the process manually and everything goes back to normal, but it's annoying.

Hmm it was my mistake, I had changed the administrative setting but not inside the "Change for all users" section. Now I tried it like you said and after returning from hibernation everything seems fine, WTClient doesn't even show up in the process list!!

Not my case. When I saw your reply, I thought it was solved, but now when I'm using tablet again, I can see that nothing had been changed. Checked "Run as administrator" inside "Change for all users", but after normal Reboot, Hibernation and returning from it I'm getting 50% of CPU usage of WTClient.exe. If in order to solve this issue someone needs to have some more dumps, just ask...

Meanwhile, Windows 7 is not on my netbook anymore, especially after this annoying problem.

I have the same problem in Windows 7. I didn´t find a good solution either. I use Systernals Process Explorer and I manually SUSPEND the process WTClient.exe. Once you do it every startup, it will not get the CPU anymore.

I had the same problem with my Genius 8x6 MousePen: WTClient using 50% of my CPU after resuming from Standby/Sleep. Ending the process in Task Manager and restarting it does reduce CPU use to 2% but doing that every time is ridiculous.

However, setting WTClient.exe to "Run as Administrator" did work for me on my Windows 7 Home Premium, but there were a couple of tricky things.

1. There are multiple WTClient.exe files in C:\Windows. One is in "System32" and the other is in "SysWOW64". For each of these, right click on the file and choose Properties. Select the Compatibility tab and click "Change settings for all users" at the bottom.
In the window that pops up, check the "Run this program as an administrator" box at the bottom. Click Ok a couple of times and repeat for the other file.

2. I used CCleaner to disable WTClient.exe at startup.

3. My MousePen tablet works perfectly when I plug it into the USB port, but the WTClient.exe process never appears at all in Task Manager. Maybe WTClient.exe isn't even necessary?

Well I also had the problem above with a Trust Tb-6300 (with trust the product doesn't matter you download the same driver package for all, the installer finds out which one you have ("Please plug your device in")).

So for this WTclient thing well on a my win7x64 the one that is running is from the system32 dir(and I'm pretty sure this is the case for any trust product) and your pen's working when wtclient isn't running because of the win7 native support for similar
devices implemented in wisptis.exe that is part of the "Tablet PC Input Service" (as the name states it's a service).

The problem occurs when your tablet can do better than win7 can support, like a multilevel pressure input (pressure sensitivity) so you need to use the buggy WTclient served by the manufacturer.

So the solution that worked for me:

1:Disable the Tablet PC Input Service in the services list (in control panel services find Tablet Pc Input Service and change the startuptype to disabled)

2:Create a new file somewhere that's going to be the small program restarting wtclient after hibernate and resume from sleep name it something.cmd

3:Edit the something.cmd write inside line-by-line:

taskkill /F /IM wtsrv.exe

taskkill /F /IM wisptis.exe

taskkill /F /IM wtclient.exe

start wtclient

4: Go to Task Scheduler and create a new task that starts "On workstation unlock of any user" and runs our something.cmd

Then you'r done and here is the way I found out how to solve this:

I inspected the wtclient when it was in it's "using a whole cpu core" state (this is the case mentioned above; 50% means you have a dual core system) and the first stack trace posted is correct the application hangs in a spinwait in the wintab32 module in
the RunTaskbarIcon() function trying to wait for multiple handles (MsgWaitForMultipleObjects) well in fact it waits for two: one is \BaseNamedObjects\UCQUEUEMSGEVENTNAME (that's always 0xD8 and is a event) and the other is not present in wtclient.
MsgWaitForMultipleObjects returns 0 every time called by wtclient, that means none of the two handles given satisfies the "wait condition" so it tries again and again and again... , but never succeed.
Well I figured maybe if it would return; it didn't work I could not reproduce a proper state to return from because the problem causing the malfunction is not in the wintab32 module not even in wtclient, the RunTaskbarIcon calls the wintab32.1000BFA0 function
and that send a message to some window (via PostMessage) with a msg_id of 0x600 (it may be some custom message) with no parameters (lparam,wparam = 0) I think that's suppose to register the device or something so I didn't stand a chance in resolving this
by just modifying some return value (of course).

I figured there's gotta be something other that wtclient that causing this. I looked around realising that my pen works even without the wtclient.exe running that gave me the idea that maybe the wtclient can't process it's functionality because some other
program claims it's already processing the input (from the tablet (this is the case with webcams: only one program can use your webcam at a time)) so I dug into the services list and found Tablet PC Input Service I was like "yeah I found it" shut it down immediately,
well who would think, it didn't work... my pen was still working without wtclient and now without TabetPCInputService (that's ridiculous) but then again I noticed the TabFlicks icon on the taskbar (at the system tray part) and found out it was the
same program running as the TabletPcInputService (wisptis.exe) so I killed that too and finally my cursor stayed still no matter how hard I brushed my tablet with the pen (now I was like "yeah" for real).

Then I restarted the wtclient from console (in the startup(msconfig) list (you can see that only the wtclient starts wtsrv is launched by wtclient)), and voilà after
like 2 seconds wait that is needed to start the wtclient and the wtserv register the taskbaricon and everything, my tablet finally works like it should.

What I have done and it seems to work is disable the tray icon for the pointing device. If you right click on the tray icon and go to properties you will see an option to disable the tray icon.

This may be a a temp fix and would like to know if you could try it please and let me know if it works. It seems to work on my machine. Its possible that there is a bug in the microsoft code when the tray icon activates.

I just end the process when it takes up all my CPU. This is not my problem. My problem is that, when I turn it on, my tablet limits the cursor movement to the actual dimensions of the tablet, which is considerably smaller than my screen. End the process,
tablet funstions normally. This wouldn't be a problem if I didn't require WTClient to use pen pressure. This is aggravating, as I can't access my layers or color selection while WTClient is on.

Nagyszulejman,
you are the man. You should be awarded a prize by Trust who have consistently showed up tiny on this one.

jebbushell*yahoo!com

However, now a week later I notice that I sometimes have to reboot to straighten it out. Manually running the task in Task Scheduler sometimes does not work. The Tablet PC icon was visible in the tray at the time I first noticed this and I was unable
to identify its process in order to try killing it.

The post marked as the answer is not the answer anymore: Start the Win7-64 system, note that wtclient.exe is not using cpu. Lock windows and then unlock. Note that wtclient.exe is now using a whole processor. Repeat with Trust tablet
disconnected and get same result: Flake City.

Microsoft is conducting an online survey to understand your opinion of the Technet Web site. If you choose to participate, the online survey will be presented to you when you leave the Technet Web site.