Surface Type Cover Filter Device Not In Device Manager
I have two users who have Microsoft Surface Pro 4 (Win 10 Pro x64 ver 1709) with type covers and surface docks. Both of them had issues this morning where the type cover didn't work nor did the USB keyboard and mouse plugged into the dock (the external monitor and ethernet ports on the docks were working). Looking in Device Manager I noticed this. I have tried doing a restart, hard restart, uninstalling the existing keyboard drivers and clicking on scan for hardware changes, but the surface type cover filter device doesn't come back. The package provides the installation files for Microsoft Surface Type Cover Integration Driver version 1.1.362.0. If the driver is already installed on your system, updating (overwrite-installing) may fix various issues, add new functions, or just upgrade to the available version.
If restarting and re-attaching doesn't fix the problem, try reinstalling the driver for your Surface Cover.
For Surface Type Cover
Select the search box in the taskbar, enter device manager, and select Device Manager in the results.
Expand Keyboards.
Right-click Surface Type Cover Filter Device.
Select Uninstall > OK.
Restart your Surface. It'll automatically download and install the Surface Cover driver the next time you connect to the Internet.
For Surface Book
Select the search box in the taskbar, enter device manager, and select Device Manager in the results
Expand Keyboards.
Right-click *NEED DRIVER NAME*
Select Uninstall > OK.
Note: There are two drivers listed. One for the Clipboard battery, and one for the keyboard battery. Perform steps 3 and 4 on both drivers listed.Restart your Surface. It'll automatically download and install the Surface Keyboard drivers the next time you connect to the Internet.
Did this work? Test your keyboard in an available app like Microsoft Sticky Notes , or Notepad. Use the same program throughout your troubleshooting.
Surface Type Cover Device Driver
Surface Type Cover Filter Device Not In Device Manager Description
Did this resolve your issue?