Surface Pro 4 type cover suddenly not working.

Anonymous
2018-07-12T03:26:44+00:00

I don't know what happened. I turned my Surface Pro 4 on the other day and the type cover is dead. No lights. No response. No indication that it's working at all.  I rarely take my surface anywhere. 

This started on July 9th 2018. My system information is below. I've gone through all of the steps in the "Troubleshoot your Surface Type Cover or keyboard" page. I've tried to manually download and install the latest firmware and drivers from the "Download firmware and drivers for surface" page. I picked SurfacePro4_Win10_16299_1801701_1.msi. My device manager does not show the "Surface Touch Cover Filter Device" under keyboards or anywhere. It only shows the HID keyboard and cannot detect my type cover. The type cover is completely unresponsive. Also, my windows updates are completely up to date. I've provided the links to the troubleshooting pages I used below.

AGAIN, WTH

Troubleshoot your Surface Type Cover or keyboard

Download drivers and firmware for Surface 

Edition

Windows 10 Professional

Version

1803

OS Build

10.0.17134.165

Serial #

035060755053

Processor

Intel(R) Core(TM) i5-6300U CPU @ 2.40GHz

Graphics card

Intel(R) HD Graphics 520

System

OSType64BitX64

RAM

8 GB

Surface | Surface Pro | Install and update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

689 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2018-08-27T19:49:26+00:00

    I think the surface line of kit is great from a usability standpoint when it works. The problem is its had so many issues with updates that its a standing joke among IT pros. We had a few of them in work and whilst users love them they end coming back and swapping for normal Lenovo X series laptops as they are just too unstable.

    The surface book well they all came back and now the cover not working on the pros...............

    Can MS actually fix the fault - even rolling back the firmware would be great until they can fix it properly but I guess that is not possible......... what a shambles.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-08-27T09:39:12+00:00

    Same issue here. 

    July update appears to have stopped the Type Cover from being detected. 

    I have tried another Type Cover on the Surface Pro 4, with no joy. I tried the Surface Pro 4 cover on a 2017 Surface Pro and it worked just fine, ergo the issue is with the Surface Pro 4. 

    The contacts are fine, I have disabled and re-enabled the Type Cover port in the UEFI, again with no joy. 

    I've gone through all of the troubleshooting advice given here and nothing works. 

    The machine was working perfectly before the update. 

    This really is a poor show from Redmond.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-08-25T16:54:04+00:00

    Have the same issue. Nothing works. Sigh. Giving up hope.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-08-12T19:44:08+00:00

    Thanks  looks like just the thing I need.

    I tried my wifes Ipads bluetooth keyboard and that worked straight away so bluetooth is the way to go.

    I will be selling my MS typecover and using the proceeds to get a bluetooth one.

    Given up on waiting for MS to fix it and from what I have heard unlikely anyway.

    Good job I was gifted the surface and didn't pay for it or I would be royally hacked off.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2018-08-12T16:35:43+00:00

    Hi Walesdragon, I went ahead and purchased the 1byone bluetooth keyboard off of Amazon. It was $45.00 here is the link: https://www.amazon.com/gp/aw/d/B01LRR2GJC?psc=1&ref=yo_pop_mb_yo_pop_mb_pd_t2

    It has been working great for me. I haven’t tried the touchpad yet because I use the microsoft flex mouse. This type cover issue has been going on since April of 2017. I hope Microsoft will still fix it even though it doesn’t appear to be the case right now.

    Was this answer helpful?

    0 comments