Should this be needed in the future the steps to address are:ġ. We created a replacement usb interface using an open source tool libusbk and this, surprisingly, fixed 'the issue'!

Then install other software and see what, if anything, replaced the USB system driver.įortunately there is an alternative approach to resolve this issue albeit it will need some manual setup. We concluded that for UPDD to install and work “out of the box” is was best to start with a clean W7 system fully patched and install UPDD first.

It could and been relate to the patch level on the system. On this system we did note that other touch software was installed (Microtouch) and there is a possibility that this interfered in some way but we saw nothing to indicate that this was happening. We’ve never seen this before where our driver package is reported as installed but clearly a module from a different package is in place. We occasionally see failures to install but they generally show a clear error status and can easily be corrected with a manual driver update. On this particular system even when we forcibly replaced the driver with the correct one it continued to show as above. On a properly working system you would expect to see winusb.sys The connected USB device, serviced by UPDD, was shown in Device Manager as being controlled by the built in driver hidusb.sys The issue was related to the wrong system USB driver in place and not the one expected by UPDD and why this should be was unclear. Customer reported touch not working after a successful install.

Winusb setup