A Wacom tablet that worked flawlessly on Intel can turn temperamental on a Snapdragon laptop: the pen moves but pressure is gone, express keys do nothing, or the driver installer refuses to finish. Drawing tablets sit at the intersection of hardware drivers and creative apps, which makes them one of the trickier peripherals on Windows on ARM. The core question is always the same — is the right driver actually installed and running, or is Windows limping along on generic pen input? Drawing tablets combine kernel drivers, user-mode services, and per-app pen APIs — three layers where ARM differences can hide — so methodical, layer-by-layer testing beats guessing every time.

Start in Device Manager and the Wacom Desktop Center: if the tablet appears as a generic HID device rather than a Wacom device, the driver stack is the problem. This is the peripheral version of drivers missing on Windows ARM — same triage, different device. App-side issues compound it; Photoshop issues on ARM laptops are worth reading if the tablet misbehaves only inside Adobe apps. And if Recall captures private browsing concerns you while working, that is a separate privacy setting.

The fixes below cover driver selection, clean reinstallation, pressure restoration, and the app-specific gotchas that follow. For offline captioning while you work, Live Captions offline speech models are a handy separate setup.

Why this happens

  • Wrong-architecture driver installed: An x64 driver under emulation may install but fail to communicate reliably with the tablet’s firmware.
  • No ARM64 driver for older tablets: Wacom prioritizes current models for ARM64 drivers; older tablets may be stuck with emulated x64 drivers.
  • Generic Windows pen driver taking over: If the Wacom driver fails, Windows falls back to basic pen input — movement without pressure or buttons.
  • Driver blocked by memory integrity: Windows security features can block improperly signed or incompatible driver components.
  • Conflicting tablet drivers: Leftover drivers from previous tablets fight over the device.
  • USB power or hub issues: Tablets are sensitive to underpowered hubs; connection flakiness masquerades as driver failure.

How to fix it

Work through these in order — diagnose first, then act.

Fix 1: Install the correct Wacom driver for ARM

The right driver for your architecture and model is the whole battle.

  1. Identify your exact tablet model from its underside label.
  2. Check Wacom’s download page for ARM64 or Windows-on-ARM driver notes.
  3. Download the newest driver matching your model.
  4. Uninstall any existing Wacom driver first via Settings.
  5. Install fresh with the tablet disconnected, then connect when prompted.

Fix 2: Do a clean driver reinstall

Layered installs accumulate conflicts. A purge followed by one clean install resolves most cases.

  1. Uninstall all Wacom software from Settings, then Apps.
  2. Restart the laptop.
  3. Check Device Manager for leftover Wacom devices and remove them.
  4. Install the latest driver as administrator.
  5. Open Wacom Desktop Center and confirm the tablet is recognized.

Fix 3: Restore pressure sensitivity

Pressure loss with a working cursor almost always means the driver stack is incomplete.

  1. Confirm Wacom Desktop Center shows the tablet, not a generic device.
  2. Check the pen settings for pressure curve configuration.
  3. Test pressure in Wacom’s own test area before blaming apps.
  4. In the app, verify Windows Ink or Wintab settings match the driver.
  5. Toggle between Wintab and Windows Ink APIs if the app offers the choice.

Fix 4: Check USB connection and power

Rule out the physical layer before deeper driver surgery.

  1. Connect the tablet directly to the laptop, bypassing hubs.
  2. Try a different USB port, preferably USB-C or a rear port.
  3. Test with the tablet’s original cable.
  4. Watch Device Manager while unplugging and replugging for detection.
  5. If wireless, re-pair the Bluetooth connection from scratch.

Fix 5: Handle memory integrity blocks

Security features can silently block driver components.

  1. Open Windows Security, then Device security, then Core isolation.
  2. Note whether Memory integrity is on and whether the driver complains.
  3. Check Wacom’s support notes for compatibility statements.
  4. Update to the newest driver before considering any security changes.
  5. Never disable memory integrity permanently for a peripheral — seek a driver update instead.

Fix 6: Fix app-specific tablet issues

When the tablet works in one app but not another, the app’s pen API setting is usually wrong.

  1. Identify whether the app uses Wintab or Windows Ink.
  2. Match the app’s setting to what the Wacom driver provides.
  3. Check the app vendor’s ARM-specific notes.
  4. Test in a simple app like Whiteboard to isolate the variable.
  5. For vendor driver help, see Wacom-adjacent guidance via Microsoft on pen input.

Fix 7: Test with the Windows Ink fallback

If the Wacom driver refuses to cooperate, Windows Ink provides a usable fallback for basic drawing while you sort out the driver situation. It will not replace pressure curves and express keys, but it keeps you working — and comparing Ink behavior against Wacom-driver behavior is itself a useful diagnostic that tells support exactly where the failure lies.

  1. Unplug the tablet and uninstall the Wacom driver temporarily.
  2. Reconnect and let Windows install its generic pen driver.
  3. Test basic pen input in a simple drawing app.
  4. Note what works under Ink versus what needs the Wacom stack.
  5. Reinstall the Wacom driver with this comparison in hand.

Closing

Wacom tablets on ARM Windows demand the right driver and a clean install — get those two right and pressure, express keys, and pen buttons behave as they should. When in doubt, simplify: direct USB connection, one driver version, and the app’s pen API set to match. Keep notes on which driver version works with your tablet model; when Wacom ships updates, you will know exactly what good looks like and can spot regressions immediately.

Frequently asked questions

Does Wacom officially support Windows on ARM?
Support has been evolving. Check Wacom’s driver download page for explicit Windows-on-ARM or ARM64 notes for your tablet model. Older models may rely on x64 drivers running under emulation, which works but can be finicky.
Why does my tablet connect but pressure sensitivity not work?
Pressure needs the full Wacom driver stack, not just the generic Windows pen input. If Windows sees the tablet as a basic pen device, the Wacom driver is missing, mismatched, or blocked.
Can I use my Wacom tablet without the official driver?
Partially. Windows Ink provides basic pen input without Wacom’s driver, but you lose pressure curves, express keys, and per-app settings — the reasons most people buy a Wacom.
Will an x64 Wacom driver work on ARM Windows?
It can install and run under emulation, and many users report it works. But driver-level emulation is less forgiving than app emulation, so prefer an ARM64-native driver whenever Wacom offers one.