Windows Hello broken [Fixed in Windows 10 19025 Insider update]
As you can see, the Windows Hello options are always disabled, even though they work fine on the lock screen. Is this a known issue? I'm on the Windows Insider Fast 18995 build.
1Password Version: 7.3.12
Extension Version: Not Provided
OS Version: Not Provided
Sync Type: Not Provided
Comments
-
@kop48: Unfortunately it's a known issue with some Windows Insider builds.
0 -
I can try on my Surface Laptop, tho this should be irrelevant from the app's perspective - if Hello is available at the system level, then the app can use it without knowing what kind of gesture is being used to unlock the container.
0 -
Hi @kop48,
if Hello is available at the system level, then the app can use it without knowing what kind of gesture is being used to unlock the container.
Exactly, it's a simple Windows call we're making, there is nothing else we can customize or control. We haven't changed anything with Hello in a few years, so the issue is with Windows itself.
But the problem is, we cannot reproduce this on our own machines and we only got a few reports of this not working, all on Insider builds. As we can't reproduce this yet, we cannot forward this information to Microsoft as we have nothing actionable to share.
The best thing you can do for now is file a bug report with Microsoft via their Feedback Hub on the affected machines.
just tried this on my Surface Laptop with internal Face IR camera and it's running into the same issue.
The laptop is with Insider Fast Ring builds?
0 -
@kop48 if you can pass to Hello team, it's started to report
UserConsentVerificationResult.DeviceNotPresent
fromUserConsentVerifier.CheckAvailabilityAsync
andIUserConsentVerifierInterop.RequestVerificationForWindowAsync
methods. Thanks!0 -
And they can get in touch with us at
support+windows@1Password.com
.0 -
Does anyone have any progress to report on this?
I'm running Windows Insider 19018, and Windows Hello is disabled in 1Password Version 7.3.712, despite working perfectly for logging in to Windows.
0 -
Fantastic, thank you!!
0 -
This has been fixed in today's 19025 build update.
0