Surface Detach Icon says Detached when it's not

Anonymous
2016-02-24T05:02:59+00:00

After installing system updates on 02/17/16 for Windows 10, the Surface Detach icon in the taskbar is grayed out and when I mouse over it, it says "Surface Detach: Detached" when it's actually attached and connected to the keyboard. Keyboard works fine but when I try to detach, I have to hold the keyboard detach button for over 10 seconds before the light turns green and I hear the detach sound. 

Also, since this started happening, after detaching, the screen no longer rotates in Tablet Mode. Tried locking and unlocking Autorotation and nothing will rotate the screen anymore.

Not sure if these two problems are related.

Surface | Surface Book | Display and screen

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

73 additional answers

Sort by: Newest
  1. Anonymous
    2016-03-03T00:46:57+00:00

    I'm glad shutting off fast startup has helped, but it is disappointing that we, the end users, are having to do the testing for MS on both their hardware and software. At least when you test for some companies they give you discounted or free hardware and you know you are testing. Running my business on an alpha grade product just isn't acceptable.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2016-03-03T00:34:53+00:00

    Had the same problems as everyone else and, so far, for 2 days the "disabling fast startup" in the power options has also fixed my windows hello camera and detach notification glitch. 2000$ and nothing but problems

    Rob

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2016-02-29T02:07:51+00:00

    I also find that disabling Fast Startup allows the computer to realize that the clipboard is really not detached when it says it is.

    It just seems unfortunate and, theoretically unnecessary, that it should be necessary to disable a "recommended" function in order to somehow kludge a solution to something that shouldn't be happening in the first place.

    Just another example of how the 2/17 updates have been a step backward in many ways.

    John

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2016-02-29T01:15:35+00:00

    This has seemed to fix it for me as well -- finally a workaround that actually works!

    Was this answer helpful?

    0 comments No comments