Surface Pro 1 on Windows 8.1 reboots when Type Cover 2 is removed

Anonymous
2013-11-12T17:57:47+00:00

I just noticed this recently but sometimes I get a Random reboot not even doing anything particular. I also noticed twice that when I attached my Type Cover 2 it reboots.  Example I attached it and the SURFACE logo shows and it boots up.

Anyone else experiencing this.?

Surface | Surface Pro | USB-C

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

281 answers

Sort by: Most helpful
  1. Anonymous
    2014-08-14T13:24:33+00:00

    The same thing happen with Surface Pro 1 and Type cover 1 ... sometimes, I have the Surface on my lap and the cover twist a little bit and boom ... it restarts.  Sometimes the type cover just stop registering keys ... I plug and unplug it, sometimes it works again, sometimes it still doesn't response, sometimes, hard reboot.  It really look like a firmware problem.  It is clearly not related to Windows itself.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2014-08-14T03:29:14+00:00

    This issue is NOT Windows specific.  If I boot to the UEFI screen on my Surface Pro 2 and fold my Type Cover 2 a number of times back and forth, I still hit the spontaneous reboot.

    That points this towards firmware/hardware.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2014-08-05T04:53:10+00:00

    Hi, I would like to provide a possible solution. Clean the connector both on surface pro and type cover. It could reduces random reboot.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2014-07-08T01:04:17+00:00

    Replying just to subscribe to this thread.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2014-06-28T22:00:20+00:00

    THE SOLUTION HAS BEEN FOUND!

    I think all of us posters owe MS an apology.  We've questioned if anyone at MS was working on this issue which, in just this one posting, has 225 replies.  We should apologize to MS because they HAVE been working on this issue and they HAVE issued a solution!  They've been working diligently on the Surface 3 and now all we have to do is pay another 1+ grand to MS for the Surface 3 and the problem is solved!

    Such a simple solution!

    Was this answer helpful?

    0 comments No comments