- Microsoft Surface Type Cover Filter Device Drivers
- Microsoft Surface Type Cover Filter Device Driver Backup
- Microsoft Surface Type Cover Filter Device Driver Download
Go to Control Panel Hardware and Sound Devices and Printers Open the Properties of 'Surface Type Cover' and select the Hardware tab. From this tab, open the properties of each associated device. Uninstall each device, deleting drivers when the option is available. Microsoft Surface Pro 3 laptop drivers for Windows 10 x64. Install drivers automatically. Surface Type Cover Filter Device. Download driver. Describes an update for the Surface Pro 4 Surface Type Cover Filter Device. My Surface Type Cover and Surface Mouse stopped working suddenly 2 days ago but I can't link that to an upgrade. I suspect a download of Epson drivers but that may just be paranoia. I spent around 30 hours downloading driver packs, resets, Bluetooth tests etc., without success.
Microsoft Surface Type Cover Filter Device Drivers
Symptoms:
- Following imaging with Windows 10 1903 using Configuration Manager OSD, the Type Cover doesn’t work at all (keyboard, trackpad).
- When rebooting the machine, the keyboard and trackpad both work when in the BIOS.
- When imaging the machine, both the keyboard and trackpad work in Windows PE.
The Surface Pro 3 was imaged and then patched up-to-date and the most recent Surface Pro 3 drivers available from Microsoft were applied, however the issue persisted.
To correct this issue, complete the following steps:
Microsoft Surface Type Cover Filter Device Driver Backup
- Open Control Panel and navigate to ‘Hardware and Sound’ and then ‘Devices and Printers’.
- Select the Surface Type Cover and open the properties for this device. Select the ‘Hardware’ tab on the dialog:
- In turn, select each of the device functions shown in the list and click the ‘Properties’ button:
- Click the ‘Change Settings’ button, then from the dialog that is shown select ‘Uninstall Device’. If offered the option to delete the driver software for this device, ensure that the checkbox to do so is selected (not all devices offer this option) and click ‘Uninstall’:
- Ensure this has been completed for all device functions shown in the list, then close the main properties dialog.
- Open the Device Manager for the computer, right-click the computer name at the top and select ‘Scan for Hardware Changes’.
- Expand the firmware section within Device Manager. For each of the items shown, right click the item and select ‘Update Driver’. Click ‘Search automatically for updated driver software’ from the dialog that is shown:
Note that if you’ve installed the latest Surface Pro 3 drivers, none of the firmware items shown are likely to be updated, but attempt to update each item. If you’ve not installed the latest drivers, the firmware list may have more generic titles which will be updated as the appropriate firmware is applied. - Repeat the process of updating the driver for each item under the Keyboards section of the Device Manager. Note that even with the most recent driver pack installed, all of these entries on the device I was working on were the generic ‘HID Keyboard Device’. We don’t know which one of the keyboard devices listed is the Type Cover, however when you get to the correct one you’ll that the driver that is installed is listed as ‘Surface Type Cover Filter Device’:
- As soon as this driver is installed, the Type Cover should start working again. In my case no reboot was required.
Microsoft Surface Type Cover Filter Device Driver Download
I own a surface pro 3 running on OS Windows 10.
It's on version: 1703 (Os Build 15063.540).
Recently my Type Cover Keyboard stopped working. I then looked at the 'Device Manager' to check the driver and saw that the Type Cover Driver is missing. This is probably the reason why SP3 does not recognize the keyboard. I tried looking for a downloadable driver for this but i could not find one. I also tried following every alternative solutions that I can see from the internet and nothing seems to have worked for me. I even came across a forum in microsoft, wherein someone reported a similar issue but we are all waiting for an answer from Microsoft. Then I saw this Forum, maybe one of you guys might have encountered the same problem and is able to find a working solution that I can try.
Hope to hear from you guys here.
Thanks!