Keyboard on new Surface Pro 11 does not always pair with unit upon startup

Anonymous
2024-08-24T16:52:33+00:00

I am on my second keyboard/cover for my new Surface Pro 11 and am experiencing the following issue: On some startups -- not the majority of them -- the keyboard does not pair with the Surface Pro unit. The only solution has been to detach the keyboard from the unit and reattach it. I have cleaned the contacts (although this issue arose almost immediately out of the box after purchase), and followed a few other suggestions that I found online. One thing I have not done is reinstall the drivers. I can't imagine that they are out of date and a check of each says that they are up to date and the best drivers for the unit.) So, my question is this: if two different, new keyboards have experienced the same problem, does it sound like the issue is with the Surface unit itself? And if so, what other remedies are there before I turn it over to an expert?

Surface | Surface Pro | Performance and maintenance

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

126 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2025-01-02T10:39:47+00:00

    I've been dealing with this issue since launch. Suggesting a fix as removing the keyboard and re-attaching is like the old adage "Did you try turning it off and back on again". This laptop has come nowhere near living up to the Microsoft hype or the ridiculous price tag, and MS is already doing what they always do with their supporters - forget about them.

    I totally agree. But can anyone actually talk to Microsoft? I've looked for email or phone number for them. They hide behind the Chatbot!

    Can anyone actually make contact and tell them this is widespread and unacceptable.

    Paul.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2025-01-01T14:33:04+00:00

    I've been dealing with this issue since launch. Suggesting a fix as removing the keyboard and re-attaching is like the old adage "Did you try turning it off and back on again". This laptop has come nowhere near living up to the Microsoft hype or the ridiculous price tag, and MS is already doing what they always do with their supporters - forget about them.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2024-12-31T17:16:48+00:00

    Thanks, I'll try it. But that's a workaround, not an acceptable long-term solution. One of the key features of a surface is its portability, and having to wait several minutes before I can fold it up and put it in my sleeve for travel goes against that purpose.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2024-12-31T09:18:20+00:00

    Same issue here with Surface 11 base model--keyboard usually isn't recognized on reboot unless I detach and reattach it. I'll try the suggestion to set touch keyboard to "never," but that's not a solution as I'll need it sometimes when using as a tablet.

    I avoid detaching the keyboard when not necessary, as I figure the connectors may wear out over time. This needs to be resolved.

    I have recently been following JDuplay's advice and it seems to work. Not a fix, but a work around.

    When you switch off, wait a minute or two, then slowly close the keyboard. I agree switching off touch keyboard is impractical and it didn't work for me.

    Not ideal, and Microsoft need to fix it as it seems common to all Surface 11's.

    Paul.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2024-12-31T04:54:07+00:00

    Same issue here with Surface 11 base model--keyboard usually isn't recognized on reboot unless I detach and reattach it. I'll try the suggestion to set touch keyboard to "never," but that's not a solution as I'll need it sometimes when using as a tablet.

    I avoid detaching the keyboard when not necessary, as I figure the connectors may wear out over time. This needs to be resolved.

    Was this answer helpful?

    0 comments