Surface Pro 4 - Screen won't wake from sleep

So I have checked this and all of my updates have successfully installed. But still having the issue. I also have experienced finding my SP4 very hot in my bag after falling asleep for an extended period. Hibernate seems to be better. I have also found that when it goes into hibernate I have to wait a while or press the power button 2-3 times for it to wake up

Same with me on the heat issues.  Fan runs much more after the updates.  The device is much hotter now.

Hi All,

We released an update on 2/17/2016 that addresses this issue.

We recommend that you install this update to keep your Surface performing its best. You can get updates now by checking Settings> Update & security> Windows Update.

To confirm the updates are installed, check Settings> Update & security> Windows Update> Advanced options> View your update history.

Thanks,

Josh

I installed all the 2/17 updates and now its worse - much worse.  Before the updates it would fail to wake up maybe 1 out of 10 times, which was annoying.  Now its EVERY time.  Agh!  Now it's almost unusable. 

Batter still drains during sleep.  Put it to sleep at 8 am.  Woke it at noon - had to do a 2 button reset - 1/3 was drained  By 5, another 2 button reset necessary to wake it, 2/3 drained, all with no usage whatsoever throughout the day. 

Since new battery use has been maybe 3 to 4 hours.  Haven't tested since the 2/17 updates - I'm not sure I can since every time if goes to sleep I have to do a 2 button reset. 

I want to through this thing out the window ...

Hi All,

We released an update on 2/17/2016 that addresses this issue.

We recommend that you install this update to keep your Surface performing its best. You can get updates now by checking Settings> Update & security> Windows Update.

To confirm the updates are installed, check Settings> Update & security> Windows Update> Advanced options> View your update history.

Thanks,

Josh

No, you did not.

To be honest, this is even worse than if nothing was done at all. Clearly "Josh" simply didn't read our concerns, as he's talking about the heating up while sleeping issue.

Why is MSFT not listening? What's the point of a computer that needs a hard reset all the time? Don't they realize that we're trying to use this system for WORK???

Experiencing the same and I’m also exacerbated from these updates. After a snafu with the SP2 update that caused similar problems, I had hoped to avoid updates for good. I made good with that promise with the SP3. But with SP4 and Windows 10, avoiding updates is very difficult. But because I have the phantom touch problem, I’m in need of a proper update to fix it.

Fortunately pre 2/17/2016 update, I had no issues with sleep and only occasional issues with heat (always found a culprit and found rebooting fixed it). Immediately after the update my SP4 changed.  At first I thought it was a one off crash when the power button was unresponsive to wake. Then I thought it was related to my keyboard cover.  Pre update I may have had 1 or 2 nonwake experiences ever. Now it happens 5 times a day.

One observation is that under the new update, “sleepstudy” showed that my system is, for the first time, running in a low power state while asleep. I’ve never seen that before. I wonder though, if the new low power state is causing the difficulty in waking. 

Fed up with another hard reboot because of the non-responsive wake, I attempted a restore. Note, given my aforementioned desire to avoid certain updates, I’ve invested in understanding the use of ‘wushowhide’ where I can hide unwanted updates.

I checked the drivers and noted their January dates. Then performed a system restore. Dates rolled back to November.  Great!  Feels like the computer I had before the update.  I hide all the firmware updates – but apparently I couldn’t hide the one referred to as ”system hardware update 2/17/2016”. Before I knew it started to install.  My display adapter date changed to January. 

I don’t know if I will experience continuous wake issues but after several short tests and a 30 minute test, I hadn’t experienced it yet.  Now what has me curious is if the new wake issue is related to the new low power state – which I believe I was able to roll back as evidenced in the sleepstudy.  Note the update caused the green low power state and at a Power rate of 38 mW which experienced a wake crash.  Now, I’m back to the numbers I have come to expect with the 350 mW rate and no crash.

I wonder if anyone here might have thoughts on this theory. Of course, I still may experience wake issues after posting this. So this is just a preliminary theory.

I would not recommend to anyone to system restore as I do expect some fix eventually.