Welcome to the Windows driver Quick Installation Guide which covers the key elements for installing the UPDD Windows version 6 and 7 drivers.
We can supply Windows drivers for Windows XP (Service pack 3 and above) thro’ Windows 11. UPDD V6 supports XP and above. UPDD V7 is available for Win7 and above, currently 64 bit only.
However, there are some considerations that need to be taken into account relevant to the Windows version:
Version |
Consideration |
XP |
This requires a version of the driver built with older development libraries. Valid UPDD V6 versions are: 433,522,551 |
Win 7 |
Requires a certain patch level for the drivers kernel modules to successfully load.
For multi-touch to work Tablet Input Services must be available. This service is omitted from W7 starter edition.
UPDD V6 supports both 32 and 64 bit. UPDD V7 only supports 64 bit and must be custom-built to support Win 7. |
Win 8 |
Requires version 564 and above. |
Win 10/11 |
No known issues with current release. |
A full UPDD driver installation document is available here and contains comprehensive installation and usage instructions and should be referenced if installation fails or the touch screen does not function as expected and for a greater understanding of the UPDD driver software.
Important signing notice - April 2021
Microsoft have withdrawn the ability to utilise cross sign kernel certificates on XP, Win 7 and Window 10, and they have been replaced with Attestation certificates that can only be used for Win 10 kernel modules. This means that we can no longer supply signed kernel modules for Window XP and Windows 7. Therefore, during installation, you will be presented with a warning that the publisher of the driver software cannot be verified. This warning will be issued on the first discovery of a USB type device. Once you 'Allow' the software to install this warning will no longer be shown for that USB device type.
The software is delivered via email as a HTTP download link to a Windows installer package. The actual name of the .exe file reflects the version of the driver being installed, e.g.updd_06_00_28.exe.
It is our recommendation that you download and save the file rather than run from within the browser (as offered by some browsers). In Windows XP you must save the file - running from within the browser will not work.
Prior to installing, if the system has an old UPDD V3 or V4 installed then as a precaution it should be uninstalled prior to installing UPDD V6/7. Trying to install over V5 will issue a warning that V5 should be uninstalled as noted here.
To install the software double click on the installer file and follow the instructions on the install dialog until the ‘Installation has completed’ screen is seen.
In most cases, the installer will only install the touch driver and related driver utilities, but in other cases it will also install UPDD Commander.
Touch delay after install - The Windows UPDD V6 driver will request control from the Windows native drivers and this can take a short time to complete, sometimes up to 30 seconds, during which time the touch may not function and / or the UPDD utilities may not respond. Only when the status dialog shows all expected devices is UPDD in control.
Multi-monitor considerations - UPDD employs a number of system interfaces to post data into the operating system, one being a virtual HID interface and for Win 7,8 and 10 this will be the default interface. However, under Win 8 and 10 if you configure a multi-monitor system you may need to reboot the system to pick up the new monitor / desktop associations! However, since UPDD version 6.0.408 we have made changes to try and overcome the need to reboot in a multi-monitor environment. For the driver to accurately determine this association the driver needs to move the system pointer on each screen when it first loads, so it is our recommendation that after installation in a multi monitor environment you should avoid using touch for a short while to avoid conflicting with this procedure. A notification is issued at the start and end of this procedure.
A reboot should not be necessary for the driver to load and touch to work, except possibly with Windows XP.
Following a successful install, the touch screen should be working and the point of touch activated under the stylus. If the touch is working, but the point of touch is not accurate, then invoke the configure procedure.
If touch is not working, you may see a notification to reboot the system. This is issued if the driver gets a Windows issued 'reboot required' status when loading the driver and will be repeated at 1 minute intervals for 5 minutes.
If there is no touch response after a reboot, please refer to the troubleshooting document. Should you need to contact Touch-Base please run diagnostics and send us the resultant file.
System Tray Items
There will be a System Tray item for each UPDD component installed (in some OEM installs these may be disabled):
With UPDD version 6/7, applications that connect to the driver via the driver's API, such as the three above, will receive notification if the connection to the API drops, implying the driver is not available. In this instance, the system tray icons will show an exclamation mark and touch is unlikely to be active, such as the driver's menu bar icon:
- driver disconnected / connected notification
If installing an evaluation version of the driver then the 'Register' option will be shown in the UPDD Daemon menu. Prior to being registered the driver will work for a certain number of touches (normally 200) per reboot for 7 days. This restriction is removed once the driver is registered. The UPDD Status screen indicates if you are running an evaluation version and shows number of touches remaining for this session and the number of days remaining:
The UPDD utilities programs are placed in the driver's application folder, by default this is C:\program files (x86)\UPDD for V6 and C:\program files\UPDD for V7.
There are a number of utilities related to the driver and gestures and TUIO server when they are installed (either by the driver installer or separately):
Driver |
|
Gestures and TUIO Server |
Calibration |
Test |
Settings |
|
|
|
Following installation the touch should be working and calibrated, if not please review the troubleshooting guide.
Test utility
A simple test utility exist to test the touch mouse interface and the UPDD API and TUIO Server data input.
Calibration
If the registered touch point is offset from the point of touch, or the touch is not associated with the correct monitor, then the touch screen will need to be calibrated with the video area. The simplest way to achieve this is to invoke the Configure option from the Daemon menu.
System Interfaces
A number of system interfaces are used to post touch data into the Windows system and applications as described below:
Interface
|
Description
|
Driver |
|
The driver reads all touch data from the touch screen but only posts single touches directly into the system such that the touch screen acts like a mouse type device.
|
Docs |
|
The complete documentation is here.
|
Settings |
|
Common settings can be adjusted via the Settings dialog. All user controlled driver settings can be adjusted via the command line interface, set command.
|
Updates |
|
The Daemon menu, About option shows the version in use. Contact the driver supplier for any updates.
|
Virtual HID |
|
A multi touch Virtual HID interface for Windows systems running Pen Services (supporting native touch functions). This is the default interface for these OS.
|
Driver API |
|
All touch data received from the device is made available on the driver’s Application Programmers Interface (API). |
Docs |
|
The complete documentation is here. |
Gestures API |
|
The gesture application receives touch data from the driver API, calculates the incoming gesture which is returned to the driver for delivery via the driver's API. This software is only required if you are running a UPDD Client application that utilises the Gesture APIs.
|
Docs |
|
The complete documentation is here.
|
Settings |
|
The gesture settings can be adjusted in the Gesture settings dialog. |
Updates |
|
The Gesture System Tray item ‘Change History’ will show the version in use. Release notes can be found here. The latest software is available via a link in the Gesture API documentation.
|
TUIO |
|
The TUIO Server receives touch data from the driver API and posts the touch data to TUIO Client applications. This software is only required if you are running TUIO client applications.
|
Docs |
|
The complete documentation is here.
|
Settings |
|
The TUIO settings can be adjusted in the TUIO settings dialog.
|
Updates |
|
The TUIO system tray item ‘Change History’ will show the version in use. Release notes can be found here.
The latest Window software is available here. |
Uninstall
To uninstall, simply locate and select the UPDD entry in the Windows Program and Features (or equivalent in your Windows version):