Surface Detach Icon says Detached when it's not

This whole situation is beyond frustrating. Before the 2/17 update, I used hibernation exclusively, and my Surface book ran perfectly. After the update, I started having all the problems with Windows Hello and the detach button. I ran sfc /scannow and dism as documented previously in this thread, and I did find and repair the corruption. My SB ran fine for about a day, and then problems started again. If I have sleep enabled and it sleeps for a while (like overnight) it crashes when I wake it up. Sometimes it crashes when it goes to sleep. I can tell because all my running programs are gone and the event viewer shows critical errors about an unexpected shutdown. If I go back to hibernation, the crashes stop but when I wake from hibernation, the Windows Hello camera stops working, the software detach button stops working and the hardware detach button takes at least twice as long as normal. A reboot fixes these problems until the next time it hibernates, then they start again. I have fast startup turned off, and running sfc and dism shows no integrity violations.

At this point, I wonder if Microsoft even realizes that these problems are still occurring. It's been over a month, and I haven't seen anything official from them. I won't even bother calling tech support because I've never had a good experience with them. It's clear that they're just reading from a script with no understanding beyond what the script tells them, which invariably ends with a recommendation to do a reset.

I get Error code 87 and a notice that "Dism/online/cleanup-image/restorehealth" is unknown.

You omitted quite a lot of whitespace there. Insert a blank before each slash and you should be good to go.

Ok, I tried this, here's what I got:

PS C:\windows\system32> sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.

Verification 100% complete.

Windows Resource Protection found corrupt files but was unable to fix some

of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For

example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not

supported in offline servicing scenarios.

PS C:\windows\system32> dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool

Version: 10.0.10586.0

Image Version: 10.0.10586.0

[==========================100.0%==========================]

Error: 0x800f081f

The source files could not be found.

Use the "Source" option to specify the location of the files that are required to restore the feature. For more information

 on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077.

The DISM log file can be found at C:\windows\Logs\DISM\dism.log

PS C:\windows\system32> dism /online /cleanup-image /restorehealth /source:WIM:E:\sources\install.wim:1 /limitaccess

Deployment Image Servicing and Management tool

Version: 10.0.10586.0

Image Version: 10.0.10586.0

[==========================100.0%==========================]

The restore operation completed successfully.

The operation completed successfully.

PS C:\windows\system32> sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.

Verification 100% complete.

Windows Resource Protection found corrupt files and successfully repaired

them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For

example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not

supported in offline servicing scenarios.

PS C:\windows\system32>

Not sure what to make of this, dism repaired missing files successfully and right after sfc finds corrupted files yet again. It always boils down to opencl.dll,

2016-03-26 06:49:28, Info                  CSI    000060bc [SR] Repairing 1 components

2016-03-26 06:49:28, Info                  CSI    000060bd [SR] Beginning Verify and Repair transaction

2016-03-26 06:49:28, Info                  CSI    000060be Hashes for file member ??\C:\windows\SysWOW64\opencl.dll do not match actual file [l:10]"opencl.dll" :

  Found: {l:32 8qj6omMiXdZloIM27OmJd/IiV6A2rHZP9sBst8IgNZw=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}

2016-03-26 06:49:28, Info                  CSI    000060bf [SR] Repairing corrupted file [l:23 ml:24]"??\C:\windows\SysWOW64"[l:10]"opencl.dll" from store

2016-03-26 06:49:28, Info                  CSI    000060c0@2016/3/26:05:49:28.300 Primitive installers committed for repair

2016-03-26 06:49:28, Info                  CSI    000060c1 [SR] Repair complete

From a completely different post somewhere around these forums I gather that

"The missing DLL is typically associated with gaming drivers on AMD systems, but it seems that it fails to install properly on most Intel systems."

So does that mean it wasn't an issue to start with? Checking with sfc once again yields

PS C:\windows\system32> sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.

Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

PS C:\windows\system32>

Will try a reboot and see if it stays that way. See you on the other side.

EDIT: Another scan after reboot revealed no more inconsistencies. Fingers crossed.

Had the same problems as everyone else and, so far, for 2 days the "disabling fast startup" in the power options has also fixed my windows hello camera and detach notification glitch. 2000$ and nothing but problems

Rob

Hi Rob,

Perhaps you will want to try this WITH MS Surface Support on phone and with back door LOG ME IN RESCUE access you give them to run your Surface with you.  What has been uncovered is that there is a basic but important ERROR that is hidden in computers running the latest Windows 10 (version 1511) that was released last Fall.  I have had many returns/exchanges of Surface Book 17, 512 gb... because I found that even after every Firmware or Windows Cumulative Updates my SBs were still not working properly.  Read my post below and see if you wish to attempt with Surface Support assisting you.  As long as your SB has ALL of the latest updates successfully installed AND you run Windows Defender (Full Scan - to be sure there are NO viruses) this process may help you and MANY others.  My SBS run near flawlessly now!  (The only imperfections are two minor things MS is working on:  distortion that comes from the speakers when detaching or reattaching the clipboard AND that the Airplane Mode tab in the ACTION CENTER enables itself even when it is turned OFF in Settings)....

To the MS Community:

Today, March 2nd, Lee of MS Surface Support RECONFIRMED to me that MS top engineers say that this one error in Windows 10 (1511) - the one missing and corrupt files that is present with Error code:  0x800f081f -- IS ENOUGH OF AN ERROR TO CAUSE ALL OF OUR DEVICES NOT TO WORK PROPERLY.  A few on the Community have written that "there is 'only one' missing and corrupt file'  But as Lee reconfirmed that this is problem MS is working on for all computers running the latest Windows 10 (1511).. not just Surface devices.

If you find that your Surface Book is STILL running poorly EVEN after the 03/01/2016 UPDATES, check to see if you have ERRORS / missing and corrupt files.  If you do, here is how to repair them (with or without MS Surface Tech Support on phone).

Run the COMMAND PROMPT (ADMIN) and enter this code where the cursor is flashing:  sfc /scannow

If the report comes back detailing errors/missing/corrupt files then run the more advanced command in the same window, right below the error report you just received.

Enter this code after windows32 where the cursor is flashing:  Dism /online /cleanup-image /restorehealth

If the report comes back with Error code:  0x800f081f    then your SB has missing and corrupt files having to do with Windows Updates.  And as my case proved to MS Surface and Windows 10 Support, and contrary to some here on the Community who have insisted these files make no difference to the smooth operation of the SB, THEY DO MAKE A HUGE DIFFERENCE if files are missing and corrupted for Windows Update Error Code:  0x800f081f

If you need Support help, call them.  Ask them to go through the back door of your SB and conduct a LOG ME IN / RESCUE session to control your SB with you and execute this process below EXACTLY as written by LEE of MS Surface.   GOOD LUCK!  It worked for me and my two SB 512s have been running flawlessly since we performed this repair process.  NOTE:  This repair process DOES NOT require you to wipe your SB to factory settings!  This process REPAIRS the corrupt files AND replaces the missing files....

Step 1: Download the Tech Bench Upgrade Program using this link: http://www.microsoft.com/en-us/software-download/techbench

Step 2: Delete any existing CBS Log file. The path is: "C:\Windows\Logs\CBS\CBS.log "

Step 3: Mount the downloaded techBench with file name: "Win10_1511_English_x64", make sure not to install the setup.exe.

Run the DISM command in Command Prompt (Admin): DISM /Online /Cleanup-Image /RestoreHealth /source:WIM:D:\Sources\Install.wim:1 /LimitAccess

* Note: Make sure that the source is correct, for example "/source:WIM:D:\Sources\Install.wim:1 /LimitAccess" in this case the source of the Mounted ISO is D:. If you will use a USB stick, most probably it will become E:, just check the file explorer after mounting the ISO.

Best Regards,

Lee (Mark Mazzetti's  Surface Support Tech)

Microsoft Surface | Device Specialist

Microsoft Toll Free #: 1-800-642-7676

Microsoft Surface Answer Desk: http://www.microsoft.com/surface/en-us/support/contact-us

Operating Hours: Weekdays: 8:00 am EST to 12:00 am EST; Weekend: 9:00 am EST to 6:00 pm EST

Thanks so much! These instructions are succinct and helpful. Did everything without a hitch and cleaned up everything. Will let everyone know how things go.

If the report comes back with Error code:  0x800f081f    then your SB has missing and corrupt files having to do with Windows Updates.  And as my case proved to MS Surface and Windows 10 Support, and contrary to some here on the Community who have insisted these files make no difference to the smooth operation of the SB, THEY DO MAKE A HUGE DIFFERENCE if files are missing and corrupted for Windows Update Error Code:  0x800f081f

I get Error code 87 and a notice that "Dism/online/cleanup-image/restorehealth" is unknown.