Face-recognition not working after Windows 10 update 1709

Anonymous
2017-10-28T12:58:02+00:00

After receiving the Windows upate 1709 (KB4041994) the Face Recognition doesn't allow my Surface Pro 4 to get into Windows. It recognizes me but stays on the login spash screen. I have to switch to a different login option to actually get into Windows.

Moved from: Surface / Surface Pro 4 / Sound and camera

Windows for home | Windows 10 | Windows Hello, lock screen and sign-in

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2017-12-27T22:31:26+00:00

I have the same problem as many of you.  I had to use my PIN number during initially logon because Face-recognition (hello) wasn't working.  Face-recognition would worked when my computer would go to sleep/hibernate but not if I shut down and re-boot.  I spent the better part of a day reloading drivers and trying all kinds of other things people were suggestion online.  Today I checked out another thread of questioning on this website titled "Windows 10 Creator Update must login twice" not thinking that was my problem at all but read the thread anyway.  The Microsoft rep replied to the login twice question with a suggestion and OMG when I tried it fixed my problem.  Since it sounds like a number of you might have the same problem as I was experiencing I thought I would pass this tip on... maybe it will fix your problem too.

Adrienne

Below is the tip from the Microsoft Rep.

****************************************************************************

Anne Ros replied on

Microsoft

Hi,

If you're having trouble with logging in on your PC twice, then you can try the following steps to remove double login:

  1. Go to Settings, then select Account.
  2. On the left panel, select Sign-in options.
  3. Under Privacy or Confidentiality section, turn off Use my sign in info to automatically finish setting up my device after an update or restart.

After doing so, reboot your PC and see if the same issue will occur.

Get back to us with the outcome so we can provide further assistance

*******************************************************************************

Was this answer helpful?

30+ people found this answer helpful.
0 comments No comments

74 additional answers

Sort by: Most helpful
  1. Anonymous
    2017-12-28T22:04:13+00:00

    Sadly this did NOT fix my issue.  I can turn on the camera myself from the app (program, software, whatever it's called these days).  And it DOES WORK fine.  Although I CANNOT sign-in with facial recognition.  The error message I get is that, Windows is having trouble turning on the camera.  Sign-in using an alternate method.  Is the long and short of it, not verbatim.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2017-12-28T18:28:12+00:00

    I'm still waiting for Microsoft to send out the appropriate drivers for Win 1709 on a Microsoft Surface Pro 4.  I've updated everything both through Windows Update and looking for new drivers in Device Manager - I've got the latest and face recognition does not work.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2017-12-28T16:00:59+00:00

    Shortly after experiencing this problem, I updated the camera driver and VIOLA!, the camera worked fine once again AND, even better and more responsive than before!

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2017-12-25T18:08:18+00:00

    I have been waiting for a Windows fix for this for weeks on my Dell. Roll Back Driver was unavailable for me and none of the Windows updates in the last month have helped, but I was able to right click on the webcam in Device Manager and selected Update Driver. I chose Browse my computer for drivers and pick form a list of drivers on my computer. Then I chose the one dated 9/30/16 and it fixed the problem. The other available driver was dated 12/15/16 for some reason and wasn't working.

    Hope this helps someone!

    Was this answer helpful?

    0 comments No comments