Surface Pro 4 - Screen won't wake from sleep

I've had my until since day 1 when it came out, got it at Best Buy. So I have very early hardware, Lot# 1541. My SP4 came out of sleep 95% of the time if not higher until the 2/17 update when it didn't come out of sleep 95% of the time if not higher. Completely useless to rely on sleep after that, so everything was changed to hibernate. Every time there is an idea, a driver update, a windows update, etc... I try it again. Every time I'm disappointed.

I did wipe out the drivers about a month ago, even through they installed correctly when the 2/17 update came down through Windows update and it made zero difference. I suppose I could do the same thing again now since other drivers have changed as had the Windows Production Builds. It will likely be just another disappointment in a line of them so far after 2/17

Would you believe it - yet another update in just a day:

Frustrated as I was, went back to store on Friday evening.  Explained previous day's "repairs" were of no consequence.  Had not installed Preview or anything beyond Office and logging in with Microsoft account.  Left Surface in black screen state, clearly showing device is on and keyboard lit.

After a mere 45 minutes or so, walked out with a brand new Surface Pro 4.  Super-helpful store clerk assured me device is from very recent batch - from this year. 

It's Saturday afternoon now and it's as if all of it was a bad dream: not a single problem, flawless waking from sleep, no hibernate settings anywhere.

But, battery life still stinks. 

I will now install all current Preview updates and see what happens.  It seems that the early batch hardware reason may well be an accurate diagnosis. 

We shall see.

Aaaand back already from store - got notification much earlier than expected.  Thought it was too soon to be of any use.

Aaaand I was right.

All they did was remove Preview, revert everything to regular Windows 10 that's publicly available, "run hardware diagnostics" which apparently confirmed this isn't a faulty unit, and then tested Sleep a few times. 

I was exasperated with the conversation with the person who returned it to me - essentially he said they are aware of the problem, it is less, it "happens sometimes", and there is no known permanent solution ("what do you want me to tell you - they haven't told us anything else").

So, a load of nothing. 

Anyway, for now at least Sleep is working.  I guess I will have to assume that the Preview builds were at fault - for my instance at least.  And let's try this for a few days and see how many times it happens again.

Sigh.  Sorry all - no good news to report.

Curious.

In my case, the sleep performance definitely degraded after I bought it.  I only started noticing the problems over the last few months -- quite possibly right after the 2/17 update.

Did the unit you tried immediately work better, and then return to the former sleep performance?  If that's the case, I guess I'll need to monitor closely for changes.

On the other hand, if the install of the MSI made no difference, that's definitely something different than I'm seeing.

Then again, there are a lot of complexities to any system like this, so it could certainly be that the procedure I tried doesn't work all the time.  Many settings and options can probably interfere with how things work on a unit like this.

At this point, it is working for me.   I just hope some later update doesn't return mine to narcolepsy-mode.

I still recommend wiping out the drivers are trying that.  It is just good to clean up things fully that way.

I did the same a month ago and it didn't work, so don't hold your breath. And I also checked "Delete the driver software for this device", which Josh F also fails to mention (which I find lackluster and partially incompetent)!

Also I don't know what this is, nor did I have it come up...the BIOS never got booted into

"

• After solution 4, the unit boots into the BIOS, so I exited the BIOS and that presented me with a "Restart" button.
• Pressed the restart button in the BIOS, and the unit restarted

"