Chrome Does Not Ask to Save Passwords – How to Fix It

A good security practice is to have a unique, hard-to-guess password for each login you use. That's fine in theory, but we can't remember all the connections we use on a daily basis. That's why web browsers offer to remember them for you. So whenever you need to log into a website, it remembers it for you. But what happens when Chrome does not ask to save the password?

First of all, you really shouldn't depend on your browser to remember logins. They are not currently considered secure enough. You're much better off using a dedicated password manager. I'll cover them some more in a minute. Let me fix the original problem first, by making Chrome ask again to save the password.

Troubleshooting Chrome When It Doesn't Ask to Save Passwords

The first thing to do when Chrome stops asking to save passwords is to make sure the setting to save them hasn't been turned off. This shouldn't happen unless you share access to your computer, but this is a quick check, so it makes sense to do this first.

  1. Open Chrome and type 'chrome://settings/passwords' in the URL bar.
  2. Make sure Offer to save passwords is on.
  3. Check under Never recorded for the site you are connecting to, remove it from the list if it is there.

You should see a list of saved passwords under the Auto-login section, which should show your last logins used through Chrome. The Never Saved section is a list of websites for which you have instructed Chrome not to save passwords. Check this list for the site you're on that doesn't ask to save the password, just in case.

If Chrome is set to ask to save passwords and the particular website is not in the Never Saved list, we need to do a bit more troubleshooting.

Log in and out of your Google account again

The password issue may be a sync issue between Chrome and your Google account. Even though passwords are saved locally, they are also synced to the cloud.

Sign out of your Google account and sign back in. Retry the connection.

Clear browsing data

Chrome cache can sometimes cause issues with the browser. It's not unique to Chrome and happens to all browsers and dozens of apps. To clear cache in Chrome, follow these steps:

  1. Open Chrome and select the three-dot menu icon at the top right.
  2. Select More tools > Clear browsing data…
  3. Select all options for All the time and then the Erase data button.
  4. Try connecting to the website again.

Clear Chrome Password Folder in Windows

A more complex fix requires you to find your existing passwords folder and delete two files. This should force Chrome to download new copies and should reset the password process.

  1. Navigate to 'C:Users[Username]AppDataLocalGoogleChromeUser DataDefault' using file explorer. Where you see [Username], enter your Windows profile name.
  2. Copy the two files named, Login details et Data-log connection and stick them in a safe place.
  3. Delete these two files from the folder indicated above and wait to recopy them.
  4. Perform the above process to delete browsing data, but select the Advanced tab from time to time Passwords and other login details.
  5. Go back to a website that you know is connected, enter your information to sign in, then close Chrome.
  6. Copy the two files you saved to a safe place in their original position. Chrome should have recreated the files but you should overwrite them with the originals.
  7. Retester.

Check your registry files

If you're feeling brave or know what you're doing, then you might want to check your registry files for problems. Note that it is recommended to create a backup of your registry before making any changes.

  1. To create a backup, tap Windows + R , type “regedit” and press Enter.
  2. Now click on File> Export.
  3. From there, select the Export Range, choose its location, name your file and click save.

With that out of the way, let's edit the registry.

  1. Navigate to ComputerHKEY_LOCAL_MACHINESOFTWAREPoliciesGoogleChrome.
  2. From there, right click on PasswordManagerEnabled and select Clear.
  3. Close Registry Editor and restart Chrome before testing to see if it's fixed.

Why a password manager is better than a browser

Using a third-party password manager like 1Password or LastPass is preferable to a browser. They tend to be more secure, more flexible, and can do more than just store passwords. Making browsers save passwords instead of using a password manager really isn't the best for privacy and security, here's why.

For example, LastPass uses 256-bit AES encryption to save all of its data, passwords, and associated sites. It is currently the most secure encryption standards available for public use and is implemented both locally and in the cloud. Exact details of Chrome's encryption are very hard to find, but it probably doesn't exceed that number.

LastPass and other password managers offer plenty of options for creating passwords of almost any length and complexity. They also use salting to make them even safer. Although Chrome offers to help create passwords, the options are more limited than Chrome.

Password managers can also store credit card details, social security and driver's license numbers, offer two-factor authentication and advanced vulnerability scanning such as the LastPass Security Challenge.

The most important thing to keep in mind is that password managers are built with the explicit purpose of keeping passwords secure and manageable, so encryption and usability are core components of their design. .

There are plenty of other great password managers available, check out which is best for you. Next time Chrome won't ask to save passwords, take that as a sign and try something else.

Saving passwords

Saving and managing passwords in Chrome isn't usually a problem, but when it does, you now know a few ways to fix it. If a simple restart or logging in and out of your account doesn't work, try clearing some Chrome caches or files on your device.

Audio Video Chrome Does Not Ask to Save Passwords – How to Fix It
add a comment of Chrome Does Not Ask to Save Passwords – How to Fix It
Comment sent successfully! We will review it in the next few hours.