nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Why LastPass Entering Wrong Master Password?

LastPass User

When I log in to Google Chrome browser, my LastPass master password is a massive garbled string of around 64 letters, numbers and symbols instead of my actual master password.

To be clear, my master password works fine, but it isn't autofilling the correct master password. The issue is only with Chrome as other browsers work fine.

I have done everything in the recommended steps such as clearing cache, resinstalling the extension and disabling Chrome password manager. I also don't have LasPass saved in Google password manager either.

I know this isn't critical, but it's annoying AF. Any help appreciated.

Cheers,

Michael.

Find more posts tagged with

Accepted answers

LastPass Support

Hi, all.

This is a known issue we are fixing currently. You don't have to do anything but allow for automatic updates to resolve the issue, coming in the next few days.

All comments

LastPass User

I also have the same issue and I tried the above solution and the problem is still present.

LastPass Support

Hello! @LastPass User

Welcome to the LastPass Community.

We truly apologize for the problem, since is your Google chrome the one who autofill the data, I will recommend you follow the steps below:

Go to the 3 dots at the top right corner.

Go to delete Browsing data

Make sure you choose the option ALL TIME

In the dropdown list please remove the check mark from all options except Autofill Data

I will also recommend you delete all saved passwords in your Google Chrome password manager and try again.

Please let me know if you need additional help.

Greetings!

Verlaine | Customer Care

LastPass Support

Hi, all.

This is a known issue we are fixing currently. You don't have to do anything but allow for automatic updates to resolve the issue, coming in the next few days.