KeePassWinHello Error

[JRMara]

Describe the bug Error Message Pop Up at Program Start. KeePass does not recognize WinHello.

To Reproduce Steps to reproduce the behavior:

1. Download KeePass 3.1.1
2. Input Trigger

3. Install Plugin
4. Start KeePass

Expected behavior After installing the Plugin I expected KeePass to recognize WinHello. Instead every time I start KeePass I get the Error message. KeePass starts normally after that, but does not recognize my WinHello.

Screenshots

Desktop (please complete the following information):

• OS Version - Win10 Enterprise
• KeePass Version 3.1.1
• Plugin Version KeePassWinHelloPlugin.plgx from Version 3.1.1

• Dell Latitude 7400 + DELL UltraSharp U4919DW + Dell MS819 (fingerprint sensor)

  KeePass settings and environment

• Is secure desktop enabled - No
• Is KeePass running under Administrator (in elevated process) - Yes
• Installed plugins - Yes see above

Additional context Add any other context about the problem here.

[sirAndros]

Hello! It's interesting. Can you check: does problem reproduce if you don't use trigger and try to open some database in clean KeePass with our plugin? (Also elevated, as you using it usually)

[JRMara]

I have deleted the trigger, rebooted my device and tried again. Same error, still does not recognize WinHello.

[sirAndros]

Thank you! Please, tell us your windows version. https://support.microsoft.com/en-us/help/13443/windows-which-version-am-i-running eg:

[sirAndros]

And if it possible, checkout if you have this registry key: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System. More valuable property of this key for us is "EnableLUA". It can be 0 or 1.

[JRMara]

Windows specifications

Edition - Windows 10 Enterprise Version - 1909 Installed on - 31.08.2020 OS build - 18363.1082

This registry property does not exist on my PC.

[sirAndros]

Thank you! I will research your case in freetime

[shuffle-c]

Hi JRMara, Can you please also let us know your current UAC settings? You can find it by typing 'uac' in the windows settings dialog: and you'll get something like this:

[JRMara]

It is in german, if you need it in english please let me know.

[shuffle-c]

Thank you, that's sufficient. As a current workaround, if you wish to, you can manually add the absent value EnableLUA to the registry:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System]
"EnableLUA"=dword:00000001

It won't affect your system since the value is meant for UAC being enabled which is actually enabled on your system anyway. Meanwhile we'll fix the issue in the next release. Thank you for the report.

[JRMara]

Adding the "EnableLUA" value at 1 fixed the problem for me.