Method 1 seemed to make it work for me! Thanks for the tip!
Windows 20H2 update seems to have broken Windows Hello Face Recognition
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.
110 answers
Sort by: Most helpful
-
Anonymous
2021-04-11T09:36:37+00:00 -
Anonymous
2021-04-10T07:32:34+00:00 Hi Colin. I'm not sure where you are at with this but this solved it for me. It appears ever since Microsoft decided to take on an Agile approach to its software development processes, they are breaking things while fixing things or while they introduce new features without realizing they have broken things. i.e. regression testing isn't airtight at Microsoft.
The issue with the way this solves the issue is that each time Microsoft updates your system via Windows Update, it will override and restore the broken state so you may find yourself doing this on a monthly basis. Do what I did. Script the solution in a .cmd batch script or similar so all you do is run it every month.
Good luck!
-
Anonymous
2021-04-08T07:46:46+00:00 Hi Colin,
The Version is Win Pro19042.906
Regards KvsToc.
-
Anonymous
2021-04-07T17:46:09+00:00 After trying a lot of the suggestions on this thread, what worked for me was to disable the integrated laptop camera (from the Device Manager).
This is a known issue that has existing before the 20H2 update that should be fixed on the 21H1 update coming out from MS shortly. That's a different problem than the BRIO4K not working only after updating to 20H2, even when it's the only camera.
-
Anonymous
2021-04-07T17:28:15+00:00 @KVSTOC, unfortunately, mine is connected to USB 3.0 port (appears like in your last picture). But it is encouraging to know that the BRIO 4k works for some people. While that doesn't help me, I can be a bit more forgiving to MS (and even Logitech) if I know it's not a universal problem.
Just to be sure, are you on Windows 20H2 or later? (if not sure, run winver)