Surface Pro 4 - Screen won't wake from sleep

I've read a large fraction, maybe most, of the postings here.  It does not seem probable to me that this is entirely a hardware problem on specific machines.  

Certainly, that could be a factor.  But Windows inappropriately handling something that a sizable minority of SP users do better explains why the problem recurs with certain users through many different replacement machines.  That also better explains why it is hard for Microsoft to fix the problem.  

I don't claim to be an expert.  But it seems to me that Microsoft failure is more related to inadequate diagnostic software than to using cheap hardware components.  I too suffer from this wake-up problem but only about five to 10 percent of the time.  

So I have mixed feelings about the time it takes MIcrosoft to react to problems like this.  I want my SP4 to wake up EVERY time but have also suffered the mess created when inadequately tested fixes are hastily published.

Unfortunately, nearly all software publishers avoid disclosing to users when they are working on a problem and what they are doing.  I suspect they are reluctant to acknowledge the possibility of a problem they haven't precisely confirmed.  And once they have precisely confirmed it, the solution is so automatic there's no value in updating users.

I wish I still had my SP3 running Windows 8.1, great hw/sw combination. For me on SP4 system aggregator version is 103.1135.257.0 from March 2016.

If I were you, I'd return your device asap, or "downgrade" it to Windows 8.1, which actually worked.

I've been using the USB hub fix for about a month now and haven't had a single failure to wake yet and I lose less than 1% of battery an hour when asleep. I've used the USB fix on another machine that had the same problem and it worked for years.

What is this usb hub fix? How i can do?

1) Right click on the start button and select device manager. 

2) Go to the bottom and expand "Universal Serial Bus controllers"

3. Right click on "USB Root Hub (xHCI)" and select properties.
4. Click the "Power Management" tab and uncheck the box for "Allow the computer to turn off this device to save power"
5. Click ok, and that should do it! It's been working great for me so far.

Followed this suggestion. Testing...

I'm still waiting to swap again - I've been through eight or nine SP3s/SP4s since January 2015, and have had to do restores and/or resets on most of those to satisfy Microsoft's pitiful efforts at support, so I really don't have much of an appetite for swapping out yet again unless I'm SURE it's going to actually going to make a difference.

So far, nothing ever has, and so far today Microsoft and Intel are 0 for 2 on wake attempts - both failures required hard poweroff and reboot, and the first one lost application data.  In the second failure, the machine had only been asleep (put to sleep via power button w/o keyboard attached) for about ten minutes.

Maybe there are *finally* SP4s being built with Intel parts that are not fatally flawed, but I really kind of doubt it - if that were the case, I think Microsoft would be crowing about it from the rooftops.  In any case, we DO NOT know how to distinguish an SP4/SB that may have a chance of working from another one that will likely fail.

(And keep in mind that one of the Techs at the Microsoft Store here in Austin said it's still a craps shoot and that there's no sure fix that they know of.)

I'd love to have a working SP4, but we've heard way too many reports (some by me) of "everything seems to be working now", only to find that wake failures reoccur within a short time, or after the next updates are pushed out.

I'm also convinced that Microsoft really doesn't even begin to have a handle on application compatibility in Win10 - among many other things they really don't understand about their own flagship software product.  I myself have anecdotal evidence that some *desktop* programs appear to work perfectly after installation, except that *Windows* corrupts itself after they are installed, refusing to allow some or all Win10 *apps* to run.  (This appears to be the cause of Win10's failure to run ANY Modern/UWA/UWP app, including the Start Menu and Activity Center - this most severe form of failure has bitten me twice, and a machine swap or a full OS Reset is the only way to fix it.  Microsoft's techs tried for 2 days to fix this before giving up and offering me my latest swap.)  Oddly, some portions (even all or most) of the Win10 system will work correctly after installation of these programs, but the problem will eventually affect more or even all Modern apps at some indeterminate time in the future when a forced poweroff/reboot cycle triggers some kind of fatal self-corruption.

This is just one more instance of the hideous Frankenstein-like seams that show where the "Modern" Win8/8.1/10 OS has been clumsily stitched, stapled, lashed, and taped onto the old "desktop" Win 7 OS. 

Since it now looks like we're stuck with non-functional PCs until the release of the "Redstone" or "Anniversary Update" indefinitely scheduled for "later this summer", we can only hope they finally get some of this insane brokenness fixed, and may finally come clean about swapping hardware when there really is an effective and reliable SP4/SB hardware available.  (It looks like Intel is abandoning Skylake as unfixable and pinning their hopes on the upcoming Kaby Lake, so we're all probably screwed, though.  This may be as good as the SP4/SB hardware gets.)

The Microsoft and Apple dinosaurs may rule the current Jurassic computer world now (and believe me, I'm a fan of real OSes), but they had better watch it - those scrappy little Chrome/Android mammals are eating their eggs.  Especially after my experiences of the last year and a half with machines that aren't usable and don't deliver what they promise, I'm ready go for a Chromebook just to get something that I can turn on.  Give me one with a good pen and I'm outta here...