Why Edge keeps filling the old password
After you change a password on a website, two separate records exist: the credential the site now accepts, and the copy Edge saved from an earlier visit. If the site’s change form did not trigger Edge’s save prompt, or you dismissed it, Edge keeps offering the old value. The result looks like a login failure, but it is really a mismatch between the site and your local record.
Keep three things apart before you touch anything:
| Layer | What it holds | Who controls it |
|---|---|---|
| Website credential | The password the site currently accepts | The website account |
| Local saved record | The value Edge autofills | You, on this device/profile |
| Sync scope | Whether that record spreads to other signed-in devices | Your Microsoft account and profile setup |
Editing the local record fixes autofill. It does not revoke sessions that are already signed in elsewhere, and it does not change anything server-side. If you changed the password because you suspect someone else has it, treat the correction below as cleanup, not as containment — sign out other sessions or contact the site’s support through its own account settings, and confirm what options it actually offers rather than assuming a menu exists.
Check which record is wrong
Before editing, confirm the stale copy is the problem and not something else.
- Sign in to the website with the new password typed manually, without autofill. If that works, the site credential is fine and Edge is the stale layer.
- If manual entry also fails, stop: the issue is the website account (wrong account, pending confirmation email, or a change that never completed), not Edge.
- Note the exact site address you used. A saved entry for
example.comand a login page onaccounts.example.comcan be different records, and editing one will not fix the other. - Note the profile you are signed in with. Work and personal profiles in Edge keep separate password stores.
Microsoft Password Manager in Edge is available through a personal account profile; organizational policies may restrict features. Source
If a feature you expect is missing, that policy boundary is the likely reason; ask your administrator rather than trying workarounds.
Correct the saved record
Saved passwords can be inspected and edited through Edge Settings, Passwords and autofill, then Microsoft Password Manager; device authentication may be required. Source
In practice, the task is:
- Open the password list, find the entry for the exact site, and open it for editing.
- Replace the password value with the new one, keeping the username unchanged unless that also changed.
- Save, then reload the site’s login page and test autofill in a fresh tab.
- If the old value still appears, check whether a second entry exists for a variant of the address, and whether you are in the profile you edited.
Editing a password stored in Edge does not change the password on the website. Source
The website remains the source of truth. If the site later rejects the new password, do not keep editing Edge to match guesses — resolve the credential on the site first, then update Edge once.
A worksheet to keep the layers straight
Use one row per site so you do not confuse a fixed local record with a fixed account.
| Field | Example (hypothetical) | Why it matters |
|---|---|---|
| Site and exact login address | shop.example / login.shop.example | Entries are per address, not per brand |
| Edge profile | Personal | Profiles keep separate stores |
| Website password changed? | Yes, 12 March | If no, the local record is not the problem |
| Other active sessions reviewed? | Yes, signed out others | Editing Edge does not do this |
| Edge record edited? | Yes | Confirms which layer was touched |
| Autofill retested in new tab? | Passed | The only meaningful check |
| Sync on this profile? | Yes | Explains other devices |
Sync and other devices
If the profile syncs, an edit made on one signed-in device can reach the others — but do not assume it has. Check the second device directly by testing autofill there, and treat “it should have synced” as unverified until you see the new value fill correctly. If a device still fills the old password, edit the record on that device too rather than waiting.
A few failure paths worth knowing:
- Two entries for one site. Remove or correct the stale one; leaving both means autofill may pick either.
- A shared or family device. Correct the record there as well, or the old value stays available to the next person who signs in.
- A password you no longer recognize. Do not edit it to match; change it on the website first, then update Edge.
What this does not fix
- It does not sign you out of the website on other browsers, apps or devices.
- It does not tell you whether the old password was exposed.
- It does not confirm the new password is strong; that is a separate decision.
- It does not prove a matching username elsewhere belongs to the same person. If a password change followed a suspicious contact or an unfamiliar profile, a public username search can surface leads across social, developer and other communities, but a match is a lead, not proof of ownership.
TraceSeek, the app covered by this publication, checks a username across 3,000+ platforms and offers a free first scan that takes 20–30 seconds according to the product. It is a way to gather leads, not a way to verify identity or recover an account.
When to stop editing and escalate
Stop and go to the website’s own account recovery if: manual entry of the new password fails; the site says the password was changed when you did not change it; or you cannot complete device authentication to open the Edge password list. For the last case, resolve the device sign-in first — do not disable authentication to get around it.
If your next task is moving saved credentials between browsers, read the guide on moving Chrome password records without leaving an exposed export before creating any file of plaintext secrets. Never screenshot a password field or paste secrets into a note, chat or search box to “check” them. Demand for this particular workflow is an editorial assumption, not a measured figure.