Fingerprint issue

[Anon6197]

This is happening with me as well.  I tried different combinations of disabling/reenabling the FPR feature in lastpass vault, uninstalling/reinstalling binary support / native messaging, uninstalling/reinstalling standalone chrome plugin and uninstalling/reinstalling lastpass desktop.

The aforementioned workaround does work for me.  Just to be clear, you've gotta click the second "LastPass" (it just says "LastPass").

Firefox works as it should.  Just Chrome having the issue, and it is on all the PCs I use (different FPRs including USB ones like digitalpersona U.are.U 4500 and Kensington VeriMark USB, as well as built-in ones such as the ones on the ThinkPad x390 and T480s).

Google Chrome Version 87.0.4280.66 (Official Build) (64-bit)

Windows 10 Pro Version 2004 OS build 19041.630

[centicon]

I have had this issue too, for about two months

As this seems to be an issue that the Devs are working on, I have found a work-around and posted it 

on another thread, here 

With this work-around, I can get the LastPass Chrome extension to ask for the fingerprint again

• Right click on Chrome LastPass Extension - go to Options
• in Chrome LastPass Extension Options --> General: enable: "Log out when all browsers are closed"
• in Chrome LastPass Extension Options  --> Advanced --> enable: "Open login dialog when browser starts"
• in Chrome --> Settings -->  Advanced --> System:  disable "Continue running background apps when Google Chrome is closed"

Now when Chrome is closed it should close completely, and when it opens again is asks for the fingerprint.

This is not very satisfactory, but at least it seems to work

[buzzword]

It's also an issue with Firefox, but the workaround for Chrome works for Firefox as well. It's not "Solved!" It's a workaround. They need to fix this.

[centicon]

Completely agree - this is just a stop-gap solution that "kind of works" but is nowhere near satisfactory - it needs to be fixed properly

[seudónimo]

I agree with @buzzword and @centicon. I'm not sure whether it was OP or the LogMeIn folks who marked this as resolved, but it is absolutely not—the issue needs to be fixed properly.

[RachelO]

Hello,

Our development team is aware of this issue and working on a resolution, although we do not have a date for an ETA to share currently. The workaround has been marked as a solution in the meantime so users can quickly find a workaround, and as soon as I have more news from our development team I will update this thread.

[PeterTGIT]

This workaround does not work for me (Version 88.0.4324.182 (Official Build) (64-bit) & Version 88.0.4324.190 (Official Build) (64-bit)). Did this workaround stop being viable for anyone else for more recent versions of Chrome? Unfortunately, I haven't been able to find another alternative.

[yaytech]

I had several devices where the workaround stopped, but worked again after logging in with the password once. I don't have any where the workaround continued to not work.

[Maarten2]

Same here, suddenly my fingerprint doesn't work anymore although it's been functioning for years.

[Anon6197]

Workaround still “works” for me. I keep Chrome and FF fairly updated and the workaround hasn’t stopped yet really. I right-click the grey LastPass extension icon and click the lone “LastPass” entry in the context menu. Anytime it prompts for authentication beyond my fingerprint (including password and 2FA) I close out of the browser completely and get back in and try it again and it always works the 2nd time (unless my 30 day 2fa session has actually expired).