If you are using Chrome as your primary browser, follow these instructions specifically:
There could also be some confusion within the LastPass cache itself, which can be cleared through the browser app: Account > Fix a Problem > Clear Local Data.
** If you are using something like DuckDuckGo or Brave, I'm afraid these browsers are not currently supported with LastPass, but you may be able to locate that browser's autosave / password-fill function and disable it to ensure LastPass is functioning as intended.
Hi @rdaltvater
Welcome to the LastPass Community.
There may be an issue with caching within your LastPass Vault. You can try clearing this cache yourself, through the browser app > Account > Fix a problem > Refresh.
@lindsey_gladwell
You can also try updating your login password to re-encrypt the vault data to see if that resolves the confusion.
I'm having the same issue! This fix did not help.
I have the same issue, something has changed on the LastPass site. I don't use the LastPass browser extension, so the browser password manager is auto-filling the password field I am trying to view with my master password.
I have the same issue, unable to view saved password.
Question: Why has a last pass support specialist NOT provided a way to fix the problem or provide a reason why it happens? Does a support specialist know the answer?
Hello,
To help us understand the source of this problem, please provide the following:
- The device in use - My personal desk top
- The web browser version in use - Google Chrome (as always)
- The LastPass version installed - how to I determine?
- If you have any other password management systems in place, such as your default browser's pw manager - None (never used)
- Ifclearing the LastPass cachefixes the issue - done - did not fix the issue
Faye Chenier-White
The Device used has Windows 11 Pro
Web Browser is Chrome (have used DuckDuckGo but uninstalled a couple months ago)
LastPass version installed is Premium User
Not using any other Password Management system
Did not clear LastPass cache - the original fix seems to have worked
It appears as though you do NOT know how to correct the issue. Why don't you tell me what is needed (required) to accomplish what I'm looking to do?