Support in other languages: 
Showing results for 
Search instead for 
Do you mean 
Welcome to the Lenovo Community

Welcome to the Forums!

Welcome to Lenovo's Peer-to-Peer Discussion Community!
Please note our guidelines. How to register and login and Community FAQs.
Shape the Future of PCs

Help Lenovo Shape the Future of PCs

Take the ownership survey. Share your ideas with our product team
Fanfold Paper
Posts: 4
Registered: ‎02-27-2009
Location: France
0 Kudos
Accepted Solution

Wacom Virtual Human Interface Devices Driver - Error Code 52 "Windows cannot verify ..."

" signature for drivers required for this device. A recent HW or SW change might have installed a file that is signed incorrectly or damaged, or that might be malicious SW from an unknown source."  Driver version, date 9/21/2009, Provider Wacom, Digital Signer MS Windows Hardware Compatibility Publisher. 

Events leading up to the above error: 

- Noticed DigiMon.exe was using 25% of CPU (W700, Intel dual core Extreme @ 2.53GHz each, 8 GB RAM, Win 7 X64).

- This didn't seem right, so I downloaded and installed current ThinkVantage Toolbox.

- Executed Toolbox, 1 diagnostic alert "Driver problem on Wacom Virtual HID driver" followed by link to Reinstall driver.

- Clicked on this link.  Preferences box of the driver came up, with the Code 52 error message.

- Downloaded TV Toolbox again, installed it, same diagnostic alert, same results from Reinstall driver.

- Full system scan by Norton 360 detected no viruses.

Please advise.



Posts: 2,416
Kudos: 376
Solutions: 128
Registered: ‎06-05-2010
Location: Rosario, Santa Fe, Argentina

Re: Wacom Virtual Human Interface Devices Driver

[ Edited ]

Uninstall this driver first, then install it again.


Use the version publishen on Lenovo's site.


Best regads.

First Spanish Community Guru - Colaborador ad honorem

Fanfold Paper
Posts: 4
Registered: ‎02-27-2009
Location: France
0 Kudos

Re: Wacom Virtual Human Interface Devices Driver

Thanks for your help. Uniinstall and install from the Lenovo download-driver site did the trick. The new driver is the same version as the old. I guess something "walked on" the old driver. Regards and thanks again, Para.