August 15, 20214 yr Hi all, I am currently testing Windows 11 (22000.132) with Enpass (6.6.3 (836)) and find that (what still worked under Windows 10) unfortunately does not currently work under Windows 11, namely logging into the Enpass app (from the Windows Store) with Windows hello via fingerprint reader. It is not possible to activate Windows Hello within Enpass, although I can log in to Windows 11 with Windows hello. So OS wide Windows Hello is working. Have you been able to test this yourself? Is there perhaps a beta that already works (better) under Windows 11?
August 16, 20214 yr Hello @Bob___! Welcome to the Enpass Community. Since Windows 11 is still in the beta phase, there might be some features that might not be compatible with Enpass at the moment and bugs within Windows 11 as well. Also, I have shared this issue with our dedicated team for further investigation. In the meantime, you can refer to this link https://www.windowscentral.com/windows-11-windows-hello-broken-fix. Let me know if it helps.
August 17, 20214 yr Author No, unfortunately the link to the "Windows-Hello-broken-fix" did not affect the issue at all. As I said, when logging in to Windows 11, Windows Hello with the fingerprint reader works without any problems, it is just currently not possible to use this option within Enpass.
August 18, 20214 yr Hello @Bob___! Are you able to see "Windows Hello" option under security settings. If yes, try "Security -> Quick Unlock -> Disable and Enable the Windows Hello". Let us know if there any error message. It will be helpful if you can provide us a screenshot.
August 22, 20214 yr Author Yes, of course I see the checkbox under Quick Unlock "Windows Hello" in this menu, but it cannot be clicked or the checkmark does not stay in the checkbox. Under Windows 10 this was possible without problems on the same computer. Under Windows 11 there is the TPM management console (no idea if this was already available under Windows 10) and if you call it with tpm.msc in a console it confirms to me that my TPM is ready for use (see screenshot, sorry it is in German, but it says that everything concerning TPM is OK). Only within Enpass it does not seem to be recognized at the moment.
August 23, 20214 yr Hello @Bob___! I would like to inform you that recently we have released a new update of Enpass 6.7.1. Please update it to the newest version and set up the Windows Hello, and let me know if it works.
August 23, 20214 yr Author Hi @Manish Chokwal, currently I only see in the (German) Windows Store the following app version: Even after log out and log in of my user the "old" version is only available. Could you please check, if you can en-force the update to be visible in the German Windows-Store (if possible)? UPDATE: I even tried to uninstall the "old" Enpass App and reinstall it again from the (German) Windows Store but got again only the 6.7.0 (866) version Edited August 23, 20214 yr by Bob___
August 24, 20214 yr Hey @Bob___ The version 6.7.0 866 is the latest build. Have you tried re-setup the Windows Hello from device settings and leter on try to enable on Enpass.
August 24, 20214 yr Author Hi @Samuela but @Manish Chokwal wrote this ... Quote I would like to inform you that recently we have released a new update of Enpass 6.7.1. Please update it to the newest version and set up the Windows Hello, and let me know if it works. So that's why I assumed that there is already the new release 6.7.1? available. What is correct now? Edited August 24, 20214 yr by Bob___
August 24, 20214 yr @Bob___ might he will be confused about version number, the latest one is 6.7.0 866. Have you tried deleting old fingerprint and adding new one?
August 24, 20214 yr Author Hi @Samuela Yes, I have already tried that, but unfortunately nothing changes in the behavior of Enpass, the checkbox to enable Windows Hello can not be set to active.
August 25, 20214 yr Hello @Bob___ and @Samuela! Enpass version 6.7.1 is released for macOS and version 6.7.0 is for Windows. I apologize for the confusion here. About Windows 11 Hello issue, we have tested this issue on multiple systems/versions and found it working as expected. Still, our team is exploring the possible reasons that might cause this behaviour. So please be with us, your patience is highly appreciated here.
Create an account or sign in to comment