The criteria are described below:įilters 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. Microsoft provides the following guidance for IHVs writing drivers:ĭriver developers are allowed to add additional drivers in the form of a filter driver or a new HID Client driver. The system provides support for horizontal/vertical wheels with smooth scrolling capabilities.The system prevents disable/enabling a keyboard.The system opens all keyboard and mouse collections for its exclusive use.Avoid using filter drivers unless critical. Vendors should create separate TLCs, that are vendor specific, to exchange vendor proprietary data between their hid client and the device.
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.