Surface Pro 4 - Screen won't wake from sleep

Anyone notice 2 UEFI updates, first on the 21st and another today ??

Also no published information ... useful !

I am a long-standing, long-suffering member of this club.

I am fearful to report, but ... it seems as though my Surface Pro 4 (bought back in December) is waking from sleep. 

Things have been steadily improving, and the 20/6 firmware etc. updates have seemed to clinch it.  I have had 27 wakes from sleep on battery and 10 on charge, and no failures.  This has NEVER happened before.

I am also in the Insider fast ring, currently running build 14367, and it feels as if that is helping too.  Somewhere a 'Getting Ready' stage appeared at wake up, and that seems to be involved ...

It would be nice to have an explanation of what has been going on for the past seven months :-)

Now I have to keep my fingers crossed that things stay good!

I can also confirm that the 6/20 fix has NOT fixed the problem.

In fact, the very first wake attempt after the update and a reboot resulted in yet another hard wedge requiring a forced shutdown/reboot - for the THIRD time today.  (The customers, clients, and vendor partners that aren't outright pissed off by the repeated reboots just shake their heads and laugh, wondering why I put up with this piece of dung...)   Sleepstudy for last ten days (powercfg /sleepstudy /duration 10) is below - note that at this scale, some of the wedges can't be clearly seen.  I avoid even trying to use the SP4 unplugged, given its staggering likelihood to crash:


It's time to issue a recall.  It's been nearly a year since the intro of the SP4 and SB, and power management and wake issues have actually gotten worse despite a slow and endless series of updates that we've been led to believe should "fix" the problems.  As often as not, the fixes really do make the problems worse.

I'm incredibly disappointed, and it's time for Microsoft and Intel to come clean and do something to make this right for the customers who have waited far too long through official silence and unofficial false hopes. 

The opposite of love isn't hate, it's indifference and disregard.  Microsoft clearly has no love or respect for its customers.

I'll say it again: The SP4 is without question the worst, most poorly performing, most unreliable, and most completely unacceptable and unusable technology product I've ever encountered (even counting sleazy Chinese **** from eBay), and Microsoft's refusal to even admit to the problems after many failed attempts to patch around the fundamental brokenness of these systems is even more galling.   This is in spite of the fact that if it just worked, it would be my ideal computer.

Clearly, the SP4/SB simply cannot be made to work as designed and advertised.  It's time to recall and replace them all, but with what, when nothing else works?

With all due respect for both Barb and Greg I have unmarked this as an answer.  Let's let this update "bake" for a few days and really make sure it's a fix, shall we?

There are a LOT of very very patient people in this thread and Microsoft can be just a teensy bit more patient before marking this as answered.

Thank you Susan. Sorry if I got upset, I was just shocked at the issue being marked "answered". 

It sounds like the 6/20 update just further demonstrates that this is a hardware issue. I was pretty nervous letting my SP4 update. After the 2/17 update actually made matters worse for many people I didn't want to ruin my so far perfect new SP4. After an hour with the update my SP4 still works fine, hopefully it won't go bad. 

Pretty clearly, the only solution is a new SP4 and hope you get a good one.