Windows 7 Keyboard Driver Download
Kathrine Selvage
Upon imaging a Surface Laptop 2 with our basic image from the older Surface laptop model the Surface Hid Mini Driver driver fails to power and thus the keyboard doesn't work. if I revert back to 03/27/2017 driver it works fine... but then the laptop automatically updates itself to the latest version that brakes again. I have blocked the update in WSUS.
Is anybody aware of a fix for the latest driver? Does the PC somehow think its a Surface Laptop 1st gen and somehow downloading the incorrect driver possibly? I also downloaded the latest firmware/driver package from MS and tried that version and it also doesn't work. Seems to be the same exact version that gets downloaded from Windows Update.
Being the very-smart, highly-intelligent person that I am () I tried to install the Windows Bootcamp drivers on the machine manually. What I mean by manually is, I opened the Bootcamp installer in 7-zip and found what looked like they keyboard drivers' setup component. I extracted this piece and ran the .exe.
Because it was not installed in the conventional manner, I didn't get any prompts and, at first, I didn't notice it did anything, presumably because there were other components I didn't install. Eventually I realized that my many of my Function keys (any with other controls on them, such as F1-F4 & F7-F12) didn't seem to work. I later found out that they only work when pressing the "fn" button above the arrow keys on the keyboard.
I've tried manually uninstalling the Keyboard drivers from the Device Manager in Windows. The device manager shows two keyboard devices (no idea why), so I've de-installed both and re-installed them. This didn't change anything at all.
This should display every driver windows considers compatible with your hardware, hopefully the list will include a few items one of which will be the original driver.
If what you are looking for does not appear there, you can uncheck the "show compatible hardware" box and look through the whole list, mainly under the "(standard keyboards)" category.
This time, when it looks for a keyboard driver, it will not find the Bootcamp one that is considered to be newer (and thus presumably better). Therefore it will search for the next best driver it can, building a new cache and driver database, and then install whatever you used before.
It would be worth a try to install the drivers as they were meant to be, then uninstall them the right way.At least, once their install correctly, there is probably an option in the program to use the F-Keys as normal, and using the "Fn" key as a modifier.
thanks for your quick reply IIIaass. I have downloaded all the windows support drivers from bootcamp assistant but nothing seems to be working, reinstalled, repaired the drivers etc. it says 'driver error' could you send a link to correct driver for wireless keyboard. Maybe, it is the driver!
I installed bootcamp the both to a mac mini, and everything works fine there (wireless keyboard too), but for the installation onto a macpro late 2013 everything works fine, WI-FI, GPU, wireless mouse, BT, etc. all of the drivers are OK, with the exception of the wireless keyboard where the bluetooth manager says: Driver Error.
You have to go to "Device Manager" (right click on Start: Device Manager option), at the HID leaf (that stands open 'cause of a driver error), simply uninstall and delete the wrong driver. Magically everything works fine, and the wireless keyboard will be reported on the Keyboards leaf of the Device Manager.
This didn't work for me. I have exactly the same problem. It says "driver error" for the keyboard, while the magic mouse works fine. If I delete the driver, it shows a "System Administrator's Keyboard" is connected with bluetooth, but the keyboard still doesn't work.
The only thing I can think of is that this model of Dell Precision was not tested in the Fall Creator update back in OCT17 by Dell. Drivers were not updated, so either some other driver might work or there is no telling if something could hose the drivers all together. It also could be possible that Windows 10 is not supported for this machine all together.
Another possibility is that someone could have plugged something into the USB ports causing Windows to flake out for I/O device drivers. I did one more test and was able to read/write a flash drive, but not a desktop scanner or other brand/model keyboard and mouse.
I was having this same issue, just with a different model of keyboard/mouse (Dell machine and wireless keyboard/mouse combo) and after uninstalling the KB4074588 update like michellelieske suggested, the issue was resolved. I was able to remote into the machines and uninstall that way. My best guess is that it was a registry change made by the patch that caused the issue.
The issue was that most USB devices would not be recognized, as well as the touch screen would not work. The USB devices would return a code 28. For example, plugging in a mouse would cause the red light on it to appear for several seconds before turning off. I had tried disabling selective suspend by editing the registry and a lot of other unsuccessful items.
I recently updated to Windows 10 anniversary update and recentlly noticed the PS/2 Keyboard has stopped working in Windows 10 apps such as the settings menu and the start menu. Desktop apps and control panel work fine including shortcuts buttons such as volume up, web browser etc.
The default driver installed seems to be Lenovo ThinkPad driver PS/2 keyboard (which the keyboard Is not). I uninstalled the driver, un-plugged keyboard and tried changing the driver to the standard driver and HID keyboard driver with no luck.
None of the answers worked for me, so I simply opened Task Manager, killed explorer.exe (Task Manager - Details - locate explorer.exe and kill it) and run it again (Task Manager - File - Run new task - type "explorer").
I was wondering if anybody out there has had experience writing keyboard device drivers. I know the basics of how keyboard interrupts work however don't really know the details of everything. Is it difficult? Too difficult for one person?
I ask this because recently I purchased a Apple keyboard and the windows driver doesn't seem to recognize a lot of keys. Also if you know an easier solution to solve this other than writing a driver I would appreciate that as well. (I've already tried SharpKeys, seems like it's a windows driver problem that it can't recognize certain scan codes)
If you are interested in device drivers, try starting by writing a software-only driver. It will most likely be just a "toy", but you can do some really neat stuff in the kernel so maybe its worth having a toy driver. You can communicate between a user-mode .exe and your driver with an IOCTL. Maybe eventually you can update it into a software-only keyboard emulating driver, then try to upgrade it into the actual keyboard device driver that you want.
Non-HID keyboards and mice can connect over multiple legacy buses but still use the same class driver. This section contains details on the class drivers themselves. The following sections go into details on the controllers.
The figure shows a keyboard and a mouse connected to a system bus through independent controllers. A typical configuration consists of a POWERSHELL/2-style keyboard operated through an i8042 controller, and a serial-style mouse operated through a serial port controller.
The following figure shows the configuration of device objects for a Plug and Play PS/2-style keyboard and mouse device. Each class driver creates an upper-level class filter device object (filter DO) that is attached to a function device object (FDO) through an optional upper-level device filter DO. An upper-level device filter driver creates the upper-level device filter DO. I8042prt creates the function DO and attaches it to a physical device object (PDO) created by the root bus driver.
Kbdclass and Mouclass can support more than one device in two different modes. In the one-to-one mode, each device has an independent device stack. The class driver creates and attaches an independent class DO to each device stack. Each device stack has its own control state and input buffer. The Microsoft Win32 subsystem accesses input from each device through a unique file object.
Kbdclass and Mouclass operate in the one-to-one mode if their registry entry value ConnectMultiplePorts is set to 0x00 (under the key HKLM\Services\CurrentControlSet\\Parameters, where class service is Kbdclass or Mouclass). Otherwise Kbdclass and Mouclass operate in grandmaster mode.
The Microsoft Win32 subsystem opens all keyboard and mouse devices for its exclusive use. For each device class, the Win32 subsystem treats input from all the devices as if the input came from a single input device. An application can't request to receive input from only one particular device.
The Win32 subsystem dynamically opens Plug and Play input devices after it receives notification from the Plug and Play manager that a GUID_CLASS_KEYBOARD or GUID_CLASS_MOUSE device interface is enabled. The Win32 subsystem closes Plug and Play devices after it receives notification that an opened interface is disabled. The Win32 subsystem also opens legacy devices by name (for example, "\Device\KeyboardLegacyClass0"). Once the Win32 subsystem successfully opens a legacy device, it can't determine if the device is later physically removed.
If the device is in the Plug and Play started state, the class driver sends the IRP_MJ_CREATE request down the driver stack. Otherwise the class driver completes the request without sending the request down the driver stack. The class driver sets the trusted file with read access to the device. If there's a grandmaster device, the class driver sends a create request to all the ports that are associated with the subordinate class devices.
ff7609af8f