Windows Hello Compatibility
in progress
A
Alder Alderson
We have some clients who exclusively use Azure joined devices and use Windows Hello for logins which overrides the UAC prompts to ask for Windows Hello. As more and more clients/companies are moving to cloud-based systems, we need Windows Hello to be able to work as it currently fails and locks the user accounts out.
D
Daniel Rivera
updated the status to
in progress
This is in active development! We're extending AutoElevate's credential provider to cover UAC prompts, so elevation works properly on devices using Windows Hello and other passwordless sign-in. If your clients are Azure-joined and rely on Windows Hello, this addresses the UAC failures and lockouts you've been seeing. The work is in review now — we'll post here when it ships. Thanks to everyone who voted and described their environments; that detail directly shaped the fix.
L
Liam Snack
It looks like this feedback hasn't been moved to consideration yet? Are there any plans to put this on the roadmap?
D
Daniel Rivera
Thank you for your feedback, Alder. We definitely see the trend and will be working toward not having this disrupt our agent. In the meantime, you may be able keep Windows Hello for sign-in but hide it from UAC prompts. In regedit, if you go to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
Add a new String value named ExcludedCredentialProviders and set the data to the Hello CLSIDs (PIN, fingerprint, face, etc.), then reboot. UAC should default to username/password while sign-in stays unchanged.
If you need further assistance with setting that up, please reach out to support team at support@cyberfox.com
Roman S
Yes, please!
J
Joe Fabrie
I second this