Surface Pro 3 Type Cover Driver Download
Surface Pro 4 Type Cover Filter Device Driver Download
Reinstall Surface Pro 4 Type Cover Driver
Surface Type Cover Filter Device Missing
Surface Pro 4 Type Cover Filter Device Drivers

-->

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:

FINALLY FOUND THE SOLUTION!!!!!!

PC Pitstop - PC Performance Roots. PC Pitstop began in 1999 with an emphasis on computer diagnostics and maintenance. During the early days of the dot com boom, our online PC maintenance tools were skyrocketing.
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: 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.
The package provides the installation files for Microsoft Surface Pro 4 Type Cover Integration Driver version 1.1.359.0. If the driver is already installed on your system, updating.
Even when I update the driver and specify 'Surface type cover filter device' from HID kybd device It still doesn't work. Not sure why it should be so difficult to get A Microsoft surface cover kybd to work on A Microsoft surface pro using Microsoft Windows 10.

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.

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.
Driver developers should leverage driver Frameworks (KMDF or UMDF) and not rely on WDM for their filter drivers.
Driver developers should reduce the number of kernel-user transitions between their service and the driver stack.
Driver developers should ensure ability to wake the system via both keyboard and touchpad functionality (adjustable by the end user (device manager) or the PC manufacturer). In addition on SoC systems, these devices must be able to wake themselves from a lower powered state while the system is in a working S0 state.
Driver developers should ensure that their hardware is power managed efficiently.
- Device can go into its lowest power state when the device is idle.
- Device is in the lowest power state when the system is in a low power state (for example, standby (S3) or connected standby).

Keyboard layout

A keyboard layout fully describes a keyboard's input characteristics for Microsoft Windows 2000 and later versions. For example, a keyboard layout specifies the language, keyboard type and version, modifiers, scan codes, and so on.

See the following for information about keyboard layouts:

Keyboard header file, kdb.h, in the Windows Driver Development Kit (DDK), which documents general information about keyboard layouts.
Sample keyboard layouts.

To visualize the layout of a specific keyboard, see Windows Keyboard Layouts.

For additional details around the keyboard layout, visit Control PanelClock, Language, and RegionLanguage.

Supported buttons and wheels on mice

The following table identifies the features supported across different client versions of the Windows operating system.

Feature	Windows XP	Windows Vista	Windows 7	Windows 8 and later
Buttons 1-5	Supported (P/2 & HID)	Supported (PS/2 & HID)	Supported (PS/2 & HID)	Supported (PS/2 & HID)
Vertical Scroll Wheel	Supported (PS/2 & HID)	Supported (PS/2 & HID)	Supported (PS/2 & HID)	Supported (PS/2 & HID)

Surface Pro 4 Type Cover Filter Device Driver