Surface Pro 4 - Screen won't wake from sleep

I am always interested in the continuing debate (well it's not a debate as Microsoft are not participating) and applaud all the strenuous efforts by all to try and fix a Microsoft problem. I don't have the skills to follow much of what is being suggested and don't want to try in case I make bad worse. I have to wait until Microsoft fix it, no doubt plagiarising some of the suggestions put forward in this forum. I don't care why things have gone wrong and what part of the kit (or parts) are responsible, I just want it fixed. Microsoft it's your name on the product so fix please.

Feel better now I've had a moan.

FINALLY

Through trial and error I finally managed to get a clean SFC / SCANNOW 

and I have not had the sleep issue since doing this and getting a clean system.

Knock on wood.

Here is the summary of what I did, leaving out the parts where I banged my head against a wall.

I started with my Surface Pro4 fully updated.  The build number was 10.0.10586.0

I have never done a reset.  The Pro4 is pretty new, but I wanted to avoid a full reset.

My problem was I had no image to run the DISM command against because there wasn't one on my machine, and it wasn't able to use Windows Update to get the image.  DISM command would always report Error 0x800f081f - no matter what I tried.  It could not find the source for some reason.

So this is what I had to do to clean up my system:

Step 1:  Run CMD as Administrator.  Click Start, type CMD, right click Command Prompt, and run as Administrator.

Step 2:  I ran this command three times in a row as suggested on a technet article:  SFC /SCANNOW

This detected corrupted files, and a bunch of issues but it could not fix some of the issues.

Step 3:   Ran checks:

This command told me I had corruption:

DISM /Online /Cleanup-Image /ScanHealth

This command reported that the corruption could be repaired:

DISM /Online /Cleanup-Image /CheckHealth

Step 4: Found an image, finally!  

I had no image for the DISM command to use!  My C:$Windows_BT and C:$Windows_RT folders did not have the image anywhere within.

I tried creating an image with the online Microsoft ISO Tool but that didn't work with DISM.

It would not recognise the install.ESD as a source no matter what I tried.

So I downloaded a tech bench Windows 10 image from Microsoft from this URL:

https://www.microsoft.com/en-us/software-download/techbench

Step 5: Mount the image downloaded

I mounted the image that was downloaded, by right clicking the file, and selecting Mount.

This will assign a drive letter (say D:) to that mounted image, which is used in the command below.

Step 6:  This command finally repaired the damage:

DISM /Online /Cleanup-Image /RestoreHealth /Source:WIM:**D:**Sources\Install.WIM:1

This fixed my issue with the opencl.dll

        This also resulted in clean scans coming out of SFC /SCANNOW

So far I have allowed the Surface Pro 4 to sleep for various periods of 5 minutes, up to a half hour, and it has been waking up each time.   I haven't had to do a forced reboot (Hold power down 30 seconds, let go, and push power button to turn on) yet.

Thanks - Reliability History is new to me.  (Although it's true that reliability *IS* history with a Surface Pro 4...)

The *really* sad thing is that they made sure Candy Crush Soda Saga (which I never even want to see an ad for again, much less have on my machine) was correctly updated even before they got around to making sure I had working Bluetooth drivers, current security signatures, the Flash security update, or the big Windows update.  [shakes head, in sad disbelief...]

Because "We're Microsoft, and the fact that you just paid us thousands of dollars for a machine that doesn't work isn't important.  What's important is that we get money to put that stupid game on your machine and in your face whether you want it or not!", right?

I was also surprised to see that short list of updates appear after a restore from a recovery image that was issued before the April updates.  I have discovered that the new drivers are in fact installed by Windows after the reset.  They don't show up under the list of installed updates, but they are visible in the reliability history:


The drivers started installing silently soon after the reset completed.  This morning I ran Update and saw the same patches as on your list get installed.