Share via

Surface pro 6 type cover not recognized

Anonymous
2020-08-17T13:58:44+00:00

I went through all troubleshooting, cleaned contacts with alcohol, reinstalled windows, but always Type cover not recognized. It lights up, but it must be a driver issue... Downloaded any driver msi package i could find, but still nothing. Restored system from USB.

the suggested microsoft fix on this less than 2 year old computer? A $450 'standard exchange'.

Outside of the driver issue, the computer works fine, and the type cover seems to work fine if it had a correct driver. Through no fault of mine, but flaky hardware, Microsoft gives me the opportunity to give them $450 to keep this junk.

Any solutions for this problem that I may not have uncovered?

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

6 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2020-10-02T12:56:50+00:00

    Sorry to hear -- they wanted $450 to exchange for a new surface. Thankfully for me it was a work computer, and even before attempting to buy a new type cover POS, or attempt an exchange, the experience of using the surface when it worked was infuriating enough for me to look elsewhere.

    Instead, I got a new MacBook Pro.

    Never again attempting a Microsoft product.

    8 people found this answer helpful.
    0 comments
  2. Anonymous
    2020-10-04T00:10:06+00:00

    Thanks much. That's probably the best solution to this teething issue, which sounded trivial for a keyboard not working for its own notebook.

    2 people found this answer helpful.
    0 comments
  3. Anonymous
    2020-08-17T23:59:57+00:00

    Hi, Green Valleyxx!

    Thanks for reaching out to Microsoft Community. We are sorry to learn you have issues with your Type Cover on your Surface Pro 6. Thanks for taking the time to let us know about this.

    It seems you've done most of the steps to troubleshoot the issue. May we know if you went to Surface UEFI? If not, please do these steps:

    1.    Select Start> Settings > Update & security  > Recovery.

    2.    Under Advanced startup, select Restart Now.

    3.    Under Choose an option, select Troubleshoot > Advanced Options > UEFI Firmware Settings, and then select Restart.

    4.    Verify if keyboard (arrow key) allows you to progress through the menus, or the touchpad allows control of the mouse arrow.

    Does the Type Cover (keyboard and touchpad) work there? If it doesn't work, the Surface Pro 6 needs to be replaced. 

    Also, can you go to Devices in the UEFI? Try to disable Type Cover port, then enable.  Hit on Exit, then Restart. If the Type Cover still doesn't work, I am afraid the device needs to sent in for replacement. 

    If this answers your question, please let our Community know by marking this post as an answer. Otherwise, don't hesitate to respond to this thread if there’s anything else that needs to be addressed. 

    Kind regards,

    Janette_Z

    2 people found this answer helpful.
    0 comments
  4. Anonymous
    2020-10-02T10:09:41+00:00

    Worse experience here, in the midst of trouble-shooting, I bought another type cover, ~USD180, thinking that it was faulty. However, the problem persists. I have done the same on my Surface Pro 6 - all troubleshooting steps, including checking Surface UEFI that the "Type Cover port" is enabled under "Devices". cleaned contacts, and just reinstalled Windows. The Type Cover key board could type but not the touch pad. After restart, the Type Cover has no response at all or touch paid not working - problem not solved at all!

    Same less than 2yo unit, now with 2 type covers that can't work on it. Is there any way to exchange as it's just slightly over the 1 year warranty.

    1 person found this answer helpful.
    0 comments
  5. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more