Wacom Input Devices Driver Download For Windows



Corporate installation of the DisplayLink graphics driver

  1. Download Wacom Driver Windows 10
  2. Wacom Tablet Download Driver
  3. How To Download Wacom Driver

Problem

Download Wacom Device Windows Drivers Device. Input Devices: Operating Systems: Windows 10 32 & 64bit, Windows 8.1 32 & 64bit, Windows 7 32 & 64bit, Windows Vista. On your keyboard, press the Windows logo key + R key together to open a Run box. Type services.msc in the box and press Enter to open the Services window. Scroll down on Services window, find and right-click on your Wacom service. Like Wacom Profession Service, Wacom Consumer Service and TabletServiceWacom. Then click Restart.

Download Wacom Driver Windows 10

I want to install the DisplayLink graphics driver in a corporate environment where DTU devices are already connected to the PCs

Solution

Please see the DisplayLink corporate installation guide

Device is not connected (Windows 7)

Problem

After installing the Wacom tablet driver the pen tablet will not work properly and on trying to access the control panel (Wacom Tablet Properties) the following error appears:

Solution

On some versions of Windows, particularly Windows 7, this can happen if Windows is not fully updated.
The solution is to run Windows Update until you are sure that nothing is missing.

Alternatively you can apply these 3 updates individually:

KMDF - https://support.microsoft.com/en-us/help/2685811/kernel-mode-driver-framework-version-1-11-update-for-windows-vista-win

UMDF - https://support.microsoft.com/en-us/help/2685813/user-mode-driver-framework-version-1-11-update-for-windows-vista-windo

SHA-2 - https://docs.microsoft.com/en-us/security-updates/securityadvisories/2015/3033929

DTH 1152 Touch Screen not working with XenApp

The pen on the 1152 only works with XenApp if Windows Ink is disabled in the Wacom Tablet control panel because of a known issue between Citrix and Microsoft.
Due to the nature of XenApp and the way that it works with shared resources, Windows Ink is unable to work on a XenApp host.
By default the Wacom pen attempts to use Windows Ink, which is why it then works in XenApp when the use of Ink is disabled.
For touch the 1152 always uses Windows Ink for one and two finger inputs.
This issue has been reported to Citrix by multiple sources and we know that they are working with Microsoft to resolve it in a future update to XenApp.
At the time of writing (Nov 2018) there is no work-around for this issue - it depends upon Citrix and Microsoft between them to produce a solution in a later release of XenApp and/or Windows.

DTH-1152 Touch works on primary monitor instead of the extended screen

Windows touch input is mapped by the operating system. The Wacom driver attempts to override this but may not always be successful in certain environments.
Touch mapping is easily set by opening the Tablet PC Settings, selecting the Display tab, clicking the <Setup> button to configure pen and touch displays, and selecting Touch to calibrate.
This Touch calibration tool is hidden on Windows 10 and there is no way to access it through the Windows 10 menu system - it can only be accessed through the Run dialog.
The following commands will open the Tablet PC Settings window:

Windows touch display mapping is stored in the Windows registry as the device path and the video path. These paths are unique to each machine and device, so it cannot be shared between machines.
So, this mapping will need to be performed individually on each machine, but the settings will stay for that device as it is currently connected to the computer.
It is possible to write a script to create these registry keys without calibration, but this would need to be created by the local IT services.
Relevant information for these registry keys and the Tablet PC Settings shortcut can be found in the screenshot below.

DTU 1141 not recognised on Mac OS 10.13.6 High Sierra

DisplayLink has a FAQ for this issue.
Please see the necessary steps to get a DisplayLink capable display working on 10.13.6 athttps://support.displaylink.com/knowledgebase/articles/1854724.

DTU-1141 not recognised on Mac OS Catalina 10.15

Please see the following FAQ for proper driver functionality on Mac OS 10.15 Catalina:

DTU-1031X does not work on Mac OS 11

The DTU-1031X is not supported on Mac OS 11 - although the pen works the display will not.

Please note however that the later model DTU-1031AX is supported and works fine.

DTU/DTH/DTK Troubleshooting Guide

  1. Ideally the DTU should be connected directly to a USB port on the PC using both cables. If it is necessary to use a USB hub it should be an A/C powered one.

  2. For the DTU 1141 it is advisory to connect the second USB plug to make sure the unit is receiving enough power.

  3. Ensure the latest release of the Wacom tablet driver is installed from the Wacom Drivers support page

  4. Ensure the latest release of the relevant video driver for the particular DTU model is installed as below.

DTU 1031/1141

For Windows 10 Anniversary Update version 1607 no graphics driver is needed.
For all other versions the DisplayLink driver for these devices is available here: DisplayLink driver download

The DisplayLink driver appears in Programs and Features as 'DisplayLink Core Software'. Older releases also show a second entry for 'DisplayLink Graphics'

DTU 1031X

Please download the UV-A8301 USB 2.0 Display Adapter. (Please note that the MAC driver supplied in the download file is not compatible with the 1031X). Normally the MCT driver will update automatically to the latest version from the Internet if your PC is connected to it. The 1031X MCT driver will appear in 'Programs and Features' on your PC as 'Trigger External Graphics Family....' - see the screenshot at the bottom of this page

  1. Reboot the PC after installing any of the above drivers

  2. Check that the DTU appears as a 'Wacom Tablet' under Human Interface Devices in Device Manager. In most versions of Windows it should also appear as a USB Display Adapter as below

On Windows 10 Anniversary Update version 1607 it will appear under Display Adapters and also under Human Interface Devices as shown below.

  1. Check that the DTU is recognised by Windows as a monitor in the Windows Screen Resolution dialog

  2. Once the relevant drivers are installed please check that the 'Wacom Professional Service' service is running in Windows Services - if not then uninstall and reinstall the driver and check again.

  3. For the DisplayLink driver there should also be a Windows Service called 'DisplayLinkManager' and this should also be running. If not start it manually.If it doesn't start automatically at the next reboot try uninstalling and re-installing the DisplayLink driver.

  4. For the DTU-1031X the Wacom Professional Service should be running but there is no graphics driver service as such. You should however find a new purple icon in your system tray.Please see the 'Programs and Features' screenshot below for an illustration of what the icon looks like.

  5. From the Wacom Desktop Center, under 'Backup Settings' select 'Reset settings' under 'Local backup'.

  6. Calibrate the pen using the Wacom Tablet Control Panel which should appear in your Start menu as 'Wacom Tablet Properties' (this is not normally required but if your pen is out of line that it may help).

  7. After completing the above tasks, if the signature capture window fails to appear or appears but does not ink then proceed as follows:

    • Uninstall and reinstall the tablet driver
    • If this fails then run the capture analyser test tool. If you can't find this in your list of programs then the executable is called 'FlCaptureAnalyser.exe' and can be found in either:
Wacom tablet drivers windows 10

If you haven't installed the SDK (perhaps because you have sign pro PDF instead) please download the analyser from the Capture Analyser download link on our Test signature capture page.
After starting the capture analyser please select the 'Test Capture' option under the Service menu and then select 'wintab'.
Save the output in a text file and send it to us as an attachment on a support ticket.Support tickets can be created by clicking the 'Initial Support Request' button on our Support Page.
We will endeavour to respond within one business day.
Please note that you will need to register on the Developer Relations site first via the 'Login' link if you haven't already done so.

  1. If none of the above actions resolves the problem then it will probably be necessary to enable driver logging and send the log files via a support ticket.

'Programs and Features' showing the Trigger Family video driver and Wacom tablet driver:

Enable driver logging

Driver version 6.3.36 and later

  • Open the Wacom Desktop Center and select Support on the left
  • Click on 'Driver logging'
  • Press the 'Clear log files' button to remove the old logfiles from your logs folder
  • Click the 'Logging' on/off switch - this enables logging and restarts the tablet driver
  • When the driver has finished starting up, you should see new logfiles in the logs folder (the default is C:wacomlogs)
  • Use the tablet until a problem occurs
  • When the problem happens, press the 'Package log files' button to create a zip file, WacomLogs.waczip, on your desktop
  • Send the zip file to the Wacom Support system by attaching it to your Support Ticket

The driver logs are created in C:WacomLogs and logs will continue to generate in that location until logging is disabled.
The logs only capture the Wacom driver's trace statements, the username of the current user session, the OS version of the machine in use, and theapplication name of the front-most application as that changes.

Wacom Tablet Download Driver

Driver version 6.3.28-3 and later

  • Open the Wacom Tablet Preference Utility - this now has some controls to manage log files
  • Press the 'Clear Logs' button to remove the old logfiles from your logs folder
  • Check the checkbox: 'Diagnostic Logging On' - this enables logging and restarts the tablet driver
  • When the driver has finished starting up, you should see new logfiles in the logs folder (the default is C:wacomlogs)
  • Use the tablet until a problem occurs
  • When the problem happens, press the 'Package Logs' button to create a zip file, WacomLogs.waczip, on your desktop
  • Send the zip file to the Wacom Support system by attaching it to your Support Ticket

The driver logs are created in C:WacomLogs and logs will continue to generate in that location until logging is disabled.
The logs only capture the Wacom driver's trace statements, the username of the current user session, the OS version of the machine in use, and theapplication name of the front-most application as that changes.

Driver versions up to 6.3.27

Download the zip file debuggingProRegistryScripts.zip. This contains two reg files; one to enable logging and one to disable logging.
To use these, you have to manually create a folder for the logs.
The scripts use C:wacomlogs by default, but you can edit the scripts to use any folder with permissions.

  1. Create the logs folder (see 1 above)
  2. Stop the driver service
  3. Execute the debuggingprofull.reg script to enable logging
  4. Start the driver service
  5. Run until the problem occurs
  6. Create a minidump from the task manager as follows:
    1. Open Task Manager
    2. Select the Details tab
    3. Right-click on Wacom_Tablet.exe
    4. Select 'Create Dump File'
    5. The pop-up will indicate where the minidump file was written
  7. Execute the debuggingprofullu.reg script to disable logging
  8. Stop the driver service
  9. Zip up the logs folder and the minidump
  10. Add the zip file as an attachment to a Support Ticket.

Crash dumps

If you want to generate a crash dump from Internet Explorer please see these Microsoft instructions

Alternatively Procdump can be used to capture all crash dumps, including the full dump.

For example, use

in the Windows command line to set procdump as the last chance debugger. Removal is as simple as deleting the procdump executable when finished.

Installer Command Line Parameters

The parameters listed below can be passed in the command line to modify the driver installation process.
In the 'Example' column <Installer.exe> represents the installer file which was downloaded e.g.

C:Users<current user>DownloadsWacomTablet_6.3.36-1.exe

Function (Release)ParameterExampleDescription
Uninstall/u<Installer.exe> /uThe uninstall argument is useful for quickly cleaning up installations that did not succeed or were partially successful.
Silent Install/s<Installer.exe> /sThe silent install option is usually used by companies or organisations for mass deployment without disrupting users. It should install the driver without any user input and no messages should occur during the install that are visible by the user. Silent installs will skip the .NET download and installation as that function is not silent.
STU Mode Install/custom STU_MODE<Installer.exe> /custom STU_MODEThe 'STU mode' install option is typically used in signature environments as it prevents the tablet from functioning normally. The pen cannot be used for navigation in STU mode, instead it can only be used when a signature application assigns a signature window to the tablet. Once the signature is complete and submitted the pen should become inactive again.
No WDC Install (6.3.19)/opt nowdc<Installer.exe> /opt nowdcThe 'No WDC' install option allows users to skip the installation of the WDC (Wacom Desktop Center) during the install process. This is helpful for large deployments of devices that don't use the WDC, taking up less space after the install and removing any requirements the machine may need for .NET 4.0/4.5. at least on the part of Wacom.
No User Help Install (6.3.16)/opt nohelp<Installer.exe> /opt nohelpThe 'No User Help' install option allows users to skip the installation of the local User Help content during the install process. Online User Help content will still be accessible so long as a web connection is present.
No Internet Checks Install (6.3.29)/opt noinet<Installer.exe> /opt noinetThe 'No Internet' install option allows users to skip the checks for, downloads of, and installation of any driver/WDC prerequisites during the install process.
Enable Driver Logging (6.3.31)/opt DebugDrv<Installer.exe> /opt DebugDrvThe Enable Driver Logging argument is useful for enabling full driver logging on install.
Enable Wintab and Driver Logging (6.3.31/opt DebugDll<Installer.exe> /opt DebugDllThe Enable Wintab logging argument is useful for enabling full Wintab and driver logging on install.

Silent installation or uninstallation of tablet and video drivers

As of release 6.3.21-3 the Wacom driver can be installed silently using the command shown below from a prompt with administrator privileges:

To uninstall silently simply add /u to the command above.

How To Download Wacom Driver

Alternatively (and for older releases) you can proceed as below:

  • Rename the downloaded .exe extension to .zip, e.g. 'WacomTablet_6.3.21-3.exe' becomes 'WacomTablet_6.3.21-3.zip'
  • Extract all the files and folders from the zip file
  • Run 'setup.exe /silent (/uninstall)'

To install/uninstall the DisplayLink video driver silently (e.g. via SCCM or a batch script) you will need to use the DisplayLink corporate installer guide:

The silent installation switch for the MCT driver (for the 1031X) is '/s' - see also the MCT silent install command list:

Support for problems with the DisplayLink driver

DisplayLink do not provide support directly to end users. Some assistance is available from their DisplayLink Support Page.

A number of common problems are covered in the knowledge base. The forum contains a wide range of issues reported by DisplayLink users.

They also have a support tool which can be used to generate a log file which can then be forwarded to DisplayLink for their investigation or sent to us.
Please see How can I report Windows issues to DisplayLink?

Alternatively please raise a ticket on our system by clicking the 'Initial Support Request' button on our Wacom Support PageWe will endeavour to respond within one business day.
Please note that you will need to register on the Developer Relations site first via the 'Login' link if you haven't already done so.

Tablet installation

SYSTEM REQUIREMENTS

Wacom Tablet Driver

In terms of system specification there are no recommended RAM requirements for installing the Wacom tablet driver.
Our Pen Tablets use so few resources that we consider any computer that can operate a mouse and keyboard should be compatible with our tablets and drivers.

DisplayLink Graphics Driver

DisplayLink provide information about system compatibility with their graphics driver, which is required for some of our tablets (for more details see the overview below):
https://support.displaylink.com/knowledgebase/articles/544297-is-my-windows-computer-compatible-with-displaylink

MCT (Trigger Family) Driver

The recommended minimum hardware requirements for the MCT driver (required for the DTU-1031X) are as follows:

  • Available USB 2.0 port
  • 1~2 Displays (office application)
  • CPU: Intel/AMD Single Core 1.5GHz or higher processor
  • RAM: 1GB memory or higher
  • It is not recommended to play DVD (720p) via USB port because the USB2.0 bandwidth is not adequate and the performance of playing the DVD may be poor
  • Windows XP/Vista/7/8/8.1/10 (32-bit / 64-bit)
  • Higher processor recommended for multi-displays and optimal performance

TABLET AND DRIVER OVERVIEW

Our most commonly used tablets for business purposes are the 1031X, 1031, 1141 and 1152 (in ascending order of resolution).
For the 1031X, 1031 and 1141 two drivers are normally required:

  • Wacom tablet driver (to control features such as the pen and buttons)
  • Graphics driver to handle the USB video

For DTH and DTK models no graphics driver is required because the graphics signal is carried separately via an HDMI cable, not via USB.
The tablet driver is the same for all pen tablets but the 1031X requires a different video driver from the 1031 and 1141.

Please note that these 2 video drivers are mutually incompatible and cannot normally be installed together (it may be possible on the very latest version of Windows 10 but is not recommended).
This means that you cannot use the 1031 or 1141 at the same time as a 1031X on the same PC.
The installation of the DisplayLink graphics driver is normally handled by the Windows platform when a compatible DisplayLink display is connected.
Windows 10 has included basic DisplayLink support since the Anniversary update.
On Windows 7, Windows Update will fetch the appropriate driver for you and install it, but the installation is not silent.

MANUAL DRIVER INSTALLATION

Normally drivers are provided on a CD accompanying your Wacom device. If you do not have a CD you can proceed as follows:

  1. Navigate to the Wacom Drivers support page
  2. Select the appropriate driver for your operating system and download it
  3. Run the installer file - please note that the PC will need to be rebooted before continuing to complete this process
  4. If using the 1031 or 1141 download the DisplayLink driver from http://www.displaylink.com/downloads/windows
  5. For the DTU 1031X download the UV-A8301 USB 2.0 Display Adapter published on MCT's Web site. (Please note that the MAC driver included in the download file is not compatible with the 1031X).
  6. Please note that the MCT driver will update automatically to the latest version from the Internet if your PC is connected to it.
  7. Check that the installation was successful:
    • For the DisplayLink driver you should see an item called 'DisplayLink Core Software' in 'Programs and Features'. On old releases you will also see 'DisplayLink Graphics'
    • The 1031X driver will appear in 'Programs and Features' on your PC as 'Trigger External Graphics Family....' - see the screenshot at the bottom of this page.

Once the relevant drivers are installed please check that the 'Wacom Professional Service' service is running in Windows Services - if not please start it manually.
For the DisplayLink driver there should also be a service called 'DisplayLinkManager' and this should also be running.

For the DTU-1031X there is no service as such but you should find a new purple icon in your system tray.
Please see the 'Programs and Features' screenshot below for an illustration of what the icon looks like.
Before trying to capture a signature please check the following:

  • The pen tablet in question is configured to operate as an extended desktop
  • The tablet is displaying the Windows background
  • The pen is calibrated - the calibration dialogue should appear automatically the first time you touch the pen on the tablet - if it does not please run it from the Wacom Control Panel

TROUBLESHOOTING

After completing the above tasks, if the signature capture window fails to appear or appears but does not ink then proceed as follows:

  • Uninstall and reinstall the tablet driver
  • If this fails then run the capture analyser test tool - this is called 'FlCaptureAnalyser.exe' and can be found in either:
    C:Program Files (x86)Common FilesWacomGSS
    or
    C:Program FilesCommon FilesWacomGSS (if you have run the 64-bit installer for the Signature SDK)
    If you haven't installed the SDK (perhaps because you have sign pro PDF instead) please download CaptureAnalyser from the Test signature capture page.

After starting the capture analyser please select the 'Test Capture' option under the Service menu and then select 'wintab' and attach the output as a text file to a Support Ticket.

If you have any difficulty with following the above procedure please raise a Support Ticket.

'Programs and Features' showing the Trigger Family video driver and Wacom tablet driver:

Test the correct functioning of a DTU

1. Check Device Manager to make sure that all HID displays are displayed without any incident (i.e. a yellow exclamation mark).

2. Check that the Wacom driver is operating correctly using one of the following methods:

  • Open Wacom Desktop Center
  • Go to 'Support', the button is on the left side pane
  • Select 'Driver check'
  • Click 'Start'
  • If the next dialog says the check was successful, that is an indicator that the driver is not experiencing any problems

Another method is:

  • Open the Wacom Tablet Properties
  • Select the DTU device in the 'Device' row at the top
  • Select the 'About' button
  • Select 'Diagnose...' to see real time stylus input
  • If you hold the CTRL button while selecting 'Diagnose' you will get what we describe as 'Raw' data - i.e. it is essentially unprocessed

Wacom tablet driver 6.3.30 requires .NET framework 4.5

.NET 4.5 is only required for the Wacom Desktop Center, which is included in the 6.3.30 driver package.
The Wacom Desktop Center software does not support the DTU-1141 or 1141B, so it is not necessary to install it for use with that device.
If the customer uses the '/opt nowdc' parameter during install they can exclude this software and .NET 4.5 will not try to install.

Example:

What graphics driver is required for my DTU?

In addition to the Wacom tablet driver the DTU 1031, 1141 and 1141B require the installation of the DisplayLink graphics driver

The 1031X and 1031AX (Adonis Light) require a different graphics driver provided by MCT.
For this please download the UV-A8301 USB 2.0 Trigger Family Display Adapter. (Please note that the MAC driver included in the download file is not compatible with the 1031X or AX).

All other DTU, DTH, and DTK tablets use a standard video connection such as DVI, HDMI, DisplayPort, or USB Type-C and do not require a supplementary video graphics driver.

PLEASE NOTE:
The DisplayLink and MCT drivers should not normally be installed together on the same PC because they are incompatible - in fact they mutually exclude each other at installation time.
It may be possible to avoid conflicts on the very latest releases of Windows 10 where DisplayLink have worked with Microsoft to provide support natively within Windows.

With older releases of Windows installation of both drivers is not possible so in those cases the DTU 1031 and 1031X cannot be used together on the same computer.

Where are the log files for the DisplayLink driver installation?

The installation log files for the DisplayLink driver are called setupapi.xxx.log
(where 'xxx' could be for example 'offline' or 'setup' or 'dev' or 'upgrade')
and are found in C:WindowsINF

Windows cannot verify the digital signature for the drivers required for this device

Scenario

  1. Wacom tablet driver has been installed on the PC
  2. The appropriate graphics driver (MCT or DisplayLink) has been installed
  3. Wacom Tablet Properties displays an error 'Your device is not connected to your computer'
  4. Device Manager reports error 52: 'Windows cannot verify the digital signature for the drivers required for this device'
  5. Windows Update KB 3153171 has been installed or is not appropriate for the computer

Probable solution

It is very likely that the computer does not have the necessary SHA-2 driver signature support. This was distributed through Windows updates, and the customer can review their installed updates to see if it's installed.
SHA-2 driver signatures are required for all new hardware drivers produced after October 2014. SHA-2 driver signatures are native to Windows 8 and Windows 10, but not to Windows 7.
Without the necessary update, Windows 7 will believe that a driver signed with SHA-2 is invalid, as it will not recognize the signature.

More information on this can be found in Microsoft's Support articles for the associated KB updates here: https://docs.microsoft.com/en-us/security-updates/securityadvisories/2015/3033929

Wacom Ink SDK for devices


Wacom Ink SDK for devices allows you to integrate Wacom and third-party inking devices into your applications. The Common Device Library (CDL) SDK currently supports:


  • Wacom Smartpads (Folio, Slate)
  • Intuos Pro Paper Edition
  • Apple pencil on iPad Pro.

Future releases will add support for additional Wacom devices, as well as inking devices from other vendors.


Platform-specific packages are also available for iOS, Android, Windows, UWP/Desktop, and Web, depending on the device.


The Common Device Library (CDL) SDK within Wacom Ink Connectivity is designed as one library that can handle different types of pen or touch input. The advantages of this approach include:


  • Less implementation effort for developers: Integration of only one library, support for several pen input devices
  • The flexibility to include support for non-Wacom devices in your applications
  • The freedom to take full advantage of Wacom Ink Technologies to provide a high quality front-end and UI through optional receipt of RAW data from the device, without sacrificing the original data for internal/back-end usage i.e. it can deliver ink data but also retain raw pen data to be used in other ways.
  • Easy access to the Wacom Ink technology ecosystem through smooth integration of Wacom ink technology.

Wacom Device Kit


Use the Wacom Device Kit to add a Wacom device to your application using a variety of low-level tools.


No license key is required in your application, as the tools are free to use.


STU SDK


An input library for capturing pen data from all Wacom STU-series signature pads on Windows and Linux platforms.


Wintab API


An input API for capturing data from Wacom tablets and pen displays running Windows and OSX. Compatible tablets and displays include:


  • Intuos, Intuos 4, Intuos 5 and Intuos Pro display tablets
  • Cintiq and Cintiq Companion devices
  • ExpressKey Remote devices
  • Wacom MobileStudio Pro, Cintiq Pro and Intuos Pro devices

Wacom Digitizer Pen for Android API


An input API for integrating pen technology with applications running on Android.


Feel Multi-touch APIs


These APIs enable you to build applications that utilize the powerful finger detection and location capabilities of Wacom touch tablets. This stream of finger information can be used to create unique application features, including custom gestures or direct on screen manipulation.


Bluetooth Stylus SDK


This input SDK enables discovery of and connection to stylus devices, and the receipt of raw pressure and button state data. It also includes functionality to enable Touch Rejection, so that users can maintain a natural handwriting position without the display reacting to unintentional touches.