Fingerprint doesn't work with LastPass in Chrome

[mikedig]

I'm having a fingerprint issue with the Lastpass Chrome extension.

It no longer asks me for my fingerprint when I go to log into the extension (rather, it asks for my password).  However, once I'm logged in, if I do something in the extension that would require me to re-authenticate (like trying to export my passwords), it does pop up the fingerprint window.

I'm running Google Chrome Version 87.0.4280.66 (Official Build) (64-bit) on Windows 10 64-bit build 19042.630.

My fingerprint reader is built into my laptop.  The brand of the reader is Goodix.  The Laptop itself is Dell Inspiron 5770.

I'm not sure if the issue is with Windows, Chrome, or the Lastpass Installer, as I've recently updated all three.

If anyone has any suggestions, I would appreciate them.

Thanks.

[pug1]

I'm having a similar, possibly the same issue. Suddenly Chrome doesn't let me log into the LastPass extension with my fingerprint. I've had this problem occasionally in the past, and fixed it by logging in, going into settings, and turning the fingerprint multifactor feature off and back on again. However, this time around I'm having it revert to not asking for the fingerprint again the following day. I use a long complex password, and auto-logout quickly for security, and typing my whole password in every time is a major inconvenience!

*edit* 
Windows 10 (3 machines - 2 Home, 1 Pro, up to date on Windows Updates)
Chrome browser
Multiple fingerprint reader models, all working fine for Windows Hello login

[seudónimo]

I have been having the same issue since yesterday. I also tried disabling the fingerprint option in settings and turning it back on again, but that hasn't worked. I had the same issue two or three years ago and contacted customer service and they told me to completely uninstall and reinstall LastPass, and although it worked (at the time) it was a pain and I'd rather not have to try it again.

ETA:

Windows 10 64-bit
Kensington USB Fingerprint Reader (K67977WW)

FWIW, the reader works when I use it to log into Windows. And if I disable and reenable the fingerprint option in settings, LastPass asks me to scan my fingerprint and accepts it. Thus the problem for me seems to be with the Chrome extension.

[99969frankie]

I don't know if I was just unlucky with timings but I got a new laptop with integrated fingerprint reader and Lastpass just won't prompt me to use it, it did ask me to do it in the set up but not again. I signed up for premium exactly for this feature so hopefully we can get a solution. Lastpass support have not been a great help so far, gave me information I found on my first google search.  I'm on windows 10 64 bit 10.0.19042 Hp Envy with integrated reader

[GlennD]

Hi,

Can you please edit your posts and include your operating systems and the type of fingerprint reader you have (built-in, USB, make and model)?

[99969frankie]

Since you guys have had it working before this probably wont work for you but the solution in this thread helped me https://community.logmein.com/t5/Support-Discussions/Biometric-or-Fingerprint-Log-In-Error-no-Pop-Up...

[mikedig]

I can confirm when doing what 99969frankie posted...

Checking the option for "Open login dialog when browser starts"

...the fingerprint box *does* pop up when Chrome starts.  So it seems issue (no fingerprint box) is happening only when specifically clicking on the LastPass icon in the toolbar.

[dh29 · Accepted solution]

O/S: Win10 Pro 64-bit (10.0.18363 Build 18363)

Browser: Chrome 87.0.4280.66 (^4-bit)

I have also been having this issue for a few days. Left-clicking the LastPass icon extension in Chrome (...) does not prompt for a fingerprint anymore, but prompts for your master-password. Something has been broken!

My temporary workaround is to single-right-click the LastPass icon extension in Chrome (...), and then single-left-click "LastPass". With this method you do get prompted for a fingerprint. 

[seudónimo]

Thanks dh29. That works for me too. It's not ideal but it should get me through until they fix the issue.

[pug1]

Yup, that workaround works for me too. Silly that it's needed, but I'm very thankful for a simple workaround!