Windows Hello Support with Logitech Brio

I have AMC Ryzen AI 9 HX 370. I also have a Logitech Brio connected to my dock station which I have successfully used with Windows Hello on all my other laptops and my desktop.

However, I cannot get it to be recognized as a Windows Hello compatible camera with my Framework laptop, either directly connected or via my hub.

It registers as an “Imaging Device” instead of a Camera within Device Manager. I have tried all suggestions online, including uninstalling the drivers and instead picking a “USB Camera” from existing drivers availabe on my computer. While that can get it recognized as a camera, it is not recognized as a Windows Hello with IR capabilities camera. If you then update it back to picking the Logitech drivers, I’m back to having it be an imaging device.

It does function as a camera and you can do Teams/Zoom. It just can’t be used for Windows Hello. I’ve tried disabling the internal camera. And uninstalling the Brio, then rebooting with it directly connected to the laptop. Still an Imaging Device.

I’ve read there may be a compatibility issue with chips specifically within Framework related to AMD audio coprocessing. I do not see that as a device I can disable within device manager.

I do not see any recent community support articles related to the Brio, only desires to have Windows Hello support.

Is there a path to getting this to work? When using a docking station I normally have my laptop lid closed so while the fingerprint reader is cool, it is not convenient vs. just looking at my monitor.

I did not know it was originally supported as a Windows Hello camera…did a little digging and found this on a Reddit thread:

"Note: Since ESS for external Windows Hello capable USB devices is not supported yet, if you want to use it for Windows Hello, you need to disable ESS.

TDLR: Enhanced Sign-in Security doesn’t work well with external cameras, so it seems…

More info: Windows Hello Enhanced Sign-in Security | Microsoft Learn

You can disable this with this command prompt (run as administrator):

REG ADD “HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WinBio” /v SupportPeripheralsWithEnhancedSignInSecurity /t REG_DWORD /d 1 /f

Don’t forget to reboot after this. After a reboot, my camera was recognized by Windows Hello and I could train it.

For those with similar issues, try this. It might help."

Apparently there are additional security measures in Windows 11 by default that conflict with the camera. Also, note that in many cases the camera had to be plugged directly into the computer/laptop and not through a hub. This probably has to do with the additional security restrictions between Windows 10 and 11 though.

There was this summary that came up on a Google search:

" * Disable Enhanced Sign-In Security: If you have this feature enabled, you may need to disable Virtualization-based Security (VBS) and Memory Integrity to use the Brio with Windows Hello. Navigate to Windows Security > Device Security > Core Isolation and turn off Memory Integrity."

1 Like

Thanks. I will try it next time I am at my desk with the camera. I did try doing it with the Brio directly connected. My other laptops, and all of ours at work, have no problems using the Brio externally whether it is on a dock or directly connected. However, their internal cameras also already support Windows Hello so perhaps that is why they don’t have the conflict with the enhanced security. I will have to check the registry key on my work laptop that does not have this issue and see if it already is set to 1.

Thanks for the find. I did try Google but I didn’t find anything on my own.

1 Like

Thank you pkunk! I brought my Framework laptop back downstairs to my dock, which has my Brio plugged into it. Turned on the laptop, went to sign-in options, and facial recognition was now available. I still have the internal camera active.

I was able to set up facial recognition with zero issues.

One thing that I found interesting is that the Brio still shows up under Imaging devices instead of Camera on Device manager. I guess that was somewhat of a red herring for me that it wasn’t a camera, and really it was enabling the SupportPeripheralsWithEnhancedSignInSecurity setting in the registry.

That is great news! Glad to hear the solution worked.

Outside of built-in cameras; there are not too many external cameras that support Windows Hello. I always felt that it was a little bit of a missed market by Microsoft to not develop their own or partner with a vendor and make an affordable Windows Hello camera to make it more mainstream.

The security on the back end is much more robust and tied right into Microsoft’s push for TPM module requirements for Windows 11 machines. Meanwhile it would have created an easier way for everyday users to login to their computers.