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 No comments

126 answers

Sort by: Newest
  1. Anonymous
    2025-01-31T14:39:28+00:00

    It is interesting that a new computer fixed the keyboard concern but I think we need to identify how to duplicate the concern. This is with my Surface Pro 11 where I can duplicate the keyboard concern 100 percent of the time. 1: Shutdown using Windows "Shut down". 2: Fold keyboard/cover over display/screen immediately. 3: Wait overnight before using computer. 4; Lower keyboard/cover and turn on computer with the power button. When the computer boots, the keyboard should be unresponsive. You don't even have to try the keyboard. You could tell by the size of the icons in the task bar, they are larger.

    To avoid this from happening. 1: Shutdown using Windows "Shut down". 2: Delay folding keyboard/cover over display/screen by a few minutes. It should start up with the keyboard responsive.

    Or, sometimes I don't have the time to wait to do the above. This is the procedure when starting the computer up the next day. 1: Press power button BEFORE lowering keyboard/cover. The keyboard should be responsive.

    If a new computer did actually fix this keyboard concern, Microsoft will have a lot of computers being returned since all of the computers are still under warranty. I won't be returning my computer even if a new one does fix it for this keyboard concern being I can adapt to the above and I don't want to get a computer back with a different concern.

    Was this answer helpful?

    6 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2025-01-31T08:41:45+00:00

    Be wary that this issue might crop up later on down the line as the staff here have had their surface pro 7's for about 3 years now and the issue has only started appearing which makes me think it's an firmware update that caused this issue.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2025-01-31T05:20:53+00:00

    Thank you so much for this! I have only 5 days left on my warranty, so this was very timely.

    I called tonight, and the support agent told me she doesn't have any record of this being a known problem. (Interesting....As someone else suggested here, it would be nice to have a case number to tell them to look at.) Of course, she wants to walk me through various troubleshooting steps. She connected to my computer, checked to make sure Defender was up to date and all my updates were current. I hadn't had it on for a while, so we needed to run some updates. She also installed any new drivers and firmware updates, then uninstalled and reinstalled the keyboard drivers.

    At that point, of course the keyboard worked on a boot up, so she's supposed to call me back tomorrow. In the meantime, I will try turning it on and off several times to see what happens. I'm hopeful that either she has managed to fix it or they will give me a replacement. She sounded somewhat encouraging about that possibility, which leads me to think maybe if it's not listed as a known problem, at least they're aware that they're not supposed to fight requests for replacement. Time will tell, and I'll try to update this.

    Was this answer helpful?

    0 comments No comments
  4. 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

  5. Anonymous
    2025-01-30T23:09:30+00:00

    Personally, I'd still like some info on what the actual problem is. What component, driver, assembly, etc.
    And any acknowledgement that there is a problem should be accompanied by a link or reference to a problem ticket tracking the issue.

    Without documentation, comments even from MS staff are just heresay.

    As much as I find the issue annoying, I do really like the device.

    So I'll keep mine and continue hoping that they push a patch some day.

    Was this answer helpful?

    0 comments No comments