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-04-20T16:59:53+00:00

    I too am still having the "No Wake" issue after the 4/19/16 update*. While my system was not "fine" pre 2/17/16 update, it was much better and would only fail to wake a couple times a week. Post 2/17/16 update (and 4/19/16 update) it fails to wake more often than not. Thus I am back to using hibernation.

    I love the idea of the Surface Pro, I had the original (version 1) and was excited to get version 4 on launch day. It should be the best computer I have ever had, but nearly 6 months after launch and I have a machine that cannot reliably perform the most basic of functions. And Microsofts refusal to even acknowledge this issue makes it all the more infuriating.

    * Yes, I have verified that the updated installed and that there are no errors under the device manager (and the release dates of the drivers were changed by the update). I even uninstalled the drivers and installed them again.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2016-04-20T16:57:50+00:00

    Got all the latest updates no joy but whats odd is it appears to wake from sleep but none of the previous programs are running.

    It looks like its done a reboot whilst sleeping - this occurs on mains, attached to an external monitor after 30 minutes being left.

    Not sure how but the power settings had gone back to sleep after 10 minutes.

    I will try some tests on battery with the keyboard attached but I am not hopeful.

    The latest updates (19/4) went in fine.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2016-04-20T16:46:00+00:00

    I just installed the update...

    On first boot Hello! also did not recognise me and froze for a while.

    Had to key in login password to enter my account too.

    Rebooted and the restarted.

    I closed the keyboard cover and left it for 2 hours before returning to the SP4.

    SP4 machine felt warm and no wake again... keyboard lights up but screen stay black.

    Was hopeful that it would work but it didn't seem to work for me.

    Pretty disappointing.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2016-04-20T15:39:11+00:00

    After finally succeeding to install the 4/19/2016 update, I can say I still have a sleep/wake issue.  It was looking good yesterday but this morning 2 non-wakes.  Several times I have added to this forum but for review:

    • Pre 2/17/2016 No sleep/wake issue
    • After 2/17/2016, around 60% of the time NoWake
    • Rolled back drivers (notably the graphics driver)
    • Occasional NoWake
    • Problem seemed related to batter drain while in sleep. 
      • Pre 2/17/2016 used 400mW per hour in sleep
      • After 2/17/2016 uses <200mW per hour in sleep
    • Wake always works while plugged into power but consistently has problem after fully charging then going to battery.  However, after being on battery for some time, Wake works fine.
    • Testing the consistency of this pattern, I used hibernate (instead of sleep) after fully charging while using battery power.  If I keep to this practice, I can go weeks without a sleep/wake issue.
    • Last night Windows 10 forces the 4/19/2016 update.  In panic, quickly went to this blog to see how other have dealt with it before it finished.
    • dkb1898 comments helped prepare me for a lengthy install. Which I did experience. 
      • Had "!" on some firmware drivers
      • Rebooted.  Took some time but completed.
      • On first signon lost touch capability.  Had to use keyboard.
      • Rebooted and everything worked and no longer had “!” under Devices Manager.
    • Sleep/wake worked perfectly.  But hadn’t gone through a full-charge to battery transition yet.
    • After a full charge, tested sleep/wake and it worked well.  Tested several more time while still on same battery charge and all successes.
    • Fully charged overnight, then transitioned to battery and wake/sleep works as long as the sleep time under a minute or so.  After a 5 minute sleep, NoWake.  Hard restart and sleep/wake works in short intervals.  Did a longer test and NoWake.  These are my 2 NoWakes.

    I seem to be in the same place after my driver rollback fix.  My power usage while asleep is still <200mW per hour and I suspect my issue continues to involve the transition between power and battery use and the fact that my battery usage is <200mW.

    I hope someone from MSFT studies this particular issue and finds a fix.  After all, pre 2/17/2016 update, my system worked fine.

    Was this answer helpful?

    0 comments No comments