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

110 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2021-09-19T15:04:29+00:00

    I had a peak on this in a debugger (Since I have the same camera, and suffers from the same problem.)

    It seem like there is a race condition // dangling handle error in WINBIOSTORAGEADAPTER.DLL.

    The process is crashing due to UnlockFileEx throwing an INVALID_HANDLE exception.

    And the reason for this is that the file handle passed to UnlockFileEx has been closed already by another thread. - So the handle is accessed after closure.

    ...

    So.. We need Microsoft - to investigate this since it's their module.

    Per Larsson, as there have been a few different issues raised here, which one is this? Does this align with the message when trying to set up the BRIO for Hello "Sorry, something went wrong. Camera is currently in use by another app. Close the app and try again." (when it's obviously not in use, as easily proven by the fact that it works with any other app started after this and by the fact that the attempt to set up Hello does turn on the camera red light) or one of the other reported problems using Brio 4k with Hello?

    Currently, my hope is that a new install of the upcoming Windows 11 or the new Dell 4k camera will resolve the problem. I have lost any hope of the BRIO working on my desktop PC with Windows 10 Hello. I currently use a fingerprint reader with Hello, which is not as convenient as when the BRIO worked for Face Recognition, but it's not too bad. And the BRIO still works fine for everything else, just not with Hello.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2021-09-15T13:06:38+00:00

    Mine is till not working on my Dell Inspiron 3670

    Was this answer helpful?

    0 comments
  3. Anonymous
    2021-09-15T05:45:30+00:00

    In case people following this thread have not noticed yet, the latest Windows update fixed this issue, at least on my Surface Book 3 Business (update also contained several firmware updates).

    My Logitech Brio camera now unlocks the computer upon facial recognition.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2021-09-12T21:24:12+00:00

    I had a peak on this in a debugger (Since I have the same camera, and suffers from the same problem.)

    It seem like there is a race condition // dangling handle error in WINBIOSTORAGEADAPTER.DLL.

    The process is crashing due to UnlockFileEx throwing an INVALID_HANDLE exception.

    And the reason for this is that the file handle passed to UnlockFileEx has been closed already by another thread. - So the handle is accessed after closure.

    KERNELBASE!CloseHandle

    rcx=0000000000000814 Handle

    1  Id: 8c4.7354 Suspend: 1 Teb: 0000005d`ee5fa000 Unfrozen

          Start: ntdll!TppWorkerThread (00007ffb`33762ad0)

          Priority: 0  Priority class: 32  Affinity: ff

     # Child-SP          RetAddr               Call Site

    00 0000005dee77ce78 00007ffb2b663a97     KERNELBASE!CloseHandle

    01 0000005dee77ce80 00007ffb2b664208     WINBIOSTORAGEADAPTER!wil::details::CloseHandle+0xb

    02 0000005dee77ceb0 00007ffb2b664bdc     WINBIOSTORAGEADAPTER!wil::details_abi::SemaphoreValue::TryGetValueInternal+0x1c0

    03 0000005dee77d120 00007ffb2b6646e0     WINBIOSTORAGEADAPTER!wil::details_abi::ProcessLocalStorageData<wil::details_abi::ProcessLocalData>::Acquire+0xfc

    04 0000005dee77d3d0 00007ffb2b664991     WINBIOSTORAGEADAPTER!wil::details_abi::GetThreadLocalDataCache+0x34

    KERNELBASE!UnlockFileEx
    rcx=0000000000000814 rdx=0000 0000 r8=00000000ffffffff r9=00000000ffffffff

    (8c4.4c24): Invalid handle - code c0000008 (first chance)

    First chance exceptions are reported before any exception handling.

    This exception may be expected and handled.

    ntdll!KiRaiseUserExceptionDispatcher+0x3a:

    00007ffb337b0d2a 8b8424c0000000  mov     eax,dword ptr [rsp+0C0h] ss:0000005dee77ea20=c0000008

    0:023> k

    0000005dee77e960 00007ffb31237afe     ntdll!KiRaiseUserExceptionDispatcher+0x3a

    01 0000005dee77ea30 00007ffb2b667fe7     KERNELBASE!UnlockFileEx+0x3e

    02 0000005dee77ea80 00007ffb2b67150d     WINBIOSTORAGEADAPTER!LockBoxUnlockDatabase+0x2b

    03 0000005dee77eae0 00007ffb2b67110c     WINBIOSTORAGEADAPTER!wil::details::ScopeExitFn<<lambda_7542fa4b78c356caa15f108e46ea04c1> >::~ScopeExitFn<<lambda_7542fa4b78c356caa15f108e46ea04c1> >+0x29

    04 0000005dee77eb10 00007ffb0c9d8b78     WINBIOSTORAGEADAPTER!StorageAdapterUpdateRecordCommit+0x8fc

    05 0000005dee77eec0 00007ffb0c9cd96b     wbiosrvc!AdapterCallWrapper<<lambda_9c35c0f790d7b12a348b369081d9ecd2> >+0x118

    06 0000005dee77ef60 00007ffaa8500bbf     wbiosrvc!InterceptStorageUpdateRecordCommit+0x2b

    So.. We need Microsoft - to investigate this since it's their module.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2021-09-07T06:55:32+00:00

    I found the problem for me. Closing the laptop lid made the brio not work. Leaving the lid open fixed the issue. Not ideally the best solution, but it's better than nothing.

    Was this answer helpful?

    0 comments