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 did a reset and that did not help.

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.