The system builds the driver stack as follows: The HID Class driver is the glue between KBDHID.sys and MOUHID.sys HID clients and various transports (USB, Bluetooth, etc). This is not the driver for touchscreens as that is managed by a different driver in Windows. The driver does support both absolute and relative pointing devices.

MOUCLASS.sys – The mouse class driver maintains functionality for all mice / touchpads on the system.

KBDCLASS.sys – The keyboard class driver maintains functionality for all keyboards and keypads on the system in a secure manner.

Converts HID usages into mouse commands (X/Y, buttons, wheel) to interface with the existing keyboard class driver.

MOUHID.sys – HID client mapper driver for mice/touchpads.

Converts HID usages into scancodes to interface with the existing keyboard class driver.

KBDHID.sys – HID client mapper driver for keyboards.

The figure above includes the following components: The following figure illustrates the system-supplied driver stacks for USB keyboard and mouse/touchpad devices. Windows provides system-supplied HID mapper drivers for HID keyboard, and HID mice devices. The mapper driver maps the I/O requests and data protocols of one to the other. 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. Keyboard and mouse HID client drivers are implemented in the form of HID Mapper 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. This topic discusses keyboard and mouse HID client drivers.

Troubleshoot a wireless mouse that does not function correctly.

Mouse, touchpad, and keyboard problems in Windows.

If you are looking to fix a mouse or keyboard, see:

This topic is for developers who are creating drivers for keyboard and mouse HID clients.

Keyboard error windows 8