Password · guide

Can’t reach Google Password Manager, and what actually causes it

By Alberto Gulotta · Updated · 19 min read

If you can’t reach Google Password Manager, your saved passwords are almost certainly still there: the list belongs to your Google Account, and passwords.google.com opens it from any browser. The error describes a service that will not answer, not a broken file. Google documents three causes, and only one of them is fixed by signing out and back in.

Three documented causes behind a Google Password Manager that will not answer Three branches: on Android, Google Play services waiting to be updated; on a computer, a Google Password Manager PIN created with your first passkey; and on any device, on-device encryption with a lost key. Each has a different fix. The box underneath is the check to run first, and it names the case in which that check itself needs a key: under on-device encryption the address opens only with the Google password or a screen lock. WHICH ONE YOU HAVE, BEFORE YOU FIX ANYTHING On Android Google Play services waiting to be updated, or a migration that never finished On a computer a Password Manager PIN you never set, created with your first passkey On any device on-device encryption, and a key you no longer have on any of them First: open passwords.google.com in any browser If the list is there, nothing has been lost In the third case it opens only with your Google password or a screen lock; lose both and every signed-in device, and Google says the passwords are gone AI Tools Primer · figure
The three branches need three different fixes, and the check underneath comes before all of them — except that in the third case the check has a condition of its own. Figure drawn by AI Tools Primer.

What the error actually is, and the route that works anyway

Google Password Manager is not a file on your machine that can go bad. Google describes two places a password can be, and the difference is the whole story: “save passwords to your Google Account: when you’re signed in to Chrome, you can save your passwords to your Google Account and use them across your devices”, or “save passwords to your device: when you’re not signed in to Chrome, it stores passwords locally”. If you are signed in, the list you are looking for is a service. An error that says it cannot be reached is a report about that service, not about your computer.

Which is why the first thing to do is not a repair at all. Google puts the same line at the top of two different help pages: “you can manage passwords saved to your Google Account in Chrome or any other web browser at passwords.google.com”. Open that address in anything — a second browser, a phone, a borrowed laptop — and if the list is there, nothing has been lost and you are dealing with one broken path to it rather than a broken drawer.

That test also splits the problem in two, which is more than the usual advice does. If the web page shows your passwords and Chrome does not, the fault is on the device. If the web page will not show them either, the fault is between your account and the service, and clearing a cache is not going to reach it. Do that one check before spending an evening on the four things everyone recommends.

Two different credentials are both called a PIN, and telling them apart decides which fix is the right one
Your device PIN, or Windows HelloThe Google Password Manager PIN
Who made it You did, when you set up the computer or phone Nobody, on purpose: Google creates it “when you create a passkey for the first time on a computer, iPhone, or iPad”
What it protects The machine in front of you Encrypted data in your Google Account, so that “no one, not even Google, can access your encrypted data”
Where you change it Windows or Android settings Chrome, at chrome://password-manager/settings, and only “from a non-Android device on which you’ve previously used Google Password Manager”
If you cannot recover it Reset it the usual way; nothing else is lost Reset your passkeys instead, which Google says “deletes all your passkeys”

The PIN you never set up, and why resetting Windows Hello does nothing to it

This is the version of the problem that traps people for days. You go to move to a new machine, it asks for a “Google Password Manager PIN”, and you have never set one. You reset the device PIN, you toggle Windows Hello, you reinstall the browser, and the message comes back.

It comes back because those are the wrong credential. Google gives this PIN its own help page, and the first sentence explains where it came from: “when you create a passkey for the first time on a computer, iPhone, or iPad, a Google Password Manager PIN is created”. It was made for you, silently, the first time you used a passkey. And its job is to be something the device cannot supply on your behalf: it exists to “make sure that no one, not even Google, can access your encrypted data”.

The documented route is narrow, and worth following exactly. You change it in Chrome — Passwords and autofill, then Google Password Manager, then Settings, then Change Google Password Manager PIN, or straight to chrome://password-manager/settings — and Google adds a condition that the four quick fixes never mention: do it “from a non-Android device on which you’ve previously used Google Password Manager”. If that button is not there at all, Google lists four reasons: your first passkey was created on Android, you have not used Google Password Manager passkeys on this device, you used passkeys with a different Google Account, or access to passkeys was removed here.

And if none of your devices can do it, the last resort has a price that ought to be stated before you reach for it. Google: “you can reset your passkeys. This deletes all your passkeys, which means you’ll need to create new passkeys for each site.” Your saved passwords survive that; your passkeys do not.

Why this is the fact to lead with, rather than the four quick fixes. Sign out and back in, re-enable sync, clear the cache, check the PIN: four remedies, and between them not one cause. The trouble is not that they never work — it is that three of them cost an evening and the fourth sends you to reset the wrong credential entirely. Google has written a page about each real cause; none of them turns up in a summary because none of them is on the page a search puts in front of you. That is the same test being applied across this group of guides: not which manager is best, but what each one does on its worst day, and whether the maker says so.

The cause Google names out loud, and the notification you may have dismissed

On Android there is a documented reason for passwords to stop being available that has nothing to do with sync, caches or profiles, and Google gives it a page of its own. It opens like this: “You might’ve received a notification that your passwords will soon stop working on your device or in your Chrome settings to update Google Play services. To maintain your passwords, you need to update Google Play services.”

That is worth reading twice, because it points at a component nothing else here touches. The manager on an Android phone runs inside Google Play services; if that component is behind, the passwords do not move with it, and no amount of signing out of Chrome will help. The fix is an update, and Google describes it as a notification you tap.

If the automatic migration did not happen, Google documents doing it by hand, and the steps are worth knowing because they pass a plain text file across your phone. Export from Google Password Manager in Chrome after unlocking with your fingerprint or PIN, save it to Downloads, then import it back into your account from the same menu. Then delete the file, and Google is blunt about why: “if you don’t delete your password file, anyone who uses the device can open the file and access your passwords.”

On-device encryption, and the setting there is no way back from

The third cause is the one that is not a fault at all. On-device encryption is a choice about who holds the key, and Google explains it with a bank metaphor it is honest enough to follow through: with standard encryption “the encryption key, used to access your passwords, is safely stored in your Google Account”, so Google can unlock the list on your behalf. With on-device encryption “you take the key with you instead”.

Two sentences on that page matter more than the rest, and neither is in any summary of this error. The first: “Once on-device encryption is set up, it can’t be removed. Over time, this security measure will be set up for everyone to help protect password security.” The second is the list of when the drawer is gone for good — when you lose every recovery option, Google password and screen lock included, or lose access to every device signed in to the account with the passwords on it.

There is a way to start over, and it is a deletion rather than a repair: go to passwords.google.com/encryption/reset, select Turn off, and “confirm that you want to delete all saved passwords”. Which is why the advice you will find in forums — to switch encryption back to the ordinary kind and clear the PIN that way — describes something Google’s own page says cannot be done. The people offering it are trying to help, and they are not Google.

On-device encryption is a one-way door, and Google says so Standard encryption keeps the key in your Google Account, so Google can unlock the list for you. On-device encryption moves the key to you, cannot be removed once set, and the only way back is a reset that deletes every saved password. WHO HOLDS THE KEY TO YOUR SAVED PASSWORDS Standard encryption the key stays “safely stored in your Google Account” On-device encryption “you take the key with you”, and “it can’t be removed” The only way back, in Google’s own steps: passwords.google.com/encryption/reset, Turn off, and then “confirm that you want to delete all saved passwords”. AI Tools Primer · figure
Worth reading before you switch it on, because Google adds that in time it will be set up for everyone. Figure drawn by AI Tools Primer.
The route that does not depend on Chrome, and the way out Any browser, then passwords.google.com, gets to the same list. From Chrome the export path is Passwords and autofill, Google Password Manager, Settings, then Export passwords and Download file. WHEN CHROME WILL NOT REACH IT Any browser including a phone passwords.google.com the same list, signed in Search, view, edit, delete without touching Chrome settings AND THE WAY OUT, FROM CHROME Passwords and autofill then Google Password Manager Settings scroll down Export passwords · Download file a plain .csv, so delete it afterwards AI Tools Primer · figure
Two routes that do not care whether Chrome can reach the service. Figure drawn by AI Tools Primer.

What the standard says about the moment you cannot get in

Quoted from NIST SP 800-63B, Digital Identity Guidelines, read in full on 9 September 2026.

This is the known weak point of the whole design, not a Google problem “The weak point in many authentication mechanisms is the process followed when a subscriber loses control of one or more authenticators and needs to replace them.”
And the standard names the risk that comes with a synced list In its table of threats to synced credentials: “Synced keys are accessible via cloud-based account recovery processes, which represent a potential weakness to the authenticators.” Recovery is the front door, which is why it is the part that is made hard.
The mitigation is the only prevention that works here “To minimize the need for account recovery, CSPs and verifiers SHOULD encourage subscribers to maintain at least two separate means of authentication.” In practice: keep a second device signed in, and keep the recovery phone and email current, before anything goes wrong.

What the Google community thread on this error actually contains. It is worth opening, and it is not quoted here because the page renders in a way that cannot be checked back automatically, so what follows is a reading rather than a transcript. A user, posting in May, described being asked for a Google Password Manager PIN he says he never set up, after clearing caches, reinstalling the browser, removing and remaking the passkey and toggling Windows Hello. Seventeen other people marked the question as theirs too; it is now locked to further replies. Both answers come from other users, which the page flags itself as content that may not be verified. One of them suggests asking Google to reset the PIN from its own side; the other suggests switching encryption back to the ordinary kind. Google’s pages say the first is the thing the PIN exists to prevent, and that the second cannot be done at all. Kind people, wrong answers, and nowhere else to send the question.

And the case where none of this is the real problem. If you can reach the list but a password in it has stopped working, that is the account at the other end, not the manager: resetting a Gmail password is the commonest version. If you cannot sign in to the Google Account at all, the manager is downstream of that. And if a saved password has surfaced in a leak, work through what to do after a data breach.

Every cause above is one Google documents by name, on the dates below.

Where to start

Three ways in.

“I just want to see my passwords now.”
The address that still works — what it is
“It wants a PIN I never made.”
The credential everyone mistakes — the pin
“It broke on my Android phone.”
The cause Google names — play services

When the account is the problem, not the manager

A password manager that will not answer and an account you cannot sign in to look identical from the outside, and they are fixed in opposite directions.

Resetting a Gmail passwordNo limit on attempts, a seven-day wait on new recovery details, and no number to call.Open this guide → Changing a Microsoft passwordSix things share that name, and three are changed somewhere other than where you are looking.Open this guide → After a data breachWhat a reused password becomes once a company loses a list of them.Open this guide →

The same drawer, other lids

Every browser keeps a version of this list, and each answers the same four questions differently.

The Apple password managerTwo names, one drawer, and a ten-attempt limit written into firmware.Open this guide → The Edge password managerOne condition decides whether you have it at all, and it is which profile you signed in with.Open this guide → Is Bitwarden safeTwenty-five published audits with the auditors named, and the password nobody can reset.Open this guide → The Firefox password managerTwo locks, and one of them empties the drawer if you forget it.Open this guide → The Opera password managerTwo of the four questions answered, and two the maker’s own help does not touch.Open this guide →

Questions people also ask

Why is Google Password Manager not working?

Because it is a service rather than a file. Google documents three causes: Google Play services waiting to be updated on Android, a Google Password Manager PIN created with your first passkey, and on-device encryption whose key you no longer have. Each needs a different fix.

How do I reach Google Password Manager?

Go to passwords.google.com in any browser, not only Chrome. Google puts that line at the top of its own help pages. If the list appears there, nothing has been lost and the fault is in one path to it rather than in the drawer.

What is the Google Password Manager PIN, and why do I have one?

It is not your device PIN and not Windows Hello. Google creates it “when you create a passkey for the first time on a computer, iPhone, or iPad”, so that “no one, not even Google, can access your encrypted data”. It is changed in Chrome, not in Windows.

Can Google reset my Password Manager PIN for me?

Google’s own page says the PIN exists so that no one, Google included, can reach the encrypted data. The documented route is to change it from a non-Android device where you have used Google Password Manager before; failing that, resetting passkeys deletes all of them.

Can I turn off on-device encryption?

No. Google writes: “Once on-device encryption is set up, it can’t be removed.” There is a reset at passwords.google.com/encryption/reset, but it asks you to confirm that you want to delete all saved passwords, which is a fresh start rather than a way back.

How do I get my passwords out of Google Password Manager?

In Chrome: Passwords and autofill, then Google Password Manager, then Settings, then Export passwords and Download file. The result is a plain .csv, so delete it once it is imported. Google caps imports at 3,000 at a time and storage at 10,000 passwords.

Not covered here. It does not recover a Google Account, which is the problem underneath if you cannot sign in at all rather than cannot reach the manager.

It does not treat passkeys as a subject in their own right, only the PIN that arrives with the first one; and it does not promise a time by which a service error clears, because Google publishes no error page for this message and this page will not invent one.

For the rest of the family, the way in is the guides on passwords and the ways in. What holds instead is simple: each of the three causes is one Google documents by name, quoted from the page that documents it, the statement that Google publishes no error page for this message is written as what twelve help articles do and do not contain rather than as a claim about Google, and the community thread is reported as the testimony of the people who wrote it, in summary rather than in quotation, because that page cannot be re-read from the command line.

Sources

  1. Google Chrome Help — Fix issues with passwords and passkeys (Computer, and the Android version of the same article): the four problems Google does treat here, and the line that saved passwords can be managed “in Chrome or any other web browser at passwords.google.com” — support.google.com, read 9 September 2026.
  2. Google Chrome Help — Manage your Google Password Manager PIN: that the PIN is created with your first passkey on a computer, iPhone or iPad; that it exists so that no one, not even Google, can reach the encrypted data; the route through chrome://password-manager/settings; the non-Android condition; the four reasons the button may be missing; and that resetting passkeys deletes all of them — support.google.com, read 9 September 2026.
  3. Google Chrome Help — Migrate passwords to Google Play services: the notification that passwords will stop working, that the fix is updating Google Play services, the manual migration through export and import, and the warning about deleting the exported file — support.google.com, read 9 September 2026.
  4. Google Account Help — Get started with on-device encryption: that once it is set up it cannot be removed and will in time be set up for everyone, where the key sits under each kind of encryption, the list of ways to lose access to every saved password, and the reset that deletes them all — support.google.com, read 9 September 2026.
  5. Google Chrome Help — Manage passwords in Chrome: the distinction between passwords saved to the Google Account and passwords stored locally when you are not signed in, which is why an unreachable manager is a service fault — support.google.com, read 9 September 2026.
  6. Google Account Help — Get started with Google Password Manager: the index of the twelve help articles Google publishes on the manager, read title by title, and what the manager collects for analytics and troubleshooting — support.google.com, read 9 September 2026.
  7. Google Account Help — Use passwords & passkeys across your devices: where the same list appears on Android, that offering to save is on by default, and that an enterprise administrator may manage the setting instead — support.google.com, read 9 September 2026.
  8. Google Chrome Help — Import or export passwords and passkeys with Google Password Manager: the export path through Settings and Download file, the 3,000-per-import and 10,000-per-account limits, and the instruction to delete the file afterwards — support.google.com, read 9 September 2026.
  9. Google Chrome Help Community, thread #432140968 — “Can’t connect to google password manager to set up google password manager pin”: read with a browser and reported as the testimony of the people who wrote it, not as a statement by Google, which the page itself flags as content that may not be verified — support.google.com, read 9 September 2026.
  10. NIST SP 800-63B, Digital Identity Guidelines: that authenticator replacement is the weak point of these systems, the threat table entry naming cloud-based account recovery as a weakness of synced credentials, and the recommendation to keep at least two separate means of authentication — pages.nist.gov, read 9 September 2026.

Written by Alberto Gulotta

Founder and editor of AI Tools Primer, writing from Palermo, Italy. Thirty-five years of taking computers apart, starting with a Commodore 64 — the long version is on the about page.

Something wrong on this page? Write to aitoolsprimer@gmail.com and it gets fixed.

Written on 9 September 2026.

Independence and limits

No affiliate links and no paid placements anywhere on this site. Nobody pays to appear here, and no company has seen this page before you did.

This is general information, not professional advice. Where a page touches money, health, safety or the law, it names its source and the date it was read — and your situation may still differ. See the privacy page and the cookie policy.