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: Newest
  1. Anonymous
    2016-05-11T21:06:42+00:00

    How can you be sure that the new one is actually fixed though? It took 4 moths for the no wake issue to show up on my unit, who's to say that it won't just happen again on the new units? Using the USB hub fix everything works the way it's supposed to on mine. It enters deep sleep and wakes every time, haven't had a problem with it. Also, this problem has manifested on many different Windows 8 and 10 machines, not just the Surface line. How then can it be fixed with a new lot number of the same device and who's to say MS didn't change something that does the same thing as the USB hub fix but it's not visible to the end user? I guess what I'm saying is there is too much uncertainty with exchanging as a fix and I don't have a single complaint with my SB after using the USB fix. 

    So far I agree with this observation in that there isn't any certainty that this wont just appear on new machines with higher lot numbers. I few users have already reported the problem existing on 17xx lot numbers. So far the USB workaround has been way more successful for my SP4 after the tease of the SFC and DISM worked for 36hrs and everything else utterly failed.

    I'm happy to live with this workaround especially since I'm not in the US and also cannot wait an entire month for the Germany based returns center to simply ship out a refurb like we know they do.

    Do what you must do. If you're having the issue, you have defective equipment. Believe what you want though.

    For what it's worth, I ALSO do not believe it is a matter of getting a specific lot number. I do however believe that regardless of which lot # you have, this sleep issue is a known hardware issue by microsoft and it seems to be random and in all lots. Microsoft did tell me it was a hardware issue, that it was a known issue, and without question they gave me a new device. I didn't say anything except, "im here because i have a sleep issue with this device, it will not resume from sleep, but keyboard lights up, system is up-to-date".

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2016-05-11T20:25:40+00:00

    How can you be sure that the new one is actually fixed though? It took 4 moths for the no wake issue to show up on my unit, who's to say that it won't just happen again on the new units? Using the USB hub fix everything works the way it's supposed to on mine. It enters deep sleep and wakes every time, haven't had a problem with it. Also, this problem has manifested on many different Windows 8 and 10 machines, not just the Surface line. How then can it be fixed with a new lot number of the same device and who's to say MS didn't change something that does the same thing as the USB hub fix but it's not visible to the end user? I guess what I'm saying is there is too much uncertainty with exchanging as a fix and I don't have a single complaint with my SB after using the USB fix. 

    So far I agree with this observation in that there isn't any certainty that this wont just appear on new machines with higher lot numbers. I few users have already reported the problem existing on 17xx lot numbers. So far the USB workaround has been way more successful for my SP4 after the tease of the SFC and DISM worked for 36hrs and everything else utterly failed.

    I'm happy to live with this workaround especially since I'm not in the US and also cannot wait an entire month for the Germany based returns center to simply ship out a refurb like we know they do.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2016-05-11T20:07:28+00:00

    MS told you it was faulty hardware? Did they say what exactly was causing the problem? There is a MS store near me, might be worth the trip to go have a chat with them. It would take them telling me directly that I need to exchange in order to get me to give up my SB, which by all appearances and functions is working normally with the USB fix. I've had two previous Windows 8 machines that had this same problem out of the box and both were fixed with patches and work correctly to this day.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2016-05-11T17:30:12+00:00

    Hibernate is one of the quick fix solutions going around, you're not experiencing it because you're not using the sleep mode the way it was intended. You're avoiding the issue by using hibernate. That's an option, many of us feel we should not have to do that which is why we've exchanged for newer devices.

    Was this answer helpful?

    0 comments No comments