Surface Type Cover Filter Device 1.1.504.0 enables support for new Surface Pro Type Cover and Surface Pro Signature Type Cover. Note: - When Surface updates are provided via the Windows Update service, they are delivered in stages to Surface customers. To use this site to find and download updates, you need to change your security settings to allow ActiveX controls and active scripting. To get updates but allow your security settings to continue blocking potentially harmful ActiveX controls and scripting from other sites, make this site a trusted website.
Reinstall Type Cover Driver
Hi Guys,
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!
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!