4,553 drivers total Last updated: Jan 19th 2021, 19:54 GMT RSS Feed. Latest downloads from ASUS in Keyboard & Mouse. Sort by: last update. ASUS Laptop X541UAK Touchpad Handwriting Driver 2.0.6 for Windows 10 64-bit 337 downloads. Keyboard & Mouse ASUS. Having an issue with your display, audio, or touchpad? Whether you're working on an Alienware, Inspiron, Latitude, or other Dell product, driver updates keep your device running at top performance. Step 1: Identify your product above. Step 2: Run the detect drivers scan to see available updates. Step 3: Choose which driver updates to install. The package provides the installation files for ELAN Touchpad Driver version 21.2.16.2. If the driver is already installed on your system, updating (overwrite-installing) may fix various issues, add new functions, or just upgrade to the available version. Get the best deals on Generic Wired Computer Mice and find everything you'll need to improve your home office setup at eBay.com. Fast & Free shipping on many items!

Related Assets

Product	Asset Type	Title	Date
TouchPad Family	Security Brief	TouchPad Security Brief - Jan 24, 2019	Jan 24, 2019
Product: TouchPad Family Asset Type: Security Brief Title: TouchPad Security Brief - Jan 24, 2019 Date: Jan 24, 2019			Download
TouchPad Family	Security Brief	TouchPad Security Brief - Dec 14, 2017	Dec 14, 2017
Product: TouchPad Family Asset Type: Security Brief Title: TouchPad Security Brief - Dec 14, 2017 Date: Dec 14, 2017			Download
TouchPad Family	Product Brief	ClickPad^TM	May 23, 2016
Product: TouchPad Family Asset Type: Product Brief Title: ClickPad^TM Date: May 23, 2016			Download
TouchPad Family	Product Brief	ForcePad®	May 23, 2016
Product: TouchPad Family Asset Type: Product Brief Title: ForcePad® Date: May 23, 2016			Download
TouchPad Family	Product Brief	SecurePad^TM	May 23, 2016
Product: TouchPad Family Asset Type: Product Brief Title: SecurePad^TM Date: May 23, 2016			Download
TouchPad Family	Product Brief	TouchPad^TM	May 23, 2016
Product: TouchPad Family Asset Type: Product Brief Title: TouchPad^TM Date: May 23, 2016			Download

-->

Note

This topic is for developers who are creating drivers for keyboard and mouse HID clients. If you are looking to fix a mouse or keyboard, see:

This topic discusses keyboard and mouse HID client drivers. Keyboards and mice represent the first set of HID clients that were standardized in the HID Usage tables and implemented in Windows operating systems.

Keyboard and mouse HID client drivers are implemented in the form of HID Mapper Drivers. A HID mapper driver is a kernel-mode WDM filter driver that provides a bidirectional interface for I/O requests between a non-HID Class driver and the HID class driver. The mapper driver maps the I/O requests and data protocols of one to the other.

Windows provides system-supplied HID mapper drivers for HID keyboard, and HID mice devices.

Architecture and overview

The following figure illustrates the system-supplied driver stacks for USB keyboard and mouse/touchpad devices.

Euresys driver download for windows. The figure above includes the following components:

KBDHID.sys – HID client mapper driver for keyboards. Converts HID usages into scancodes to interface with the existing keyboard class driver.
MOUHID.sys – HID client mapper driver for mice/touchpads. Converts HID usages into mouse commands (X/Y, buttons, wheel) to interface with the existing keyboard class driver.
KBDCLASS.sys – The keyboard class driver maintains functionality for all keyboards and keypads on the system in a secure manner.
MOUCLASS.sys – The mouse class driver maintains functionality for all mice / touchpads on the system. The driver does support both absolute and relative pointing devices. This is not the driver for touchscreens as that is managed by a different driver in Windows.
HIDCLASS.sys - The HID class driver. The HID Class driver is the glue between KBDHID.sys and MOUHID.sys HID clients and various transports (USB, Bluetooth, etc).

The system builds the driver stack as follows:

The transport stack creates a physical device object (PDO) for each HID device attached and loads the appropriate HID transport driver which in turn loads the HID Class Driver.
The HID class driver creates a PDO for each keyboard or mouse TLC. Complex HID devices (more than 1 TLC) are exposed as multiple PDOs created by HID class driver. For example, a keyboard with an integrated mouse might have one collection for the standard keyboard controls and a different collection for the mouse.
The keyboard or mouse hid client mapper drivers are loaded on the appropriate FDO.
The HID mapper drivers create FDOs for keyboard and mouse, and load the class drivers.

Important notes:

Vendor drivers are not required for keyboards and mice that are compliant with the supported HID Usages and top level collections.
Vendors may optionally provide filter drivers in the HID stack to alter/enhance the functionality of these specific TLC.
Vendors should create separate TLCs, that are vendor specific, to exchange vendor proprietary data between their hid client and the device. Avoid using filter drivers unless critical.
The system opens all keyboard and mouse collections for its exclusive use.
The system prevents disable/enabling a keyboard.
The system provides support for horizontal/vertical wheels with smooth scrolling capabilities.

Driver Guidance

Microsoft provides the following guidance for IHVs writing drivers:

Driver developers are allowed to add additional drivers in the form of a filter driver or a new HID Client driver. The criteria are described below:
1. Filters Drivers: Driver developers should ensure that their value-add driver is a filter driver and does not replace (or be used in place of) existing Windows HID drivers in the input stack.
  - Filter drivers are allowed in the following scenarios:
    - As an upper filter to kbdhid/mouhid
    - As an upper filter to kbdclass/mouclass
  - Filter drivers are not recommended as a filter between HIDCLASS and HID Transport minidriver
2. Function Drivers: Alternatively vendors can create a function driver (instead of a filter driver) but only for vendor specific HID PDOs (with a user mode service if necessary).
  Function drivers are allowed in the following scenarios:
  - Only load on the specific vendor’s hardware
3. Transport Drivers: Windows team does not recommend creating additional HID Transport minidriver as they are complex drivers to write/maintain. If a partner is creating a new HID Transport minidriver, especially on SoC systems, we recommend a detailed architectural review to understand the reasoning and ensure that the driver is developed correctly.

Generic Mice & Touchpads Driver Download