Surface Pro 3 Type Cover Not Working, In BIOS/UEFI or Windows 10 after 1803 Update

Anonymous
2018-06-27T15:11:46+00:00

My Surface Pro 4 Keyboard with Touch is no longer being recognized by my Surface Pro 3 after updating to 1803.

I have disconnected and reconnected dozens of times.  

I have cleaned my connectors on both the Surface Pro and the Keyboard unit.

I have uninstalled the keyboard in Device Manager, as well as the mouse however the only things showing up there are HID compliant Mouse and Keyboard, nothing that says Surface or Type Cover.

I have hard reset the device several times (Volume Up and Power), also booting into UEFI/BIOS several times where the keyboard also does not work.

I registered my device with Microsoft to of course be told it is Out of Warranty.

I am in the process of downloading the Recovery Image from 2015 from a trustable 3rd party website since I cannot find any links to the recovery image on Microsoft's website.  This will I think put me back in time to before the 1803 update as far as Windows is concerned, however I am not sure if that will fix my problem since it is not being recognized in the BIOS.

Any suggestions you have would be greatly appreciated.

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

167 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2019-10-26T01:10:12+00:00

    This works for me.. but you need to follow Aziz's  instructions very closely.. it goes thru many windows ... you have to look for related settings then decices and printer.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2019-10-10T18:44:39+00:00

    A futile gesture, agreed. But sometimes persistence meets random coincidence and someone pays attention. I was banging on for a decade about a small aspect of Microsoft's implementation of TCP, and they eventually fixed it.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2019-10-09T20:23:25+00:00

    There's so many things this could be - smells to me like an old-school "CMOS battery" issue, because that matches the idea of "old(er) computer gets the issue, draining the battery sometimes fixes the problem until the next power event". I don't feel like mine coincided exactly with an update installation, though it is difficult to be certain. I'm based in the Seattle area, in case any Redmond-based engineers fancy investigating a unit with this issue.

    Was this answer helpful?

    0 comments
  4. Barb Bowman 80,805 Reputation points MVP Volunteer Moderator
    2019-10-09T16:20:39+00:00

    Thanks. Do you have a guess as to whether Microsoft can fix this with an update?

    Seems unlikely.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2019-10-09T16:17:14+00:00

    Thanks. Do you have a guess as to whether Microsoft can fix this with an update?

    Was this answer helpful?

    0 comments