Surface Pro 4 - Screen won't wake from sleep

Anonymous
2015-10-27T05:32:42+00:00

I received my Surface Pro 4 today and it worked fine. I put it on "sleep" for awhile, came back and turned it on. Once again it worked fine. I made an error and instead of putting it on "sleep" I  hit the power button to turn it off when I finished. Now it won't come on at all. The screen stays dark. If I push the power button I can see lights under the keyboard keys, then if I hit the power switch again they go off. But nothing happens to the screen no matter what I do. Has anyone else suffered from this?

Surface | Surface Pro | 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
Answer accepted by question author
Anonymous
2016-08-19T19:27:34+00:00

It works fine for me after the Anniversary Update to Windows 10 Pro (Version 1607). It no longer goes into a coma.

I just traveled all week. Put my Surface Pro 4 (SP4) to sleep 10 to 20 times each day, and currently my task manager shows the up time to be 7:21:35:21 - 7 days! It is actually working the way I expected it to when I bought it!

It was such a relief to not be scared to put it to sleep during meeting breaks to save battery when working with my Pen and OneNote. For the past 7 months I've had to have it on power when in meetings so that it wouldn't go into a coma. That was always so embarrassing.

You can update to the latest version of Windows 10 by opening Settings > Update & security > Windows Update, and selecting Check for updates.

Was this answer helpful?

10 people found this answer helpful.
0 comments

2,411 additional answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2016-04-26T22:44:06+00:00

    Thanks Susan, it is about time someone removed the 'answered' tag on this thread!  I doubt that Microsoft cares as they don't seem to want to acknowledge this problem and the fact it is a continued problem for all of us.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2016-04-26T22:51:35+00:00

    Thanks Susan, it is about time someone removed the 'answered' tag on this thread!  I doubt that Microsoft cares - they don't seem to want to acknowledge this major continued problem and I wish they would at least have someone explain why the surface engineers cannot come up with a solution.

    Is it because the surface engineers cannot reproduce the problem?  Is it because they have no idea what component is causing the issue?  Is it because no one is working on the issue?  If you know anyone on the surface team maybe you can nudge or poke them?  Thank you for your volunteer efforts and time by the way and I do realize your influence is limited but do you know if anyone on the surface team monitors or follows the community forum for the Surface Pro 4?  Any insight would be great.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2016-04-26T23:42:30+00:00

    Are you using Chrome to browse?  I have noticed that Chrome tends to introduce little freezes to the system, including the start button, taskbar ect.  In fact sometimes I have to exit chrome to get the system moving again.  I've found notifications not popping up as well.  I only just installed chrome to try out the new .50 version and immediately noticed all the unresponsive behavior.  

    I don't get these problems with firefox.

    I use Chrome occasionally, but Firefox is my primary browser as well - and it will be until I find something that's at least as good as Firefox and TabMix Plus at flawlessly handling 100-200 tabs. (Don't even try to tell me I shouldn't have that many tabs...)

    BTW, the whole system doesn't freeze, just some part that's needed to run "Modern/UWA/UWP" apps.  Apparently, parts of the OS are now Modern apps: the Start menu, Cortana, and Activity Center, at least...

    Was this answer helpful?

    0 comments
  4. Anonymous
    2016-04-26T23:44:43+00:00

    I am going to unmark the proposed answer as not being an answer as I'm still seeing pain here in this thread and I don't think the issue has been solved.  My apologies to Josh_F but I'd rather be honest here.

    Thank You, Thank You, Thank You!!  I just wish someone at Microsoft had been this honest months ago...

    Was this answer helpful?

    0 comments