Windows 20H2 update seems to have broken Windows Hello Face Recognition

Anonymous
2020-10-27T22:00:14+00:00

With the recent update to Windows 20H2 (version 19042.572), the Windows Hello no longer works with the Logitech BRIO 4K camera. I have uninstalled and reinstalled the drivers, disabled and re-enabled Windows Hello. The BRIO works fine with Teams, Skype, Windows Camera, Logitech Capture, and Logitech Camera Settings. The problem ONLY occurs with Windows Hello. It had worked fine for years prior to the 20H2 update.

Also, Windows Hello works fine with the fine with PIN and with my fingerprint scanner. Only facial recognition is now broken.

So BRIO works with apps other than Hello and Hello works fine with everything but facial recognition via the BRIO 4K, but the combination of BRIO + Windows Hello broke with the latest Windows update.

Is this working for anyone with the same configuration?

The error message Windows Hello gives is, "Sorry something went wrong. Camera is currently in use by another app. Close the app and try again." But nothing else is using the camera (proven by the fact that all the apps listed above will launch and use the camera just fine).

One other note, which may be helpful diagnostically: when Hello is trying to scan for my face, the red light on the BRIO does flash for several seconds as if it's working, but no picture ever comes through. There is obviously at least some successful communication between Hello and the BRIO.

I also tried plugging the BRIO both directly into different USB ports on the computer and into various hubs. Always got exactly the same results.

Any suggestions? Do we need to wait for a patch from MS to fix this defect in 20H2?

Thanks,

Colin

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

110 answers

Sort by: Most helpful
  1. Anonymous
    2021-01-23T19:16:09+00:00

    Had the same problem as GraniteStateColin, running with windows version 20H2 with webcam Logitech BRIO 4K Stream edition.

    The error message was slightly different in Windows Hello:

    Sorry something went wrong. Camera cannot be turned on

    Same diagnostic info, red light flashes on camera for several seconds with no picture when trying to setup face recognition.

    I've only just purchased this camera, today, and had never had it installed in previous windows versions.

    Tried all the suggestions in this post, nothing worked.

    I did find something that worked!

    used - Option 2: Try to install compatible firmware updates for your BRIO Camera. Check this link:

    ftp://ftp.logitech.com/pub/techsupport/cameras/...

    Downloaded LogiBrioStreamFWUpdate_1.3.14.exe

    Detected my camera and updated firmware from 1.1 to 1.3.

    Camera now works perfectly with windows hello and I did'nt need to reboot.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2021-01-05T15:08:19+00:00

    I had already raised this with Microsoft Support and received an acknowledgement.

    I next received a notice saying my query was resolved. I told them it was not and despite three reminders I have received no acknowledgement or solution.

    They need to setup a Microsoft Customer Disservice Department!

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2020-12-29T22:26:18+00:00

    Did you set AllowDomainPINLogon to 1 in the registry?

    Yeah. Well, more confirmed that it was already set to that. The GPEdit changes force that I believe. In any case, yes that was set to 1.

    Cheers,

    Colin

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2020-12-29T21:12:10+00:00

    Thanks for the new (to me) firmware info :) they hide these things quite well. 

    Sorry to say, though, that it made no difference to the Hello problem.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2020-12-29T18:33:06+00:00

    Did you set AllowDomainPINLogon to 1 in the registry?

    Was this answer helpful?

    0 comments No comments