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

2,411 additional answers

Sort by: Most helpful
  1. Anonymous
    2016-05-26T23:29:31+00:00

    Early report: Mixed results for me after this update - an improvement, for sure, but no where near what's required for a "fix".  I may have to look at swapping hardware, if that truly helps.  It's not *just* software/firmware, that's for sure (assuming all of that is "fixed", which I kind of doubt...)

    On the plus-side, my SP4 has not (yet?) wedged hard (requiring forced power-off/reboot) on waking after this latest update, and I've been using it as I wished I could (mixed PC/tablet use, so frequent sleeping and waking at irregular intervals.  It even seems to have  prayer of waking with the Type Cover connected.  Bloody amazing - it now wakes more often than it fails - we'll see how it holds up.  This is definitely better than it's been since before the 2/17 updates.  I've gone back to the default power policies and even turned Windows Hello back on.  A huge improvement, but not "fixed" yet.

    On the minus side, the upgrade left my SP4 unable to use its touchscreen and pen.  This seemed to clear itself after another extra reboot cycle, but it's still pretty discomforting that it seemed to both fail and start working again for no apparent reason.  (All updates appear to have installed correctly the first time through.)

    It also seems to be (even more) easily confused about what orientation the screen should be in - it took a minute of two of futzing earlier today to convince it that it should be using landscape mode, even though the keyboard was attached and open (and not folded back, of course...)  This took plenty long enough to keep from "just opening and using it" as designed.

    Worse, the Hot Bag problem is back - I hadn't seen this in a long time (and I never suffered from it as badly as some), but I definitely put my SP4 to sleep (with the power button) after leaving a meeting this afternoon and after a 45-minute drive back, it was cooking itself in its sleeve.  It wasn't the hottest I've seen (I could still touch and hold it), but it was really, really warm.  The machine definitely appeared to be "asleep" while cooking itself (despite the sleepstudy below) - I plugged it into the dock, and had to press the power button to wake it up (shouldn't docking just wake automatically?)  Once awakened, it seemed to drop back into more normal power usage, with the fan quickly dropping off.

    In addition, battery life is putrid - I was on pace for only about 4 hours this morning (mostly browsing/reading over WiFi, with a little light OneNote and Sketchbook Pro).  I'm coming to think is as much as an SP4 is capable of.  (My SP3 was usually good for about 9 hours of real-world use.)

    So overall, I have to say that although this is the first set of updates I've seen that has made any substantial progress in a positive direction, it is very clearly NOT NEARLY enough to qualify as a fix (to deliver the functionality promised and advertised.)  Still, I welcome any forward progress, it just needs to continue and speed up. 

    I'm also quite concerned about the recurrence of the Hot Bag problem, which hadn't happened for me in a long time before today.  A machine that gets as hot as mine was a few months ago would be truly approaching fire hazard level - there had to be some kind of permanent damage (to battery lifespan, if nothing else).  I suppose I'll quit using the sleeve to give it at least some chance of cooling itself - it may prevent a fatally destructive meltdown, anyway.

    The image below shows the Hot Bag "failure to sleep" in sleepstudy, as well as two other wake wedgies in the last couple of days. Note that unlike the earlier failures, this last one was *after* the 5/24 updates and a few reboots. (I didn't work yesterday, as my Mom was having surgery, but it wedged when I tried to wake it up last evening.  I stayed plugged in almost all of the previous day (as usual for the world's thinnest desktop PC), except for an evening meeting where I took notes in OneNote and then suffered yet another wakefail.  The system *should* have been on (either awake or asleep) the entire time, so the white bands should not be there...)

    ![](http://fud.community.services.support.microsoft.com/Fud/FileDownloadHandler.ashx?fid=85e0fcbd-5f16-4723-97ff-ef8c122deac7)

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2016-05-26T22:47:31+00:00

    Well, I'd truly want to send the sp4 back and having it replaced.

    Problem is, and that may surprise you, I can't at the moment. I use it, daily, A LOT: losing days/weeks is not a possibility at the moment, with exams approaching.

    I'm not waiting for anything magical, I'm waiting the day I'll be able to send a replacement request: meanwhile though, I try to make it work, and I do hope it get somewhat mitigated (if not resolved).

    I'm glad you had the possibility to have it replaced, I do not: I do not want to mask anything, I have to.

    No need to lose your mind.

    The last crash happened in a truly average situation : edge playing youtube. Screen went off, Surface never woke up.

    Not many programs installed atm, drawboard, office, eclipse...Problem is present even with a clean install.

    They send you a replacement unit, and THEN you send the defective one back. You would never be without it. BUT, they do put a hold on your credit card until they get the defective unit back. They put a hold, not a charge.

    Was this answer helpful?

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

  4. Anonymous
    2016-05-26T22:22:01+00:00

    P.S. yes I think the time it has taken is excessive.  I also think the push to upgrade from 7/8 to 10 are excessive but as  you can see my opinion doesn't count for much.

    The only thing I will say  - not as an excuse mind you - is that I just feel it's good that Microsoft sees first hand that building solid equipment and getting to root causes isn't easy.  In their role as an OEM, I think they can do better.

    Was this answer helpful?

    0 comments No comments