Surface Pro 11 Keyboard Not Responding when Turning off at Night and Turning on the Next Day

Anonymous
2024-07-22T16:37:34+00:00

I have a Surface Pro 11 where the keyboard will not respond when turning it off at night and turning it back on the next morning. The only way I have found to get it to respond is to unmount and mount keyboard. It will not occur when putting it in sleep mode overnight. It will not occur when turning the tablet off and back on when not sitting overnight. I have checked for updates. I have tried cleaning the contacts.

I have contacted support through the Surface app doing a chat session. I was transferred to 4 different departments. More time was spent transferring me then resolving the concern. Yes, the concern was never resolved. The last transfer was to the business department because although I purchased both the Surface Pro and keyboard online through retail channels support says the keyboard is a business keyboard. I haven't heard back from business support yet. I don't know if they will tell me that since the Surface Pro is retail so they will not be able to help me. Another remedy was to reinstall the recovery software but there would be no guarantee the problem would be resolved. I declined since I spent hours installing all my apps.

I also contacted CoPilot but it had the usual remedies. I do not want to mount and unmount the keyboard every day to use it. The Surface Pro and keyboard is still within the return period.

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

52 answers

Sort by: Most helpful
  1. Anonymous
    2025-01-14T14:38:55+00:00

    Just to reiterate: step 1 can also be Hibernate, but that is really not needed now on an ARM64 Pro because Sleep's battery usage is minimal.

    How are you hibernating your Surface Pro? As I mentioned earlier, I rarely do this. Incidentally, it appears that using the power button to turn on the computer before lowering the keyboard will make the keyboard responsive. This does not seem to depend on whether I delay folding the keyboard over the display or not during shut down. I checked this procedure over 10 times and the keyboard was always responsive. As I mentioned before, I am uncertain about the consequences of hibernating.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2025-01-12T22:06:03+00:00

    Just so I understand: are you sure it didn't enter Sleep state (as opposed to Hibernate or Off) after these moves?

    I don't know if I fully understand your question but the SETTING for the lid opening and closing is SLEEP. Whether it actually goes to sleep or hibernate, I have to say I don't know. I rarely use either option or think I am not using it. I normally turn off the computer with Windows shut down and turn on with the power button. Whether the lid closing caused the system to sleep instead of honoring the first request of turning off, I don't know. Like I mentioned, this is no longer a concern for me anymore so I am not going to investigate the lid closing or opening settings.

    I know what it would take to avoid the keyboard issue. If I don't have the time to delay closing the lid, I have to remember to use the power button before lowering the lid. If I forget to do this, I have to be prepared to unmount the keyboard. Not really a big deal considering all the other concerns others are having with their Surface Pro. Yes, it shouldn't be like this but not worth obsessing over for me.

    What should be acknowledged from Microsoft is if they are aware of this and if they are considering fixing this. If they say they aren't going to fix it, then at least people considering purchasing this Surface Pro can make an informed decision of whether they can tolerate this or not. If they can't, buy something else or wait and see if Surface Pro 12 has the same issue. Or, instead of wondering, move on and just don't purchase it. For those who did purchase it that are still within the 60 day return period, just return it. For others, go through the process of getting it repaired and maybe they could get a refund if it can't be fixed. If there are others who don't want to get stressed with it, adapt?

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2025-01-12T21:28:48+00:00

    Just to reiterate: step 1 can also be Hibernate, but that is really not needed now on an ARM64 Pro because Sleep's battery usage is minimal.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2025-01-12T21:26:49+00:00

    Just so I understand: are you sure it didn't enter Sleep state (as opposed to Hibernate or Off) after these moves?

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2025-01-12T16:50:28+00:00

    The problem only happens intermittently with my Surface Pro 11 - so it may take me a bit to figure out whether this work around has solved my problem. However, as soon as I can confirm, I will reply back to let you (and everyone else) know. Thanks for the tip!

    If you read this COMPLETE thread I mention how I was able to duplicate the concern every time. To summarize: 1. Turn off computer. 2. Fold keyboard/cover over display/screen IMMEDIATELY. 3. To be sure, wait overnight or maybe at least 6 hours? 4. Lower cover/keyboard and turn computer on. I believe this is the normal process for most who use their Surface Pro mobile. To avoid the keyboard concern (unresponsive), delay folding cover/keyboard over for a few minutes. Yes, others may hibernate instead of turning off which I may not be familiar with but there is one user here that does this and he has similar keyboard concerns and very versed on how to duplicate his concern.

    Personally, I have given up on this being fixed so it is no longer a concern for me anymore. I do stop by once in a while to see if there has been any progress. I have just learned to live with it and adapt.

    Was this answer helpful?

    0 comments No comments