Surface Pro 4 - Screen won't wake from sleep

Thanks, MikeKirnak.  You are right.  I did not see your June 8 reply.  From your latest information, I agree that you have convincing evidence that there is a hardware difference among some Surfaces.  True, it is anecdotal because it applies to only two platforms.  But still, that's two out of two that are different from the working machine.  I would really like Microsoft to respond to that.  Surely, Microsoft has done similar testing.

Hi Dub.  I sympathize.  The 6/20/16 updates did not solve the problem.  And I agree that nothing in this long thread of anecdotes convinces me that the problem is in the hardware or that swapping machines will solve it.  The fact that no one has demonstrated that the same system image behaves differently on different Surfaces (something that would take only a few hours to confirm) should cast doubt on all these anecdotes.  

I'm sure Microsoft must be trying to solve this problem.  I can only hope it's a priority.  It's certainly a priority for me.

And for reasons that go beyond just waking up from sleep.  While the failure to wake is an apt caption for this problem, the problem involves more severe consequences for me.   When sleep doesn't work properly, it means you cannot count on having battery power when you need it.  It's inconvenient to spend a minute or two doing a hard reset and reloading programs then correcting any file corruption.  But It's utterly hopeless to not have any battery power when there's no auxiliary power and you need your Surface to work.   If sleep doesn't work, there's no guarantee you'll have any battery power remaining when you try to wake the Surface.

Jay, your assertion that no one has tried the same image on different machines is not true. You asked about that earlier this month and I replied that I had done just that. I  replied in detail about the process. On June 8th you posted that the hole in my assertion was that I may have used a different downloaded image. I replied on June 8th that I used the same thumb drive with the same image, no new download, on all three machines.

The two older machines failed miserably within the first day on that image. The new lot 1613 machine has performed flawlessly, for over a month now, with that same image. I have no idea if any changes were made in production, or if I finally got lucky with a good machine. Looking at this thread, you see a lot fewer people complaining about machines that are lot 1612 or later. That, of course, is anecdotal and not conclusive. It does bear consideration though. What I am convinced of, 100%, is that my first three machines had some type of hardware flaw. My current machine seems to be free of that flaw. Hopefully, the flaw will not manifest in the future.

Thanks Dyndragon.  I disagree that a problem that persists after a fresh factory reset would confirm that the problem is in the hardware.  Whether the problem is in the hardware or software, you would get the same result.  I believe the only way to demonstrate a hardware defect is to repeatedly load the identical system image on two different Surfaces and get different results.  This would take at least a few hours.  But given all the interest in this subject, it might be worth someone's time.  Someone else's time, that is.

The fact that no one has demonstrated that the same system image behaves differently on different Surfaces (something that would take only a few hours to confirm) should cast doubt on all these anecdotes.  

I have tried this in one of my last replies, and the same system image that was on a lot 15xx unit that had major wake up issues also had identical wake issues on my new lot 1617 unit. So to me, this does say that part of the problem is having to do with USER software or configuration that is installed.

When I wiped and started fresh on my new lot 1617 unit, I had no issues, and still have had no issues whatsoever with my new 1617 unit.

What I was not able to try was a fresh reset of my old 15xx unit because of other issues.

I would strongly recommend that someone with the patience to try it, is try a fresh factory reset of their tablet from Microsoft (i.e. DON'T use the built in reset and recovery tools--those might be corrupted for some reason too), and update all the way to the latest 6/20 updates, and see if the problems still persist even after factory reset. That would lock it in as a hardware issue to me, and rule out any of the different variations of the wake up problem.