-->

Get drivers and downloads for your Dell Dell Multi-Device Wireless Keyboard and Mouse Combo KM7120W. Download and install the latest drivers, firmware and software. Support Dell.com DellTechnologies.com Search. Dell Wireless Keyboard free download - Wireless Wizard, Avro Keyboard, Ralink 802.11n Wireless LAN Card, and many more programs.

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.

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:

1. 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.

2. Driver developers should leverage driver Frameworks (KMDF or UMDF) and not rely on WDM for their filter drivers.

3. Driver developers should reduce the number of kernel-user transitions between their service and the driver stack.

4. 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.

5. 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.

Activating buttons 4-5 and wheel on PS/2 mice

The method used by Windows to activate the new 4&5-button + wheel mode is an extension of the method used to activate the third button and the wheel in IntelliMouse-compatible mice:

• First, the mouse is set to the 3-button wheel mode, which is accomplished by setting the report rate consecutively to 200 reports/second, then to 100 reports/second, then to 80 reports/second, and then reading the ID from the mouse. The mouse should report an ID of 3 when this sequence is completed.
• Next, the mouse is set to the 5-button wheel mode, which is accomplished by setting the report rate consecutively to 200 reports/second, then to 200 reports/second again, then to 80 reports/second, and then reading the ID from the mouse. Once this sequence is completed, a 5-button wheel mouse should report an ID of 4 (whereas an IntelliMouse-compatible 3-button wheel mouse would still report an ID of 3).

Note that this is applicable to PS/2 mice only and is not applicable to HID mice (HID mice must report accurate usages in their report descriptor).

Standard PS/2-compatible mouse data packet format (2 Buttons)

Note

Windows mouse drivers do not check the overflow bits. In case of overflow, the mouse should simply send the maximal signed displacement value.

Standard PS/2-compatible mouse data packet format (3 Buttons + VerticalWheel)

Standard PS/2-compatible mouse data packet format (5 Buttons + VerticalWheel)

Important

Notice that the Z/wheel data for a 5-button wheel mouse has been reduced to four bits instead of the 8 bits used in the IntelliMouse-compatible 3-button wheel mode. This reduction is made possible by the fact that the wheel typically cannot generate values beyond the range +7/-8 during any given interrupt period. Windows mouse drivers will sign extend the four Z/wheel data bits when the mouse is in the 5-button wheel mode, and the full Z/wheel data byte when the mouse operates in the 3-button wheel mode.

Buttons 4 & 5 on are mapped to WM_APPCOMMAND messages and correspond to App_Back and App_Forward.

Devices not requiring vendor drivers

Vendor drivers are not required for the following devices:

• Devices that comply with the HID Standard.
• Keyboard, mouse, or game port devices operated by the system-supplied non-HIDClass drivers.

Kbfiltr sample

Kbfiltr is designed to be used with Kbdclass, the system class driver for keyboard devices and I8042prt, the function driver for a PS/2-style keyboard. Kbfiltr demonstrates how to filter I/O requests and how to add callback routines that modify the operation of Kbdclass and I8042prt.

For more information about Kbfiltr operation, see the following:

• The ntddkbd.h WDK header file.

• The sample Kbfiltr source code.

Kbfiltr IOCTLs

IOCTL_INTERNAL_I8042_HOOK_KEYBOARD

The IOCTL_INTERNAL_I8042_HOOK_KEYBOARD request does the following:

• Adds an initialization callback routine to the I8042prt keyboard initialization routine.
• Adds an ISR callback routine to the I8042prt keyboard ISR.

The initialization and ISR callbacks are optional and are provided by an upper-level filter driver for a PS/2-style keyboard device.

After I8042prt receives an IOCTL_INTERNAL_KEYBOARD_CONNECT request, it sends a synchronous IOCTL_INTERNAL_I8042_HOOK_KEYBOARD request to the top of the keyboard device stack.

After Kbfiltr receives the hook keyboard request, Kbfiltr filters the request in the following way:

• Saves the upper-level information passed to Kbfiltr, which includes the context of an upper-level device object, a pointer to an initialization callback, and a pointer to an ISR callback.
• Replaces the upper-level information with its own.
• Saves the context of I8042prt and pointers to callbacks that the Kbfiltr ISR callback can use.

IOCTL_INTERNAL_KEYBOARD_CONNECT

The IOCTL_INTERNAL_KEYBOARD_CONNECT request connects the Kbdclass service to the keyboard device. Kbdclass sends this request down the keyboard device stack before it opens the keyboard device.

After Kbfiltr received the keyboard connect request, Kbfiltr filters the connect request in the following way:

• Saves a copy of Kbdclass's CONNECT_DATA (Kbdclass) structure that is passed to the filter driver by Kbdclass.
• Substitutes its own connect information for the class driver connect information.
• Sends the IOCTL_INTERNAL_KEYBOARD_CONNECT request down the device stack.

If the request is not successful, Kbfiltr completes the request with an appropriate error status.

Kbfiltr provides a template for a filter service callback routine that can supplement the operation of KeyboardClassServiceCallback, the Kbdclass class service callback routine. The filter service callback can filter the input data that is transferred from the device input buffer to the class data queue.

IOCTL_INTERNAL_KEYBOARD_DISCONNECT

The IOCTL_INTERNAL_KEYBOARD_DISCONNECT request is completed with a status of STATUS_NOT_IMPLEMENTED. Note that a Plug and Play keyboard can be added or removed by the Plug and Play manager.

For all other device control requests, Kbfiltr skips the current IRP stack and sends the request down the device stack without further processing.

Callback routines implemented by Kbfiltr

KbFilter_InitializationRoutine

See PI8042_KEYBOARD_INITIALIZATION_ROUTINE

The KbFilter_InitializationRoutine is not needed if the I8042prt default initialization of a keyboard is sufficient.

I8042prt calls KbFilter_InitializationRoutine when it initializes the keyboard. Default keyboard initialization includes the following operations:

• reset the keyboard
• set the typematic rate and delay
• set the light-emitting diodes (LED)

KbFilter_IsrHook

See PI8042_KEYBOARD_ISR. This callback is not needed if the default operation of I8042prt is sufficient.

The I8042prt keyboard ISR calls KbFilter_IsrHook after it validates the interrupt and reads the scan code.

KbFilter_IsrHook runs in kernel mode at the IRQL of the I8042prt keyboard.

KbFilter_ServiceCallback

See PSERVICE_CALLBACK_ROUTINE.

The ISR dispatch completion routine of the function driver calls KbFilter_ServiceCallback, which then calls the keyboard class driver's implementation of PSERVICE_CALLBACK_ROUTINE. A vendor can implement a filter service callback to modify the input data that is transferred from the device's input buffer to the class data queue. For example, the callback can delete, transform, or insert data.

Moufiltr sample

Moufiltr is designed to be used with Mouclass, the system class driver for mouse devices used with Windows 2000 and later versions, and I8042prt, the function driver for a PS/2-style mouse used with Windows 2000 and later. Moufiltr demonstrates how to filter I/O requests and add callback routines that modify the operation of Mouclass and I8042prt.

For more information about Moufiltr operation, see the following:

• The ntddmou.h WDK header file.

• The sample Moufiltr source code.

Moufiltr control codes

IOCTL_INTERNAL_I8042_HOOK_MOUSE

The IOCTL_INTERNAL_I8042_HOOK_MOUSE request adds an ISR callback routine to the I8042prt mouse ISR. The ISR callback is optional and is provided by an upper-level mouse filter driver.

I8042prt sends this request after it receives an IOCTL_INTERNAL_MOUSE_CONNECT request. I8042prt sends a synchronous IOCTL_INTERNAL_I8042_HOOK_MOUSE request to the top of the mouse device stack.

After Moufiltr receives the hook mouse request, it filters the request in the following way:

• Saves the upper-level information passed to Moufiltr, which includes the context of an upper-level device object and a pointer to an ISR callback.
• Replaces the upper-level information with its own.
• Saves the context of I8042prt and pointers to callbacks that the Moufiltr ISR callbacks can use.

Moufiltr Callback Routines

IOCTL_INTERNAL_MOUSE_CONNECT

The IOCTL_INTERNAL_MOUSE_CONNECT request connects Mouclass service to a mouse device.

IOCTL_INTERNAL_MOUSE_DISCONNECT

The IOCTL_INTERNAL_MOUSE_DISCONNECT request is completed by Moufiltr with an error status of STATUS_NOT_IMPLEMENTED.

For all other requests, Moufiltr skips the current IRP stack and sends the request down the device stack without further processing.

Callback routines

MouFilter_IsrHook

See PI8042_MOUSE_ISR.

A MouFilter_IsrHook callback is not needed if the default operation of I8042prt is sufficient.

The I8042prt mouse ISR calls MouFilter_IsrHook after it validates the interrupt.

To reset a mouse, I8042prt goes through a sequence of operational substates, each one of which is identified by an MOUSE_RESET_SUBSTATE enumeration value. For more information about how I8042prt resets a mouse and the corresponding mouse reset substates, see the documentation of MOUSE_RESET_SUBSTATE in ntdd8042.h.

MouFilter_IsrHook runs in kernel mode at the IRQL of the I8042prt mouse ISR.

MouFilter_ServiceCallback

See PSERVICE_CALLBACK_ROUTINE

The ISR DPC of I8042prt calls MouFilter_ServiceCallback, which then calls MouseClassServiceCallback. A filter service callback can be configured to modify the input data that is transferred from the device's input buffer to the class data queue. For example, the callback can delete, transform, or insert data.

After several days of waiting, you finally got your Dell wireless keyboard delivered to home. With much excitement, you opened the package and connected the wireless keyboard to your computer. However, in an air of awkwardness, you found your keyboard not working at all, as if it’s making some sort of silent protest.

Rest assured that you’re not alone – many people have reported the same issue. Usually it’s not that difficult to solve. Just follow this tutorial and do the troubleshooting by yourself!

How to fix Dell wireless keyboard not working

The first thing you should do is to pinpoint the cause of your issue. Take the steps in the following order:

Step 1: Check the batteries

1. First of all, look for any battery tabs that may prevent your batteries from offering power to the wireless keyboard. Then, make sure you remove the tabs.
2. Replace the old batteries with a brand new pair. While replacing the batteries, make sure that you align the positive end of a battery with the positive side of the battery compartment and vice versa.
3. See if your wireless keyboard gets back on track after you do the replacement; if so, then congrats – you’ve fixed the problem! Obviously the culprit for everything should be your worn-out batteries.

Step 2: Turn on the power

If there’s a power switch on your wireless keyboard, you should check whether you’ve turned it on. Usually you can find that switch at the bottom of your keyboard so make certain that the switch is set to ON.

Step 3: Plug the USB receiver into another port

Note that if you’re using an all-in-one PC, the USB receiver may be preinstalled in it. In this case, you should skip this step and head to the next one.

1. Remove the USB receiver of your wireless keyboard from the port you’re using currently. Then wait for about 10 seconds.
2. Plug the receiver into another USB port. Generally the port located at the back of your computer chassis is preferred because it has more electricity than the other ones. It might take you a minute or two to wait till your PC recognizes a new device plugged in.
3. Check to see if your keyboard is working properly now. If not, go on to the next step.

Step 4: Remove any devices that may weaken the wireless signal

Chances are that some devices nearby have interrupted the wireless connection between your device and its USB receiver. In this sense, you should:

1. Remove nearby objects such as TVs, cordless phones, and speakers far enough from your keyboard.
2. Turn off all your wireless devices including Bluetooth.
3. Make sure that your keyboard is close enough to its USB receiver, usually within 30 centimeters (1 foot).

Check to see if your wireless keyboard is working properly now. If not, please proceed to the next step.

Step 5: Connect your keyboard to another computer/laptop

This is a crucial step to determine whether it’s your keyboard or your PC that causes the problem. After connecting your wireless keyboard to another computer/laptop, test the device and see if it works well:

• If yes, then the culprit should be the previous computer you’re using.
• If not, the issue probably arises from an equipment malfunction in your wireless keyboard.

In the former scenario, you may go to Step 6 and take a closer look at your problem; in the latter however, you should visit Dell Support for technical support or warranty options.

Step 6: Reconnect your device

• If your USB receiver doesn’t have a Connect button on it, you should ignore this step and proceed to the next one. Or you may look for more specific instructions in your user manual on how to reconnect the wireless keyboard to its USB receiver.
• If your USB receiver has a Connect button, read on and follow the instructions below.

1. Plug your USB receiver into a usable port. Then press and hold the Connect button on it until the LED light flashes.
2. Press and hold the Connect button on your wireless keyboard until the light on its USB receiver stops flashing. Now your keyboard is in sync with the USB receiver.
3. Test to see whether your keyboard is functioning well. If not, please move on to the next step.

Step 7: Update the device driver

If you haven’t installed the driver for your Dell wireless keyboard properly, that may also lead to the keyboard-not-working issue. To solve it, you should update the corresponding driver right away.

There’re 3 ways you can update your Dell wireless keyboard driver:

Option 1 – Automatically (Recommended) – This is the quickest and easiest option. It’s all done with just a couple of mouse clicks – easy even if you’re a computer newbie.

Option 2 – Manually via Device Manager – It’s a simple method but sometimes Windows may not detect or provide you with the latest drivers. What’s more, it might take you some effort to open Device Manager without a physical keyboard.

Option 3 – Manually via the official website – You’ll need some computer skills and patience to update your drivers this way, because you need to find exactly the right the driver online, download it and install it step by step.

Option 1 – Automatically update your driver (Recommended)

If you don’t have the time, patience or computer skills to update the Dell wireless keyboard drivermanually, you can do it automatically with Driver Easy. More importantly, you don’t even need a physical keyboard to perform the update.

Driver Easy will automatically recognize your system and find the correct drivers for it. You don’t need to know exactly what system your computer is running, you don’t need to risk downloading and installing the wrong driver, and you don’t need to worry about making a mistake when installing. Driver Easy takes care of everything.

You can update your drivers automatically with either the FREE or the Pro version of Driver Easy. But with the Pro version it takes just 2 clicks:

1. Download and install Driver Easy.
2. Run Driver Easy and click the Scan Now button. Driver Easy will then scan your computer and detect any problem drivers.
3. Click Update All to automatically download and install the correct version of all the drivers that are missing or out of date on your system (this requires the Pro version – you’ll be prompted to upgrade when you click Update All). Or if you just want to update the keyboard driver for now, simply click the Update button next to it.

Note: you can do it for free if you like, but it’s partly manual.

Option 2 – Manually update your driver via Device Manager

You can also update your driver manually via Device Manager without the help of a keyboard. It might take you some effort, but it’s also the most commonly used method.

1. Right-click any empty space of the taskbar that locates at the bottom of your computer screen to open its context menu. Then make sure you enable the Show touch keyboard button option.
2. There appears a keyboard icon in the notification area on your taskbar. Click the icon to invoke a virtual keyboard.
3. Click the Windows logoicon at the left corner of your taskbar to open the Start menu. Then use the virtual keyboard to type device into the search box and select the Device Manager result.
4. Click the Keyboards category to open its drop-down list. Right-click on the keyboard model you’re using and select Update driver.
5. Click Search automatically for updated driver software.
6. Wait till the download and installation process finishes.
7. Click Close when it’s all done.
8. Now your driver has been updated by Windows successfully. Don’t forget to restart your computer for the changes to take effect even if you’re not asked to.

Option 3 – Manually update your driver via the official website

If you feel like updating your driver from the site of Dell, here’s how to do it:

1. Find your way to the official website of Dell, or you may simply click:
   https://www.dell.com/en-us
2. Move your mouse cursor to the Support option located in the upper part of the site. Then select Drivers & Downloads from its drop-down list.
3. Type your keyboard model into the search box if you know it clearly; otherwise you could just type wireless keyboard. Usually, you’ll be presented with a list of search suggestions below, so go on to select one from the list according to your keyboard model. (If you don’t know how to invoke a virtual keyboard on your computer, you may refer to Option 2.)
4. In the next window, make sure you choose the correct edition of your Windows system. Then download all the drivers you need.
5. Open the file where you’ve just downloaded the driver. In most situations, you’ll get a file with an EXE extension. Double-click on it and follow the onscreen instructions to install the driver.
6. Don’t forget to restart your computer for the changes to take effect even if you’re not asked to.

So far, have you succeeded in getting your Dell wireless keyboard to work? If not, I’ll suggest you read the user manual once again and see if you’ve missed anything during the setup process. As a last resort, you should contact Dell Support for more in-depth instructions.

Dell Keyboard Driver

If you have any questions or ideas about this article, please feel free to leave a comment below. Thanks for reading!