probably he is referring to this. I got the error too, but to do the image and fix may be too much work for me. Just dl the Tech Bench takes forever.
https://www.reddit.com/r/Surface/comments/49g46p/i_am_going_to_make_one_post_to_convey_a_fix_for/
Good info, I think.
I was able to fix my error when I run "sfc /scannow". No idea if it will fix any problems I am having. The only thing I have wrong is that after hours asleep, it does a full shutdown. Not a big issue, but I would like to have it fixed.
This is interesting as I have the exact opposite experience. I have specifically set everything to hibernate to avoid the windows 'Hello' issue and I never have it. I close the book then put on charge all the time - no problems with 'Hello'. However, after the recent firmware update, I did try going back to sleep. This is what causes my windows 'Hello' issues.
Interesting that we have opposite problems.
FYI...
my surface book has updated the 17/2 firmware but it never has hello problem. I never let it sleep. screen will never go off when the lid is open. screen will go off when the lid is closed. the system will never go off no matter the lid is open or closed. each time I open the lid the hello works fine. I don't care the battery drain. my surface book can last 10 hours for my normal daily usage. it is more than enough to me. I don't need to save the battery.This is interesting as I have the exact opposite experience. I have specifically set everything to hibernate to avoid the windows 'Hello' issue and I never have it. I close the book then put on charge all the time - no problems with 'Hello'. However, after the recent firmware update, I did try going back to sleep. This is what causes my windows 'Hello' issues.
Interesting that we have opposite problems.
FYI...
Per some of the other people on the boards, I have completely turned off sleep and changed all actions to hibernate. I never have a Hello problem. In truth, my behavior is always closing the lid (I never cause a hibernate from the GUI or the power button or a timeout)...
FYI